MDS 2.4 Object ID's
OID's must be unique for all objectclass and attributetype definitions throughout a directory namespace.
Although we highly recommend that organizations obtain their own Private Enterprise Numbers directly from IANA, the Globus team will upon request assign a subspace of the MDS OID to anyone publishing data into MDS.
| 1.3.6.1.4.1 | IANA PEN |
| 3536 | Globus |
| 2 | Information Services |
| 6 | MDS |
| 3536 | MDS subspace for community registrations |
| n | number assigned by mds-oid-registrar |
So, your assigned OID will look like this:
1.3.6.1.4.1.3536.2.6.3536.n
Where "n" is your specific assigned number. You have the ability to subdivide an assigned OID as you choose.
Please note that just like OID's, objectclass names and attributetype names must also be unique across the entire directory name space. MDS addresses this issue by prefixing all names with "Mds".
We recommend that if you are obtaining an OID to add items to the directory service schema, that you also select a prefix to use on all objectclass and attributetype names. Sending this prefix to the mds-oid-registrar as part of your OID request will help ensure uniqueness of names for items added to the information services name space.