Multiple textual identifiers for one OID

Holger Klaas <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <CACxs4dF+Kp-ykL2ct1xTcKd81npCHbgWpTV-2uDUTveFDu7fQg@mail.gmail.com>
Hi,

I always thought that for each OID there can only be one textual
identifier. Now I came across this FAQ:
http://www.oid-info.com/faq.htm#iri
Under question 28 the following is written:

Just as an OID node can have multiple identifiers in ASN.1 notation,
it can have multiple Unicode labels (this allows
backwards-compatibility when a company changes its name, for example).

If I understand that right it means that an OID could have multiple
textual identifiers?
E.g.:
iso.org.dod.internet.private.enterprises.99999 is defined in
COMPANY-MIB-1 as companName  and
iso.org.dod.internet.private.enterprises.99999 is defined in
COMPANY-MIB-2 as newCompanName

The two MIBs could then be loaded at the same time without causing any
clashes, and a walk on
iso.org.dod.internet.private.enterprises.companName   and
iso.org.dod.internet.private.enterprises.newCompanName
would return the same results?
Would IANA need to be notified about the change of the textual
identifier (in case of an enterprise OID)?

I have created two MIBs as in the example above and with net-snmp I
can use either textual OID for a walk without any problems. I have
also tested the MIB with smilint while preloading the second MIB and
no errors were returned.

So are multiple identifiers allowed for one OID?

Thanks in advance,

Holger

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.