Tech-invite3GPPspaceIETFspace
959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 5060

Protocol Independent Multicast MIB

Pages: 90
Proposed Standard
Errata
Part 1 of 4 – Pages 1 to 4
None   None   Next

Top   ToC   RFC5060 - Page 1
Network Working Group                                        R. Sivaramu
Request for Comments: 5060                                 Cisco Systems
Category: Standards Track                                     J. Lingard
                                                            Arastra, Inc
                                                             D. McWalter
                                                     Data Connection Ltd
                                                                B. Joshi
                                                Infosys Technologies Ltd
                                                              A. Kessler
                                                           Cisco Systems
                                                            January 2008


                   Protocol Independent Multicast MIB

Status of This Memo

   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.

Abstract

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.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. The Internet-Standard Management Framework . . . . . . . . . . 2 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . 82 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 86 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 86 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 86 9.1. Normative References . . . . . . . . . . . . . . . . . . . 86 9.2. Informative References . . . . . . . . . . . . . . . . . . 87
Top   ToC   RFC5060 - Page 2

1. Introduction

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 [RFC4601], BIDIR-PIM [RFC5015], and PIM-DM [RFC3973]). This document is part of work in progress to obsolete RFC 2934 [RFC2934]. RFC 2934 defined an experimental MIB module for managing the PIM protocols. The MIB module defined by this document is a re- working of the MIB module from RFC 2934, with major changes that include the following. o This MIB module is independent of IP version, whereas RFC 2934 only supported IPv4. o This MIB module includes support for managing BIDIR-PIM. o This MIB module retains limited support for managing PIM-DM [RFC3973], but that is no longer its primary purpose. o This MIB module does not include support for managing PIM-SM v1. o This MIB module does not depend on the IPv4 Multicast Routing MIB defined in RFC 2932 [RFC2932]. o This MIB module includes support for configuring static Rendezvous Points (RPs). o This MIB module includes support for configuring anycast RPs [RFC4610].

2. Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

3. The Internet-Standard Management Framework

For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP).
Top   ToC   RFC5060 - Page 3
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

4. Overview

This MIB module contains the following tables. 1. The PIM Interface Table, which contains one row per IP version for each interface of the router which is running PIM. 2. The PIM Neighbor Table, which contains one row for each of the router's PIM neighbors. 3. The PIM Neighbor Secondary Address Table, which contains one row for each secondary address advertised by each of the router's PIM neighbors. 4. The PIM (*,G) State Table, which contains one row for each group for which PIM has (*,G) state. 5. The PIM (*,G,I) State Table, which contains one row for each group and interface for which PIM has interface-specific (*,G) state. 6. The PIM (S,G) State Table, which contains one row for each source and group for which PIM has (S,G) state. 7. The PIM (S,G,I) State Table, which contains one row for each source, group, and interface for which PIM has interface- specific (S,G) state. 8. The PIM (S,G,rpt) State Table, which contains one row for each source and group for which PIM has (S,G,rpt) state. 9. The PIM (S,G,rpt,I) State Table, which contains one row for each source, group, and interface for which PIM has interface- specific (S,G,rpt) state. 10. The PIM Bidir DF-Election Table, which contains one row per interface for each Rendezvous Point (RP) for which Bidirectional-PIM Designated Forwarder (DF) election state is maintained.
Top   ToC   RFC5060 - Page 4
   11.  The PIM Static RP Table, which contains one row per range of
        multicast group addresses for which a particular configured RP
        should be used.

   12.  The PIM Group Mapping Table, which contains one row for each
        mapping from a multicast group address prefix to the PIM mode
        and RP address to use for groups within that group prefix,
        regardless of the source of the group mapping information.

   13.  The PIM Anycast-RP Set Table, which contains one row for each RP
        within each Anycast-RP set of which the local router is a
        member.

   This MIB module uses textual conventions defined in the IF-MIB
   [RFC2863], the INET-ADDRESS-MIB [RFC4001], and the IANA-RTPROTO-MIB
   [RTPROTO].  This MIB module REFERENCEs [RFC3376], [RFC3569],
   [RFC3618], [RFC3810], [RFC3956], [RFC3973], [RFC4601], [RFC4610],
   [RFC5015], [RFC5059], and [IPMCAST-MIB].



(page 4 continued on part 2)

Next Section