Skip to main content

Introduction to the Remote Monitoring (RMON) Family of MIB Modules

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3577.
Authors Robert G. Cole , Dan Romascanu , Carl W. Kalbfleisch , Steven Waldbusser
Last updated 2015-10-14 (Latest revision 2003-06-04)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3577 (Informational)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Bert Wijnen
IESG note
Send notices to <>
A new Request for Comments is now available in online RFC libraries.

        RFC 3577

        Title:      Introduction to the Remote Monitoring (RMON)
                    Family of MIB Modules
        Author(s):  S. Waldbusser, R. Cole, C. Kalbfleisch,
                    D. Romascanu
        Status:     Informational
        Date:       August 2003
        Pages:      31
        Characters: 68551
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-rmonmib-framework-05.txt


The Remote Monitoring (RMON) Framework consists of a number of
interrelated documents.  This memo describes these documents and how
they relate to one another. 

This document is a product of the Remote Network Monitoring Working
Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.