draft-ietf-smime-cms-auth-enveloped-01.txt   draft-ietf-smime-cms-auth-enveloped-02.txt 
S/MIME Working Group R. Housley S/MIME Working Group R. Housley
Internet-Draft Vigil Security Internet-Draft Vigil Security
Updates: 3852 (if approved) January 2007 Updates: 3852 (if approved) February 2007
Cryptographic Message Syntax (CMS) Cryptographic Message Syntax (CMS)
Authenticated-Enveloped-Data Content Type Authenticated-Enveloped-Data Content Type
<draft-ietf-smime-cms-auth-enveloped-01.txt> <draft-ietf-smime-cms-auth-enveloped-02.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that other
other groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-Drafts.
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than a "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Abstract Abstract
This document describes an additional content type for the This document describes an additional content type for the
skipping to change at page 5, line 20 skipping to change at page 5, line 20
management algorithm. It may contain certificates and CRLs, management algorithm. It may contain certificates and CRLs,
and the OriginatorInfo type is defined in Section 6.1 of [CMS]. and the OriginatorInfo type is defined in Section 6.1 of [CMS].
recipientInfos is a collection of per-recipient information. recipientInfos is a collection of per-recipient information.
There MUST be at least one element in the collection. The There MUST be at least one element in the collection. The
RecipientInfo type is defined in Section 6.2 of [CMS]. RecipientInfo type is defined in Section 6.2 of [CMS].
authAttrs optionally contains the authenticated attributes. The authAttrs optionally contains the authenticated attributes. The
CMS authenticated-data content type uses the same type to carry CMS authenticated-data content type uses the same type to carry
authenticated attributes. The AuthAttributes type is defined authenticated attributes. The AuthAttributes type is defined
in Section 9.1 of [CMS]. Useful attribute types are defined in in Section 9.1 of [CMS]; however, in this case, there is no
Section 11 of [CMS]. requirement to include the message-digest attribute. Useful
attribute types are defined in Section 11 of [CMS].
authEncryptedContentInfo is the authenticated and encrypted authEncryptedContentInfo is the authenticated and encrypted
content. The CMS enveloped-data content type uses the same content. The CMS enveloped-data content type uses the same
type to carry the encrypted content. The EncryptedContentInfo type to carry the encrypted content. The EncryptedContentInfo
type is defined in Section 6.1 of [CMS]. type is defined in Section 6.1 of [CMS].
mac is the integrity check value (ICV) or message authentication mac is the integrity check value (ICV) or message authentication
code (MAC) that is generated by the authenticated encryption code (MAC) that is generated by the authenticated encryption
algorithm. The CMS authenticated-data content type uses the algorithm. The CMS authenticated-data content type uses the
same type to carry a MAC. In this case, the MAC covers the same type to carry a MAC. In this case, the MAC covers the
skipping to change at page 9, line 31 skipping to change at page 9, line 31
Russell Housley Russell Housley
Vigil Security, LLC Vigil Security, LLC
918 Spring Knoll Drive 918 Spring Knoll Drive
Herndon, VA 20170 Herndon, VA 20170
USA USA
EMail: housley@vigilsec.com EMail: housley@vigilsec.com
Copyright and IPR Statements Copyright and IPR Statements
Copyright (C) The Internet Society (2007). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published and or assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are
skipping to change at page 10, line 8 skipping to change at page 10, line 8
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein This document and the information contained herein
are provided on an "AS IS" basis and THE CONTRIBUTOR, THE are provided on an "AS IS" basis and THE CONTRIBUTOR, THE
ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE
INTERNET SOCIETY, (THE IETF TRUST) AND THE INTERNET ENGINEERING INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 7 change blocks. 
9 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/