< draft-ietf-smime-rfc3278-update-02.txt		draft-ietf-smime-rfc3278-update-03.txt >
	S/MIME WG Sean Turner, IECA		S/MIME WG Sean Turner, IECA
	Internet Draft Daniel Brown, Certicom		Internet Draft Daniel Brown, Certicom
	Intended Status: Informational April 22, 2008		Intended Status: Informational May 2, 2008
	Updates: 3278 (once approved)		Updates: 3278 (once approved)
	Expires: October 22, 2008		Expires: November 2, 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-02.txt		draft-ietf-smime-rfc3278-update-03.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 October 22, 2008.		This Internet-Draft will expire on November 2, 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
	hash algorithms.		hash algorithms, Elliptic Curve Digital Signature Algorithm (ECDSA)
			224-512, and Key Derivation Functions (KDFs) that utilize SHA2
	Conventions used in this document		algorithms.
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [MUST].
	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
			1.1. Overview of Changes to RFC 3278...........................2
			1.2. Conventions Used in this Document.........................3
	2. Updates to Paragraph 2.1.1.....................................3		2. Updates to Paragraph 2.1.1.....................................3
	3. Updates to Paragraph 3.1.1.....................................4		3. Updates to Paragraph 3.1.1.....................................4
	4. Updates to Paragraph 3.2.1.....................................4		4. Updates to Paragraph 3.2.1.....................................4
	5. Updates to Paragraph 5.........................................5		5. Updates to Paragraph 5.........................................5
	6. Updates to Paragraph 7.........................................5		6. Updates to Paragraph 7.........................................6
	7. Updates to Paragraph 8.1.......................................9		7. Updates to Paragraph 8.1.......................................9
	8. Updates to Paragraph 9........................................12		8. Updates to Paragraph 9........................................13
	9. Changes to Security Considerations............................13		9. Changes to Security Considerations............................13
	10. Add Annex A: ASN.1 Module....................................14		10. Add Annex A: 2004 ASN.1 Module...............................14
	11. Security Considerations......................................24		11. Security Considerations......................................25
	12. IANA Considerations..........................................24		12. IANA Considerations..........................................25
	13. References...................................................25		13. References...................................................25
	13.1. Normative References....................................25		13.1. Normative References....................................25
	13.2. Informative References..................................25		13.2. Informative References..................................26
	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, Elliptic Curve Digital Signature Algorithm (ECDSA)
			224-512, and Key Derivation Functions (KDFs) that utilize SHA2
			algorithms.
			1.1. Overview of Changes to RFC 3278
	The following summarizes the changes:		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-
	384, and SHA-512.		384, and SHA-512.
	- Paragraph 3.1.1 used SHA1 in the KDF with ECDH std and cofactor		- Paragraph 3.1.1 used SHA1 in the KDF with ECDH std and cofactor
	methods. This document expands the options to the allowed		methods. This document expands the set of allowed algorithms by
	algorithms to SHA-224, SHA-256, SHA-384, and SHA-512.		adding SHA-224, SHA-256, SHA-384, and SHA-512.
	- Paragraph 3.1.2 used SHA1 in the KDF with ECMQV. This document		- Paragraph 3.1.2 used SHA1 in the KDF with ECMQV. This document
	expands the options to the allowed algorithms to SHA-224, SHA-		expands the set of allowed allowed algorithms by adding SHA-224,
	256, SHA-384, and SHA-512.		SHA-256, SHA-384, and SHA-512.
	- Paragraph 5 was update to include requirements for hash algorithms		- Paragraph 5 is updated to include requirements for hash algorithms
	and recommendations for matching curves and hash algorithms. It		and recommendations for matching curves and hash algorithms. It
	also was expanded to indicate which ECDH and ECMQV variants are		also was expanded to indicate which ECDH and ECMQV variants are
	required.		required.
	- Paragraph 7 was update to include S/MIME capabilities for ECDSA		- Paragraph 7 is updated to include S/MIME capabilities for ECDSA
	with SHA-224, SHA-256, SHA-384, and SHA-512. It was also updated		with SHA-224, SHA-256, SHA-384, and SHA-512. It was also updated
	to include S/MIME capabilities for ECDH and ECMQV using SHA2		to include S/MIME capabilities for ECDH and ECMQV using SHA2
	algorithms as the KDF.		algorithms as the KDF.
	- 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 algorithm identifiers for SHA-224,
	SHA-384, and SHA-512 and SHA-224, SHA-256, SHA-384, and SHA-512		SHA-256, SHA-384, and SHA-512 as well as SHA-224, SHA-256, SHA-
	with ECDSA. This document also updates the list of algorithm		384, and SHA-512 with ECDSA. This document also updates the list
	identifiers for ECDH std, ECDH cofactor, and ECMQV with SHA2		of algorithm identifiers for ECDH std, ECDH cofactor, and ECMQV
	algorithms as the KDF.		with SHA2 algorithms as the KDF.
	- Paragraph 9 references need to be updated.		- Paragraph 9 references need to be updated.
	- Added ASN.1 module.		- Added ASN.1 module.
	- Security considerations paragraph referring to definitions of SHA-		- Security considerations paragraph referring to definitions of SHA-
	224, SHA-256, SHA-384, and SHA-512 needs to be deleted.		224, SHA-256, SHA-384, and SHA-512 needs to be deleted.
			1.2. Conventions Used in this Document
			The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
			"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
			document are to be interpreted as described in [MUST].
	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
	algorithm.		algorithm.
	skipping to change at page 5, line 13 ¶		skipping to change at page 5, line 24 ¶
	in paragraph 5.		in paragraph 5.
	5. Updates to Paragraph 5		5. Updates to Paragraph 5
	Add the following to the end of the section:		Add the following to the end of the section:
	Implementations of this specification MUST implement the SHA-256		Implementations of this specification MUST implement the SHA-256
	hash algorithm. The SHA-1, SHA-224, SHA-384, SHA-512 hash		hash algorithm. The SHA-1, SHA-224, SHA-384, SHA-512 hash
	algorithms MAY be supported.		algorithms MAY be supported.
	When ECDSA, ECDH, or ECMQV is used, it is RECOMMENDED that the P-		When ECDSA, ECDH, or ECMQV is used, it is RECOMMENDED that the
	256 curve be used with SHA-256, the P-384 curve be used with SHA-		P-256 curve be used with SHA-256, the P-384 curve be used with
	384, and the P-521 curve be used with SHA-512.		SHA-384, and the P-521 curve be used with SHA-512.
	Implementations of this specification that support EnvelopedData		Implementations of this specification that support EnvelopedData
	with ephemeral-static ECDH standard primitive MUST support the		with ephemeral-static ECDH standard primitive MUST support the
	dhSinglePass-stdDH-sha256kdf-scheme algorithm. They MUST also		dhSinglePass-stdDH-sha256kdf-scheme algorithm. They MUST also
	support the id-aes128-wrap algorithm.		support the id-aes128-wrap algorithm. The dhSinglePass-stdDH-
			sha1kdf-scheme, dhSinglePass-stdDH-sha224kdf-scheme,
			dhSinglePass-stdDH-sha384kdf-scheme, and dhSinglePass-stdDH-
			sha512kdf-scheme algorithms MAY be supported. Likewise, the id-
			alg-CMS3DESwrap, id-aes198-wrap, and id-aes256wrap MAY be
			supported.
	Implementations of this specification that support EnvelopedData		Implementations of this specification that support EnvelopedData
	with ephemeral-static ECDH cofactor primitive MUST support the		with ephemeral-static ECDH cofactor primitive MUST support the
	dhSinglePass-cofactorDH-sha256kdf-scheme algorithm. They MUST		dhSinglePass-cofactorDH-sha256kdf-scheme algorithm. They MUST
	also support the id-aes128-wrap algorithm.		also support the id-aes128-wrap algorithm. The dhSinglePass-
			cofactorDH-sha1kdf-scheme, dhSinglePass-cofactorDH-sha224kdf-
			scheme, dhSinglePass-cofactorDH-sha384kdf-scheme, and
			dhSinglePass-cofactorDH-sha512kdf-scheme algorithms MAY be
			supported. Likewise, the id-alg-CMS3DESwrap, id-aes198-wrap, and
			id-aes256wrap MAY be supported.
	Implementations of this specification that support EnvelopedData		Implementations of this specification that support EnvelopedData
	with ECMQV MUST support the mqvSinglePass-sha256kdf-scheme		with ECMQV MUST support the mqvSinglePass-sha256kdf-scheme
	algorithm. They MUST also support the id-aes128-wrap algorithm.		algorithm. They MUST also support the id-aes128-wrap algorithm.
			The mqvSinglePass-sha1kdf-scheme, mqvSinglePass-sha224kdf-scheme,
			mqvSinglePass-sha384kdf-scheme, and mqvSinglePass-sha512kdf-
			scheme algorithms MAY be supported. Likewise, the id-alg-
			CMS3DESwrap, id-aes198-wrap, and id-aes256wrap MAY be supported.
	Implementations of this specification that support		Implementations of this specification that support
	AuthenticatedData with ECMQV MUSt support the		AuthenticatedData with ECMQV MUST support the
	mqvSinglePass-sha256kdf-scheme algorithm. They MUST also support		mqvSinglePass-sha256kdf-scheme algorithm. They MUST also support
	the id-aes128-wrap algorithm.		the id-aes128-wrap algorithm. The mqvSinglePass-sha1kdf-scheme,
			mqvSinglePass-sha224kdf-scheme, mqvSinglePass-sha384kdf-scheme,
			and mqvSinglePass-sha512kdf-scheme algorithms MAY be supported.
			Likewise, the id-alg-CMS3DESwrap, id-aes198-wrap, and id-
			aes256wrap MAY be supported.
	6. Updates to Paragraph 7		6. Updates to Paragraph 7
	Old:		Old:
	The SMIMECapability value to indicate support for the ECDSA		The SMIMECapability value to indicate support for the ECDSA
	signature algorithm is the SEQUENCE with the capabilityID field		signature algorithm is the SEQUENCE with the capabilityID field
	containing the object identifier ecdsa-with-SHA1 with NULL		containing the object identifier ecdsa-with-SHA1 with NULL
	parameters. The DER encoding is:		parameters. The DER encoding is:
	skipping to change at page 6, line 46 ¶		skipping to change at page 7, line 29 ¶
	for ephemeral-static ECDH with cofactor method, and		for ephemeral-static ECDH with cofactor method, and
	30 1c 06 09 2b 81 05 10 86 48 3f 00 10 30 0f 06		30 1c 06 09 2b 81 05 10 86 48 3f 00 10 30 0f 06
	0b 2a 86 48 86 f7 0d 01 09 10 03 06 05 00		0b 2a 86 48 86 f7 0d 01 09 10 03 06 05 00
	for ECMQV.		for ECMQV.
	New:		New:
	The SMIMECapability value to indicate support for the ECDH		The SMIMECapability value to indicate support for
	standard key agreement algorithm is the SEQUENCE with the		a) the standard ECDH key agreement algorithm,
	capabilityID field containing the object identifier		b) the cofactor ECDH key agreement algorithm, or
	dhSingPass-stdDH-sha*kdf-scheme (where * is 1, 224, 256, 384, or		c) the 1-Pass ECMWV key agreement algorithm
	512) with the parameters present. The parameters indicate the		is a SEQUENCE with the capabilityID field containing the object
	supported key-encryption algorithm with the KeyWrapAlgorithm		identifier
	algorithm identifier. The DER encodings that indicate some		a) dhSinglePass-stdDH-sha*kdf-scheme,
	capabilities are as follows (KA is key agreement, KDF is key		b) dhSinglePass-cofactorDH-sha*kdf-scheme, or
	derivation function, and Wrap is key wrap algorithm) and NOTE		c) mqvSinglePass-sha*kdf-scheme
	this is not a complete list:		respectively (where * is 1, 224, 256, 384, or 512) with the
			parameters present. The parameters indicate the supported key-
			encryption algorithm with the KeyWrapAlgorithm algorithm identifier.
			Example DER encodings that indicate some capabilities are as follows
			(KA is key agreement, KDF is key derivation function, and Wrap is key
			wrap algorithm):
	KA=ECDH standard KDF=SHA1 Wrap=3DES		KA=ECDH standard KDF=SHA1 Wrap=3DES
	30 1c		30 1c
	06 09 2b 81 05 10 86 48 3f 00 02		06 09 2b 81 05 10 86 48 3f 00 02
	30 0f		30 0f
	06 0b 2a 86 48 86 f7 0d 01 09 10 03 06		06 0b 2a 86 48 86 f7 0d 01 09 10 03 06
	05 00		05 00
	KA=ECDH standard KDF=SHA256 Wrap=AES128		KA=ECDH standard KDF=SHA256 Wrap=AES128
	30 1a		30 1a
	06 09 2b 81 05 10 86 48 3f 00 TBD		06 09 2b 81 04 01 0B 01
	30 0f		30 0f
	06 09 60 83 48 01 65 03 04 01 05		06 09 60 83 48 01 65 03 04 01 05
	05 00		05 00
	KA=ECDH standard KDF=SHA256 Wrap=AES256		KA=ECDH standard KDF=SHA384 Wrap=AES256
	30 1a		30 1a
	06 09 2b 81 05 10 86 48 3f 00 TBD		06 06 2b 81 04 01 0B 02
	30 0f		30 0f
	06 09 60 83 48 01 65 03 04 01 2D		06 09 60 83 48 01 65 03 04 01 2D
	05 00		05 00
	The SMIMECapability value to indicate support for the ECDH		KA=ECDH cofactor KDF=SHA1 Wrap=3DES
	cofactor key agreement algorithm is the SEQUENCE with the
	capabilityID field containing the object identifier
	dhSingPass-cofactorDH-sha*kdf-scheme (where * is 1, 224, 256,
	384, or 512) with the parameters present. The parameters indicate
	the supported key-encryption algorithm with the KeyWrapAlgorithm
	algorithm identifier. The DER encodings that indicate some
	capabilities are as follows (KA is key agreement, KDF is key
	derivation function, and Wrap is key wrap algorithm) and NOTE
	this is not a complete list:
	KA=ECDH cofactor KDF=SHA256 Wrap=3DES
	30 1c		30 1c
	06 09 2b 81 05 10 86 48 3f 00 03		06 09 2b 81 05 10 86 48 3f 00 03
	30 0f		30 0f
	06 0b 2a 86 48 86 f7 0d 01 09 10 03 06		06 0b 2a 86 48 86 f7 0d 01 09 10 03 06
	05 00		05 00
	KA=ECDH cofactor KDF=SHA256 Wrap=AES128		KA=ECDH cofactor KDF=SHA256 Wrap=AES128
	30 1a		30 1a
	06 09 2b 81 05 10 86 48 3f 00 TBD		06 06 2b 81 04 01 0E 01
	30 0f		30 0f
	06 09 60 83 48 01 65 03 04 01 05		06 09 60 83 48 01 65 03 04 01 05
	05 00		05 00
	KA=ECDH cofactor KDF=SHA256 Wrap=AES256		KA=ECDH cofactor KDF=SHA384 Wrap=AES256
	30 1a		30 1a
	06 09 2b 81 05 10 86 48 3f 00 TBD		06 06 2b 81 04 01 0E 02
	30 0f		30 0f
	06 09 60 83 48 01 65 03 04 01 2D		06 09 60 83 48 01 65 03 04 01 2D
	05 00		05 00
	The SMIMECapability value to indicate support for the 1-Pass		KA=ECMQV 1-Pass KDF=SHA1 Wrap=3DES
	ECMWV key agreement algorithm is the SEQUENCE with the
	capabilityID field containing the object identifier
	mqvSinglePass-sha*kdf-scheme (where * is 1, 224, 256, 384, or
	512) with the parameters present. The parameters indicate the
	supported key-encryption algorithm with the KeyWrapAlgorithm
	algorithm identifier. The DER encodings that indicate some
	capabilities are as follows (KA is key agreement, KDF is key
	derivation function, and Wrap is key wrap algorithm) and NOTE
	this is not a complete list:
	KA=ECMQV 1-Pass KDF=SHA256 Wrap=3DES
	30 1c		30 1c
	06 09 2b 81 05 10 86 48 3f 00 10		06 09 2b 81 05 10 86 48 3f 00 10
	30 0f		30 0f
	06 0b 2a 86 48 86 f7 0d 01 09 10 03 06		06 0b 2a 86 48 86 f7 0d 01 09 10 03 06
	05 00		05 00
	KA=ECMQV 1-Pass KDF=SHA256 Wrap=AES128		KA=ECMQV 1-Pass KDF=SHA256 Wrap=AES128
	30 1a		30 1a
	06 09 2b 81 05 10 86 48 3f 00 TBD		06 06 2b 81 04 01 0F 01
	30 0f		30 0f
	06 09 60 83 48 01 65 03 04 01 05		06 09 60 83 48 01 65 03 04 01 05
	05 00		05 00
	KA=ECMQV 1-Pass KDF=SHA256 Wrap=AES256		KA=ECMQV 1-Pass KDF=SHA384 Wrap=AES256
	30 1a		30 1a
	06 09 2b 81 05 10 86 48 3f 00 TBD		06 06 2b 81 04 01 0F 02
	30 0f		30 0f
	06 09 60 83 48 01 65 03 04 01 2D		06 09 60 83 48 01 65 03 04 01 2D
	05 00		05 00
	7. Updates to Paragraph 8.1		7. 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)
	oiw(14) secsig(3) algorithm(2) 26 }		oiw(14) secsig(3) algorithm(2) 26 }
	New:		New:
	The algorithm identifiers used in this document are taken from
	[SMIME-SHA2]
	The following object identifier indicates the hash algorithm used		The following object identifier indicates the hash algorithm used
	in this document:		in this document:
	id-sha1 OBJECT IDENTIFIER ::= { iso(1) identified-		id-sha1 OBJECT IDENTIFIER ::= { iso(1) identified-
	organization(3) oiw(14) secsig(3) algorithm(2) 26 }		organization(3) oiw(14) secsig(3) algorithm(2) 26 }
	id-sha224 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)		id-sha224 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)
	country(16) us(840) organization(1) gov(101) csor(3)		country(16) us(840) organization(1) gov(101) csor(3)
	nistalgorithm(4) hashalgs(2) 4 }		nistalgorithm(4) hashalgs(2) 4 }
	id-sha256 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)		id-sha256 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)
	country(16) us(840) organization(1) gov(101) csor(3)		country(16) us(840) organization(1) gov(101) csor(3)
	nistalgorithm(4) hashalgs(2) 1 }		nistalgorithm(4) hashalgs(2) 1 }
	id-sha384 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)		id-sha384 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)
	country(16) us(840) organization(1) gov(101) csor(3)		country(16) us(840) organization(1) gov(101) csor(3)
	nistalgorithm(4) hashalgs(2) 2 }		nistalgorithm(4) hashalgs(2) 2 }
	id-sha512 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)		id-sha512 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2)
	country(16) us(840) organization(1) gov(101) csor(3)		country(16) us(840) organization(1) gov(101) csor(3)
	nistalgorithm(4) hashalgs(2) 3 }		nistalgorithm(4) hashalgs(2) 3 }
	Old:		Old:
	skipping to change at page 10, line 45 ¶		skipping to change at page 11, line 6 ¶
	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 }
	When the object identifiers ecdsa-with-SHA1, ecdsa-with-SHA224,		When the object identifiers ecdsa-with-SHA1, ecdsa-with-SHA224,
	ecdsa-with-SHA256, ecdsa-with-SHA384, or ecdsa-with-SHA512 is		ecdsa-with-SHA256, ecdsa-with-SHA384, or ecdsa-with-SHA512 are
	used within an algorithm identifier, the associated parameters		used within an algorithm identifier, the associated parameters
	field contains NULL.		field contains NULL.
	Old:		Old:
	The following object identifiers indicate the key agreement		The following object identifiers indicate the key agreement
	algorithms used in this document:		algorithms used in this document:
	dhSinglePass-stdDH-sha1kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-stdDH-sha1kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme 2}		x9-63-scheme 2}
	skipping to change at page 11, line 38 ¶		skipping to change at page 11, line 43 ¶
	New:		New:
	The following object identifiers indicate the key agreement		The following object identifiers indicate the key agreement
	algorithms used in this document:		algorithms used in this document:
	dhSinglePass-stdDH-sha1kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-stdDH-sha1kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme 2 }		x9-63-scheme 2 }
	dhSinglePass-stdDH-sha224kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-stdDH-sha224kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 11 0 }
	dhSinglePass-stdDH-sha256kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-stdDH-sha256kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 11 1 }
	dhSinglePass-stdDH-sha384kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-stdDH-sha384kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 11 2 }
	dhSinglePass-stdDH-sha512kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-stdDH-sha512kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 11 3 }
	dhSinglePass-cofactorDH-sha1kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-cofactorDH-sha1kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme 3 }		x9-63-scheme 3 }
	dhSinglePass-cofactorDH-sha224kdf-scheme OBJECT IDENTIFIER ::=		dhSinglePass-cofactorDH-sha224kdf-scheme OBJECT IDENTIFIER ::=
	{ x9-63-scheme TBD }		{ secg-scheme 14 0 }
	dhSinglePass-cofactorDH-sha256kdf-scheme OBJECT IDENTIFIER ::=		dhSinglePass-cofactorDH-sha256kdf-scheme OBJECT IDENTIFIER ::=
	{ x9-63-scheme TBD }		{ secg-scheme 14 1 }
	dhSinglePass-cofactorDH-sha384kdf-scheme OBJECT IDENTIFIER ::=		dhSinglePass-cofactorDH-sha384kdf-scheme OBJECT IDENTIFIER ::=
	{ x9-63-scheme TBD }		{ secg-scheme 14 2 }
	dhSinglePass-cofactorDH-sha512kdf-scheme OBJECT IDENTIFIER ::=		dhSinglePass-cofactorDH-sha512kdf-scheme OBJECT IDENTIFIER ::=
	{ x9-63-scheme TBD }		{ secg-scheme 14 3 }
	mqvSinglePass-sha1kdf-scheme OBJECT IDENTIFIER ::= {		mqvSinglePass-sha1kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme 16 }		x9-63-scheme 16 }
	mqvSinglePass-sha224kdf-scheme OBJECT IDENTIFIER ::= {		mqvSinglePass-sha224kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 15 0 }
	mqvSinglePass-sha256kdf-scheme OBJECT IDENTIFIER ::= {		mqvSinglePass-sha256kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 15 1 }
	mqvSinglePass-sha384kdf-scheme OBJECT IDENTIFIER ::= {		mqvSinglePass-sha384kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 15 2 }
	mqvSinglePass-sha512kdf-scheme OBJECT IDENTIFIER ::= {		mqvSinglePass-sha512kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 14 0 }
	where		where
	x9-63-scheme OBJECT IDENTIFIER ::= {		x9-63-scheme OBJECT IDENTIFIER ::= {
	iso(1) identified-organization(3) tc68(133) country(16) x9(840)		iso(1) identified-organization(3) tc68(133) country(16)
	x9-63(63) schemes(0) }		x9(840) x9-63(63) schemes(0) }
			and
			secg-scheme OBJECT IDENTIFIER ::= {
			iso(1) identified-organization(3) certicom(132) schemes(1) }
	When the object identifiers are used here within an algorithm		When the object identifiers are used here within an algorithm
	identifier, the associated parameters field contains the CMS		identifier, the associated parameters field contains the CMS
	KeyWrapAlgorithm algorithm identifier.		KeyWrapAlgorithm algorithm identifier.
	8. Updates to Paragraph 9		8. 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
	skipping to change at page 14, line 5 ¶		skipping to change at page 14, line 5 ¶
	9. Changes to Security Considerations		9. 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.
	10. Add Annex A: ASN.1 Module		10. Add Annex A: 2004 ASN.1 Module
	Add the following section as Annex A ASN.1 Module.		Add the following section as Annex A ASN.1 Module.
			This appendix provides the ASN.1 definitions for the structures
			described in this specification using ASN.1 as defined in
			[X.680,X.681].
	SMIMEECCAlgs-2008		SMIMEECCAlgs-2008
	{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)		{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
	smime(16) modules(0) TBD }		smime(16) modules(0) TBD }
	DEFINITIONS EXPLICIT TAGS ::=		DEFINITIONS EXPLICIT TAGS ::=
	BEGIN		BEGIN
	-- EXPORTS ALL		-- EXPORTS ALL
	IMPORTS		IMPORTS
			-- From [PKI-ALG]
	ALGORITHM, algorithmIdentifier, MessageDigestAlgorithms,		ALGORITHM, algorithmIdentifier, MessageDigestAlgorithms,
	SignatureAlgorithms		SignatureAlgorithms
	ow-sha1, ow-sha224, ow-sha256, ow-sha384, ow-sha512,		ow-sha1, ow-sha224, ow-sha256, ow-sha384, ow-sha512,
	sa-ecdsaWithSHA1		sa-ecdsaWithSHA1
	FROM PKIXAlgs-2008		FROM PKIXAlgs-2008
	{ iso(1) identified-organization(3) dod(6) internet(1)		{ iso(1) identified-organization(3) dod(6) internet(1)
	security(5) mechanisms(5) pkix(7) id-mod(0) TBD }		security(5) mechanisms(5) pkix(7) id-mod(0) TBD }
			-- From [RFC3565]
	id-aes128-CBC, id-aes192-CBC, id-aes256-CBC, AES-IV		id-aes128-CBC, id-aes192-CBC, id-aes256-CBC, AES-IV
	id-aes128-wrap, id-aes192-wrap, id-aes1256-wrap		id-aes128-wrap, id-aes192-wrap, id-aes1256-wrap
	FROM CMSAesRsaesOaep		FROM CMSAesRsaesOaep
	{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)		{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
	smime(16) modules(0) id-mod-cms-aes(19) }		smime(16) modules(0) id-mod-cms-aes(19) }
			-- From [RFC5084]
	id-aes128-CCM, id-aes192-CCM, id-aes256-CCM, CCMParameters		id-aes128-CCM, id-aes192-CCM, id-aes256-CCM, CCMParameters
	id-aes128-GCM, id-aes192-GCM, id-aes256-GCM, GCMParameters		id-aes128-GCM, id-aes192-GCM, id-aes256-GCM, GCMParameters
	FROM CMS-AES-CCM-and-AES-GCM		FROM CMS-AES-CCM-and-AES-GCM
	{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)		{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
	smime(16) modules(0) id-mod-cms-aes(32) }		smime(16) modules(0) id-mod-cms-aes(32) }
			-- From [RFC3852]
	OriginatorPublicKey, UserKeyingMaterial		OriginatorPublicKey, UserKeyingMaterial
	FROM CryptographicMessageSyntax2004		FROM CryptographicMessageSyntax2004
	{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)		{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
	smime(16) modules(0) cms-2004(24) }		smime(16) modules(0) cms-2004(24) }
			-- From [RFC3370]
	hMAC-SHA1, id-alg-CMS3DESwrap, CBCParameter		hMAC-SHA1, id-alg-CMS3DESwrap, CBCParameter
	FROM CryptographicMessageSyntaxAlgorithms		FROM CryptographicMessageSyntaxAlgorithms
	{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)		{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
	smime(16) modules(0) cmsalg-2001(16) }		smime(16) modules(0) cmsalg-2001(16) }
	;		;
	-- Constrains the SignedData digestAlgorithms field		-- Constrains the SignedData digestAlgorithms field
	-- Constrains the SignedData SignerInfo digestAlgorithm field		-- Constrains the SignedData SignerInfo digestAlgorithm field
	-- Constrains the AuthenticatedData digestAlgorithm field		-- Constrains the AuthenticatedData digestAlgorithm field
	MessageDigestAlgorithms ALGORITHM :: {		MessageDigestAlgorithms ALGORITHM ::= {
	ow-sha1 |		ow-sha1 |
	ow-sha224 |		ow-sha224 |
	ow-sha256 |		ow-sha256 |
	ow-sha384 |		ow-sha384 |
	ow-sha512,		ow-sha512,
	... -- Extensible		... -- Extensible
	}		}
	-- Constrains the SignedData SignerInfo signatureAlgorithm field		-- Constrains the SignedData SignerInfo signatureAlgorithm field
	SignatureAlgorithms ALGORITHM :: {		SignatureAlgorithms ALGORITHM ::= {
	sa-ecdsaWithSHA1 |		sa-ecdsaWithSHA1 |
	sa-ecdsaWithSHA224 |		sa-ecdsaWithSHA224 |
	sa-ecdsaWithSHA256 |		sa-ecdsaWithSHA256 |
	sa-ecdsaWithSHA384 |		sa-ecdsaWithSHA384 |
	sa-ecdsaWithSHA512 ,		sa-ecdsaWithSHA512 ,
	... -- Extensible		... -- Extensible
	}		}
	sa-ecdsa-with-SHA224 ALGORITHM ::= {		sa-ecdsa-with-SHA224 ALGORITHM ::= {
	OID ecdsa-with-SHA224 PARMS NULL }		OID ecdsa-with-SHA224 PARMS NULL }
	skipping to change at page 16, line 50 ¶		skipping to change at page 17, line 37 ¶
	kaa-mqvSinglePass-sha256kdf |		kaa-mqvSinglePass-sha256kdf |
	kaa-mqvSinglePass-sha384kdf |		kaa-mqvSinglePass-sha384kdf |
	kaa-mqvSinglePass-sha512kdf,		kaa-mqvSinglePass-sha512kdf,
	... -- Extensible		... -- Extensible
	}		}
	x9-63-scheme OBJECT IDENTIFIER ::= {		x9-63-scheme OBJECT IDENTIFIER ::= {
	iso(1) identified-organization(3) tc68(133) country(16) x9(840)		iso(1) identified-organization(3) tc68(133) country(16) x9(840)
	x9-63(63) schemes(0) }		x9-63(63) schemes(0) }
			secg-scheme OBJECT IDENTIFIER ::= {
			iso(1) identified-organization(3) certicom(132) schemes(1) }
	kaa-dhSinglePass-stdDH-sha1kdf ALGORITHM ::= {		kaa-dhSinglePass-stdDH-sha1kdf ALGORITHM ::= {
	OID dhSinglePass-stdDH-sha1kdf-scheme PARMS KeyWrapAlgorithms }		OID dhSinglePass-stdDH-sha1kdf-scheme PARMS KeyWrapAlgorithms }
	dhSinglePass-stdDH-sha1kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-stdDH-sha1kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme 2 }		x9-63-scheme 2 }
	kaa-dhSinglePass-stdDH-sha224kdf ALGORITHM ::= {		kaa-dhSinglePass-stdDH-sha224kdf ALGORITHM ::= {
	OID dhSinglePass-stdDH-sha224kdf-scheme PARMS KeyWrapAlgorithms }		OID dhSinglePass-stdDH-sha224kdf-scheme PARMS KeyWrapAlgorithms }
	dhSinglePass-stdDH-sha224kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-stdDH-sha224kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 11 0 }
	kaa-dhSinglePass-stdDH-sha256kdf ALGORITHM ::= {		kaa-dhSinglePass-stdDH-sha256kdf ALGORITHM ::= {
	OID dhSinglePass-stdDH-sha256kdf-scheme PARMS KeyWrapAlgorithms }		OID dhSinglePass-stdDH-sha256kdf-scheme PARMS KeyWrapAlgorithms }
	dhSinglePass-stdDH-sha256kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-stdDH-sha256kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 11 1 }
	kaa-dhSinglePass-stdDH-sha384kdf ALGORITHM ::= {		kaa-dhSinglePass-stdDH-sha384kdf ALGORITHM ::= {
	OID dhSinglePass-stdDH-sha384kdf-scheme PARMS KeyWrapAlgorithms }		OID dhSinglePass-stdDH-sha384kdf-scheme PARMS KeyWrapAlgorithms }
	dhSinglePass-stdDH-sha384kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-stdDH-sha384kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 11 2 }
	kaa-dhSinglePass-stdDH-sha512kdf ALGORITHM ::= {		kaa-dhSinglePass-stdDH-sha512kdf ALGORITHM ::= {
	OID dhSinglePass-stdDH-sha512kdf-scheme PARMS KeyWrapAlgorithms }		OID dhSinglePass-stdDH-sha512kdf-scheme PARMS KeyWrapAlgorithms }
	dhSinglePass-stdDH-sha512kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-stdDH-sha512kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 11 3 }
	kaa-dhSinglePass-cofactorDH-sha1kdf ALGORITHM ::= {		kaa-dhSinglePass-cofactorDH-sha1kdf ALGORITHM ::= {
	OID dhSinglePass-cofactorDH-sha1kdf-scheme PARMS KeyWrapAlgorithms }		OID dhSinglePass-cofactorDH-sha1kdf-scheme PARMS KeyWrapAlgorithms }
	dhSinglePass-cofactorDH-sha1kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-cofactorDH-sha1kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme 3 }		x9-63-scheme 3 }
	kaa-dhSinglePass-cofactorDH-sha224kdf ALGORITHM ::= {		kaa-dhSinglePass-cofactorDH-sha224kdf ALGORITHM ::= {
	OID dhSinglePass-cofactorDH-sha224kdf-scheme		OID dhSinglePass-cofactorDH-sha224kdf-scheme
	PARMS KeyWrapAlgorithms }		PARMS KeyWrapAlgorithms }
	dhSinglePass-cofactorDH-sha224kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-cofactorDH-sha224kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 14 0 }
	kaa-dhSinglePass-cofactorDH-sha256kdf ALGORITHM ::= {		kaa-dhSinglePass-cofactorDH-sha256kdf ALGORITHM ::= {
	OID dhSinglePass-cofactorDH-sha256kdf-scheme		OID dhSinglePass-cofactorDH-sha256kdf-scheme
	PARMS KeyWrapAlgorithms }		PARMS KeyWrapAlgorithms }
	dhSinglePass-cofactorDH-sha256kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-cofactorDH-sha256kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 14 1 }
	kaa-dhSinglePass-cofactorDH-sha384kdf ALGORITHM ::= {		kaa-dhSinglePass-cofactorDH-sha384kdf ALGORITHM ::= {
	OID dhSinglePass-cofactorDH-sha384kdf-scheme		OID dhSinglePass-cofactorDH-sha384kdf-scheme
	PARMS KeyWrapAlgorithms }		PARMS KeyWrapAlgorithms }
	dhSinglePass-cofactorDH-sha384kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-cofactorDH-sha384kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 14 2 }
	kaa-dhSinglePass-cofactorDH-sha512kdf ALGORITHM ::= {		kaa-dhSinglePass-cofactorDH-sha512kdf ALGORITHM ::= {
	OID dhSinglePass-cofactorDH-sha512kdf-scheme		OID dhSinglePass-cofactorDH-sha512kdf-scheme
	PARMS KeyWrapAlgorithms }		PARMS KeyWrapAlgorithms }
	dhSinglePass-cofactorDH-sha512kdf-scheme OBJECT IDENTIFIER ::= {		dhSinglePass-cofactorDH-sha512kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 14 3 }
	kaa-mqvSinglePass-sha1kdf ALGORITHM ::= {		kaa-mqvSinglePass-sha1kdf ALGORITHM ::= {
	OID mqvSinglePass-sha1kdf-scheme PARMS KeyWrapAlgorithms }		OID mqvSinglePass-sha1kdf-scheme PARMS KeyWrapAlgorithms }
	mqvSinglePass-sha1kdf-scheme OBJECT IDENTIFIER ::= {		mqvSinglePass-sha1kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme 16 }		x9-63-scheme 16 }
	kaa-mqvSinglePass-sha224kdf ALGORITHM ::= {		kaa-mqvSinglePass-sha224kdf ALGORITHM ::= {
	OID mqvSinglePass-sha224kdf-scheme PARMS KeyWrapAlgorithms }		OID mqvSinglePass-sha224kdf-scheme PARMS KeyWrapAlgorithms }
	mqvSinglePass-sha224kdf-scheme OBJECT IDENTIFIER ::= {		mqvSinglePass-sha224kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 15 0 }
	kaa-mqvSinglePass-sha256kdf ALGORITHM ::= {		kaa-mqvSinglePass-sha256kdf ALGORITHM ::= {
	OID mqvSinglePass-sha256kdf-scheme PARMS KeyWrapAlgorithms }		OID mqvSinglePass-sha256kdf-scheme PARMS KeyWrapAlgorithms }
	mqvSinglePass-sha256kdf-scheme OBJECT IDENTIFIER ::= {		mqvSinglePass-sha256kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 15 1 }
	kaa-mqvSinglePass-sha384kdf ALGORITHM ::= {		kaa-mqvSinglePass-sha384kdf ALGORITHM ::= {
	OID mqvSinglePass-sha384kdf-scheme PARMS KeyWrapAlgorithms }		OID mqvSinglePass-sha384kdf-scheme PARMS KeyWrapAlgorithms }
	mqvSinglePass-sha384kdf-scheme OBJECT IDENTIFIER ::= {		mqvSinglePass-sha384kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 15 2 }
	kaa-mqvSinglePass-sha512kdf ALGORITHM ::= {		kaa-mqvSinglePass-sha512kdf ALGORITHM ::= {
	OID mqvSinglePass-sha512kdf-scheme PARMS KeyWrapAlgorithms }		OID mqvSinglePass-sha512kdf-scheme PARMS KeyWrapAlgorithms }
	mqvSinglePass-sha512kdf-scheme OBJECT IDENTIFIER ::= {		mqvSinglePass-sha512kdf-scheme OBJECT IDENTIFIER ::= {
	x9-63-scheme TBD }		secg-scheme 15 3 }
	KeyWrapAlgorithms ALGORITHM ::= {		KeyWrapAlgorithms ALGORITHM ::= {
	kwa-3des |		kwa-3des |
	kwa-aes128 |		kwa-aes128 |
	kwa-aes192 |		kwa-aes192 |
	kwa-aes256,		kwa-aes256,
	... -- Extensible		... -- Extensible
	}		}
	kwa-3des ALGORITHM :: = {		kwa-3des ALGORITHM :: = {
	skipping to change at page 25, line 24 ¶		skipping to change at page 25, line 42 ¶
	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.
			[RFC3370] Housley, R., "Cryptographic Message Syntax (CMS)
			Algorithms", RFC 3370, August 2002.
			[RFC3565] Schaad, J., "Use of the Advanced Encryption Standard
			(AES) Encryption Algorithm in Cryptographic Message
			Syntax (CMS)", RFC 3565, July 2003.
			[RFC3852] Housley, R., "Cryptographic Message Syntax (CMS)",
			RFC 3852, July 2004.
			[RFC5084] Housley, R., "Using AES-CCM and AES-GCM Authenticated
			Encryption in the Cryptographic Message Syntax (CMS)",
			RFC 5084, November 2007.
			[X.680] ITU-T Recommendation X.680: Information Technology -
			Abstract Syntax Notation One, 1997.
			[X.681] ITU-T Recommendation X.680: Information Technology -
			Abstract Syntax Notation One: Information Object
			Spcification, 1997.
	13.2. Informative References		13.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
End of changes. 77 change blocks.
	115 lines changed or deleted		167 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/