OID repository
OID Repository
http://oid-info.com
Display OID:
 
Action itemiso(1) Action itemmember-body(2) Action itemus(840) Action itemansi-x942(10046)  

Navigating the OID tree

kdMethods(5)
[other identifier: module]

child OIDs: Child OID separator asn1der(0) Child OID separator 1 Child OID separator
 
Separation line
 
OID description

   
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

Key derivation methods


Information:

See ANSI X9 standard "X9.42-2000, Public Key Cryptography for The Financial Services Industry: Agreement of Symmetric Keys Using Discrete Logarithm Cryptography".

From: "Phillip H. Griffin" <phil.griffin@ANTISPAM.asn-1.com>
Date: Tue, 27 May 2003
Cc: Don Johnson <DJohnson@ANTISPAM.cygnacom.com>, Jeff Stapleton <jstapleton@ANTISPAM.kpmg.com>, Pud Reaver <w3yd@ANTISPAM.arrl.net>

Olivier Dubuisson wrote:
>
> the following OID was described as:
>> OID : {iso(1) member-body(2) us(840) ansi-x962(10045) signatures(4) ecdsa-with-SHA1(1)}
>> Description: ANSI X9.62 Elliptic Curve Digital Signature Algorithm (ECDSA) signatures with SHA-1
> in the OID database.
>
> In one of the files available on your website, we've found the following information:
>> OID : {iso(1) member-body(2) us(840) 10045 module(4) 1}
>> Description: Modules
>> Registrant : "X9F"
> Which one is right? "module" or "signatures"?

Both ;)

I made an error in writing the X9.62 ASN.1 and assigned this OID twice, once to the module OID and again to the signatures. Best to let signatures win, as these actually have an effect on products and code, and change the module assignment from:
ANSI-X9-62 {iso(1) member-body(2) us(840) 10045 module(4) 1}
and
ANSI-X9-62 {iso(1) member-body(2) us(840) 10045 module(4) 2}
to
ANSI-X9-62 {iso(1) member-body(2) us(840) 10045 module(5) 1}
and
ANSI-X9-62 {iso(1) member-body(2) us(840) 10045 module(5) 2}

I'll contact by Cc some "X9F" chairs and get them to ask Miles Smid to get this changed to 5 in the next X9.62 revision.
-----
From: "Phillip H. Griffin" <phil.griffin@ANTISPAM.asn-1.com>
Date: Tue, 27 May 2003
Cc: Pud Reaver, Don Johnson, Jeff Stapleton

Olivier Dubuisson wrote:
> It looks like you did the same mistake with X9.42!
>
>> OID : {iso(1) member-body(2) us(840) ansi-x942(10046) module(5)}
>> Description : ASN.1 module called "X9-42"
>> Information : ANSI X9 standard "X9.42-2000, Public Key Cryptography for The Financial Services Industry: Agreement of Symmetric Keys Using Discrete Logarithm Cryptography
>> ------------------------------------------------------------​-----
>> OID : {iso(1) member-body(2) us(840) ansi-x942(10046) kdMethods(5)}
>> Description : Key derivation method
>> Registrant : "X9F"

Yes, please change
ANSI-X9-42 {iso(1) member-body(2) us(840) ansi-x942(10046) module(5) 1}
-- X9.42 Diffie-Hellman and Menezes-Qu-Vanstone (MQV) Symmetric Key Agreement

to
ANSI-X9-42 {iso(1) member-body(2) us(840) ansi-x942(10046) module(6) 1}
-- X9.42 Diffie-Hellman and Menezes-Qu-Vanstone (MQV) Symmetric Key Agreement

I'll contact by Cc some "X9F" chairs and get them to get this changed in the next X9.42 revision.

Current Registration Authority    

Name:

X9F

 
Short URLs for this page:

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved, Orange © 2024
Tree display Parent OID: ansi-x942(10046) First child OID: asn1der(0) First sibling OID: fieldType(0) Previous sibling OID: names(4) Next sibling OID: module(6) Last sibling OID: module(6)
Separation line
OID helper Webmaster Bullet 15 Jun 2022 Bullet Page top