RE: MIB module root assignment

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

> I would like to get feedback from this group on a proposal
> before taking it to a larger audience.
> 
> Problem:  
> 
> The MODULE-IDENTITY macro (MIB root assignment) contained 
> in a MIB module should be assigned by IANA when the RFC 
> containing the MIB module is published.  During the I-D
> development, the MIB module root assignment is done in an 
> ad-hoc manner.  This practice has led to confusion and poor
> procedures, e.g.:
>   - WG controlled naming authorities  { rmon 30 }
>   - invalid SMI syntax in MIBs under development { mib-2 xxx }
>   - random (unauthorized) temporary MIB roots { mib-2 6767 }
> 
> It is desirable to provide a consistent temporary MIB module
> root which will not require any changes to existing MIB compiler
> tools, and is easily identifiable as a temporary MIB module 
> root. 
> 
> Proposed Solution:
> 
> Ask IANA to assign the OID { mib-2 999999 } as the
> official temporary MIB module root.  Update the MIB Review
> Guidelines and MIB module template to mandate that
> MIB modules under development use this IANA assigned
> temporary MIB module root.
> 
> Comments?
> 
And REQUIRE (i.e. a MUST) that MIB documents under development
use something aka:

   ::= { mib-2 999999 } -- 999999 to be replaced by an IANA assigned
                        -- value. Be WARNED to NOT use this value for
                        -- shipping any product (not even beta level).

> thanks,
> Andy
> 
> 
> 
>