Marcus Brinkmann
2018-04-21 10:09:38 UTC
Hi,
currently, RFC4480bis specifies these curve identifiers:
1.3.6.1.4.1.11591.15.1 Ed25519
1.3.6.1.4.1.3029.1.5.1 Curve25519
These identifiers are a patchwork of private enterprise identifiers
(Werner Koch/GNU and Peter Gutmann/cryptlib resp.).
A more consistent effort is currently underway to specify curve
identifiers for these and two more variants in:
Algorithm Identifiers for Ed25519, Ed448, X25519 and X448 for use in the
Internet X.509 Public Key Infrastructure
https://datatracker.ietf.org/doc/draft-ietf-curdle-pkix
id-X25519 OBJECT IDENTIFIER ::= { 1 3 101 110 }
id-X448 OBJECT IDENTIFIER ::= { 1 3 101 111 }
id-Ed25519 OBJECT IDENTIFIER ::= { 1 3 101 112 }
id-Ed448 OBJECT IDENTIFIER ::= { 1 3 101 113 }
Maybe the working group can consider adopting these along with
clarifying the interpretation of the byte order in cv25519 (see mail
from Apr 9th).
Thanks,
Marcus
currently, RFC4480bis specifies these curve identifiers:
1.3.6.1.4.1.11591.15.1 Ed25519
1.3.6.1.4.1.3029.1.5.1 Curve25519
These identifiers are a patchwork of private enterprise identifiers
(Werner Koch/GNU and Peter Gutmann/cryptlib resp.).
A more consistent effort is currently underway to specify curve
identifiers for these and two more variants in:
Algorithm Identifiers for Ed25519, Ed448, X25519 and X448 for use in the
Internet X.509 Public Key Infrastructure
https://datatracker.ietf.org/doc/draft-ietf-curdle-pkix
id-X25519 OBJECT IDENTIFIER ::= { 1 3 101 110 }
id-X448 OBJECT IDENTIFIER ::= { 1 3 101 111 }
id-Ed25519 OBJECT IDENTIFIER ::= { 1 3 101 112 }
id-Ed448 OBJECT IDENTIFIER ::= { 1 3 101 113 }
Maybe the working group can consider adopting these along with
clarifying the interpretation of the byte order in cv25519 (see mail
from Apr 9th).
Thanks,
Marcus