< draft-ietf-smime-sha2-10.txt		draft-ietf-smime-sha2-11.txt >
	S/MIME WG Sean Turner, IECA		S/MIME WG Sean Turner, IECA
	Internet Draft December 20, 2008		Internet Draft January 16, 2009
	Intended Status: Standard Track		Intended Status: Standard Track
	Updates: 3370 (once approved)		Updates: 3370 (once approved)
	Expires: June 20, 2009		Expires: July 16, 2009
	Using SHA2 Algorithms with Cryptographic Message Syntax		Using SHA2 Algorithms with Cryptographic Message Syntax
	draft-ietf-smime-sha2-10.txt		draft-ietf-smime-sha2-11.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and 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.
	skipping to change at page 1, line 32 ¶		skipping to change at page 1, line 32 ¶
	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 June 20, 2008.		This Internet-Draft will expire on July 16, 2009.
	Copyright Notice		Copyright Notice
	Copyright (c) 2008 IETF Trust and the persons identified as the		Copyright (c) 2009 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document.		to this document.
	Abstract		Abstract
	skipping to change at page 3, line 23 ¶		skipping to change at page 3, line 23 ¶
	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		This document also specifies the SMIMECapabilities attribute values
	[RFCTBD] for each algorithm. The values provided are for the		[RFCTBD1] for each algorithm. The values provided are for the
	SMIMECapability field, which is included here for convenience:		SMIMECapability field, which is included here for convenience:
	SMIMECapability ::= SEQUENCE {		SMIMECapability ::= SEQUENCE {
	capabilityID OBJECT IDENTIFIER,		capabilityID OBJECT IDENTIFIER,
	parameters ANY DEFINED BY capabilityID OPTIONAL }		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
	skipping to change at page 8, line 20 ¶		skipping to change at page 8, line 20 ¶
	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 SMIMECapabilities attribute value indicates support for one of
	the DSA signature algorithms in a SEQUENCE with the capabilityID		the DSA signature algorithms in a SEQUENCE with the capabilityID
	field containing the object identifier sha*WithRSAEncryption (where *		field containing the object identifier sha*WithRSAEncryption (where *
	is 224, 256, 384, or 512) with NULL parameters. The DER encoding for		is 224, 256, 384, or 512) with NULL parameters. The DER encoding for
	these SMIMECapability values are:		these SMIMECapability values are:
	sha224WithRSAEncryption: 30 0d 06 08 2a 86 48 86 f7 0d 01 01 14		sha224WithRSAEncryption: 30 0d 06 09 2a 86 48 86 f7 0d 01 01 0e
	05 00		05 00
	sha256WithRSAEncryption: 30 0d 06 08 2a 86 48 86 f7 0d 01 01 11		sha256WithRSAEncryption: 30 0d 06 09 2a 86 48 86 f7 0d 01 01 0b
	05 00		05 00
	sha384WithRSAEncryption: 30 0d 06 08 2a 86 48 86 f7 0d 01 01 12		sha384WithRSAEncryption: 30 0d 06 09 2a 86 48 86 f7 0d 01 01 Oc
	05 00		05 00
	sha512WithRSAEncryption: 30 0d 06 08 2a 86 48 86 f7 0d 01 01 13		sha512WithRSAEncryption: 30 0d 06 09 2a 86 48 86 f7 0d 01 01 0d
	05 00		05 00
	3.3. ECDSA		3.3. ECDSA
	[RFC3278] section 2.1 specifies the conventions for ECDSA with SHA-1		[RFCTBD2] 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
	[ECCADD].		[ECCADD].
	The algorithm identifier for ECDSA with SHA-224 signature values is:		The algorithm identifier for ECDSA with SHA-224 signature values is:
	ecdsa-with-SHA224 OBJECT IDENTIFIER ::= { iso(1) member-body(2)		ecdsa-with-SHA224 OBJECT IDENTIFIER ::= { iso(1) member-body(2)
	us(840) ansi-X9-62(10045) signatures(4) ecdsa-with-SHA2(3) 1 }		us(840) ansi-X9-62(10045) signatures(4) ecdsa-with-SHA2(3) 1 }
	The algorithm identifier for ECDSA with SHA-256 signature values is:		The algorithm identifier for ECDSA with SHA-256 signature values is:
	skipping to change at page 9, line 21 ¶		skipping to change at page 9, line 21 ¶
	ecdsa-with-SHA384 OBJECT IDENTIFIER ::= { iso(1) member-body(2)		ecdsa-with-SHA384 OBJECT IDENTIFIER ::= { iso(1) member-body(2)
	us(840) ansi-X9-62(10045) signatures(4) ecdsa-with-SHA2(3) 3 }		us(840) ansi-X9-62(10045) signatures(4) ecdsa-with-SHA2(3) 3 }
	The algorithm identifier for ECDSA with SHA-512 signature values is:		The algorithm identifier for ECDSA with SHA-512 signature values is:
	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 field 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 SMIMECapabilities attribute value indicates support for one of
	the ECDSA signature algorithms in a SEQUENCE with the capabilityID		the ECDSA signature algorithms in a SEQUENCE with the capabilityID
	field containing the object identifier ecdsa-with-SHA1* (where * is		field containing the object identifier ecdsa-with-SHA1* (where * is
	224, 256, 384, or 512) with absent parameters. The DER encoding for		224, 256, 384, or 512) with absent parameters. The DER encoding for
	these SMIMECapability values are:		these SMIMECapability values are:
	ecdsa-with-SHA224: 30 0a 06 08 2a 86 48 ce 3d 04 03 01		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-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-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		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],
	[ECCADD] apply. No new security considerations are introduced as a		[RFCTBD2], and [ECCADD] apply. No new security considerations are
	result of this specification.		introduced as a 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
	skipping to change at page 10, line 40 ¶		skipping to change at page 10, line 40 ¶
	[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		[RFCTBD1] Ramsdell, B., and S. Turner, "S/MIME Version 3.2 Message
	Specification", draft-ietf-smime-3851bis-08.txt, work-in-		Specification", draft-ietf-smime-3851bis-08.txt, work-in-
	progress.		progress.
	//* RFC EDITOR: Note replace the above TBD with the RFC # for draft-		//* RFC EDITOR: Note replace the above TBD1 with the RFC # for draft-
	ietf-smime-3851bis-08.txt. *//		ietf-smime-3851bis-08.txt. *//
			[RFCTBD2] Turner, S., and D. Brown, "Use of Elliptic Curve
			Cryptography (ECC) Algorithms in Cryptographic Message
			Syntax (CMS)", draft-ietf-smime-3278bis-05, work-in-
			progress.
			//* RFC EDITOR: Note replace the above TBD2 with the RFC # for draft-
			ietf-smime-3278bis-05.txt. *//
	[SHS] National Institute of Standards and Technology (NIST),		[SHS] National Institute of Standards and Technology (NIST),
	FIPS Publication 180-3: Secure Hash Standard, October		FIPS Publication 180-3: Secure Hash Standard, October
	2008.		2008.
	6.2. Informative References		6.2. Informative References
	[RFC3278] Blake-Wilson, S., Brown, D., and P. Lambert, "Use of
	Elliptic Curve Cryptography (ECC) Algorithms in
	Cryptographic Message Syntax (CMS)", RFC 3278, April
	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",
	RFC4231. December 2005.		RFC4231. December 2005.
	[RFC4634] Eastlake, D., and T. Hansen, "US Secure Hash Algorithms		[RFC4634] Eastlake, D., and T. Hansen, "US Secure Hash Algorithms
	(SHA and HMAC-SHA)", RFC 4634, July 2006.		(SHA and HMAC-SHA)", RFC 4634, July 2006.
	Author's Addresses		Author's Addresses
	Sean Turner		Sean Turner
End of changes. 18 change blocks.
	23 lines changed or deleted		26 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/