Where to root MIB modules

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

MIB-Doctors,

First a happy, prosperous and healthy new year to all of you!

Mike Heard and I had a little side discussion when Mike
ran into a practice in PWE3 MIB documents.

The questionable (?) practice is that some WGs or Technologies
are requesting (I will use a well known example here):

       rmon    OBJECT IDENTIFIER ::= { mib-2 16 }

And then we keep requesting assignments for RMON related modules 
under rmon.

The MPLS WG has done a similar thing for a set of MPLS related MIB
modules, where they have:

          mplsStdMIB OBJECT IDENTIFIER

          -- This object identifier needs to be assigned by IANA.
          -- Since mpls has been assigned an ifType of 166 we recommend
          -- that this OID be 166 as well, e.g.
          --   ::= { transmission 166 }

          ::= { transmission XXX }  -- to be assigned by IANA

and then they root their various MIB modules under mplsStdMIB.

PWE3 seems to want to go down the same path.

The question that is on the table is:

  Should we (MIB Doctors)
   - discourage this practice (admitting that rmon and mplsStdMIB were
     mistakes) and instead recommend to assign directly under mib-2
     or transmission?
   - encourage this practice because it is a good way to group 
     related modules together?
   - just leave it to the various WGs and accept the way they choose
     to root their MIB modules?
   
Comments and arguments for or against various options are sollicited.

Thanks 
Bert