Reference record for OID 2.2.3
- Parent
- 2.2 (association-control)
- Node code
- 3
- Node name
- as-id
- Numeric OID
- 2.2.3
- URN notation
- urn:oid:2.2.3
- ASN.1 notation
-
{2 2 3}
- {joint-iso-itu-t(2) association-control(2) as-id(3)}
- {joint-iso-ccitt(2) association-control(2) as-id(3)}
- OID-IRI notation
- /2/2/3
- /Joint-ISO-ITU-T/2/3
- Named path variants
- /joint-iso-itu-t/association-control/as-id
- /joint-iso-ccitt/association-control/as-id
Descriptions
Descriptions may differ between sources. The primary description is shown first.
Primary description: OID Repository
Application services
View at oid-base.com
View at oid-base.com
This module is defined in Recommendation ITU-T X.227 (April 1995) and in ISO/IEC 8650-1: 1996: "Connection-oriented protocol for the Association Control Service Element: Protocol specification".
Note that the body of Rec. ITU-T X.227 defines
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.
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 (inferred from ancestor 2.2)
Current Registration Authority (inferred from ancestor 2)
ITU-T SG 17 & ISO/IEC JTC 1/SC 6
Direct children (1)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 2.2.3.1 | acse-ase | 1 | 1 | Association Control Service Element - Application Service Element |