Re: MIB module numbering for TBD MIB roots

[Andy Bierman <abierman@cisco.com>]

At 01:26 AM 1/18/2002, Juergen Schoenwaelder wrote:

>>>>>> Andy Bierman writes:
>
>Andy> The 'x' is the leaf integer of the MIB root assignment.  This is
>Andy> needed to allow more than one unassigned MIB to exist in a
>Andy> development environment, since multiple MIB modules using the
>Andy> same root won't work in most (all?) SNMP tool-kits.
>
>So you can have conflicts in your 'x' assignments and you have just
>moved the problem somewhere else, right?


apples and oranges -- I'm not trying to solve the double-assignment
problem.  I'm just trying to give MIB readers and MIB tools a clue that
the work-in-progress is an initial version of a MIB, and therefore
has not been assigned a real MIB root. { mib-2 0 <int> } will work fine.
The syntax { mib-2 xxx } is not universally accepted by MIB tools, and
it has to be edited before use for development, but this is better
than nothing.  

I think there is benefit in encouraging implementation before the 
very end of a standard MIB effort, especially since most
MIBs stabilize fairly quickly, then bog down in cycles of reviews,
clarifications, and delays. 

WGs like RMONMIB that have their own branch under mib-2 have a clear
advantage over WGs that have to wait until the end of the process
to get a number.

Andy



>/js