draft-ietf-smime-sha2-09.txt   draft-ietf-smime-sha2-10.txt 
S/MIME WG Sean Turner, IECA S/MIME WG Sean Turner, IECA
Intended Status: Standard Track Intended Status: Standard Track
Expires: April 6, 2009 Updates: 3370 (once approved)
Expires: June 20, 2009
Using SHA2 Algorithms with Cryptographic Message Syntax Using SHA2 Algorithms with Cryptographic Message Syntax
draft-ietf-smime-sha2-09.txt draft-ietf-smime-sha2-10.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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.
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 groups may also distribute working documents as Internet- other 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 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 April 6, 2008. This Internet-Draft will expire on June 20, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2008 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Abstract Abstract
This document describes the conventions for using the Secure Hash This document describes the conventions for using the Secure Hash
Algorithm (SHA) message digest algorithms (SHA-224, SHA-256, SHA-384, Algorithm (SHA) message digest algorithms (SHA-224, SHA-256, SHA-384,
SHA-512) with the Cryptographic Message Syntax (CMS). It also SHA-512) with the Cryptographic Message Syntax (CMS). It also
describes the conventions for using these algorithms with CMS and the describes the conventions for using these algorithms with CMS and the
Digital Signature Algorithm (DSA), Rivest Shamir Adleman (RSA), and Digital Signature Algorithm (DSA), Rivest Shamir Adleman (RSA), and
Elliptic Curve DSA (ECDSA) signature algorithms. Elliptic Curve DSA (ECDSA) signature algorithms. Further, it
provides SMIMECapabilities attribute values for each algorithm.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
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...................................................3 2.1. SHA-224...................................................4
2.2. SHA-256...................................................4 2.2. SHA-256...................................................5
2.3. SHA-384...................................................4 2.3. SHA-384...................................................5
2.4. SHA-512...................................................4 2.4. SHA-512...................................................5
3. Signature Algorithms...........................................4 3. Signature Algorithms...........................................6
3.1. DSA.......................................................5 3.1. DSA.......................................................6
3.2. RSA.......................................................5 3.2. RSA.......................................................7
3.3. ECDSA.....................................................6 3.3. ECDSA.....................................................8
4. Security Considerations........................................7 4. Security Considerations........................................9
5. IANA Considerations............................................7 5. IANA Considerations............................................9
6. References.....................................................7 6. References....................................................10
6.1. Normative References......................................7 6.1. Normative References.....................................10
6.2. Informative References....................................8 6.2. Informative References...................................11
1. Introduction 1. Introduction
This document specifies the algorithm identifiers and specifies This document specifies the algorithm identifiers and specifies
parameters for the message digest algorithms SHA-224, SHA-256, SHA- parameters for the message digest algorithms SHA-224, SHA-256, SHA-
384, and SHA-512 for use with the Cryptographic Message Syntax (CMS) 384, and SHA-512 for use with the Cryptographic Message Syntax (CMS)
[RFC3852]. The message digest algorithms are defined in [SHS] and [RFC3852]. The message digest algorithms are defined in [SHS] and
reference code is provided in [RFC4634]. reference code is provided in [RFC4634].
This document also specifies the algorithm identifiers and parameters This document also specifies the algorithm identifiers and parameters
for use of SHA-224, SHA-256, SHA-384, and SHA-512 with DSA [DSS], RSA for use of SHA-224, SHA-256, SHA-384, and SHA-512 with DSA [DSS], RSA
[RFC2313], and ECDSA [DSS]. (RSASSA-PKCS1-v1_5) [RFC3447], and ECDSA [DSS].
This document does not define new identifiers; they are taken from This document does not define new identifiers; they are taken from
[RFC3874], [RFC4055], and [ECCADD]. Additionally, the parameters [RFC3874], [RFC4055], and [ECCADD]. Additionally, the parameters
follow the conventions specified therein. Therefore, there is no follow the conventions specified therein. Therefore, there is no
Abstract Syntax Notation One (ASN.1) module included in this Abstract Syntax Notation One (ASN.1) module included in this
document. document.
Note that [RFC4231] specifies the conventions for the message Note that [RFC4231] specifies the conventions for the message
authentication code (MAC) algorithms: HMAC with SHA-224, HMAC with authentication code (MAC) algorithms: HMAC with SHA-224, HMAC with
SHA-256, HMAC with SHA-384, and HMAC with SHA-512. SHA-256, HMAC with SHA-384, and HMAC with SHA-512.
In CMS, the various algorithm identifiers use the AlgorithmIdentifier In CMS, the various algorithm identifiers use the AlgorithmIdentifier
syntax, which is included here for convenience: syntax, which is included here for convenience:
AlgorithmIdentifier ::= SEQUENCE { AlgorithmIdentifier ::= SEQUENCE {
algorithm OBJECT IDENTIFIER, algorithm OBJECT IDENTIFIER,
parameters ANY DEFINED BY algorithm OPTIONAL } parameters ANY DEFINED BY algorithm OPTIONAL }
This document also specifies the SMIMECapabilities attribute values
[RFCTBD] for each algorithm. The values provided are for the
SMIMECapability field, which is included here for convenience:
SMIMECapability ::= SEQUENCE {
capabilityID OBJECT IDENTIFIER,
parameters ANY DEFINED BY capabilityID OPTIONAL }
2. Message Digest Algorithms 2. Message Digest Algorithms
Digest algorithm identifiers are located in the SignedData Digest algorithm identifiers are located in the SignedData
digestAlgorithms field, the SignerInfo digestAlgorithm field, the digestAlgorithms field, the SignerInfo digestAlgorithm field, the
DigestedData digestAlgorithm field, and the AuthenticatedData DigestedData digestAlgorithm field, and the AuthenticatedData
digestAlgorithm field. The object identifiers are taken from digestAlgorithm field. The object identifiers are taken from
[RFC4055]. [RFC4055].
Digest values are located in the DigestedData digest field and the Digest values are located in the DigestedData digest field and the
Message Digest authenticated attribute. In addition, digest values Message Digest authenticated attribute. In addition, digest values
are input to signature algorithms. are input to signature algorithms.
The digest algorithm identifiers use the AlgorithmIdentifier syntax The digest algorithm identifiers use the AlgorithmIdentifier syntax
elaborated upon in Section 1. elaborated upon in Section 1.
The algorithm field is discussed in Sections 2.1-2.4 for each message The algorithm field and SMIMECapabilities attribute are discussed in
digest algorithm. Sections 2.1-2.4 for each message digest algorithm. Section 3
provides some signatures that use SHA2 algorithms. Consult the
signature algorithm definitions for the procedures to compute the
digest values (i.e., DigestInfo).
The AlgorithmIdentifier parameters field is OPTIONAL. Implementations The AlgorithmIdentifier parameters field is OPTIONAL.
MUST accept SHA2 AlgorithmIdentifiers with absent parameters. Implementations MUST accept SHA2 AlgorithmIdentifiers with absent
Implementations MUST accept SHA2 AlgorithmIdentifiers with NULL parameters. Implementations MUST accept SHA2 AlgorithmIdentifiers
parameters. Implementations MUST generate SHA2 AlgorithmIdentifiers with NULL parameters. Implementations MUST generate SHA2
with absent parameters. AlgorithmIdentifiers with absent parameters.
NOTE: There are two possible encodings for the AlgorithmIdentifier
parameters field associated with these object identifiers. The two
alternatives arise from the loss of the OPTIONAL associated with the
algorithm identifier parameters when the 1988 syntax for
AlgorithmIdentifier was translated into the 1997 syntax. Later the
OPTIONAL was recovered via a defect report, but by then many people
thought that algorithm parameters were mandatory. Because of this
history some implementations encode parameters as a NULL element
while others omit them entirely. The correct encoding is to omit the
parameters field; however, when some uses of these algorithms were
defined, it was done using the NULL parameters rather than absent
parameters. For example, PKCS#1 [RFC3447] requires that the padding
used for RSA signatures (EMSA-PKCS1-v1_5) MUST use SHA2
AlgorithmIdentifiers with NULL parameters (to clarify, the
requirement "MUST generate SHA2 AlgorithmIdentifiers with absent
parameters" in the previous paragraph does not apply to this
padding).
2.1. SHA-224 2.1. SHA-224
The SHA-224 message digest algorithm is defined in [SHS]. The The SHA-224 message digest algorithm is defined in [SHS]. The
algorithm identifier for SHA-224 is: algorithm identifier for SHA-224 is:
id-sha224 OBJECT IDENTIFIER ::= { id-sha224 OBJECT IDENTIFIER ::= {
joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101) joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101)
csor(3) nistalgorithm(4) hashalgs(2) 4 } csor(3) nistalgorithm(4) hashalgs(2) 4 }
The parameters are as specified in Section 2. The parameters are as specified in Section 2.
The SMIMECapabilities attribute value indicates support for SHA-224
in a SEQUENCE with the capabilityID field containing the object
identifier id-sha224 with absent parameters. The DER encoding for
this SMIMECapability is:
id-sha224: 30 0b 06 09 60 86 48 01 65 03 04 02 04
2.2. SHA-256 2.2. SHA-256
The SHA-256 message digest algorithm is defined in [SHS]. The The SHA-256 message digest algorithm is defined in [SHS]. The
algorithm identifier for SHA-256 is: algorithm identifier for SHA-256 is:
id-sha256 OBJECT IDENTIFIER ::= { id-sha256 OBJECT IDENTIFIER ::= {
joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101) joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101)
csor(3) nistalgorithm(4) hashalgs(2) 1 } csor(3) nistalgorithm(4) hashalgs(2) 1 }
The parameters are as specified in Section 2. The parameters are as specified in Section 2.
The SMIMECapabilities attribute value indicates support for SHA-256
in a SEQUENCE with the capabilityID field containing the object
identifier id-sha256 with absent parameters. The DER encoding for
this SMIMECapability value is:
id-sha256: 30 0b 06 09 60 86 48 01 65 03 04 02 01
2.3. SHA-384 2.3. SHA-384
The SHA-384 message digest algorithm is defined in [SHS]. The The SHA-384 message digest algorithm is defined in [SHS]. The
algorithm identifier for SHA-384 is: algorithm identifier for SHA-384 is:
id-sha384 OBJECT IDENTIFIER ::= { id-sha384 OBJECT IDENTIFIER ::= {
joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101) joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101)
csor(3) nistalgorithm(4) hashalgs(2) 2 } csor(3) nistalgorithm(4) hashalgs(2) 2 }
The parameters are as specified in Section 2. The parameters are as specified in Section 2.
The SMIMECapabilities attribute value indicates support for SHA-384
in a SEQUENCE with the capabilityID field containing the object
identifier id-sha384 with absent parameters. The DER encoding for
this SMIMECapability value is:
id-sha384: 30 0b 06 09 60 86 48 01 65 03 04 02 02
2.4. SHA-512 2.4. SHA-512
The SHA-512 message digest algorithm is defined in [SHS]. The The SHA-512 message digest algorithm is defined in [SHS]. The
algorithm identifier for SHA-512 is: algorithm identifier for SHA-512 is:
id-sha512 OBJECT IDENTIFIER ::= { id-sha512 OBJECT IDENTIFIER ::= {
joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101) joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101)
csor(3) nistalgorithm(4) hashalgs(2) 3 } csor(3) nistalgorithm(4) hashalgs(2) 3 }
The parameters are as specified in Section 2. The parameters are as specified in Section 2.
The SMIMECapabilities attribute value indicates support for SHA-384
in a SEQUENCE with the capabilityID field containing the object
identifier id-sha384 with absent parameters. The DER encoding for
this SMIMECapability value is:
id-sha512: 30 0b 06 09 60 86 48 01 65 03 04 02 03
3. Signature Algorithms 3. Signature Algorithms
This section specifies the conventions employed by CMS This section specifies the conventions employed by CMS
implementations that support DSA, RSA, and ECDSA with SHA2 implementations that support DSA, RSA, and ECDSA with SHA2
algorithms. algorithms.
Signature algorithm identifiers are located in the SignerInfo Signature algorithm identifiers are located in the SignerInfo
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.
skipping to change at page 5, line 22 skipping to change at page 6, line 44
object identifiers are taken from [ECCADD]. object identifiers are taken from [ECCADD].
DSA has not been specified with SHA-384 and SHA-512. SHA-384 and DSA has not been specified with SHA-384 and SHA-512. SHA-384 and
SHA-512 are not supported because the maximum bit length of p SHA-512 are not supported because the maximum bit length of p
(specified as L) is 3072 for DSA. For consistent cryptographic (specified as L) is 3072 for DSA. For consistent cryptographic
strength, SHA-384 would be used with DSA where L is 7680, and SHA-512 strength, SHA-384 would be used with DSA where L is 7680, and SHA-512
would be used with DSA where L is 15360. would be used with DSA where L is 15360.
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 ::= {
country(16) us(840) organization(1) gov(101) csor(3) joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)
algorithms(4) id-dsa-with-sha2(3) 1 } csor(3) algorithms(4) id-dsa-with-sha2(3) 1 }
The algorithm identifier for DSA with SHA-256 signature values is: The algorithm identifier for DSA with SHA-256 signature values is:
id-dsa-with-sha256 OBJECT IDENTIFIER ::= { joint-iso-ccitt(2) id-dsa-with-sha256 OBJECT IDENTIFIER ::= {
country(16) us(840) organization(1) gov(101) csor(3) joint-iso-ccitt(2) country(16) us(840) organization(1) gov(101)
algorithms(4) id-dsa-with-sha2(3) 2 } csor(3) algorithms(4) id-dsa-with-sha2(3) 2 }
When either of these algorithm identifiers is used, the When either of these algorithm identifiers is used, the
AlgorithmIdentifier parameters field MUST be absent. AlgorithmIdentifier parameters field MUST be absent.
The SMIMECapabilities attribute value indicates support for one of
the DSA signature algorithms in a SEQUENCE with the capabilityID
field containing the object identifier id-dsa-with-sha* (where * is
224 or 256) with absent parameters. The DER encoding for these
SMIMECapability values are:
id-dsa-with-sha224: 30 0b 06 09 60 86 48 01 65 03 04 03 01
id-dsa-with-sha256: 30 0b 06 09 60 86 48 01 65 03 04 03 02
3.2. RSA 3.2. RSA
[RFC3370] section 3.2 specifies the conventions for RSA with SHA-1 [RFC3370] section 3.2 specifies the conventions for RSA with SHA-1
(PKCS #1 v1.5) public key algorithm identifiers, parameters, public (RSASSA-PKCS1-v1_5) public key algorithm identifiers, parameters,
keys, and signature values. RSA with SHA2 algorithms uses the same public keys, and signature values. RSA with SHA2 algorithms uses the
conventions for these public key algorithm identifiers, parameters, same conventions for these public key algorithm identifiers,
public keys, and signature values. RSA (PKCS #1 v1.5) MAY be used parameters, public keys, and signature values. RSA (RSASSA-PKCS1-
with SHA-224, SHA-256, SHA-384, or SHA-512. The object identifiers v1_5) [RFC3447] MAY be used with SHA-224, SHA-256, SHA-384, or SHA-
are taken from [RFC4055]. 512. The object identifiers are taken from [RFC4055].
The object identifier for RSA with SHA-224 signature values is: The object identifier for RSA with SHA-224 signature values is:
sha224WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1) sha224WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 14 } member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 14 }
The object identifier for RSA with SHA-256 signature values is: The object identifier for RSA with SHA-256 signature values is:
sha256WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1) sha256WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 11 } member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 11 }
The object identifier for RSA with SHA-384 signature values is: The object identifier for RSA with SHA-384 signature values is:
sha384WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1) sha384WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 12 } member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 12 }
The object identifier for RSA with SHA-512 signature values is: The object identifier for RSA with SHA-512 signature values is:
sha512WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1) sha512WithRSAEncryption OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 13 } member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 13 }
When any of these four object identifiers appears within an When any of these four object identifiers appears within an
AlgorithmIdentifier, the parameters MUST be NULL. Implementations AlgorithmIdentifier, the parameters MUST be NULL. Implementations
MUST accept the parameters being absent as well as present. MUST accept the parameters being absent as well as present.
The SMIMECapabilities attribute value indicates support for one of
the DSA signature algorithms in a SEQUENCE with the capabilityID
field containing the object identifier sha*WithRSAEncryption (where *
is 224, 256, 384, or 512) with NULL parameters. The DER encoding for
these SMIMECapability values are:
sha224WithRSAEncryption: 30 0d 06 08 2a 86 48 86 f7 0d 01 01 14
05 00
sha256WithRSAEncryption: 30 0d 06 08 2a 86 48 86 f7 0d 01 01 11
05 00
sha384WithRSAEncryption: 30 0d 06 08 2a 86 48 86 f7 0d 01 01 12
05 00
sha512WithRSAEncryption: 30 0d 06 08 2a 86 48 86 f7 0d 01 01 13
05 00
3.3. ECDSA 3.3. ECDSA
[RFC3278] section 2.1 specifies the conventions for ECDSA with SHA-1 [RFC3278] section 2.1 specifies the conventions for ECDSA with SHA-1
public key algorithm identifiers, parameters, public keys, and public key algorithm identifiers, parameters, public keys, and
signature values. ECDSA with SHA2 algorithms uses the same signature values. ECDSA with SHA2 algorithms uses the same
conventions for these public key algorithm identifiers, parameters, conventions for these public key algorithm identifiers, parameters,
public keys, and signature values, except that the digestAlgorithm public keys, and signature values, except that the digestAlgorithm
MUST include the corresponding message digest algorithm identifier, MUST include the corresponding message digest algorithm identifier,
and not the sha-1 object identifier. ECDSA MAY be used with SHA-224, and not the sha-1 object identifier. ECDSA MAY be used with SHA-224,
SHA-256, SHA-384, or SHA-512. The object identifiers are taken from SHA-256, SHA-384, or SHA-512. The object identifiers are taken from
skipping to change at page 7, line 15 skipping to change at page 9, line 25
ecdsa-with-SHA512 OBJECT IDENTIFIER ::= { iso(1) member-body(2) ecdsa-with-SHA512 OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) ansi-X9-62(10045) signatures(4) ecdsa-with-SHA2(3) 4 } us(840) ansi-X9-62(10045) signatures(4) ecdsa-with-SHA2(3) 4 }
When any of these four object identifiers appears within an When any of these four object identifiers appears within an
AlgorithmIdentifier, the parameters filed MUST be absent. That is, AlgorithmIdentifier, the parameters filed MUST be absent. That is,
the AlgorithmIdentifier SHALL be a SEQUENCE of one component: the OID the AlgorithmIdentifier SHALL be a SEQUENCE of one component: the OID
ecdsa-with-SHA224, ecdsa-with-SHA256, ecdsa-with-SHA224, ecdsa-with-SHA256,
ecdsa-with-SHA384 or ecdsa-with-SHA512. ecdsa-with-SHA384 or ecdsa-with-SHA512.
The SMIMECapabilities attribute value indicates support for one of
the ECDSA signature algorithms in a SEQUENCE with the capabilityID
field containing the object identifier ecdsa-with-SHA1* (where * is
224, 256, 384, or 512) with absent parameters. The DER encoding for
these SMIMECapability values are:
ecdsa-with-SHA224: 30 0a 06 08 2a 86 48 ce 3d 04 03 01
ecdsa-with-SHA256: 30 0a 06 08 2a 86 48 ce 3d 04 03 02
ecdsa-with-SHA384: 30 0a 06 08 2a 86 48 ce 3d 04 03 03
ecdsa-with-SHA512: 30 0a 06 08 2a 86 48 ce 3d 04 03 04
4. Security Considerations 4. Security Considerations
The security considerations in [RFC3370], [RFC3874], [RFC4055], and The security considerations in [RFC3370], [RFC3874], [RFC4055], and
[ECCADD] apply. No new security considerations are introduced as a [ECCADD] apply. No new security considerations are introduced as a
result of this specification. result of this specification.
5. IANA Considerations 5. IANA Considerations
None: All identifiers are already registered. Please remove this None: All identifiers are already registered. Please remove this
section prior to publication as an RFC. section prior to publication as an RFC.
6. References 6. References
6.1. Normative References 6.1. Normative References
[ECCADD] Dang, S., Santesson, S., Moriarty, K., and Brown, [ECCADD] Dang, S., Santesson, S., Moriarty, K., and Brown,
"Internet X.509 Public Key Infrastructure: Additional "Internet X.509 Public Key Infrastructure: Additional
Algorithms and Identifiers for DSA and ECDSA", draft- Algorithms and Identifiers for DSA and ECDSA", draft-
ietf-pkix-sha2-dsa-ecdsa-04.txt (work-in-progress). ietf-pkix-sha2-dsa-ecdsa-05.txt (work-in-progress).
[DSS] National Institute of Standards and Technology (NIST), [DSS] National Institute of Standards and Technology (NIST),
FIPS Publication 186-3: Digital Signature Standard, FIPS Publication 186-3: Digital Signature Standard,
(draft) March 2006. (draft) November 2008.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119. March 1997. Requirement Levels", BCP 14, RFC 2119. March 1997.
[RFC2313] Kaliski, B., "PKCS #1: RSA Encryption Version 1.5", RFC
2313, March 1998.
[RFC3370] Housley, R., "Cryptographic Message Syntax (CMS) [RFC3370] Housley, R., "Cryptographic Message Syntax (CMS)
Algorithms", RFC 3370, August 2002. Algorithms", RFC 3370, August 2002.
[RFC3447] Kaliski, B. and J. Jonsson "Public-Key Cryptography
Standards (PKCS) #1: RSA Cryptography Specifications
Version 2.1", RFC 3447, February 2003.
[RFC3852] Housley, R., "The Cryptographic Message Syntax (CMS)", [RFC3852] Housley, R., "The Cryptographic Message Syntax (CMS)",
RFC 3852. July 2004. RFC 3852. July 2004.
[RFC3874] Housley, R., "A 224-bit One Way Hash Function: SHA-224", [RFC3874] Housley, R., "A 224-bit One Way Hash Function: SHA-224",
RFC 3874. September 2004. RFC 3874. September 2004.
[RFC4055] Schaad, J., Kaliski, B., and R. Housley, "Additional [RFC4055] Schaad, J., Kaliski, B., and R. Housley, "Additional
Algorithms and Identifiers for RSA Cryptography for use Algorithms and Identifiers for RSA Cryptography for use
in the Internet Public Key Infrastructure Certificate and in the Internet Public Key Infrastructure Certificate and
Certificate Revocation List (CRL) Profile", RFC 4055. Certificate Revocation List (CRL) Profile", RFC 4055.
June 2005. June 2005.
[RFCTBD] Ramsdell, B., and S. Turner, "S/MIME Version 3.2 Message
Specification", draft-ietf-smime-3851bis-08.txt, work-in-
progress.
//* RFC EDITOR: Note replace the above TBD with the RFC # for draft-
ietf-smime-3851bis-08.txt. *//
[SHS] National Institute of Standards and Technology (NIST), [SHS] National Institute of Standards and Technology (NIST),
FIPS Publication 180-3: Secure Hash Standard, (draft) FIPS Publication 180-3: Secure Hash Standard, October
June 2003. 2008.
6.2. Informative References 6.2. Informative References
[RFC3278] Blake-Wilson, S., Brown, D., and P. Lambert, "Use of [RFC3278] Blake-Wilson, S., Brown, D., and P. Lambert, "Use of
Elliptic Curve Cryptography (ECC) Algorithms in Elliptic Curve Cryptography (ECC) Algorithms in
Cryptographic Message Syntax (CMS)", RFC 3278, April Cryptographic Message Syntax (CMS)", RFC 3278, April
2002. 2002.
[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",
skipping to change at page 9, line 4 skipping to change at line 470
Author's Addresses Author's Addresses
Sean Turner Sean Turner
IECA, Inc. IECA, Inc.
3057 Nutley Street, Suite 106 3057 Nutley Street, Suite 106
Fairfax, VA 22031 Fairfax, VA 22031
USA USA
EMail: turners@ieca.com EMail: turners@ieca.com
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
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 30 change blocks. 
51 lines changed or deleted 165 lines changed or added

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