IDMR Working Group Keith McCloghrie
INTERNET-DRAFT Dino Farinacci
Expires January 1999 cisco Systems
Dave Thaler
Microsoft
28 July 1998
Protocol Independent Multicast MIB<draft-ietf-idmr-pim-mib-05.txt>
Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working
documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as ``work in progress.''
Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved.
1. Introduction
This memo defines an experimental 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) protocol
[16,17,18,19]. This MIB module is applicable to IP multicast routers
which implement PIM.

Draft PIM MIB July 1998
2. Revision History
A record of changes which will be removed before publication.
28 July 1998
(1) added sparseDense as a legal value for pimInterfaceMode for
backwards compatability with PIMv1 routers which can do both modes
on the same interface.
(2) filled in Security Considerations, added copyright, updated SNMP
boilerplate, and updated references
20 November 1997
(1) undeprecated pimInterfaceMode since ipMRouteInterfaceProtocol was
changed to read-only.
(2) added pimRPSetComponent as an index to the RP-Set Table.
25 March
(1) deprecated pimInterfaceMode, which is obsoleted by
ipMRouteInterfaceProtocol in the IP Multicast MIB.
(2) deprecated pimNeighborMode (to retain support for PIM version 1).
(3) moved pimCandidateBSRPreference to the PIM Interface Table and
renamed it pimInterfaceCBSRPreference.
(4) moved pimBSRAddress, pimBSRExpiryTime, and pimCandidateRPHoldTime
to the new PIM Component Table, to manage border routers connected
to multiple PIM-SM domains.
(5) renamed pimMessageInterval to pimJoinPruneInterval and
pimInterfaceQueryInterval to pimInterfaceHelloInterval.
(6) added pimInterfaceJoinPruneInterval.
(7) added pimRPSetComponent as an INDEX in the PIM RP-Set Table
9 June:
(1) added pimRPSetTable and pimCandidateRPTable.
Expires January 1999 [Page 2]

Draft PIM MIB July 1998
(2) deprecated pimRPTable (to retain support for PIM version 1).
(3) removed pimGroupTable.
(4) added pimBSRAddress, pimBSRExpiryTime, pimCandidateBSRPreference
and pimCandidateRPHoldTime.
4 November:
(1) changed the PIM Group table to hold information common to all RPs
of a group.
(2) added the PIM RP table with each entry specific to an RP of a
group.
(3) added pimNeighborMode
(4) modified the pimGroupTable to be indexed by pimGroupAddress and
pimGroupRP, in order to allow for multiple RPs per group.
15 July - initial version.3. The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2271 [1].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in RFC1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called
SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].
Expires January 1999 [Page 3]

Draft PIM MIB July 1998
o Protocol operations for accessing management information. The first
set of protocol operations and associated PDU formats is described
in RFC 1157 [8]. A second set of protocol operations and associated
PDU formats is described in RFC 1905 [13].
o A set of fundamental applications described in RFC 2273 [14] and
the view-based access control mechanism described in RFC 2275 [15].
Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined
using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB
conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
3.1. Object Definitions
Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined
using the subset of Abstract Syntax Notation One (ASN.1) defined in the
SMI. In particular, each object type is named by an OBJECT IDENTIFIER,
an administratively assigned name. The object type together with an
object instance serves to uniquely identify a specific instantiation of
the object. For human convenience, we often use a textual string,
termed the descriptor, to refer to the object type.
4. Overview
This MIB module contains one scalar and six tables. The tables are:
(1) the PIM Interface Table which contains one row for each of the
router's PIM interfaces;
(2) the PIM Neighbor Table which contains one row for each of the
router's PIM neighbors; and
Expires January 1999 [Page 4]

Draft PIM MIB July 1998
(3) the PIM RP-Set Table which contains the PIM (version 2) information
for sets of candidate Rendezvous Points (RPs) for IP multicast
group addresses with particular address prefixes.
(4) the PIM Candidate-RP Table which contains the IP multicast groups
for which the local router is to advertise itself as a Candidate-
RP. If this table is empty, then the local router advertises
itself as a Candidate-RP for all groups.
(5) the (deprecated) PIM RP Table which contains the PIM (version 1)
information for IP multicast groups which is common to all RPs of a
group;
(6) the PIM Component Table which contains one row for each of the PIM
domains to which the router is connected.
Expires January 1999 [Page 5]

Draft PIM MIB July 1998
::= { pimRPSetEntry 4 }
pimRPSetExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum time remaining before the Candidate-RP will be
declared down. If the local router is not the BSR, this
value is 0."
::= { pimRPSetEntry 5 }
pimRPSetComponent OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A number uniquely identifying the component. Each protocol
instance connected to a separate domain should have a
different index value."
::= { pimRPSetEntry 6 }
-- The PIM Candidate-RP Table
pimCandidateRPTable OBJECT-TYPE
SYNTAX SEQUENCE OF PimCandidateRPEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the IP multicast groups for
which the local router is to advertise itself as a
Candidate-RP when the value of pimCandidateRPHoldTime is
non-zero. If this table is empty, then the local router
will advertise itself as a Candidate-RP for all groups
(providing the value of pimCandidateRPHoldTime is non-
zero)."
::= { pim 11 }
pimCandidateRPEntry OBJECT-TYPE
SYNTAX PimCandidateRPEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the pimCandidateRPTable."
Expires January 1999 [Page 15]

Draft PIM MIB July 1998
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of the bootstrap router (BSR) for the local
PIM region."
::= { pimComponentEntry 2 }
pimComponentBSRExpiryTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum time remaining before the bootstrap router in
the local domain will be declared down. For candidate BSRs,
this is the time until the component sends an RP-Set
message. For other routers, this is the time until it may
accept an RP-Set message from a lower candidate BSR."
::= { pimComponentEntry 3 }
pimComponentCRPHoldTime OBJECT-TYPE
SYNTAX Integer32 (0..255)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The holdtime of the component when it is a candidate RP in
the local domain. The value of 0 is used to indicate that
the local system is not a Candidate-RP."
DEFVAL { 0 }
::= { pimComponentEntry 4 }
pimComponentStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this entry. Creating the entry creates
another protocol instance; destroying the entry disables a
protocol instance."
::= { pimComponentEntry 5 }
Expires January 1999 [Page 18]

Draft PIM MIB July 19986. Security Considerations
This MIB contains readable objects whose values provide information
related to multicast routing, including information on the network
topology. There are also a number of objects that have a MAX-ACCESS
clause of read-write and/or read-create, which allow an administrator to
configure PIM in the router.
While unauthorized access to the readable objects is relatively
innocuous, unauthorized access to the write-able objects could cause a
denial of service. Hence, the support for SET operations in a non-
secure environment without proper protection can have a negative effect
on network operations.
SNMPv1 by itself is such an insecure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and SET
(change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the
User-based Security Model RFC 2274 [12] and the View-based Access
Control Model RFC 2275 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity
giving access to this MIB, is properly configured to give access to
those objects only to those principals (users) that have legitimate
rights to access them.
7. Acknowledgements
This MIB module has been updated based on feedback from the IETF's
Inter-Domain Multicast Routing (IDMR) Working Group.
8. Authors' Addresses
Keith McCloghrie
cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
Phone: +1 408 526 5260
Expires January 1999 [Page 22]

Draft PIM MIB July 1998
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., January 1998.
[16] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and
L. Wei, "Protocol Independent Multicast (PIM): Motivation and
Architecture", January 1995.
[17] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and
L. Wei, "Protocol Independent Multicast (PIM): Protocol
Specification", January 1995.
[18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S.,
Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei,
"Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol
Specification", RFC 2362, June 1998.
[19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A.,
and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode
Specification". May 1997.
10. Full Copyright Statement
Copyright (C) The Internet Society (1998). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or
assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
Expires January 1999 [Page 25]