[pim] RFC 5060 on Protocol Independent Multicast MIB

rfc-editor@rfc-editor.org Sat, 26 January 2008 00:36 UTC

Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIZ1v-0001yM-Sl; Fri, 25 Jan 2008 19:36:19 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIZ1s-0001rp-DB; Fri, 25 Jan 2008 19:36:16 -0500
Received: from bosco.isi.edu ([128.9.168.207]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JIZ1r-0005Tm-V8; Fri, 25 Jan 2008 19:36:16 -0500
Received: by bosco.isi.edu (Postfix, from userid 70) id A9D1210AFD6; Fri, 25 Jan 2008 16:36:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080126003615.A9D1210AFD6@bosco.isi.edu>
Date: Fri, 25 Jan 2008 16:36:15 -0800
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: pim@ietf.org, rfc-editor@rfc-editor.org
Subject: [pim] RFC 5060 on Protocol Independent Multicast MIB
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
Errors-To: pim-bounces@ietf.org

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@cisco.com, 
                    jchl@arastra.com, 
                    dmcw@dataconnection.com,  bharat_joshi@infosys.com, 
                    kessler@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
2934.  [STANDARDS TRACK]

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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.

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.


The RFC Editor Team
USC/Information Sciences Institute

...



_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim