RFC 3737: IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modules
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3737
- Published
- April 2004
- Authors
- B. Wijnen; A. Bierman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3434Remote Monitoring MIB Extensions for High Capacity AlarmsCurrent
December 2002
- RFC 3287Remote Monitoring MIB Extensions for Differentiated ServicesCurrent
July 2002
- RFC 3273Remote Network Monitoring Management Information Base for High Capacity NetworksUpdated
July 2002
- RFC 3729Application Performance Measurement MIBCurrent
March 2004
- RFC 3728Definitions of Managed Objects for Very High Speed Digital Subscriber Lines (VDSL)Current
February 2004
- RFC 3747The Differentiated Services Configuration MIBCurrent
April 2004
- RFC 3705High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute IntervalsCurrent
February 2004
- RFC 3637Definitions of Managed Objects for the Ethernet WAN Interface SublayerCurrent
October 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?