Reference record for OID 2.2.3.1

parent

2.2.3 (as-id)

node code

1

node name

acse-ase

dot oid

2.2.3.1

asn1 oid

{joint-iso-itu-t(2) association-control(2) as-id(3) acse-ase(1)}

{joint-iso-ccitt(2) association-control(2) as-id(3) acse-ase(1)}

iri oid

/joint-iso-itu-t/association-control/as-id/acse-ase

/joint-iso-ccitt/association-control/as-id/acse-ase

iri by oid_info

/Joint-ISO-ITU-T/2/3/1

Description by oid_info

Association Control Service Element - Application Service Element
View at oid-info.com

Information by oid_info

Note that the body of Rec. ITU-T X.227 defines {joint-iso-itu-t association-control(2) as-id(3) acse-ase(1) version(1)} whereas its Annex B defines {joint-iso-itu-t association-control(2) authentication-mechanism(3) password-1(1)}.
On Jan. 22, 2003, Peter Furniss wrote: yes, the authentication mechanism OID is wrong (since it came second historically, it's Annex B that is at fault). However, the fact that no-one has ever raised this problems makes it clear that either no-one has implemented Annex B (possible), or if they have, they have not found any problems in colliding with the OID for the ASE. If anyone is using these OIDs in practice, it would be a considerable dis-service, of no benefit to anyone, to change of the OIDs.

First Registration Authority (recovered by parent 2.2)

J. Quigley & A. Fletcher

Current Registration Authority (recovered by parent 2)

ITU-T SG 17 & ISO/IEC JTC 1/SC 6

Children (1)