< draft-turner-ecprivatekey-03.txt		draft-turner-ecprivatekey-04.txt >
	Network Working Group Sean Turner, IECA		Network Working Group Sean Turner, IECA
	Internet Draft Dan Brown, Certicom		Internet Draft Dan Brown, Certicom
	Intended Status: Informational February 2, 2010		Intended Status: Informational February 3, 2010
	Expires: August 2, 2010		Expires: August 3, 2010
	Elliptic Curve Private Key Structure		Elliptic Curve Private Key Structure
	draft-turner-ecprivatekey-03.txt		draft-turner-ecprivatekey-04.txt
	Abstract		Abstract
	This document specifies the syntax and semantics for conveying		This document specifies the syntax and semantics for conveying
	Elliptic Curve (EC) private key information. This syntax and		Elliptic Curve (EC) private key information. This syntax and
	semantics defined herein are based on a similar syntax and semantics		semantics defined herein are based on a similar syntax and semantics
	defined in Standards for Efficient Cryptography Group (SECG).		defined in Standards for Efficient Cryptography Group (SECG).
	Status of this Memo		Status of this Memo
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	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 August 2, 2010.		This Internet-Draft will expire on August 3, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2010 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
	skipping to change at page 2, line 32 ¶		skipping to change at page 2, line 32 ¶
	The structure defined in this document allows the entity that		The structure defined in this document allows the entity that
	generates the private and public keys to distribute the key pair and		generates the private and public keys to distribute the key pair and
	the associated domain parameters.		the associated domain parameters.
	A scenario in which this syntax is useful distributes EC private keys		A scenario in which this syntax is useful distributes EC private keys
	using PrivateKeyInfo, as defined in PKCS #8 [RFC5208]. Distributing		using PrivateKeyInfo, as defined in PKCS #8 [RFC5208]. Distributing
	an EC private key with PKCS#8 [RFC5208] involves including:		an EC private key with PKCS#8 [RFC5208] involves including:
	a) id-ecPublicKey, id-ecDH, or id-ecMQV (from [RFC5480]) with the		a) id-ecPublicKey, id-ecDH, or id-ecMQV (from [RFC5480]) with the
	namedCurve as the parameters in the privateKeyAlgorithm field		namedCurve as the parameters in the privateKeyAlgorithm field
	b) ECPrivateKey in the PrivateKey field, which is an OCTET STRING.		b) ECPrivateKey in the PrivateKey field, which is an OCTET STRING.
	There are two possible locations to carry a public key. When one is		When a public key is included, the publicKey field in ECPrivateKey is
	included, the publicKey field in the ECPrivateKey is used. The		used.
	publicKey field in PKCS#8 is not used.
	2. Terminology		2. Terminology
	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].
	3. Elliptic Curve Private Key Format		3. Elliptic Curve Private Key Format
	This section gives the syntax for an EC private key. Computationally		This section gives the syntax for an EC private key. Computationally
End of changes. 4 change blocks.
	7 lines changed or deleted		6 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/