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

Document Type RFC - Proposed Standard (April 2004; No errata)
Last updated 2015-10-14
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3737 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Ted Hardie
Send notices to (None)
Network Working Group                                          B. Wijnen
Request for Comments: 3737                           Lucent Technologies
Category: Standards Track                                     A. Bierman
                                                     Cisco Systems, Inc.
                                                              April 2004

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

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).  All Rights Reserved.

Abstract

   This document defines the procedures for IANA to administer and
   maintain the Object Identifier (OID) tree under the Remote Monitoring
   (rmon) root.  This memo also documents the currently assigned values.

1.  Introduction

   The RMONMIB Working Group so far has maintained its own registry for
   OID assignments for new MIB modules under the root OID for rmon
   [RFC2819].  This has worked reasonably well, although errors had to
   be corrected at a late stage one or two times, and a few now defunct
   assignments have been made as well.

   It is also a somewhat non-standard way of doing things, because
   normally a new standards track MIB module will get a MIB root
   assigned at the time that the module is being published as part of an
   RFC.

   This document lists the currently assigned rmon OIDs.  It also
   describes the procedures and rules for new assignments and asks IANA
   to take over the responsibility for existing and future assignments.

   The current assignments are not all too logical.  Initially normal
   MIB OIDs were assigned under rmon, but at a later time the WG used
   the rmon root OID to create new MIB modules underneath it.  Some

Wijnen & Bierman            Standards Track                     [Page 1]
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                     [Page 2]
RFC 3737         IANA Guidelines for the RMON Registry        April 2004

   Key: nnn == { rmon nnn }

      nnn   descriptor            OID Type                 Document

        0   rmonEventsV2          Notifications root       [RFC2819]
        1   statistics            OID                      [RFC2819]
        2   history               OID                      [RFC2819]
        3   alarm                 OID                      [RFC2819]
        4   hosts                 OID                      [RFC2819]
        5   hostTopN              OID                      [RFC2819]
        6   matrix                OID                      [RFC2819]
        7   filter                OID                      [RFC2819]
        8   capture               OID                      [RFC2819]
        9   event                 OID                      [RFC2819]
       10   tokenRing             OID                      [RFC1513]
       11   protocolDir           OID                      [RFC2021]
       12   protocolDist          OID                      [RFC2021]
       13   addressMap            OID                      [RFC2021]
       14   nlHost                OID                      [RFC2021]
       15   nlMatrix              OID                      [RFC2021]
       16   alHost                OID                      [RFC2021]
       17   alMatrix              OID                      [RFC2021]
       18   usrHistory            OID                      [RFC2021]
Show full document text