http://en.wikipedia.org/wiki/Object_identifier
Every objectClass that is part of a LDAP Schema receives a dotted decimal hierarchical identifier. These OIDs can be organized in a tree structure, very similar to the X.500 DIT , called Object Identifier Tree (OIT). They were defined by the X.208 standard, and they have been revised and updated by the X.680 standard. Immediately below the root of this tree, there are only three values currently defined as shown above.
Each LDAP Schema element is identified by a globally unique Object Identifier (OID). OIDs are also used to identify other objects. They are commonly found in protocols described by ASN.1. In particular, they are heavily used by the Simple Network Management Protocol (SNMP). As OIDs are hierarchical, your organization can obtain one OID and branch it as needed.
You can design a hierarchy suitable to your organizational needs under your organization's OID. No matter what hierarchy you choose, you should maintain a registry of assignments you make. This can be a simple flat file or a something more sophisticated such as the OpenLDAP OID Registry
.
For more information about Object Identifiers (and a listing service) see http://www.alvestrand.no/harald/objectid/
.
and your official OID will be sent to you usually within a few days. Your base OID will be something like 1.3.6.1.4.1.X were X is an integer.
Microsoft has an OID for Microsft Base OID for Customer Usage
[1] and even a script to help generate them
[2]
- based on information obtained 2014-03-28
- based on information obtained 2014-03-28
- based on information obtained 2014-03-28
- based on information obtained 2014-03-28
- based on information obtained 2014-03-28
- based on information obtained 2014-03-28
- based on information obtained 2014-03-28