RFC 3737 (rfc3737) - Page 2 of 7

IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modules

RFC 3737         IANA Guidelines for the RMON Registry        April 2004


   people will claim 'an OID is just an OID', and while this is true, it
   does not make things easier if the organisation of OIDs is not
   logical.  However, we cannot change what has been assigned in the
   past.  From now on, only MODULE-IDENTITY macro (MIB root) assignments
   will be made (by IANA) under the 'rmon' node.  Within a MIB module,
   the working group authors/editors can then assign their own OIDs
   according to normal procedures.

2.  Currently assigned OIDs under the rmon root

   At the time of this writing, the following OIDs have been assigned
   and IANA has picked up this information in their public registry of
   assigned values.  They are listed as part of the already existing
   smi-numbers registry at:

       http://www.iana.org/assignments/smi-numbers

       ...mib-2.rmon (1.3.6.1.2.1.16)

   The assignments under ...mib-2.rmon were maintained by the RMONMIB
   Working Group until publication of RFC 3737.  Some (early)
   assignments may not look all too logical.  That is true, but that is
   history and cannot be changed.  From now on, only MODULE-IDENTITY
   macro (MIB root) assignments will be made (by IANA) under the 'rmon'
   node.


























Wijnen & Bierman            Standards Track