[rfc-dist] RFC 3369 and 3370 on Cryptographic Message Syntax (CMS) (fwd)

P.J. Ponder ponder at freenet.tlh.fl.us
Thu Sep 5 13:59:10 EDT 2002


For those not subscribed to RFC-Distribution or the IETF list, two new
RFC's (Proposed Standards) on 'Cryptographic Message Syntax'.  Both of the
announcements are pasted in this message.

---------- Forwarded message ----------
Date: Thu, 05 Sep 2002 09:51:07 -0700
From: rfc-editor at rfc-editor.org
To: rfc-dist at rfc-editor.org
Cc: rfc-editor at rfc-editor.org
Subject: [rfc-dist] RFC 3369 on Cryptographic Message Syntax (CMS)


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


        RFC 3369

        Title:	    Cryptographic Message Syntax (CMS)
        Author(s):  R. Housley
        Status:	    Standards Track
	Date:       August 2002
        Mailbox:    rhousley at rsasecurity.com
        Pages:      52
        Characters: 113975
        Obsoletes:  2630, 3211

        I-D Tag:    draft-ietf-smime-rfc2630bis-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3369.txt


This document describes the Cryptographic Message Syntax (CMS).  This
syntax is used to digitally sign, digest, authenticate, or encrypt
arbitrary message content.

This document is a product of the S/MIME Mail Security Working Group
of the IETF.

This is now a Proposed Standard Protcol.

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 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

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.echo
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

...

Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
---------------------------------------------

Date: 05 Sep 2002 13:53:58 -0400
From: rfc-editor at rfc-editor.org
Subject: [rfc-dist] RFC 3370 on Cryptographic Message Syntax (CMS) Algorithms


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


        RFC 3370

        Title:	    Cryptographic Message Syntax (CMS) Algorithms
        Author(s):  R. Housley
        Status:	    Standards Track
	Date:       August 2002
        Mailbox:    rhousley at rsasecurity.com
        Pages:      24
        Characters: 51001
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-smime-cmsalg-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3370.txt


This document describes the conventions for using several
cryptographic algorithms with the Cryptographic Message Syntax
(CMS).  The CMS is used to digitally sign, digest, authenticate, or
encrypt arbitrary message contents.

This document is a product of the S/MIME Mail Security Working Group
of the IETF.

This is now a Proposed Standard.

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 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

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.echo
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

...

Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
RETRIEVE: rfc
DOC-ID: rfc3370


More information about the cryptography mailing list