< draft-ietf-smime-rfc3278-update-00.txt		draft-ietf-smime-rfc3278-update-01.txt >
	S/MIME WG Sean Turner, IECA		S/MIME WG Sean Turner, IECA
	Internet Draft February 12, 2008		Internet Draft March 31, 2008
	Intended Status: Information		Intended Status: Information
	Updates: 3278 (once approved)		Updates: 3278 (once approved)
	Expires: August 12, 2008		Expires: September 31, 2008
	Update to Use of Elliptic Curve Cryptography (ECC) Algorithms		Update to Use of Elliptic Curve Cryptography (ECC) Algorithms
	in Cryptographic Message Syntax (CMS)		in Cryptographic Message Syntax (CMS)
	draft-ietf-smime-rfc3278-update-00.txt		draft-ietf-smime-rfc3278-update-01.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 35 ¶		skipping to change at page 1, line 35 ¶
	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 July 12, 2008.		This Internet-Draft will expire on September 31, 2008.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2008).		Copyright (C) The IETF Trust (2008).
	Abstract		Abstract
	RFC 3278 describes how to use Elliptic Curve Cryptography (ECC)		RFC 3278 describes how to use Elliptic Curve Cryptography (ECC)
	public-key algorithms in the Cryptographic Message Syntax (CMS).		public-key algorithms in the Cryptographic Message Syntax (CMS).
	This document updates RFC 3278 to add support for the SHA2 family of		This document updates RFC 3278 to add support for the SHA2 family of
	skipping to change at page 2, line 20 ¶		skipping to change at page 2, line 20 ¶
	Discussion		Discussion
	This draft is being discussed on the 'ietf-smime' mailing list. To		This draft is being discussed on the 'ietf-smime' mailing list. To
	subscribe, send a message to ietf-smime-request@imc.org with the		subscribe, send a message to ietf-smime-request@imc.org with the
	single word subscribe in the body of the message. There is a Web site		single word subscribe in the body of the message. There is a Web site
	for the mailing list at <http://www.imc.org/ietf-smime/>.		for the mailing list at <http://www.imc.org/ietf-smime/>.
	Table of Contents		Table of Contents
	1. Introduction...................................................2		1. Introduction......................................... 2
	2. Updates to Paragraph 2.1.1.....................................3		2. Updates to Paragraph 2.1.1............................. 3
	3. Updates to Paragraph 8.1.......................................3		3. Updates to Paragraph 5 ................................ 3
	4. Updates to Paragraph 9.........................................5		4. Updates to Paragraph 7 ................................ 4
	5. Changes to Security Considerations.............................5		5. Updates to Paragraph 8.1............................... 4
	6. Security Considerations........................................5		6. Updates to Paragraph 9 ................................ 6
	7. IANA Considerations............................................5		7. Changes to Security Considerations....................... 6
	8. References.....................................................6		8. Security Considerations................................ 6
	8.1. Normative References......................................6		9. IANA Considerations................................... 7
	8.2. Informative References....................................6		10. References ......................................... 7
			10.1. Normative References............................. 7
			10.2. Informative References ........................... 7
	1. Introduction		1. Introduction
	RFC 3278 describes how to use Elliptic Curve Cryptography (ECC)		RFC 3278 describes how to use Elliptic Curve Cryptography (ECC)
	public-key algorithms in the Cryptographic Message Syntax (CMS).		public-key algorithms in the Cryptographic Message Syntax (CMS).
	This document updates RFC 3278 to add support for the SHA2 family of		This document updates RFC 3278 to add support for the SHA2 family of
	hash algorithms.		hash algorithms.
	There are changes to four paragraphs:		The following summarizes the changes:
	- Paragraph 2.1.1 limited the digest algorithm to SHA-1. This		- Paragraph 2.1.1 limited the digest algorithm to SHA-1. This
	document expands the allowed algorithms to SHA-224, SHA-256, SHA-		document expands the allowed algorithms to SHA-224, SHA-256, SHA-
	284, and SHA-512.		384, and SHA-512.
			- Paragraph 5 added requirements for hash algorithms and
			recommendations for matching curves and hash algorithms.
			- Paragraph 7 added S/MIME capabilities for ECDSA with SHA-224, SHA-
			256, SHA-384, and SHA-512.
	- Paragraph 8.1 listed the algorithm identifiers for SHA-1 and SHA-1		- Paragraph 8.1 listed the algorithm identifiers for SHA-1 and SHA-1
	with ECDSA. This document adds algorithms for SHA-224, SHA-256,		with ECDSA. This document adds algorithms for SHA-224, SHA-256,
	SHA-284, and SHA-512 and SHA-224, SHA-256, SHA-284, and SHA-512		SHA-384, and SHA-512 and SHA-224, SHA-256, SHA-384, and SHA-512
	with ECDSA.		with ECDSA.
	- Paragraph 9 references need to be updated.		- Paragraph 9 references need to be updated.
	- Security considerations paragraph referring to definitions of SHA-		- Security considerations paragraph referring to definitions of SHA-
	224, SHA-256, SHA-284, and SHA-512 needs to be deleted.		224, SHA-256, SHA-384, and SHA-512 needs to be deleted.
	2. Updates to Paragraph 2.1.1		2. Updates to Paragraph 2.1.1
	Old:		Old:
	digestAlgorithm MUST contain the algorithm identifier sha-1 (see		digestAlgorithm MUST contain the algorithm identifier sha-1 (see
	Section 8.1) which identifies the SHA-1 hash algorithm.		Section 8.1) which identifies the SHA-1 hash algorithm.
	signatureAlgorithm contains the algorithm identifier ecdsa-with-		signatureAlgorithm contains the algorithm identifier ecdsa-with-
	SHA1 (see Section 8.1) which identifies the ECDSA signature		SHA1 (see Section 8.1) which identifies the ECDSA signature
	skipping to change at page 3, line 32 ¶		skipping to change at page 3, line 39 ¶
	algorithm (see Section 8.1): id-sha1 identifies the SHA-1 hash		algorithm (see Section 8.1): id-sha1 identifies the SHA-1 hash
	algorithm, id-sha224 identifies the SHA-224 hash algorithm, id-		algorithm, id-sha224 identifies the SHA-224 hash algorithm, id-
	sha256 identifies the SHA-256 hash algorithm, id-sha384		sha256 identifies the SHA-256 hash algorithm, id-sha384
	identifies the SHA-384 algorithm, and id-sha512 identifies the		identifies the SHA-384 algorithm, and id-sha512 identifies the
	SHA-512 algorithm.		SHA-512 algorithm.
	signatureAlgorithm contains the signature algorithm identifier		signatureAlgorithm contains the signature algorithm identifier
	(see Section 8.1): ecdsa-with-SHA1, ecdsa-with-SHA224, ecdsa-		(see Section 8.1): ecdsa-with-SHA1, ecdsa-with-SHA224, ecdsa-
	with-SHA256, ecdsa-with-SHA384, ecdsa-with-SHA512.		with-SHA256, ecdsa-with-SHA384, ecdsa-with-SHA512.
	3. Updates to Paragraph 8.1		3. Updates to Paragraph 5
			Add the following to the end of the section:
			Implementations of this specification MUST implement the SHA-256
			hash algorithm. The SHA-1, SHA-224, SHA-384, SHA-512 hash
			algorithms MAY be supported.
			When ECDSA is used, it is RECOMMENDED that the P-256 curve be
			used with SHA-256, the P-384 curve be used with SHA-384, and the
			P-521 curve be used with SHA-512.
			4. Updates to Paragraph 7
			Old:
			The SMIMECapability value to indicate support for the ECDSA
			signature algorithm is the SEQUENCE with the capabilityID field
			containing the object identifier ecdsa-with-SHA1 with NULL
			parameters. The DER encoding is:
			30 0b 06 07 2a 86 48 ce 3d 04 01 05 00
			New:
			The SMIMECapability value to indicate support for the ECDSA
			signature algorithm is the SEQUENCE with the capabilityID field
			containing the object identifiers ecdsa-with-SHA1,
			ecdsa-with-withSHA224, ecdsa-with-SHA256, ecdsa-with-SHA384, and
			ecdsa-with-SHA512 all with NULL parameters. The DER encodings
			are:
			ecdsa-with-SHA1: 30 0b 06 07 2a 86 48 ce 3d 04 01 05 00
			ecdsa-with-SHA224: 30 0c 06 08 2a 86 48 ce 3d 04 03 01 05 00
			ecdsa-with-SHA256: 30 0c 06 08 2a 86 48 ce 3d 04 03 02 05 00
			ecdsa-with-SHA384: 30 0c 06 08 2a 86 48 ce 3d 04 03 03 05 00
			ecdsa-with-SHA512: 30 0c 06 08 2a 86 48 ce 3d 04 03 04 05 00
			5. Updates to Paragraph 8.1
	Old:		Old:
	The algorithm identifiers used in this document are taken from		The algorithm identifiers used in this document are taken from
	[X9.62], [SEC1] and [SEC2].		[X9.62], [SEC1] and [SEC2].
	The following object identifier indicates the hash algorithm used		The following object identifier indicates the hash algorithm used
	in this document:		in this document:
	sha-1 OBJECT IDENTIFIER ::= { iso(1) identified-organization(3)		sha-1 OBJECT IDENTIFIER ::= { iso(1) identified-organization(3)
	skipping to change at page 4, line 48 ¶		skipping to change at page 6, line 4 ¶
	signatures(4) 1 }		signatures(4) 1 }
	ecdsa-with-SHA224 OBJECT IDENTIFIER ::= { ansi-x9-62		ecdsa-with-SHA224 OBJECT IDENTIFIER ::= { ansi-x9-62
	signatures(4) ecdsa-with-SHA2(3) 1 }		signatures(4) ecdsa-with-SHA2(3) 1 }
	ecdsa-with-SHA256 OBJECT IDENTIFIER ::= { ansi-x9-62		ecdsa-with-SHA256 OBJECT IDENTIFIER ::= { ansi-x9-62
	signatures(4) ecdsa-with-SHA2(3) 2 }		signatures(4) ecdsa-with-SHA2(3) 2 }
	ecdsa-with-SHA384 OBJECT IDENTIFIER ::= { ansi-x9-62		ecdsa-with-SHA384 OBJECT IDENTIFIER ::= { ansi-x9-62
	signatures(4) ecdsa-with-SHA2(3) 3 }		signatures(4) ecdsa-with-SHA2(3) 3 }
	ecdsa-with-SHA512 OBJECT IDENTIFIER ::= { ansi-x9-62		ecdsa-with-SHA512 OBJECT IDENTIFIER ::= { ansi-x9-62
	signatures(4) ecdsa-with-SHA2(3) 4 }		signatures(4) ecdsa-with-SHA2(3) 4 }
	4. Updates to Paragraph 9		6. Updates to Paragraph 9
	Add the following reference:		Add the following reference:
	[SMIME-SHA2] Turner, S., "Using SHA2 Algorithms with		[SMIME-SHA2] Turner, S., "Using SHA2 Algorithms with
	Cryptographic Message Syntax", work-in-progress.		Cryptographic Message Syntax", work-in-progress.
	Update the following references:		Update the following references:
	Old:		Old:
	[PKI-ALG] Bassham, L., Housley R. and W. Polk, "Algorithms and		[PKI-ALG] Bassham, L., Housley R. and W. Polk, "Algorithms and
	Identifiers for the Internet X.509 Public Key Infrastructure		Identifiers for the Internet X.509 Public Key Infrastructure
	Certificate and CRL Profile", RFC 3279, April 2002.		Certificate and CRL Profile", RFC 3279, April 2002.
	[FIPS-180] FIPS 180-1, "Secure Hash Standard", National Institute		[FIPS-180] FIPS 180-1, "Secure Hash Standard", National Institute
	of Standards and Technology, April 17, 1995.		of Standards and Technology, April 17, 1995.
	New:		New:
	[PKI-ALG] Turner, S., Brown, D., Yiu, K., Housley, R., and W.		[PKI-ALG] Turner, S., Brown, D., Yiu, K., Housley, R., and W.
	Polk, " Elliptic Curve Cryptography Subject Public Key		Polk," Elliptic Curve Cryptography Subject Public Key
	Information", work-in-progress.		Information", work-in-progress.
	[FIPS] FIPS 180-2, "Secure Hash Standard", National Institute of		[FIPS] FIPS 180-2, "Secure Hash Standard", National Institute of
	Standards and Technology, August 1, 2002.		Standards and Technology, August 1, 2002.
	5. Changes to Security Considerations		7. Changes to Security Considerations
	Delete the following:		Delete the following:
	When 256, 384, and 512 bit hash functions succeed SHA-1 in future		When 256, 384, and 512 bit hash functions succeed SHA-1 in future
	revisions of [FIPS], [FIPS-186-2], [X9.62] and [SEC1], then they		revisions of [FIPS], [FIPS-186-2], [X9.62] and [SEC1], then they
	can similarly succeed SHA-1 in a future revision of this		can similarly succeed SHA-1 in a future revision of this
	document.		document.
	6. Security Considerations		8. Security Considerations
	No new security considerations to those already specified in		No new security considerations to those already specified in
	[RFC3278], [SMIME-SHA2], and [PKI-ALG].		[RFC3278], [SMIME-SHA2], and [PKI-ALG].
	7. IANA Considerations		9. 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.
	8. References		10. References
	8.1. Normative References		10.1. Normative References
	[MUST] Bradner, S., "Key words for use in RFCs to Indicate		[MUST] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", RFC 2119, BCP 14, March 1997.		Requirement Levels", RFC 2119, BCP 14, March 1997.
	[PKI-ALG] Turner, S., Brown, D., Yiu, K., Housley, R., and W.		[PKI-ALG] Turner, S., Brown, D., Yiu, K., Housley, R., and W.
	Polk, "Elliptic Curve Cryptography Subject Public Key		Polk, "Elliptic Curve Cryptography Subject Public Key
	Information", work-in-progress.		Information", work-in-progress.
	[SMIME-SHA2] Turner, S., "Using SHA2 Algorithms with Cryptographic		[SMIME-SHA2] Turner, S., "Using SHA2 Algorithms with Cryptographic
	Message Syntax", work-in-progress.		Message Syntax", work-in-progress.
	[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.
	8.2. Informative References		10.2. Informative References
	None.		None.
	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
End of changes. 19 change blocks.
	30 lines changed or deleted		79 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/