[Date Prev][Date Next]
Re: How to construct an OID?
----- Original Message -----
From: "Eric Kilfoil" <email@example.com>
> It's pretty much personal preference. First of all, remember that things
> other than your ldap schema will be under your OID tree.
> For example, you may want to do something like this:
> enterprises.10569.1 = enterprises.yourcompany.ldapschema
> enterprises.10569.1.1 = enterprises.yourcompany.ldapschema.attributes
> enterprises.10522.214.171.124 =
> enterprises.10569.1.2 = enterprises.yourcompany.ldapschema.objectclasses
> enterprises.105126.96.36.199 =
> Then... if you needed to later:
> enterprises.10569.2 = enterprises.yourcompany.snmpoids
> And of course anything else that needs an OID can fit into this as well.
> Remember that an attribute isn't neccessarily tied to just one
Thank you, Eric. That makes a lot of sense.
I finally got the IANA enterprise numbers page
<ftp://ftp.isi.edu/in-notes/iana/assignments/enterprise-numbers> to come up
this morning at home -- I have been unable to access it from work. At the
top of the page is says,
Prefix: iso.org.dod.internet.private.enterprise (188.8.131.52.4.1)
This answers my question about the prefix part of the OID.
So am I correct in assuming that the 184.108.40.206.4.1.10569 portion is a unique
identifier that will always uniquely identify me any time an OID is required
for any object, LDAP-related or not? (As long as no one else makes up a
fictitious number and happens to pick mine.)
> On Tue, 21 Aug 2001, Chuck Coker wrote:
> > I received a IANA Private Enterprise Number, 10569, but now I am not
> > sure how to construct a proper OID.
> > Would I start with 220.127.116.11.4.1.10569 as the top of my "personal" tree?
> > And then build my hierarchy below that? For example,
> > 18.104.22.168.4.1.10569.1 Item 1
> > 22.214.171.124.4.1.10569.1.1 Item 1, Sub-Item 1
> > 126.96.36.199.4.1.10569.1.2 Item 1, Sub-Item 2
> > 188.8.131.52.4.1.10569.2 Item 2
> > 184.108.40.206.4.1.10569.3 Item 3
> > Thanks,
> > Chuck Coker