[rfc-dist] RFC 5060 on Protocol Independent Multicast MIB

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Jan 25 16:36:15 PST 2008

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

        RFC 5060

        Title:      Protocol Independent Multicast MIB 
        Author:     R. Sivaramu, J. Lingard,
                    D. McWalter, B. Joshi,
                    A. Kessler
        Status:     Standards Track
        Date:       January 2008
        Mailbox:    raghava at cisco.com, 
                    jchl at arastra.com, 
                    dmcw at dataconnection.com,  bharat_joshi at infosys.com, 
                    kessler at cisco.com
        Pages:      90
        Characters: 170123
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pim-mib-v2-10.txt

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

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing the
Protocol Independent Multicast (PIM) protocols: PIM-SM (Sparse Mode),
BIDIR-PIM (Bidirectional), and PIM-DM (Dense Mode).  This document is
part of work in progress to obsolete RFC 2934, and is to be preferred
where the two documents overlap.  This document does not obsolete RFC

This document is a product of the Protocol Independent Multicast
Working Group of the IETF.

This is now a Proposed 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 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 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.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list