OID Repository
OID Repository
https://oid-base.com
Display OID:
 

How to apply for an OID


Page section Introduction to OIDs Page section Select where to get your OID from Page section Submit an OID request Page section Manage your OID Page section 		  See alsoPresentation on OIDs
Separation line

 

Introduction to OIDs

    

An Object Identifier (OID) is a globally unique identifier for persistent objects used in various systems and protocols. OIDs are essential for ensuring interoperability and uniqueness in systems that rely on standardized naming conventions. They are widely used in areas such as information technology, telecommunications, healthcare, etc. They are structured in a hierarchical tree format, with each node in the tree representing an organization or a specific object. Any organization/entity, individual or standard can obtain an OID (if it not already has one).

Obtaining and managing an OID is a straightforward process, but it requires careful planning and documentation. By following the steps below, you can ensure that your OID is used effectively and remains a reliable part of your organization's infrastructure.

See alsoIntroduction to OIDs
Separation line

Select where to get your OID from

 Page top

Before requesting an OID, find out where you could get it from. Common use cases include:



A country wishing to establish a Registration Authority (RA) for allocating OIDs on a national basis shall follow this process (see also question 11 in the FAQ).
A company, a project or, broadly speaking, an entity can use one of the following alternatives to apply for an OID:
An invidual can use one of the following alternatives to apply for an OID:
Standardization organizations have specific rules to define OIDs in their standards. More information (including contact details) can be found at the following links: ISO, IEC, ITU-T, ITU-R, ETSI, IEEE.
If you are working for a company, an organization or, broadly speaking, an entity, it is recommended to check if your entity does not already have an OID assigned, e.g. by searching in this OID repository:
  • If an OID is already assigned to your company or entity, please contact the person in charge of that OID to get an specific OID assigned for your specific use.
  • If an OID is not yet assigned to your company or entity, please select "a company" or "an international project" in the drop-down list above.
For the health sector, see HL7's frequently asked questions.
In addition, Dave Harvey (UK) sub-delegate ranges of his own OID to anyone who uses a DICOM toolkit (communication in medicine).
If you only need an OID for an example in a document, see question 22 in the FAQ.
Separation line

Submit an OID request

 Page top

To request an OID:

  1. Contact the registration authority of the parent OID under which you want to get an OID (in particular, some registration authorities are mentioned in the previous section).
    Important: OIDs have to be requested from a registration authority because this OID repository is not a registration authority.
  2. Fill out the required application form, providing details about your organization and the intended use of the OID.
  3. Pay any applicable fees (if required).
  4. Wait for confirmation and allocation of your OID: Once allocated, you can create child OIDs your specific needs.
Separation line

Manage your OID

 Page top

After receiving your OID, you shall document its structure and usage.

  • Define your OID structure and document it:
    • Define branches (child OIDs) for different departments, systems, projects or products; for example:
      x.y.z: Your OID
      • x.y.z.1: Department A
      • x.y.z.2: Department B
      • x.y.z.3: Project X
    • Plan for the future: Design a scalable OID hierarchy to accommodate future growth.
    • Understand your standards: If your OID is used in specific protocols (e.g. SNMP, LDAP, ITU-T X.509, DICOM), follow the associated standards to avoid issues.
  • Maintain a registry of all child OIDs:
    • A well-documented structure ensures consistency and prevents conflicts.
    • Internally, maintain a registry or database to track child OIDs, their purpose and associated documentation. Tools like this OID repository or ViaThinkSoft OIDplus can help.
    • If the OIDs are used externally (or need to be discoverable), consider publishing their definitions in a public repository such as this OID repository. Clear documentation makes it easier for others to understand and use your OIDs correctly.
    • Avoid repurposing or reassigning OIDs, as this can lead to compatibility issues. Always treat assigned OIDs as immutable.
  • Keep your OIDs safe:
    • Treat your OID allocation with care (particularly when they are used in sensitive systems like healthcare or cybersecurity): Unauthorized changes can lead to interoperability problems.
    • Complies with relevant standards and regulations where applicable.

See alsoDuties of a Registration Authority