< draft-ietf-pim-mib-v2-07.txt   draft-ietf-pim-mib-v2-08.txt >
PIM WG R. Sivaramu PIM WG R. Sivaramu
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Expires: May 17, 2007 J. Lingard Expires: June 16, 2007 J. Lingard
D. McWalter D. McWalter
Data Connection Ltd Data Connection Ltd
B. Joshi B. Joshi
Infosys Technologies Ltd Infosys Technologies Ltd
November 13, 2006 December 13, 2006
Protocol Independent Multicast MIB Protocol Independent Multicast MIB
draft-ietf-pim-mib-v2-07.txt draft-ietf-pim-mib-v2-08.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 38 skipping to change at page 1, line 38
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 17, 2007. This Internet-Draft will expire on June 16, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2006).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing the In particular, it describes managed objects used for managing the
Protocol Independent Multicast (PIM) protocols (PIM-SM and BIDIR- Protocol Independent Multicast (PIM) protocols (PIM-SM, BIDIR-PIM and
PIM). This document is part of work in progress to obsolete RFC PIM-DM). This document is part of work in progress to obsolete RFC
2934, and is to be preferred where the two documents overlap. This 2934, and is to be preferred where the two documents overlap. This
document does not obsolete RFC 2934. document does not obsolete RFC 2934.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 81 5. Security Considerations . . . . . . . . . . . . . . . . . . . 81
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 87 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 88
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 87 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 88
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 88 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8.1 Normative References . . . . . . . . . . . . . . . . . . . 88 8.1 Normative References . . . . . . . . . . . . . . . . . . . 89
8.2 Informative References . . . . . . . . . . . . . . . . . . 89 8.2 Informative References . . . . . . . . . . . . . . . . . . 90
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 90 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 90
Intellectual Property and Copyright Statements . . . . . . . . 91 Intellectual Property and Copyright Statements . . . . . . . . 92
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing the In particular, it describes managed objects used for managing the
Protocol Independent Multicast (PIM) protocols (PIM-SM [RFC4601] and Protocol Independent Multicast (PIM) protocols (PIM-SM [RFC4601] and
BIDIR-PIM [I-D.ietf-pim-bidir]). BIDIR-PIM [I-D.ietf-pim-bidir]).
This document is part of work in progress to obsolete RFC 2934 This document is part of work in progress to obsolete RFC 2934
skipping to change at page 5, line 15 skipping to change at page 5, line 15
12. The PIM Group Mapping Table, which contains one row for each 12. The PIM Group Mapping Table, which contains one row for each
mapping from a multicast group address prefix to the PIM mode mapping from a multicast group address prefix to the PIM mode
and RP address to use for groups within that group prefix, and RP address to use for groups within that group prefix,
regardless of the source of the group mapping information. regardless of the source of the group mapping information.
13. The PIM Anycast-RP Set Table, which contains one row for each RP 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 within each Anycast-RP set of which the local router is a
member. member.
This MIB module uses textual conventions defined in the IF-MIB This MIB module uses textual conventions defined in the IF-MIB
[RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB. [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB
[RTPROTO].
4. Definitions 4. Definitions
PIM-STD-MIB DEFINITIONS ::= BEGIN PIM-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, MODULE-IDENTITY, OBJECT-TYPE, mib-2,
NOTIFICATION-TYPE, Unsigned32, NOTIFICATION-TYPE, Unsigned32,
Counter32, Gauge32, TimeTicks FROM SNMPv2-SMI Counter32, Counter64, Gauge32,
TimeTicks FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, TEXTUAL-CONVENTION,
RowStatus, TruthValue, RowStatus, TruthValue,
StorageType FROM SNMPv2-TC StorageType FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580]
InterfaceIndexOrZero, InterfaceIndexOrZero,
InterfaceIndex FROM IF-MIB InterfaceIndex FROM IF-MIB -- [RFC2863]
InetAddressType, InetAddressType,
InetAddressPrefixLength, InetAddressPrefixLength,
InetAddress, InetVersion FROM INET-ADDRESS-MIB InetAddress, InetVersion FROM INET-ADDRESS-MIB -- [RFC4001]
IANAipRouteProtocol FROM IANA-RTPROTO-MIB; IANAipRouteProtocol FROM IANA-RTPROTO-MIB; -- [RTPROTO]
pimStdMIB MODULE-IDENTITY pimStdMIB MODULE-IDENTITY
LAST-UPDATED "200611130000Z" -- 13 November 2006 LAST-UPDATED "200612130000Z" -- 13 December 2006
ORGANIZATION "IETF PIM Working Group" ORGANIZATION
"IETF Protocol Independent Multicast (PIM) Working Group"
CONTACT-INFO CONTACT-INFO
"Email: pim@ietf.org" "Email: pim@ietf.org
WG charter:
http://www.ietf.org/html.charters/pim-charter.html"
DESCRIPTION DESCRIPTION
"The MIB module for management of PIM routers. "The MIB module for management of PIM routers.
Copyright (C) The IETF Trust (2006). The initial version of Copyright (C) The IETF Trust (2006). This version of this
this MIB module was published in RFC yyyy; for full legal MIB module is part of RFC yyyy; see the RFC itself for full
notices see the RFC itself. Supplementary information may legal notices."
be available at:
http://www.ietf.org/copyrights/ianamib.html."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200611130000Z" -- 13 November 2006 REVISION "200612130000Z" -- 13 December 2006
DESCRIPTION "Initial version, published as RFC yyyy." DESCRIPTION "Initial version, published as RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this note -- RFC Ed.: replace XXX with IANA-assigned number & remove this note
-- --
-- Textual Conventions -- Textual Conventions
-- --
PimMode ::= TEXTUAL-CONVENTION PimMode ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 7, line 14 skipping to change at page 7, line 18
bsr(4) The PIM Bootstrap Router (BSR) mechanism. bsr(4) The PIM Bootstrap Router (BSR) mechanism.
autoRP(5) Cisco's Auto-RP mechanism. autoRP(5) Cisco's Auto-RP mechanism.
embedded(6) The Embedded-RP mechanism where the RP address embedded(6) The Embedded-RP mechanism where the RP address
is embedded in the multicast group address. is embedded in the multicast group address.
other(7) Any other mechanism." other(7) Any other mechanism."
REFERENCE "RFC 3956, I-D.ietf-pim-sm-bsr" REFERENCE "RFC 3596, RFC 3956 and I-D.ietf-pim-sm-bsr"
SYNTAX INTEGER { SYNTAX INTEGER {
fixed(1), fixed(1),
configRp(2), configRp(2),
configSsm(3), configSsm(3),
bsr(4), bsr(4),
autoRP(5), autoRP(5),
embedded(6), embedded(6),
other(7) other(7)
} }
-- --
-- Top-level structure -- Top-level structure
-- --
pimMIBObjects OBJECT IDENTIFIER ::= { pimStdMIB 1 } pimTraps OBJECT IDENTIFIER ::= { pimStdMIB 0 }
pimTraps OBJECT IDENTIFIER ::= { pimMIBObjects 0 } pim OBJECT IDENTIFIER ::= { pimStdMIB 1 }
pim OBJECT IDENTIFIER ::= { pimMIBObjects 1 }
pimKeepalivePeriod OBJECT-TYPE pimKeepalivePeriod OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The duration of the Keepalive Timer. This is the period "The duration of the Keepalive Timer. This is the period
during which the PIM router will maintain (S,G) state in the during which the PIM router will maintain (S,G) state in the
absence of explicit (S,G) local membership or (S,G) join absence of explicit (S,G) local membership or (S,G) join
skipping to change at page 9, line 18 skipping to change at page 9, line 22
pimSGRptIEntries OBJECT-TYPE pimSGRptIEntries OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of entries in the pimSGRptITable." "The number of entries in the pimSGRptITable."
::= { pim 21 } ::= { pim 21 }
pimOutAsserts OBJECT-TYPE pimOutAsserts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Asserts sent by this router." "The number of Asserts sent by this router."
REFERENCE "RFC 4601 section 4.6" REFERENCE "RFC 4601 section 4.6"
::= { pim 22 } ::= { pim 22 }
pimInAsserts OBJECT-TYPE pimInAsserts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Asserts received by this router. Asserts "The number of Asserts received by this router. Asserts
are multicast to all routers on a network. This counter is are multicast to all routers on a network. This counter is
incremented by all routers that receive an assert, not only incremented by all routers that receive an assert, not only
those routers that are contesting the assert." those routers that are contesting the assert."
REFERENCE "RFC 4601 section 4.6" REFERENCE "RFC 4601 section 4.6"
::= { pim 23 } ::= { pim 23 }
skipping to change at page 11, line 15 skipping to change at page 11, line 19
DEFVAL { 0 } DEFVAL { 0 }
::= { pim 29 } ::= { pim 29 }
pimNeighborLossCount OBJECT-TYPE pimNeighborLossCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of neighbor loss events that have occurred. "The number of neighbor loss events that have occurred.
This count is incremented when the neighbor timer expires, This counter is incremented when the neighbor timer expires,
and the router has no other neighbors on the same interface and the router has no other neighbors on the same interface
with the same IP version and a lower IP address than itself. with the same IP version and a lower IP address than itself.
This counter is incremented whenever a pimNeighborLoss trap This counter is incremented whenever a pimNeighborLoss trap
would be generated." would be generated."
REFERENCE "RFC 4601 section 4.3.2" REFERENCE "RFC 4601 section 4.3.2"
::= { pim 30 } ::= { pim 30 }
pimInvalidRegisterTrapPeriod OBJECT-TYPE pimInvalidRegisterTrapPeriod OBJECT-TYPE
SYNTAX Unsigned32 (10..65535) SYNTAX Unsigned32 (10..65535)
skipping to change at page 12, line 24 skipping to change at page 12, line 28
The active Group to RP mapping on this device is specified The active Group to RP mapping on this device is specified
by the object pimGroupMappingPimMode. If there is no such by the object pimGroupMappingPimMode. If there is no such
mapping, then the object pimGroupMappingPimMode is absent. mapping, then the object pimGroupMappingPimMode is absent.
The RP address contained in the invalid Register is The RP address contained in the invalid Register is
pimInvalidRegisterRp. pimInvalidRegisterRp.
Multicast data carried by invalid Register messages is Multicast data carried by invalid Register messages is
discarded. The discarded data is from a source directly discarded. The discarded data is from a source directly
connected to pimInvalidRegisterOrigin, and is addressed to connected to pimInvalidRegisterOrigin, and is addressed to
pimInvalidRegisterGroup." pimInvalidRegisterGroup."
REFERENCE "RFC 4601 section 4.4.2" REFERENCE "RFC 4601 section 4.4.2, RFC 3569 and
I-D.ietf-mboned-ip-mcast-mib ipMcastSsmRangeTable"
::= { pim 32 } ::= { pim 32 }
pimInvalidRegisterAddressType OBJECT-TYPE pimInvalidRegisterAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address type stored in pimInvalidRegisterOrigin, "The address type stored in pimInvalidRegisterOrigin,
pimInvalidRegisterGroup and pimInvalidRegisterRp. pimInvalidRegisterGroup and pimInvalidRegisterRp.
skipping to change at page 13, line 47 skipping to change at page 14, line 4
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of invalid PIM Join/Prune messages that have "The number of invalid PIM Join/Prune messages that have
been received by this device. been received by this device.
A PIM Join/Prune message is invalid if either A PIM Join/Prune message is invalid if either
o the Group to RP mapping specified by this message does not o the Group to RP mapping specified by this message does not
match the Group to RP mapping on this device, or match the Group to RP mapping on this device, or
o this device believes the group address to be within an o this device believes the group address to be within an
SSM address range, but this Join/Prune (*,G) or (S,G,rpt) SSM address range, but this Join/Prune (*,G) or (S,G,rpt)
implies ASM usage. implies ASM usage.
These conditions can occur transiently while RP mapping These conditions can occur transiently while RP mapping
changes propagate through the network. If this counter is changes propagate through the network. If this counter is
incremented repeatedly over several minutes, then there is a incremented repeatedly over several minutes, then there is a
persisting configuration error that requires correction. persisting configuration error that requires correction.
The active Group to RP mapping on this device is specified The active Group to RP mapping on this device is specified
by the object pimGroupMappingPimMode. If there is no such by the object pimGroupMappingPimMode. If there is no such
mapping, then the object pimGroupMappingPimMode is absent. mapping, then the object pimGroupMappingPimMode is absent.
The RP address contained in the invalid Join/Prune is The RP address contained in the invalid Join/Prune is
pimInvalidJoinPruneRp. pimInvalidJoinPruneRp.
Invalid Join/Prune messages are discarded. This may result Invalid Join/Prune messages are discarded. This may result
in loss of multicast data affecting listeners downstream of in loss of multicast data affecting listeners downstream of
pimInvalidJoinPruneOrigin, for multicast data addressed to pimInvalidJoinPruneOrigin, for multicast data addressed to
pimInvalidJoinPruneGroup." pimInvalidJoinPruneGroup."
REFERENCE "RFC 4601 section 4.5.2" REFERENCE "RFC 4601 section 4.5.2, RFC 3569 and
I-D.ietf-mboned-ip-mcast-mib ipMcastSsmRangeTable"
::= { pim 38 } ::= { pim 38 }
pimInvalidJoinPruneAddressType OBJECT-TYPE pimInvalidJoinPruneAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address type stored in pimInvalidJoinPruneOrigin, "The address type stored in pimInvalidJoinPruneOrigin,
pimInvalidJoinPruneGroup and pimInvalidJoinPruneRp. pimInvalidJoinPruneGroup and pimInvalidJoinPruneRp.
skipping to change at page 15, line 36 skipping to change at page 15, line 40
pimRPMappingChangeCount OBJECT-TYPE pimRPMappingChangeCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of changes to active RP mappings on this device. "The number of changes to active RP mappings on this device.
Information about active RP mappings is available in Information about active RP mappings is available in
pimGroupMappingTable. Only changes to active mappings cause pimGroupMappingTable. Only changes to active mappings cause
this count to be incremented. That is, changes that modify this counter to be incremented. That is, changes that
the pimGroupMappingEntry with the highest precedence for a modify the pimGroupMappingEntry with the highest precedence
group (lowest value of pimGroupMappingPrecedence). for a group (lowest value of pimGroupMappingPrecedence).
Such changes may result from manual configuration of this Such changes may result from manual configuration of this
device, or from automatic RP mapping discovery methods device, or from automatic RP mapping discovery methods
including the PIM Bootstrap Router (BSR) mechanism." including the PIM Bootstrap Router (BSR) mechanism."
REFERENCE "I-D.ietf-pim-sm-bsr" REFERENCE "I-D.ietf-pim-sm-bsr"
::= { pim 44 } ::= { pim 44 }
pimInterfaceElectionTrapPeriod OBJECT-TYPE pimInterfaceElectionTrapPeriod OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
UNITS "seconds" UNITS "seconds"
skipping to change at page 19, line 5 skipping to change at page 19, line 11
::= { pimInterfaceEntry 3 } ::= { pimInterfaceEntry 3 }
pimInterfaceAddress OBJECT-TYPE pimInterfaceAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (4|8|16|20)) SYNTAX InetAddress (SIZE (4|8|16|20))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The primary IP address of this router on this PIM "The primary IP address of this router on this PIM
interface. The InetAddressType is given by the interface. The InetAddressType is given by the
pimInterfaceAddressType object." pimInterfaceAddressType object."
REFERENCE "RFC 4601 sections 4.1.6, 4.3.1-4.3.4 and 4.5.1"
::= { pimInterfaceEntry 4 } ::= { pimInterfaceEntry 4 }
pimInterfaceGenerationIDValue OBJECT-TYPE pimInterfaceGenerationIDValue OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the Generation ID this router inserted in the "The value of the Generation ID this router inserted in the
last PIM Hello message it sent on this interface." last PIM Hello message it sent on this interface."
REFERENCE "RFC 4601 section 4.3.1" REFERENCE "RFC 4601 section 4.3.1"
skipping to change at page 22, line 19 skipping to change at page 22, line 26
SYNTAX Unsigned32 (0..32767) SYNTAX Unsigned32 (0..32767)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The expected propagation delay between PIM routers on this "The expected propagation delay between PIM routers on this
network or link. network or link.
This router inserts this value into the Propagation_Delay This router inserts this value into the Propagation_Delay
field of the LAN Prune Delay option in the PIM Hello field of the LAN Prune Delay option in the PIM Hello
messages sent on this interface. Implementations should messages sent on this interface. Implementations SHOULD
enforce a lower bound on the permitted values for this enforce a lower bound on the permitted values for this
object to allow for scheduling and processing delays within object to allow for scheduling and processing delays within
the local router." the local router."
DEFVAL { 500 } DEFVAL { 500 }
::= { pimInterfaceEntry 16 } ::= { pimInterfaceEntry 16 }
pimInterfaceOverrideInterval OBJECT-TYPE pimInterfaceOverrideInterval OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 24, line 20 skipping to change at page 24, line 27
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether this interface is a 'stub interface'. If this "Whether this interface is a 'stub interface'. If this
object is set to TRUE, then no PIM packets are sent out this object is set to TRUE, then no PIM packets are sent out this
interface, and any received PIM packets are ignored. interface, and any received PIM packets are ignored.
Setting this object to TRUE is a security measure for Setting this object to TRUE is a security measure for
interfaces towards untrusted hosts. This allows an interfaces towards untrusted hosts. This allows an
interface to be configured for use with IGMP or MGMD, while interface to be configured for use with IGMP (Internet Group
also protecting the PIM router from forged PIM messages on Management Protocol) or MLD (Multicast Listener Discovery)
the interface. only, which protects the PIM router from forged PIM messages
on the interface.
To communicate with other PIM routers using this interface, To communicate with other PIM routers using this interface,
this object must remain set to FALSE. this object must remain set to FALSE.
Changing the value of this object while the interface is Changing the value of this object while the interface is
operational causes the interface to be deactivated and operational causes the interface to be deactivated and
then reactivated." then reactivated."
REFERENCE "RFC 3376, RFC 3810"
DEFVAL { false } DEFVAL { false }
::= { pimInterfaceEntry 23 } ::= { pimInterfaceEntry 23 }
pimInterfacePruneLimitInterval OBJECT-TYPE pimInterfacePruneLimitInterval OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum interval that must transpire between two "The minimum interval that must transpire between two
skipping to change at page 38, line 8 skipping to change at page 38, line 16
pimStarGILocalMembership OBJECT-TYPE pimStarGILocalMembership OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether the local router has (*,G) local membership on this "Whether the local router has (*,G) local membership on this
interface (resulting from a mechanism such as IGMP or MLD). interface (resulting from a mechanism such as IGMP or MLD).
This corresponds to local_receiver_include(*,G,I) in the This corresponds to local_receiver_include(*,G,I) in the
PIM-SM specification." PIM-SM specification."
REFERENCE "RFC 4601 section 4.1.6" REFERENCE "RFC 3376, RFC 3810, RFC 4601 section 4.1.6"
::= { pimStarGIEntry 3 } ::= { pimStarGIEntry 3 }
pimStarGIJoinPruneState OBJECT-TYPE pimStarGIJoinPruneState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noInfo (1), noInfo (1),
join (2), join (2),
prunePending (3) prunePending (3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 42, line 32 skipping to change at page 42, line 39
::= { pimSGEntry 4 } ::= { pimSGEntry 4 }
pimSGPimMode OBJECT-TYPE pimSGPimMode OBJECT-TYPE
SYNTAX PimMode { ssm(2), asm(3) } SYNTAX PimMode { ssm(2), asm(3) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether pimSGGrpAddress is an SSM (Source Specific "Whether pimSGGrpAddress is an SSM (Source Specific
Multicast, used with PIM-SM) or ASM (Any Source Multicast, Multicast, used with PIM-SM) or ASM (Any Source Multicast,
used with PIM-SM) group." used with PIM-SM) group."
REFERENCE "RFC 4601 section 4.5.2, RFC 3569 and
I-D.ietf-mboned-ip-mcast-mib ipMcastSsmRangeTable"
::= { pimSGEntry 5 } ::= { pimSGEntry 5 }
pimSGUpstreamJoinState OBJECT-TYPE pimSGUpstreamJoinState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notJoined (1), notJoined (1),
joined (2) joined (2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 49, line 33 skipping to change at page 49, line 43
DESCRIPTION DESCRIPTION
"The time since this entry was created by the local router." "The time since this entry was created by the local router."
::= { pimSGIEntry 2 } ::= { pimSGIEntry 2 }
pimSGILocalMembership OBJECT-TYPE pimSGILocalMembership OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether the local router has (S,G) local membership on this "Whether the local router has (S,G) local membership on this
interface (resulting from a mechanism such as IGMPv3 or interface (resulting from a mechanism such as IGMP or MLD).
MLDv2). This corresponds to local_receiver_include(S,G,I) This corresponds to local_receiver_include(S,G,I) in the
in the PIM-SM specification." PIM-SM specification."
REFERENCE "RFC 4601 section 4.1.6, 4.6.1 and 4.6.2" REFERENCE "RFC 3376, RFC 3810, RFC 4601 sections 4.1.6, 4.6.1 and
4.6.2"
::= { pimSGIEntry 3 } ::= { pimSGIEntry 3 }
pimSGIJoinPruneState OBJECT-TYPE pimSGIJoinPruneState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noInfo (1), noInfo (1),
join (2), join (2),
prunePending (3) prunePending (3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 54, line 50 skipping to change at page 55, line 12
"The time since this entry was created by the local router." "The time since this entry was created by the local router."
::= { pimSGRptIEntry 2 } ::= { pimSGRptIEntry 2 }
pimSGRptILocalMembership OBJECT-TYPE pimSGRptILocalMembership OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether the local router has both (*,G) include local "Whether the local router has both (*,G) include local
membership and (S,G) exclude local membership on this membership and (S,G) exclude local membership on this
interface (resulting from a mechanism such as IGMPv3 or interface (resulting from a mechanism such as IGMP or MLD).
MLDv2). This corresponds to local_receiver_exclude(S,G,I) This corresponds to local_receiver_exclude(S,G,I) in the
in the PIM-SM specification." PIM-SM specification."
REFERENCE "RFC 3376, RFC 3810, RFC 4601 section 4.1.6"
REFERENCE "RFC 4601 section 4.1.6"
::= { pimSGRptIEntry 3 } ::= { pimSGRptIEntry 3 }
pimSGRptIJoinPruneState OBJECT-TYPE pimSGRptIJoinPruneState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noInfo (1), noInfo (1),
prune (2), prune (2),
prunePending (3) prunePending (3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 60, line 51 skipping to change at page 61, line 13
pimStaticRPPimMode OBJECT-TYPE pimStaticRPPimMode OBJECT-TYPE
SYNTAX PimMode { ssm(2), asm(3), bidir(4) } SYNTAX PimMode { ssm(2), asm(3), bidir(4) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PIM mode to be used for groups in this group prefix. "The PIM mode to be used for groups in this group prefix.
If this object is set to ssm(2), then pimStaticRPRPAddress If this object is set to ssm(2), then pimStaticRPRPAddress
must be set to zero. No RP operations are ever possible for must be set to zero. No RP operations are ever possible for
PIM Mode SSM." PIM Mode SSM."
REFERENCE "RFC 4601 section 3.7, RFC 3569 and
I-D.ietf-mboned-ip-mcast-mib ipMcastSsmRangeTable"
DEFVAL { asm } DEFVAL { asm }
::= { pimStaticRPEntry 5 } ::= { pimStaticRPEntry 5 }
pimStaticRPOverrideDynamic OBJECT-TYPE pimStaticRPOverrideDynamic OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether this static RP configuration overrides RP "Whether this static RP configuration overrides RP
information learned dynamically for groups in this group information learned dynamically for groups in this group
skipping to change at page 61, line 28 skipping to change at page 61, line 40
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value for pimGroupMappingPrecedence to be used for this "The value for pimGroupMappingPrecedence to be used for this
static RP configuration. This allows fine control over static RP configuration. This allows fine control over
which configuration is overridden by this static which configuration is overridden by this static
configuration. configuration.
If this object is present, then pimStaticRPOverrideDynamic If this object is present, then pimStaticRPOverrideDynamic
is ignored. has no effect.
The absolute values of this object have a significance only The absolute values of this object have a significance only
on the local router and do not need to be coordinated with on the local router and do not need to be coordinated with
other routers. A setting of this object may have different other routers. A setting of this object may have different
effects when applied to other routers. effects when applied to other routers.
Do not use this object unless fine control of static RP Do not use this object unless fine control of static RP
behavior on the local router is required." behavior on the local router is required."
::= { pimStaticRPEntry 7 } ::= { pimStaticRPEntry 7 }
pimStaticRPRowStatus OBJECT-TYPE pimStaticRPRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which rows in this table can "The status of this row, by which rows in this table can
be created and destroyed. be created and destroyed.
This status object cannot be set to active(1) before valid This status object cannot be set to active(1) before a valid
values have been written to pimStaticRPRPAddress. value has been written to pimStaticRPRPAddress.
All writeable objects in this entry can be modified when the All writeable objects in this entry can be modified when the
status of this entry is active(1)." status of this entry is active(1)."
::= { pimStaticRPEntry 8 } ::= { pimStaticRPEntry 8 }
pimStaticRPStorageType OBJECT-TYPE pimStaticRPStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this row. Rows having the value "The storage type for this row. Rows having the value
'permanent' need not allow write-access to any columnar 'permanent' need not allow write-access to any columnar
objects in the row." objects in the row."
skipping to change at page 62, line 29 skipping to change at page 62, line 40
-- The PIM Anycast-RP Set Table -- The PIM Anycast-RP Set Table
-- --
pimAnycastRPSetTable OBJECT-TYPE pimAnycastRPSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF PimAnycastRPSetEntry SYNTAX SEQUENCE OF PimAnycastRPSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table is used to create and manage Anycast-RP via PIM "This table is used to create and manage Anycast-RP via PIM
Register messages, as opposed to via other protocols such as Register messages, as opposed to via other protocols such as
MSDP. MSDP (Multicast Source Discovery Protocol).
Entries must be configured in this table if and only if the Entries must be configured in this table if and only if the
local router is a member of one or more Anycast-RP sets, local router is a member of one or more Anycast-RP sets,
that is, one or more Anycast-RP addresses are assigned to that is, one or more Anycast-RP addresses are assigned to
the local router. Note that if using static RP the local router. Note that if using static RP
configuration, this is in addition to, not instead of, the configuration, this is in addition to, not instead of, the
pimStaticRPTable entries that must be configured for the pimStaticRPTable entries that must be configured for the
Anycast-RPs. Anycast-RPs.
The set of rows with the same values of both The set of rows with the same values of both
pimAnycastRPSetAddressType and pimAnycastRPSetAnycastAddress pimAnycastRPSetAddressType and pimAnycastRPSetAnycastAddress
corresponds to the Anycast-RP set for that Anycast-RP corresponds to the Anycast-RP set for that Anycast-RP
address. address.
When an Anycast-RP set configuration is active, one entry When an Anycast-RP set configuration is active, one entry
per pimAnycastRPSetAnycastAddress corresponds to the local per pimAnycastRPSetAnycastAddress corresponds to the local
router. The local router is identified by the router. The local router is identified by the
pimAnycastRpSetLocalRouter object. That entry determines pimAnycastRpSetLocalRouter object. That entry determines
the source address used by the local router when forwarding the source address used by the local router when forwarding
PIM Register messages within the Anycast-RP set." PIM Register messages within the Anycast-RP set."
REFERENCE "RFC 4610" REFERENCE "RFC 4610, RFC 3618"
::= { pim 12 } ::= { pim 12 }
pimAnycastRPSetEntry OBJECT-TYPE pimAnycastRPSetEntry OBJECT-TYPE
SYNTAX PimAnycastRPSetEntry SYNTAX PimAnycastRPSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry corresponds to a single router within a particular "An entry corresponds to a single router within a particular
Anycast-RP set. This entry is preserved on agent restart." Anycast-RP set. This entry is preserved on agent restart."
INDEX { pimAnycastRPSetAddressType, INDEX { pimAnycastRPSetAddressType,
skipping to change at page 64, line 24 skipping to change at page 64, line 35
DESCRIPTION DESCRIPTION
"Whether this entry corresponds to the local router." "Whether this entry corresponds to the local router."
::= { pimAnycastRPSetEntry 4 } ::= { pimAnycastRPSetEntry 4 }
pimAnycastRPSetRowStatus OBJECT-TYPE pimAnycastRPSetRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which rows in this table can "The status of this row, by which rows in this table can
be created and destroyed. There are no other other be created and destroyed.
writeable columnar objects in this entry."
This status object can be set to active(1) without setting
any other columnar objects in this entry.
All writeable objects in this entry can be modified when the
status of this entry is active(1)."
::= { pimAnycastRPSetEntry 5 } ::= { pimAnycastRPSetEntry 5 }
pimAnycastRPSetStorageType OBJECT-TYPE pimAnycastRPSetStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this row. Rows having the value "The storage type for this row. Rows having the value
'permanent' need not allow write-access to any columnar 'permanent' need not allow write-access to any columnar
objects in the row." objects in the row."
skipping to change at page 80, line 16 skipping to change at page 80, line 32
pimLastAssertInterface, pimLastAssertInterface,
pimLastAssertGroupAddressType, pimLastAssertGroupAddressType,
pimLastAssertGroupAddress, pimLastAssertGroupAddress,
pimLastAssertSourceAddressType, pimLastAssertSourceAddressType,
pimLastAssertSourceAddress, pimLastAssertSourceAddress,
pimNeighborLossTrapPeriod, pimNeighborLossTrapPeriod,
pimNeighborLossCount pimNeighborLossCount
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects providing additonal diagnostics related to a PIM "Objects providing additional diagnostics related to a PIM
router." router."
::= { pimMIBGroups 13 } ::= { pimMIBGroups 13 }
pimDmGroup OBJECT-GROUP pimDmGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pimRefreshInterval, pimRefreshInterval,
pimInterfacePruneLimitInterval, pimInterfacePruneLimitInterval,
pimInterfaceGraftRetryInterval, pimInterfaceGraftRetryInterval,
pimInterfaceSRPriorityEnabled, pimInterfaceSRPriorityEnabled,
pimNeighborSRCapable, pimNeighborSRCapable,
skipping to change at page 81, line 4 skipping to change at page 81, line 18
pimDeviceStorageGroup OBJECT-GROUP pimDeviceStorageGroup OBJECT-GROUP
OBJECTS { pimDeviceConfigStorageType OBJECTS { pimDeviceConfigStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that specifies the volatility of global PIM "An object that specifies the volatility of global PIM
configuration settings on this device." configuration settings on this device."
::= { pimMIBGroups 15 } ::= { pimMIBGroups 15 }
END END
5. Security Considerations 5. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
The following tables and objects could be employed to modify The following tables and objects could be employed to modify
multicast routing behavior in a way that prevents, disrupts, or multicast routing behavior in a way that prevents, disrupts, or
subverts services provided by the network, including (but not limited subverts services provided by the network, including (but not limited
to) multicast data traffic delivery. For example, attacks can be to) multicast data traffic delivery. For example, attacks can be
envisaged that would pass nominated multicast data streams through a envisaged that would pass nominated multicast data streams through a
nominated location, without the sources or listeners becoming aware nominated location, without the sources or listeners becoming aware
of this subversion. of this subversion.
pimKeepalivePeriod pimRegisterSuppressionTime pimKeepalivePeriod
pimRegisterSuppressionTime
pimNeighborLossTrapPeriod pimNeighborLossTrapPeriod
pimInvalidRegisterTrapPeriod pimInvalidRegisterTrapPeriod
pimInvalidJoinPruneTrapPeriod pimRPMappingTrapPeriod pimInvalidJoinPruneTrapPeriod
pimInterfaceElectionTrapPeriod pimRefreshInterval pimRPMappingTrapPeriod
pimInterfaceTable pimInterfaceEntry pimInterfaceElectionTrapPeriod
pimInterfaceIfIndex pimInterfaceIPVersion pimRefreshInterval
pimInterfaceTable
pimInterfaceEntry
pimInterfaceIfIndex
pimInterfaceIPVersion
pimInterfaceHelloInterval pimInterfaceHelloInterval
pimInterfaceTrigHelloInterval pimInterfaceTrigHelloInterval
pimInterfaceJoinPruneInterval pimInterfaceJoinPruneInterval
pimInterfaceDFElectionRobustness pimInterfaceHelloHoldtime pimInterfaceDFElectionRobustness
pimInterfaceHelloHoldtime
pimInterfaceJoinPruneHoldtime pimInterfaceJoinPruneHoldtime
pimInterfacePropagationDelay pimInterfacePropagationDelay
pimInterfaceOverrideInterval pimInterfaceDRPriority pimInterfaceOverrideInterval
pimInterfaceDomainBorder pimInterfaceStatus pimInterfaceDRPriority
pimInterfaceDomainBorder
pimInterfaceStatus
pimInterfaceStubInterface pimInterfaceStubInterface
pimInterfacePruneLimitInterval pimStaticRPTable pimInterfacePruneLimitInterval
pimStaticRPEntry pimStaticRPAddressType pimStaticRPTable
pimStaticRPGrpAddress pimStaticRPGrpPrefixLength pimStaticRPEntry
pimStaticRPRPAddress pimStaticRPPimMode pimStaticRPAddressType
pimStaticRPOverrideDynamic pimStaticRPRowStatus pimStaticRPGrpAddress
pimStaticRPPrecedence pimAnycastRPSetTable pimStaticRPGrpPrefixLength
pimAnycastRPSetEntry pimAnycastRPSetAddressType pimStaticRPRPAddress
pimStaticRPPimMode
pimStaticRPOverrideDynamic
pimStaticRPRowStatus
pimStaticRPPrecedence
pimAnycastRPSetTable
pimAnycastRPSetEntry
pimAnycastRPSetAddressType
pimAnycastRPSetAnycastAddress pimAnycastRPSetAnycastAddress
pimAnycastRPSetRouterAddress pimAnycastRPSetRouterAddress
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
skipping to change at page 86, line 49 skipping to change at page 87, line 31
pimGroupMappingOrigin pimGroupMappingOrigin
pimGroupMappingAddressType pimGroupMappingAddressType
pimGroupMappingGrpAddress pimGroupMappingGrpAddress
pimGroupMappingGrpPrefixLength pimGroupMappingGrpPrefixLength
pimGroupMappingRPAddress pimGroupMappingRPAddress
pimGroupMappingPimMode pimGroupMappingPimMode
pimGroupMappingPrecedence pimGroupMappingPrecedence
There is also a specific danger arising from the notification There is also a specific danger arising from the notification
pimInvalidRegister. This is originated by devices that receive an pimInvalidRegister. This is originated by devices that receive an
incorrect unicast-encapsulted multicast data packet, which poses a incorrect unicast-encapsulated multicast data packet, which poses a
clear danger of propagating a DoS (Denial of Service) attack from the clear danger of propagating a DoS (Denial of Service) attack from the
data or control plane to the network management plane. The following data or control plane to the network management plane. The following
steps are taken to guard against this. steps are taken to guard against this.
1. The notification is disabled by default. The writeable field 1. The notification is disabled by default. The writeable field
pimInvalidRegisterTrapPeriod must be set in order to enable it. pimInvalidRegisterTrapPeriod must be set in order to enable it.
2. The syntax of pimInvalidRegisterTrapPeriod prevents any given 2. The syntax of pimInvalidRegisterTrapPeriod prevents any given
device from originating the notification more frequently than device from originating the notification more frequently than
once every 10 seconds. once every 10 seconds.
skipping to change at page 87, line 43 skipping to change at page 88, line 26
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
6. IANA Considerations 6. IANA Considerations
PIM-STD-MIB should be rooted under the mib-2 subtree. IANA is The MIB module in this document uses the following IANA-assigned
requested to assign { mib-2 XXX } to the PIM-STD-MIB module specified OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
in this document.
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
pimStdMIB { mib-2 XXX }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove
this note.
7. Acknowledgements 7. Acknowledgements
This MIB module is based on the original work in RFC 2934 [RFC2934] This MIB module is based on the original work in RFC 2934 [RFC2934]
by K. McCloghrie, D. Farinacci, D. Thaler and W. Fenner and has been by K. McCloghrie, D. Farinacci, D. Thaler and W. Fenner and has been
updated based on feedback from the IETF's Protocol Independent updated based on feedback from the IETF's Protocol Independent
Multicast (PIM) Working Group. Multicast (PIM) Working Group.
Jonathan Nicholas was the editor of early versions of this document, Jonathan Nicholas was the editor of early versions of this document,
and contributed the objects for management of PIM-DM. and contributed the objects for management of PIM-DM.
skipping to change at page 88, line 34 skipping to change at page 89, line 27
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3569] Bhattacharyya, S., "An Overview of Source-Specific
Multicast (SSM)", RFC 3569, July 2003.
[RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous
Point (RP) Address in an IPv6 Multicast Address",
RFC 3956, November 2004.
[RFC3973] Adams, A., Nicholas, J., and W. Siadak, "Protocol [RFC3973] Adams, A., Nicholas, J., and W. Siadak, "Protocol
Independent Multicast - Dense Mode (PIM-DM): Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol
Specification (Revised)", RFC 3973, January 2005. Specification (Revised)", RFC 3973, January 2005.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM): "Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, Protocol Specification (Revised)", RFC 4601, August 2006.
draft-ietf-pim-sm-v2-new-12 (work in progress), Current
Status PROPOSED STANDARD, August 2006.
[RFC4610] Farinacci, D. and Y. Cai, "Anycast-RP Using Protocol [RFC4610] Farinacci, D. and Y. Cai, "Anycast-RP Using Protocol
Independent Multicast (PIM)", RFC 4610, Independent Multicast (PIM)", RFC 4610, August 2006.
draft-ietf-pim-anycast-rp-07 (work in progress), Current
Status PROPOSED STANDARD, August 2006. [RTPROTO] IANA, "IP Route Protocol MIB",
http://www.iana.org/assignments/ianaiprouteprotocol-mib,
September 2000.
[I-D.ietf-pim-bidir] [I-D.ietf-pim-bidir]
Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
"Bi-directional Protocol Independent Multicast (BIDIR- "Bi-directional Protocol Independent Multicast (BIDIR-
PIM)", draft-ietf-pim-bidir-08 (work in progress), PIM)", draft-ietf-pim-bidir-08 (work in progress),
October 2005. October 2005.
[I-D.ietf-pim-sm-bsr] [I-D.ietf-pim-sm-bsr]
Bhaskar, N., "Bootstrap Router (BSR) Mechanism for PIM", Bhaskar, N., "Bootstrap Router (BSR) Mechanism for PIM",
draft-ietf-pim-sm-bsr-08 (work in progress), draft-ietf-pim-sm-bsr-08 (work in progress), June 2006.
June 2006.
[I-D.ietf-mboned-ip-mcast-mib] [I-D.ietf-mboned-ip-mcast-mib]
McWalter, D., "IP Multicast MIB", McWalter, D., "IP Multicast MIB",
draft-ietf-mboned-ip-mcast-mib-04 (work in progress), draft-ietf-mboned-ip-mcast-mib-04 (work in progress),
November 2006. November 2006.
8.2 Informative References 8.2 Informative References
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4
Multicast Routing MIB", RFC 2932, October 2000. Multicast Routing MIB", RFC 2932, October 2000.
[RFC2934] McCloghrie, K., Farinacci, D., Thaler, D., and B. Fenner, [RFC2934] McCloghrie, K., Farinacci, D., Thaler, D., and B. Fenner,
"Protocol Independent Multicast MIB for IPv4", RFC 2934, "Protocol Independent Multicast MIB for IPv4", RFC 2934,
October 2000. October 2000.
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version
3", RFC 3376, Updated by RFC4604, October 2002.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC3692] Narten, T., "Assigning Experimental and Testing Numbers [RFC3569] Bhattacharyya, S., "An Overview of Source-Specific
Considered Useful", BCP 82, RFC 3692, Multicast (SSM)", RFC 3569, July 2003.
draft-narten-iana-experimental-allocations-05 (work in
progress), Current Status BEST CURRENT PRACTICE, [RFC3618] Fenner, B. and D. Meyer, "Multicast Source Discovery
January 2004. Protocol (MSDP)", RFC 3618, October 2003.
[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery
Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
Authors' Addresses Authors' Addresses
Raghava Sivaramu Raghava Sivaramu
Cisco Systems Cisco Systems
425 E. Tasman Drive 425 E. Tasman Drive
San Jose CA 95134 San Jose CA 95134
USA USA
Email: raghava@cisco.com Email: raghava@cisco.com
 End of changes. 59 change blocks. 
109 lines changed or deleted 145 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/