Re: MIB module numbering for TBD MIB roots

[Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>]

>>>>> 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 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'.

/js