draft-ietf-smime-sha2-01.txt   draft-ietf-smime-sha2-02.txt 
S/MIME WG S. Turner S/MIME WG Sean Turner, IECA
Internet Draft IECA, Inc.
Intended Status: Standard Track July 25, 2007 Intended Status: Standard Track
Expires: January 25, 2008 Expires: July 28, 2008
Using SHA2 Algorithms with Cryptographic Message Syntax Using SHA2 Algorithms with Cryptographic Message Syntax
draft-ietf-smime-sha2-01.txt draft-ietf-smime-sha2-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
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 as "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/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
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
This Internet-Draft will expire on January 25, 2007. This Internet-Draft will expire on June 28, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document describes the conventions for using the message digest This document describes the conventions for using the message digest
algorithms SHA-224, as defined in [RFC3874], and SHA-256, SHA-384, algorithms SHA-224, as defined in [RFC3874], and SHA-256, SHA-384,
SHA-512, as defined in [SHA2], with the Cryptographic Message Syntax SHA-512, as defined in [SHA2], with the Cryptographic Message Syntax
(CMS) [RFC3852]. It also describes the conventions for using these (CMS) [RFC3852]. It also describes the conventions for using these
algorithms with CMS and the DSA, RSA, and ECDSA signature algorithms. algorithms with CMS and the DSA, RSA, and ECDSA signature algorithms.
Conventions used in this document Conventions used in this document
skipping to change at page 2, line 21 skipping to change at page 2, line 21
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
2. Message Digest Algorithms......................................3 2. Message Digest Algorithms......................................3
2.1. SHA-224...................................................4 2.1. SHA-224...................................................4
2.2. SHA-256...................................................4 2.2. SHA-256...................................................4
2.3. SHA-384...................................................4 2.3. SHA-384...................................................4
2.4. SHA-512...................................................4 2.4. SHA-512...................................................4
3. Signature Algorithms...........................................5 3. Signature Algorithms...........................................5
3.1. DSA.......................................................5 3.1. DSA.......................................................5
3.2. RSA.......................................................6 3.2. RSA.......................................................5
3.3. ECDSA.....................................................6 3.3. ECDSA.....................................................6
4. Security Considerations........................................7 4. Security Considerations........................................7
5. IANA Considerations............................................7 5. IANA Considerations............................................7
6. References.....................................................7 6. References.....................................................7
6.1. Normative References......................................7 6.1. Normative References......................................7
6.2. Informative References....................................8 6.2. Informative References....................................8
1. Introduction 1. Introduction
This document specifies the algorithm identifiers and specifies This document specifies the algorithm identifiers and specifies
skipping to change at page 5, line 22 skipping to change at page 5, line 22
signatureAlgorithm field of SignedData. Also, signature algorithm signatureAlgorithm field of SignedData. Also, signature algorithm
identifiers are located in the SignerInfo signatureAlgorithm field of identifiers are located in the SignerInfo signatureAlgorithm field of
countersignature attributes. countersignature attributes.
Signature values are located in the SignerInfo signature field of Signature values are located in the SignerInfo signature field of
SignedData. Also, signature values are located in the SignerInfo SignedData. Also, signature values are located in the SignerInfo
signature field of countersignature attributes. signature field of countersignature attributes.
3.1. DSA 3.1. DSA
</NOTE WELL NOTE: NIST has not finalized FIPS 186-3 and there is a chance that
the draft may be changed. This may result in differences between
NIST has not finalized FIPS 186-3 and there is a chance that the what is documented here and what is in the FIPS.
draft may be changed. This may result in differences between what is
documented here and what is in the FIPS.
/NOTE WELL>
[RFC3370] section 3.1 specifies the conventions for DSA with SHA1 [RFC3370] section 3.1 specifies the conventions for DSA with SHA1
public key algorithm identifiers, parameters, public keys, and public key algorithm identifiers, parameters, public keys, and
signature values. DSA with SHA2 algorithms use the same conventions signature values. DSA with SHA2 algorithms use the same conventions
for these public key algorithm identifiers, parameters, public keys, for these public key algorithm identifiers, parameters, public keys,
and signature values. DSA MAY be used with SHA-224 and SHA-256. and signature values. DSA MAY be used with SHA-224 and SHA-256.
The algorithm identifier for DSA with SHA-224 signature values is: The algorithm identifier for DSA with SHA-224 signature values is:
id-dsa-with-sha224 OBJECT IDENTIFIER ::= { joint-iso-ccitt(2) id-dsa-with-sha224 OBJECT IDENTIFIER ::= { joint-iso-ccitt(2)
skipping to change at page 9, line 8 skipping to change at page 9, line 8
6.2. Informative References 6.2. Informative References
[RFC4231] Nystrom, A. "Identifiers and Test Vectors for HMAC-SHA- [RFC4231] Nystrom, A. "Identifiers and Test Vectors for HMAC-SHA-
224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512", 224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512",
RFC4231. December 2005. RFC4231. December 2005.
Author's Addresses Author's Addresses
Sean Turner Sean Turner
IECA, Inc. IECA, Inc.
3057 Nutley Street, Suite 106
Fairfax, VA 22031
USA
Email: turners@ieca.com EMail: turners@ieca.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 10, line 29 skipping to change at page 10, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 12 change blocks. 
35 lines changed or deleted 33 lines changed or added

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