Re: [IETF-PKIX] PKIX/ECDSA - Duplicate OIDs

["David P. Kemp" <dpkemp@xxxxxxxxxxxxxx>]

> From: Adrian De Leon <Adrian-and-Lisa-De-Leon@postoffice.worldnet.att.net>
>
> Gentlemen:
>
> It appears that some duplicate OBJECT IDENTIFER values have been
> assigned in the 21 Nov 97 IETF PKIX IPKI - ECDSA draft.  These
> are:
>
> For an ECDSA signature:
> iso(1) member-body(2) us(840) ansi-X9-62(10045) ecdsa-with-SHA1(1)
> -> { 1  2  840  10045  1 }
>
> (same value as in MISPC)
>
> The duplicate is:
> id-fieldType OBJECT IDENTIFER ::= { ansi-X9-62  fieldType(1) }
>
> Which I take to be equivalent to:
> iso(1) member-body(2) us(840) ansi-X9-62(10045) id-fieldType(1)
> -> { 1  2  840  10045  1 }
>
> Since MISPC agrees w/ the use of this OID to identify an ECDSA
> signature,
> may I presume that id-fieldType will be changed to something else?


X9.62 defines:

  id-fieldType             OID ::= { ansi-X9-62 fieldType(1) }
  prime-field              OID ::= { id-fieldType 1 }
  characteristic-two-field OID ::= { id-fieldType 2 }

and it defines the public key id to go into SubjectPublicKeyInfo:

  id-publicKeyType         OID ::= { ansi-X9-62 keyType(2) }
  id-ecPublicKey           OID ::= { id-publicKeyType 1 }

but it does not define any AlgorithmIDs for specifying ECDSA (with SHA1
or any other hash).

Presumably X9.62 is the definitive document, so it should be
up to the PKIX internet-draft and the MISPC to switch to an unused
algorithm id, if X9.62 isn't going to define one for ECDSA.