Protocol Independent Multicast MIB
RFC 5060
| Document | Type |
RFC - Proposed Standard
(January 2008; Errata)
Was draft-ietf-pim-mib-v2 (pim WG)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5060 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Bill Fenner | ||
| Send notices to | dthaler@windows.microsoft.com | ||
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
Sivaramu, et al. Standards Track [Page 1]
RFC 5060 PIM MIB January 2008
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).
Sivaramu, et al. Standards Track [Page 2]
Show full document text