[11620] in cryptography@c2.net mail archive
[rfc-dist] RFC 3369 and 3370 on Cryptographic Message Syntax (CMS)
daemon@ATHENA.MIT.EDU (P.J. Ponder)
Thu Sep 5 16:51:44 2002
Date: Thu, 5 Sep 2002 13:59:10 -0400 (EDT)
From: "P.J. Ponder" <ponder@freenet.tlh.fl.us>
To: <cryptography@wasabisystems.com>
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
--NextPart
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.OSF.4.31.0209051354012.19390@fn3.freenet.tlh.fl.us>
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@rfc-editor.org
To: rfc-dist@rfc-editor.org
Cc: rfc-editor@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@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@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
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.
---------------------------------------------
Date: 05 Sep 2002 13:53:58 -0400
From: rfc-editor@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@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@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
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.
--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"
--OtherAccess
Content-Type: Message/External-body;
access-type="mail-server";
server="RFC-INFO@RFC-EDITOR.ORG"
Content-Type: text/plain
Content-ID: <020905095135.RFC@RFC-EDITOR.ORG>
RETRIEVE: rfc
DOC-ID: rfc3370
--OtherAccess
Content-Type: Message/External-body;
name="rfc3370.txt";
site="ftp.isi.edu";
access-type="anon-ftp";
directory="in-notes"
Content-Type: text/plain
Content-ID: <020905095135.RFC@RFC-EDITOR.ORG>
--OtherAccess--
--NextPart--
_______________________________________________
rfc-dist mailing list
rfc-dist@mailman.rfc-editor.org
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org
--NextPart
Content-Type: MULTIPART/ALTERNATIVE; BOUNDARY=OtherAccess
Content-ID: <Pine.OSF.4.31.0209051354013.19390@fn3.freenet.tlh.fl.us>
Content-Description:
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
--OtherAccess
Content-Type: MESSAGE/EXTERNAL-BODY; ACCESS-TYPE=mail-server; SERVER="RFC-INFO@RFC-EDITOR.ORG"
Content-ID: <Pine.OSF.4.31.0209051354014.19390@fn3.freenet.tlh.fl.us>
--OtherAccess
Content-Type: MESSAGE/EXTERNAL-BODY; NAME="rfc3369.txt"; SITE="ftp.isi.edu"; ACCESS-TYPE=anon-ftp; DIRECTORY=in-notes
Content-ID: <Pine.OSF.4.31.0209051354015.19390@fn3.freenet.tlh.fl.us>
--OtherAccess--
--NextPart--
---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@wasabisystems.com
