[rfc-dist] RFC 4683 on Internet X.509 Public Key Infrastructure Subject Identification Method (SIM)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Thu Oct 5 09:57:29 PDT 2006

A new Request for Comments is now available in online RFC libraries.

        RFC 4683

        Title:      Internet X.509 Public Key Infrastructure 
                    Subject Identification Method (SIM) 
        Author:     J. Park, J. Lee,
                    H.. Lee, S. Park,
                    T. Polk
        Status:     Standards Track
        Date:       October 2006
        Mailbox:    khopri at kisa.or.kr, 
                    jilee at kisa.or.kr, 
                    hslee at kisa.or.kr, sjpark at bcqre.com, 
                    tim.polk at nist.gov
        Pages:      20
        Characters: 41285
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pkix-sim-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4683.txt

This document defines the Subject Identification Method (SIM) for
including a privacy-sensitive identifier in the subjectAltName
extension of a certificate.

The SIM is an optional feature that may be used by relying parties to
determine whether the subject of a particular certificate is also the
person corresponding to a particular sensitive identifier.  [STANDARDS 

This document is a product of the Public-Key Infrastructure (X.509)
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


More information about the rfc-dist mailing list