[rfc-dist] RFC 4502 on Remote Network Monitoring Management Information Base Version 2

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Mon May 22 15:24:53 PDT 2006

A new Request for Comments is now available in online RFC libraries.

        RFC 4502

        Title:      Remote Network Monitoring Management Information 
                    Base Version 2 
        Author:     S. Waldbusser
        Status:     Standards Track
        Date:       May 2006
        Mailbox:    waldbusser at nextbeacon.com
        Pages:      142
        Characters: 290816

        I-D Tag:    draft-ietf-rmonmib-rmon2-v2-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4502.txt

This document defines a portion of the Management
Information Base (MIB) for use with network management
protocols in TCP/IP-based internets.  In particular, it
defines objects for managing remote network monitoring

This document obsoletes RFC 2021, updates RFC 3273, and contains a new
version of the RMON2-MIB module.  [STANDARDS TRACK]

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

This is now a Draft Standard Protocol.

STANDARDS TRACK: 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 

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 at 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 at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


More information about the rfc-dist mailing list