[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RFC 2985 on Selected Object Classes and Attribute Types

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

        RFC 2985

        Title:	    PKCS #9: Selected Object Classes and Attribute
        Author(s):  M. Nystrom, B. Kaliski
        Status:     Informational
	Date:       November 2000
        Mailbox:    magnus@rsasecurity.com, bkaliski@rsasecurity.com
        Pages:      39
        Characters: 70703
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-nystrom-pkcs9-v2-01.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2985.txt

This memo represents a republication of PKCS #9 v2.0 from RSA
Laboratories' Public-Key Cryptography Standards (PKCS) series, and
change control is retained within the PKCS process.  The body of
this document, except for the security considerations section, is
taken directly from that specification.
This memo provides a selection of object classes and attribute types
for use in conjunction with public-key cryptography and Lightweight
Directory Access Protocol (LDAP) accessible directories.  It also
includes ASN.1 syntax for all constructs.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

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@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@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@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@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

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


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
Content-type: text/plain