RFC 3737

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

📅 published April 2004, from ietf

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

okay bestie, let's get into this one 💅 It's an Internet Standards Track doc from April 2004, so it's an official spec. It was written by B. Wijnen of Lucent Technologies and A. Bierman of Cisco Systems, Inc. 🧚 The title block doesn't list anything it obsoletes or updates.

Status of this Memo ✨

This doc specifies an Internet standards track protocol for the Internet community, and it's asking for discussion and suggestions for improvements. For the current standardization state and status of this protocol, check the current edition of the "Internet Official Protocol Standards" (STD 1) 📚 Distribution of this memo is unlimited 🌸

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

Abstract 🦋

This document is all about how IANA administers and maintains the Object Identifier (OID) tree under the Remote Monitoring (rmon) root 🌈 It also records the values that are currently assigned, so it's basically the official guest list 💅

1. Introduction 💖

The RMONMIB Working Group used to keep its own registry for OID assignments for new MIB modules under the rmon root OID [RFC2819]. Honestly it worked pretty well 🫶 but errors had to get fixed late in the game once or twice, and a few assignments that are now defunct slipped in too 😭

It's also a bit of a non-standard move, because normally a new standards track MIB module gets a MIB root assigned when it's published as an RFC 🙈

This doc lists the rmon OIDs that are currently assigned ✨ It also describes the procedures and rules for new assignments, and it asks IANA to take over responsibility for existing and future assignments. Main character energy for IANA 👑

The current assignments aren't all super logical, ngl 💀 At first normal MIB OIDs got assigned under rmon, but later the WG used the rmon root OID to create new MIB modules underneath it. Some people will say "an OID is just an OID," and yes, that's technically true 🤷‍♀️ but it doesn't make life easier when the organization of OIDs isn't logical. We can't change what's already been assigned, though 😭 From now on, only MODULE-IDENTITY macro (MIB root) assignments will be made (by IANA) under the 'rmon' node 🫶 Inside a MIB module, the working group authors and editors can assign their own OIDs following the normal procedures 💅

2. Currently assigned OIDs under the rmon root 🌸

As of when this was written, the OIDs below have been assigned, and IANA has picked up this info for its public registry of assigned values ✨ They're 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 kept by the RMONMIB Working Group until RFC 3737 got published 📚 Some of the early ones look kinda random, and yeah, that's true, but that's history and it can't be changed 🙈 From now on, only MODULE-IDENTITY macro (MIB root) assignments will be made (by IANA) under the 'rmon' node 🦋

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]
    19   probeConfig           OID                      [RFC2021]
    20   rmonConformance       OID                      [RFC2021]
    21   mediaIndependentStats OID                      [RFC3273]
    22   switchRMON            M-I                      [RFC2613]
    23   apm                   M-I                      [RFC3729]
    24   available
    25   pmCapsMIB             M-I (defunct)
    26   dsmonMIB              M-I                      [RFC3287]
    27   interfaceTopNMIB      M-I                      [RFC3144]
    28   reserved for sspmMIB  M-I    [..rmonmib-sspm-mib-nn.txt]
    29   hcAlarmMIB            M-I                      [RFC3434]
    30   reserved for tpmMIB   M-I     [..rmonmib-tpm-mib-nn.txt]
    31   reserved for raqmon   M-I  [..rmonmib-raqmon-mib-nn.txt]
    32   reserved for raqmonDs M-I  [..rmonmib-raqmon-pdu-nn.txt]

Key: xxx == { rmon.rmonConformance xxx }

...mib-2.rmon.conformance (1.3.6.1.2.1.16.20)

   xxx   descriptor            OID Type                 Document

     1   rmon2MIBCompliances   OID                      [RFC2021]
     2   rmon2MIBGroups        OID                      [RFC2021]
     3   smonMIBCompliances    OID                      [RFC2613]
     4   smonMIBGroups         OID                      [RFC2613]
     5   hcRMON                M-I                      [RFC3273]
     6   hcRmonMIBCompliances  OID                      [RFC3273]
     7   hcRmonMIBGroups       OID                      [RFC3273]
     8   rmonMibModule         M-I                      [RFC2819]
     9   rmonCompliances       OID                      [RFC2819]
    10   rmonGroups            OID                      [RFC2819]

3. How to request a new assignment for a MIB module 🧚

When anyone is writing an internet-draft that needs a new assignment under the rmon OID, the proper way to do it looks like this 💖

   EXAMPLE-MIB DEFINITIONS ::= BEGIN

   IMPORTS
     rmon          FROM RMON-MIB

     .. other imports ..

   exampleMIB  MODULE-IDENTITY

     ... other normal MODULE-IDENTITY stuff ...

   ::= { rmon nnn }  -- IANA: please assign nnn
                     -- RFC-Editor: replace nnn with IANA-assigned
                     --             number and remove this note

IANA will assign the number as part of the RFC publication process ✨

Acknowledgement ✨

okay so the last bit is a shoutout 🫶 Funding for the RFC Editor function is currently provided by the Internet Society 🌸 that's it, that's the whole ending, but it's giving thank-you-for-keeping-the-lights-on energy 💖

📦 where this page comes from