Hello all,
I have my own spanking fresh Enterprise OID number on the way from IANA,
and I have a pretty good idea that I need to pay attention when building
my OID trees lest I make hard-to-fix mistakes down the road.
It's not here yet, but for discussion let's say that it's:
iso.org.dod.internet.private.enterprise.unixwiz
-aka-
1.3.6.1.4.1.30000
We're going to use these for both SNMP and LDAP, but I'm sure I don't
want to name the first item
1.3.6.1.4.1.30000.1
This would work initially, but when I need to change my whole OID
structure around or create a second, unrelated project, I'm not sure how
to make a "version 2", so this suggests some pre-planning to allow room
for growth. I just don't know the best way to handle this.
We're also creating our own LDAP objects, and though I am almost certain
that the two systems (LDAP and SNMP) have their own namespaces, it would
not surprise me if it were a good idea to not allow overlap.
All of the above are asking for a best-practices document, and I have
not been even able to figure out what to search for.
I'd surely love some guidance.
Steve
--
Stephen J Friedl | Security Consultant | UNIX Wizard | +1 714 544-6561
www.unixwiz.net | Tustin, Calif. USA | Microsoft MVP | [EMAIL PROTECTED]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
