Elliptic Curve Private Key Structure
RFC 5915
Yes
No Objection
Note: This ballot was opened for revision 04 and is now closed.
(Russ Housley; former steering group member) (was No Objection, Discuss) Yes
The end of Section 1 says: > > When the public key is included, it is present in the ECPrivateKey > publicKey field not in the PKCS#8 publicKey field. > It would be more clear to say: > > There are two possible locations to carry a public key. When one is > included, the publicKey field in the ECPrivateKey is used. The > publicKey field in PKCS#8 is not used. In section 4, the document says: > > Local storage of an unencrypted ECPrivateKey object is out of scope > of this document. However, one popular format uses the .pem file > extension. > PEM files support encrypted storage too. In section 5, the document says: > > Protection of the private-key information is vital to public-key > cryptography. Disclosure of the private-key material to another > entity can lead to masquerades. The encryption algorithm used in the > encryption process must be as 'strong' as the key it is protecting. > This is incomplete. The consequences of disclosure depends on the purpose of the private key. If a private key is used for signature, then the disclosure allows unauthorizes signing. If a private key is used for key management, then disclosure allows unauthorized parties to acess the managed keying material.
(Tim Polk; former steering group member) Yes
(Adrian Farrel; former steering group member) No Objection
(Cullen Jennings; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Ralph Droms; former steering group member) No Objection
(Robert Sparks; former steering group member) No Objection
(Ron Bonica; former steering group member) No Objection
(Ross Callon; former steering group member) No Objection