RE: registration OIDs: do the values matter?

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

> >Indeed.  And I see a couple of assignments in that list that are
> >wrong and need to be corrected.  Specifically,
> >
> >SSPM-MIB:     sspmMIB               M-I     { mib-2 777 }
> >RAQMON-MIB:   raqmon                M-I     { mib-2 6889 }
> >
> >are listed in the corresponding I-Ds as
> >
> >SPM-MIB:      sspmMIB               M-I     { rmon 777 }
> >RAQMON-MIB:   raqmon                M-I     { rmon 6889 }
> 
> these MIB modules are under development and will be fixed soon.
> 
They should NEVER have had these numbers in. Insetaad they shoul do:

> >SPM-MIB:      sspmMIB M-I     { rmon xxx } -- to be assigned by Someone
> >RAQMON-MIB:   raqmon  M-I     { rmon xxx } -- to be assigned by Someone

The plain assignment of arbitrary numbers is a BUG in the WG process.

The "Someone" is the problem here. For WGs that do their own stuff,
it is very unclear to me how we keep control and avoid possible
bugs that turn out in conflicting (colliding) assignments.

Bert