Re: MIB module numbering for TBD MIB roots

[Andy Bierman <abierman@cisco.com>]

At 10:26 AM 1/17/2002, Juergen Schoenwaelder wrote:

>>>>>> Andy Bierman writes:
>
>Andy> I like plan (d):
>
>Andy> Create an OID rooting convention for Standard and Enterprise
>Andy> MIBs, requiring MIBs-in-progress to be rooted under a branch
>Andy> called 'unassigned'.
>
>Andy> For MIBs in Internet Drafts (mandatory):
>
>Andy>    unassigned ::= { mib-2 0 } fooMib ::= { unassigned x } ( == {
>Andy> mib-2 0 x } to keep IMPORTS stable)
>
>Andy> For vendor MIBs (suggested):
>
>Andy>    <prefix>Unassigned ::= { <enterprise-id> 0 } fooMib ::= {
>Andy> <prefix>Unassigned 0 x }
>
>Andy> e.g.  ciscoUnassigned ::= { enterprises 9 0 } cFooMib ::= {
>Andy> ciscoUnassigned x }
>
>Andy> where 'x' is a temporary assignment, which may be reused over
>Andy> time
>
>Requires even more edits to get rid of the unassigned definitions.

I think it's more important that the numerous MIB readers 
(and even MIB tools) identify a MIB root as unassigned, than it is
to save the 1 MIB writer 10 seconds of editing.

>I still think { mib-2 0 } or { mib-2 xxx } are good enough - it is
>virtually impossible to prevent someone from doing the wrong thing.
>I do not think (d) is in any way stronger than (a) or (b) - perhaps I
>mis-understand the meaning of 'x'.


The 'x' is the leaf integer of the MIB root assignment.
This is needed to allow more than one unassigned MIB to exist
in a development environment, since multiple MIB modules using
the same root won't work in most (all?) SNMP tool-kits.


>/js 

Andy