Introduction to OIDs and
OID Resolution System (ORS)
Introduction to OIDs Internationalization and the long arc concept Use of OIDs Introduction to ORS Features of the ORS
Frequently Asked Questions (FAQ)
|Introduction to OIDs||OID handbook|
The Object Identifier (OID) concept and implementation dates back to the mid-1980s, based on collaboration with the International Federation for Information Processing (IFIP) over the previous several years.
OIDs provide a persistent identification of objects based on a hierarchical structure of Registration Authorities (RA), where each parent has an object identifier and allocates object identifiers to child nodes. It provides a universal and flexible identification scheme for persistent objects. It has been supported and recommended by ITU-T, ISO and IEC, and has been used in many ITU-T (and ITU-R) Recommendations, and ISO and IEC International Standards, since the middle 1980s, as part of the ASN.1 (Abstract Syntax Notation One).
Almost any organization, Recommendation, or Standard can obtain (if it not already has) an OID node. OIDs are fundamental for all security work in ITU, ISO and IETF, and are widely used in many standards.
|Internationalization and the long arc concept|
At the same time, the concept of "long arcs" from the root of the International OID tree to a node at level 2 or below was introduced. Long arcs do not have numerical values, but provide an unambiguous reference to the node from the root using a Unicode label.
Use of a path specified purely in terms of the set of Unicode labels on the (normal or long) arcs from the root to a node is called an International Object Identifier for that node.
In order to support names of arcs in multiple languages, an arc can have multiple Unicode labels, giving rise to a need to transform a path using Unicode labels into a canonical form of purely numerical labels to identify the node. This is handled by the OID Resolution System (described below).
|What is an OID-IRI (Internationalized Resource Identifier)?|
|Use of OIDs|
Known areas of use include:
|Introduction to the ORS|
Given that there are multiple ways of identifying an International Object Identifier tree node by a set of Unicode labels defining the path from the root to that node, there was a requirement to be able to transform that by an efficient on-line look-up into a canonical form consisting of the all-numeric identification of arcs of the path (canonicalization).
There was also a requirement for the management of a node to be able to store (and applications to retrieve) information associated with a node in a flexible way (node information retrieval). This was first identified in terms of RFID applications (What is the content of this jar of jam? Who is the owner of this piece of hold baggage? etc.) but now extends more widely.
There was a requirement for both of these look-up activities to be fully supported by authentication of the returned result with a trust anchor.
The OID Resolution System (ORS) was developed from 2004 onwards, and allows an application to obtain (online) application-specific information related to any node identified by an OID.
The ORS enables any one of the OID nodes to be mapped into DNS name zone files, and information about it can be obtained by a DNS look-up for further application processing. The system was initially designed to support RFID tag activity, but also has applications in many other application areas.
|More information in the OID handbook (part 6)|
|Features of the ORS|
KISA activity report with regards to the ORS root nodes