< draft-ietf-pim-mib-v2-04.txt		draft-ietf-pim-mib-v2-05.txt >
	PIM WG R. Sivaramu		PIM WG R. Sivaramu
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Expires: April 7, 2006 J. Lingard		Expires: July 28, 2006 J. Lingard
	D. McWalter		D. McWalter
	Data Connection Ltd		Data Connection Ltd
	B. Joshi		B. Joshi
	Infosys Technologies Ltd		Infosys Technologies Ltd
	October 4, 2005		January 24, 2006
	Protocol Independent Multicast MIB		Protocol Independent Multicast MIB
	draft-ietf-pim-mib-v2-04.txt		draft-ietf-pim-mib-v2-05.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 April 7, 2006.		This Internet-Draft will expire on July 28, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2005).		Copyright (C) The Internet Society (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 and BIDIR-
	PIM). This document is part of work in progress to obsolete RFC		PIM). 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 . . . . . . . . . . . . . . . . . . . 68		5. Security Considerations . . . . . . . . . . . . . . . . . . . 75
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 74		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 81
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 74		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 81
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 74		8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 82
	8.1 Normative References . . . . . . . . . . . . . . . . . . . 74		8.1 Normative References . . . . . . . . . . . . . . . . . . . 82
	8.2 Informative References . . . . . . . . . . . . . . . . . . 75		8.2 Informative References . . . . . . . . . . . . . . . . . . 83
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 76		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 84
	Intellectual Property and Copyright Statements . . . . . . . . 77		Intellectual Property and Copyright Statements . . . . . . . . 85
	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 [I-D.ietf-pim-		Protocol Independent Multicast (PIM) protocols (PIM-SM [I-D.ietf-pim-
	sm-v2-new] and BIDIR-PIM [I-D.ietf-pim-bidir]).		sm-v2-new] and 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
	[RFC2934]. RFC 2934 defined an experimental MIB module for managing		[RFC2934]. RFC 2934 defined an experimental MIB module for managing
	the PIM protocols. The MIB module defined by this document is a re-		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		working of the MIB module from RFC 2934, with major changes that
	include the following.		include the following.
	o This MIB module is independent of IP version, whereas RFC 2934		o This MIB module is independent of IP version, whereas RFC 2934
	only supported IPv4.		only supported IPv4.
	o This MIB module includes support for managing BIDIR-PIM.		o This MIB module includes support for managing BIDIR-PIM.
	o This MIB module does not include support for managing PIM-DM.		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 include support for managing PIM-SM v1.
	o This MIB module does not depend on the IPv4 Multicast Routing MIB		o This MIB module does not depend on the IPv4 Multicast Routing MIB
	defined in RFC 2932 [RFC2932].		defined in RFC 2932 [RFC2932].
	o This MIB module includes support for configuring static RPs.		o This MIB module includes support for configuring static RPs.
	o This MIB module includes support for configuring anycast RPs		o This MIB module includes support for configuring anycast RPs
	[I-D.ietf-pim-anycast-rp]>.		[I-D.ietf-pim-anycast-rp]>.
	skipping to change at page 5, line 20 ¶		skipping to change at page 5, line 23 ¶
	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.
	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,		NOTIFICATION-TYPE, Unsigned32,
	Unsigned32, Gauge32, TimeTicks FROM SNMPv2-SMI		Counter32, Gauge32, TimeTicks FROM SNMPv2-SMI
	TEXTUAL-CONVENTION,		TEXTUAL-CONVENTION,
	RowStatus, TruthValue FROM SNMPv2-TC		RowStatus, TruthValue FROM SNMPv2-TC
	MODULE-COMPLIANCE, OBJECT-GROUP,		MODULE-COMPLIANCE, OBJECT-GROUP,
	NOTIFICATION-GROUP FROM SNMPv2-CONF		NOTIFICATION-GROUP FROM SNMPv2-CONF
	InterfaceIndexOrZero,		InterfaceIndexOrZero,
	InterfaceIndex FROM IF-MIB		InterfaceIndex FROM IF-MIB
	InetAddressType,		InetAddressType,
	InetAddressPrefixLength,		InetAddressPrefixLength,
	InetAddress, InetVersion FROM INET-ADDRESS-MIB		InetAddress, InetVersion FROM INET-ADDRESS-MIB
	IANAipRouteProtocol FROM IANA-RTPROTO-MIB;		IANAipRouteProtocol FROM IANA-RTPROTO-MIB;
	pimStdMIB MODULE-IDENTITY		pimStdMIB MODULE-IDENTITY
	LAST-UPDATED "200510040000Z" -- 4 October 2005		LAST-UPDATED "200601240000Z" -- 24 January 2006
	ORGANIZATION "IETF PIM Working Group"		ORGANIZATION "IETF PIM Working Group"
	CONTACT-INFO		CONTACT-INFO
	"Email: pim@ietf.org"		"Email: pim@ietf.org"
	DESCRIPTION		DESCRIPTION
	"The MIB module for management of PIM routers.		"The MIB module for management of PIM routers.
	Copyright (C) The Internet Society (2005). This version of		Copyright (C) The Internet Society (2005). This version of
	this MIB module is part of RFC yyyy; see the RFC itself for		this MIB module is part of RFC yyyy; see the RFC itself for
	full legal notices."		full legal notices."
	-- RFC Ed.: replace yyyy with actual RFC number & remove this note		-- RFC Ed.: replace yyyy with actual RFC number & remove this note
	REVISION "200510040000Z" -- 4 October 2005		REVISION "200601240000Z" -- 24 January 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
	DESCRIPTION		DESCRIPTION
	"The PIM mode in which a group is operating.		"The PIM mode in which a group is operating.
	none(1) The group is not using PIM, which may be the		none(1) The group is not using PIM, which may be the
	skipping to change at page 7, line 39 ¶		skipping to change at page 7, line 39 ¶
	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
	messages received to maintain it. This timer period is		messages received to maintain it. This timer period is
	called the Keepalive_Period in the PIM-SM specification."		called the Keepalive_Period in the PIM-SM specification. It
			is called the SourceLifetime in the PIM-DM specification."
	REFERENCE "I-D.ietf-pim-sm-v2-new section 4.11"		REFERENCE "I-D.ietf-pim-sm-v2-new section 4.11"
	DEFVAL { 210 }		DEFVAL { 210 }
	::= { pim 14 }		::= { pim 14 }
	pimRegisterSuppressionTime OBJECT-TYPE		pimRegisterSuppressionTime 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
	skipping to change at page 9, line 13 ¶		skipping to change at page 9, line 13 ¶
	::= { pim 20 }		::= { pim 20 }
	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
			SYNTAX Counter32
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The number of Asserts sent by this router."
			REFERENCE "I-D.ietf-pim-sm-v2-new section 4.6"
			::= { pim 22 }
			pimInAsserts OBJECT-TYPE
			SYNTAX Counter32
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The number of Asserts received by this router. Asserts
			are multicast to all routers on a network. This counter is
			incremented by all routers that receive an assert, not only
			those routers that are contesting the assert."
			REFERENCE "I-D.ietf-pim-sm-v2-new section 4.6"
			::= { pim 23 }
			pimLastAssertInterface OBJECT-TYPE
			SYNTAX InterfaceIndexOrZero
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The interface on which this router most recently sent or
			received an assert, or zero if this router has not sent or
			received an assert."
			REFERENCE "I-D.ietf-pim-sm-v2-new section 4.6"
			::= { pim 24 }
			pimLastAssertGroupAddressType OBJECT-TYPE
			SYNTAX InetAddressType
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The address type of the multicast group address in the most
			recently sent or received assert. If this router has not
			sent or received an assert then this object is set to
			unknown(0)."
			::= { pim 25 }
			pimLastAssertGroupAddress OBJECT-TYPE
			SYNTAX InetAddress (SIZE (0|4|8|16|20))
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The multicast group address in the most recently sent or
			received assert. The InetAddressType is given by the
			pimLastAssertGroupAddressType object."
			::= { pim 26 }
			pimLastAssertSourceAddressType OBJECT-TYPE
			SYNTAX InetAddressType
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The address type of the multicast source address in the
			most recently sent or received assert. If the most recent
			assert was (*,G), or if this router has not sent or received
			an assert, then this object is set to unknown(0)."
			::= { pim 27 }
			pimLastAssertSourceAddress OBJECT-TYPE
			SYNTAX InetAddress (SIZE (0|4|8|16|20))
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The multicast source address in the most recently sent or
			received assert. The InetAddressType is given by the
			pimLastAssertSourceAddressType object."
			::= { pim 28 }
			pimNeighborLossTrapPeriod OBJECT-TYPE
			SYNTAX Unsigned32 (0..65535)
			UNITS "seconds"
			MAX-ACCESS read-write
			STATUS current
			DESCRIPTION
			"The minimum time that must elapse between pimNeighborLoss
			traps originated by this router. The maximum value 65535
			represents an 'infinite' time, in which case no
			pimNeighborLoss traps are ever sent."
			DEFVAL { 0 }
			::= { pim 29 }
			pimNeighborLossCount OBJECT-TYPE
			SYNTAX Counter32
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The number of neighbor loss events that have occurred.
			This count is incremented when the neighbor timer expires,
			and the router has no other neighbors on the same interface
			with the same IP version and a lower IP address than itself.
			This counter is incremented whenever a pimNeighborLoss trap
			would be generated."
			REFERENCE "I-D.ietf-pim-sm-v2-new section 4.3.2"
			::= { pim 30 }
			pimInvalidRegisterTrapPeriod OBJECT-TYPE
			SYNTAX Unsigned32 (10..65535)
			UNITS "seconds"
			MAX-ACCESS read-write
			STATUS current
			DESCRIPTION
			"The minimum time that must elapse between
			pimInvalidRegister traps originated by this router. The
			default value of 65535 represents an 'infinite' time, in
			which case no pimInvalidRegister traps are ever sent.
			The non-zero minimum allowed value provides resilience
			against propagation of denial-of-service attacks from the
			data and control planes to the network management plane."
			DEFVAL { 65535 }
			::= { pim 31 }
			pimInvalidRegisterMsgsRcvd OBJECT-TYPE
			SYNTAX Counter32
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The number of invalid PIM Register messages that have been
			received by this device.
			A PIM Register message is invalid if either
			o the destination address of the Register message does not
			match the Group to RP mapping on this device, or
			o this device believes the group address to be within an
			SSM address range, but this Register implies ASM usage.
			These conditions can occur transiently while RP mapping
			changes propagate through the network. If this counter is
			incremented repeatedly over several minutes, then there is a
			persisting configuration error that requires correction.
			The active Group to RP mapping on this device is specified
			by the object pimGroupMappingPimMode. If there is no such
			mapping, then the object pimGroupMappingPimMode is absent.
			The RP address contained in the invalid Register is
			pimInvalidRegisterRp.
			Multicast data carried by invalid Register messages is
			discarded. The discarded data is from a source directly
			connected to pimInvalidRegisterOrigin, and is addressed to
			pimInvalidRegisterGroup."
			REFERENCE "I-D.ietf-pim-sm-v2-new section 4.4.2"
			::= { pim 32 }
			pimInvalidRegisterAddressType OBJECT-TYPE
			SYNTAX InetAddressType
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The address type stored in pimInvalidRegisterOrigin,
			pimInvalidRegisterGroup and pimInvalidRegisterRp.
			If no unexpected Register messages have been received, then
			this object is set to unknown(0)."
			::= { pim 33 }
			pimInvalidRegisterOrigin OBJECT-TYPE
			SYNTAX InetAddress (SIZE (0|4|8|16|20))
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The source address of the last unexpected Register message
			received by this device."
			::= { pim 34 }
			pimInvalidRegisterGroup OBJECT-TYPE
			SYNTAX InetAddress (SIZE (0|4|8|16|20))
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The IP multicast group address to which the last unexpected
			Register message received by this device was addressed."
			::= { pim 35 }
			pimInvalidRegisterRp OBJECT-TYPE
			SYNTAX InetAddress (SIZE (0|4|8|16|20))
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The RP address to which the last unexpected Register
			message received by this device was delivered."
			::= { pim 36 }
			pimInvalidJoinPruneTrapPeriod OBJECT-TYPE
			SYNTAX Unsigned32 (10..65535)
			UNITS "seconds"
			MAX-ACCESS read-write
			STATUS current
			DESCRIPTION
			"The minimum time that must elapse between
			pimInvalidJoinPrune traps originated by this router. The
			default value of 65535 represents an 'infinite' time, in
			which case no pimInvalidJoinPrune traps are ever sent.
			The non-zero minimum allowed value provides resilience
			against propagation of denial-of-service attacks from the
			control plane to the network management plane."
			DEFVAL { 65535 }
			::= { pim 37 }
			pimInvalidJoinPruneMsgsRcvd OBJECT-TYPE
			SYNTAX Counter32
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The number of invalid PIM Join/Prune messages that have
			been received by this device.
			A PIM Join/Prune message is invalid if either
			o the Group to RP mapping specified by this message does not
			match the Group to RP mapping on this device, or
			o this device believes the group address to be within an
			SSM address range, but this Join/Prune (*,G) or (S,G,rpt)
			implies ASM usage.
			These conditions can occur transiently while RP mapping
			changes propagate through the network. If this counter is
			incremented repeatedly over several minutes, then there is a
			persisting configuration error that requires correction.
			The active Group to RP mapping on this device is specified
			by the object pimGroupMappingPimMode. If there is no such
			mapping, then the object pimGroupMappingPimMode is absent.
			The RP address contained in the invalid Join/Prune is
			pimInvalidJoinPruneRp.
			Invalid Join/Prune messages are discarded. This may result
			in loss of multicast data affecting listeners downstream of
			pimInvalidJoinPruneOrigin, for multicast data addressed to
			pimInvalidJoinPruneGroup."
			REFERENCE "I-D.ietf-pim-sm-v2-new section 4.5.2"
			::= { pim 38 }
			pimInvalidJoinPruneAddressType OBJECT-TYPE
			SYNTAX InetAddressType
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The address type stored in pimInvalidJoinPruneOrigin,
			pimInvalidJoinPruneGroup and pimInvalidJoinPruneRp.
			If no unexpected Join/Prune messages have been received,
			this object is set to unknown(0)."
			::= { pim 39 }
			pimInvalidJoinPruneOrigin OBJECT-TYPE
			SYNTAX InetAddress (SIZE (0|4|8|16|20))
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The source address of the last unexpected Join/Prune
			message received by this device."
			::= { pim 40 }
			pimInvalidJoinPruneGroup OBJECT-TYPE
			SYNTAX InetAddress (SIZE (0|4|8|16|20))
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The IP multicast group address carried in the last
			unexpected Join/Prune message received by this device."
			::= { pim 41 }
			pimInvalidJoinPruneRp OBJECT-TYPE
			SYNTAX InetAddress (SIZE (0|4|8|16|20))
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The RP address carried in the last unexpected Join/Prune
			message received by this device."
			::= { pim 42 }
			pimRPMappingTrapPeriod OBJECT-TYPE
			SYNTAX Unsigned32 (0..65535)
			UNITS "seconds"
			MAX-ACCESS read-write
			STATUS current
			DESCRIPTION
			"The minimum time that must elapse between
			pimRPMappingChange traps originated by this router. The
			default value of 65535 represents an 'infinite' time, in
			which case no pimRPMappingChange traps are ever sent."
			DEFVAL { 65535 }
			::= { pim 43 }
			pimRPMappingChangeCount OBJECT-TYPE
			SYNTAX Counter32
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The number of changes to active RP mappings on this device.
			Information about active RP mappings is available in
			pimGroupMappingTable. Only changes to active mappings cause
			his count to be incremented. That is, changes that modify
			the pimGroupMappingEntry with the highest precedence for a
			group (lowest value of pimGroupMappingPrecedence).
			Such changes may result from configuration of this device,
			or from automatic RP mapping discovery methods including
			the PIM Bootstrap Router (BSR) mechanism."
			REFERENCE "I-D.ietf-pim-sm-bsr"
			::= { pim 44 }
			pimInterfaceElectionTrapPeriod OBJECT-TYPE
			SYNTAX Unsigned32 (0..65535)
			UNITS "seconds"
			MAX-ACCESS read-write
			STATUS current
			DESCRIPTION
			"The minimum time that must elapse between
			pimInterfaceElection traps originated by this router. The
			default value of 65535 represents an 'infinite' time, in
			which case no pimInterfaceElection traps are ever sent."
			DEFVAL { 65535 }
			::= { pim 45 }
			pimInterfaceElectionWinCount OBJECT-TYPE
			SYNTAX Counter32
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The number of times this device has been elected DR or DF
			on any interface.
			Elections occur frequently on newly-active interfaces, as
			triggered Hellos establish adjacencies. This counter is not
			incremented for elections on an interface until the first
			periodic Hello has been sent. If this router is the DR or
			DF at the time of sending the first periodic Hello after
			interface activation, then this counter is incremented
			(once) at that time."
			REFERENCE "I-D.ietf-pim-sm-v2-new section 4.3.2 and
			I-D.ietf-pim-bidir section 3.5.2"
			::= { pim 46 }
			pimRefreshInterval OBJECT-TYPE
			SYNTAX Unsigned32 (0..65535)
			UNITS "seconds"
			MAX-ACCESS read-write
			STATUS current
			DESCRIPTION
			"The interval between successive State Refresh messages sent
			by an Originator. This timer period is called the
			RefreshInterval in the PIM-DM specification. This object is
			used only by PIM-DM."
			REFERENCE "RFC 3973 section 4.8"
			DEFVAL { 60 }
			::= { pim 47 }
	--		--
	-- The PIM Interface Table		-- The PIM Interface Table
	--		--
	pimInterfaceTable OBJECT-TYPE		pimInterfaceTable OBJECT-TYPE
	SYNTAX SEQUENCE OF PimInterfaceEntry		SYNTAX SEQUENCE OF PimInterfaceEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The (conceptual) table listing the router's PIM interfaces.		"The (conceptual) table listing the router's PIM interfaces.
	skipping to change at page 10, line 12 ¶		skipping to change at page 17, line 37 ¶
	pimInterfaceGenerationIDValue Unsigned32,		pimInterfaceGenerationIDValue Unsigned32,
	pimInterfaceDRPriority Unsigned32,		pimInterfaceDRPriority Unsigned32,
	pimInterfaceLanDelayEnabled TruthValue,		pimInterfaceLanDelayEnabled TruthValue,
	pimInterfaceEffectPropagDelay Unsigned32,		pimInterfaceEffectPropagDelay Unsigned32,
	pimInterfaceEffectOverrideIvl Unsigned32,		pimInterfaceEffectOverrideIvl Unsigned32,
	pimInterfaceSuppressionEnabled TruthValue,		pimInterfaceSuppressionEnabled TruthValue,
	pimInterfaceBidirCapable TruthValue,		pimInterfaceBidirCapable TruthValue,
	pimInterfaceDRPriorityEnabled TruthValue,		pimInterfaceDRPriorityEnabled TruthValue,
	pimInterfaceDomainBorder TruthValue,		pimInterfaceDomainBorder TruthValue,
	pimInterfaceStatus RowStatus,		pimInterfaceStatus RowStatus,
	pimInterfaceStubInterface TruthValue		pimInterfaceStubInterface TruthValue,
			pimInterfacePruneLimitInterval Unsigned32,
			pimInterfaceGraftRetryInterval Unsigned32,
			pimInterfaceSRPriorityEnabled TruthValue
	}		}
	pimInterfaceIfIndex OBJECT-TYPE		pimInterfaceIfIndex OBJECT-TYPE
	SYNTAX InterfaceIndex		SYNTAX InterfaceIndex
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The ifIndex value of this PIM interface."		"The ifIndex value of this PIM interface."
	::= { pimInterfaceEntry 1 }		::= { pimInterfaceEntry 1 }
	skipping to change at page 12, line 27 ¶		skipping to change at page 20, line 8 ¶
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The minimum number of PIM DF-Election messages that must be		"The minimum number of PIM DF-Election messages that must be
	lost in order for DF election on this interface to fail."		lost in order for DF election on this interface to fail."
	DEFVAL { 3 }		DEFVAL { 3 }
	::= { pimInterfaceEntry 9 }		::= { pimInterfaceEntry 9 }
	pimInterfaceHelloHoldtime OBJECT-TYPE		pimInterfaceHelloHoldtime OBJECT-TYPE
	SYNTAX Unsigned32 (0..65535)		SYNTAX Unsigned32 (0..65535)
	UNITS "seconds"		UNITS "seconds"
	MAX-ACCESS read-only		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The value set in the Holdtime field of PIM Hello messages		"The value set in the Holdtime field of PIM Hello messages
	transmitted on this interface. A value of 65535 represents		transmitted on this interface. A value of 65535 represents
	an 'infinite' holdtime. Implementations are recommended		an 'infinite' holdtime. Implementations are recommended
	to use a holdtime that is 3.5 times the value of		to use a holdtime that is 3.5 times the value of
	pimInterfaceHelloInterval, or 65535 if		pimInterfaceHelloInterval, or 65535 if
	pimInterfaceHelloInterval is set to zero."		pimInterfaceHelloInterval is set to zero."
	DEFVAL { 105 }		DEFVAL { 105 }
	::= { pimInterfaceEntry 10 }		::= { pimInterfaceEntry 10 }
	pimInterfaceJoinPruneHoldtime OBJECT-TYPE		pimInterfaceJoinPruneHoldtime OBJECT-TYPE
	SYNTAX Unsigned32 (0..65535)		SYNTAX Unsigned32 (0..65535)
	UNITS "seconds"		UNITS "seconds"
	MAX-ACCESS read-only		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The value inserted into the Holdtime field of a PIM		"The value inserted into the Holdtime field of a PIM
	Join/Prune message sent on this interface. A value of 65535		Join/Prune message sent on this interface. A value of 65535
	represents an 'infinite' holdtime. Implementations are		represents an 'infinite' holdtime. Implementations are
	recommended to use a holdtime that is 3.5 times the value of		recommended to use a holdtime that is 3.5 times the value of
	pimInterfaceJoinPruneInterval, or 65535 if		pimInterfaceJoinPruneInterval, or 65535 if
	pimInterfaceJoinPruneInterval is set to zero."		pimInterfaceJoinPruneInterval is set to zero. PIM-DM
			implementations are recommended to use the value of
			pimInterfacePruneLimitInterval."
	DEFVAL { 210 }		DEFVAL { 210 }
	::= { pimInterfaceEntry 11 }		::= { pimInterfaceEntry 11 }
	pimInterfacePropagationDelay OBJECT-TYPE		pimInterfacePropagationDelay OBJECT-TYPE
	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
	skipping to change at page 16, line 33 ¶		skipping to change at page 24, line 15 ¶
	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."
	DEFVAL { false }		DEFVAL { false }
	::= { pimInterfaceEntry 24 }		::= { pimInterfaceEntry 24 }
			pimInterfacePruneLimitInterval OBJECT-TYPE
			SYNTAX Unsigned32 (0..65535)
			UNITS "seconds"
			MAX-ACCESS read-create
			STATUS current
			DESCRIPTION
			"The minimum interval that must transpire between two
			successive Prunes sent by a router. This object corresponds
			to the 't_limit' timer value defined in the PIM-DM
			specification. This object is used only by PIM-DM."
			REFERENCE "RFC 3973 section 4.8"
			DEFVAL { 60 }
			::= { pimInterfaceEntry 25 }
			pimInterfaceGraftRetryInterval OBJECT-TYPE
			SYNTAX Unsigned32 (0..65535)
			UNITS "seconds"
			MAX-ACCESS read-create
			STATUS current
			DESCRIPTION
			"The minimum interval that must transpire between two
			successive Grafts sent by a router. This object corresponds
			to the 'Graft_Retry_Period' timer value defined in the
			PIM-DM specification. This object is used only by PIM-DM."
			REFERENCE "RFC 3973 section 4.8"
			DEFVAL { 3 }
			::= { pimInterfaceEntry 26 }
			pimInterfaceSRPriorityEnabled OBJECT-TYPE
			SYNTAX TruthValue
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"Evaluates to TRUE if all routers on this interface are
			using the State Refresh option. This object is used only by
			PIM-DM."
			::= { pimInterfaceEntry 27 }
	--		--
	-- The PIM Neighbor Table		-- The PIM Neighbor Table
	--		--
	pimNeighborTable OBJECT-TYPE		pimNeighborTable OBJECT-TYPE
	SYNTAX SEQUENCE OF PimNeighborEntry		SYNTAX SEQUENCE OF PimNeighborEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The (conceptual) table listing the router's PIM neighbors."		"The (conceptual) table listing the router's PIM neighbors."
	skipping to change at page 17, line 21 ¶		skipping to change at page 25, line 42 ¶
	pimNeighborUpTime TimeTicks,		pimNeighborUpTime TimeTicks,
	pimNeighborExpiryTime TimeTicks,		pimNeighborExpiryTime TimeTicks,
	pimNeighborLanPruneDelayPresent TruthValue,		pimNeighborLanPruneDelayPresent TruthValue,
	pimNeighborPropagationDelay Unsigned32,		pimNeighborPropagationDelay Unsigned32,
	pimNeighborOverrideInterval Unsigned32,		pimNeighborOverrideInterval Unsigned32,
	pimNeighborTBit TruthValue,		pimNeighborTBit TruthValue,
	pimNeighborGenerationIDPresent TruthValue,		pimNeighborGenerationIDPresent TruthValue,
	pimNeighborGenerationIDValue Unsigned32,		pimNeighborGenerationIDValue Unsigned32,
	pimNeighborBidirCapable TruthValue,		pimNeighborBidirCapable TruthValue,
	pimNeighborDRPriorityPresent TruthValue,		pimNeighborDRPriorityPresent TruthValue,
	pimNeighborDRPriority Unsigned32		pimNeighborDRPriority Unsigned32,
			pimNeighborSRCapable TruthValue
	}		}
	pimNeighborIfIndex OBJECT-TYPE		pimNeighborIfIndex OBJECT-TYPE
	SYNTAX InterfaceIndex		SYNTAX InterfaceIndex
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The value of ifIndex for the interface used to reach this		"The value of ifIndex for the interface used to reach this
	PIM neighbor."		PIM neighbor."
	::= { pimNeighborEntry 1 }		::= { pimNeighborEntry 1 }
	pimNeighborAddressType OBJECT-TYPE		pimNeighborAddressType OBJECT-TYPE
	SYNTAX InetAddressType		SYNTAX InetAddressType
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The address type of this PIM neighbor."		"The address type of this PIM neighbor."
	::= { pimNeighborEntry 2 }		::= { pimNeighborEntry 2 }
	skipping to change at page 20, line 15 ¶		skipping to change at page 28, line 35 ¶
	pimNeighborDRPriority OBJECT-TYPE		pimNeighborDRPriority OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The value of the Designated Router Priority from the last		"The value of the Designated Router Priority from the last
	PIM Hello message received from this neighbor. This object		PIM Hello message received from this neighbor. This object
	is always zero if pimNeighborDRPriorityPresent is FALSE."		is always zero if pimNeighborDRPriorityPresent is FALSE."
	::= { pimNeighborEntry 14 }		::= { pimNeighborEntry 14 }
			pimNeighborSRCapable OBJECT-TYPE
			SYNTAX TruthValue
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"Evaluates to TRUE if this neighbor is using the State
			Refresh Capable option. This object is used only by
			PIM-DM."
			::= { pimNeighborEntry 15 }
	--		--
	-- The PIM Neighbor Secondary Address Table		-- The PIM Neighbor Secondary Address Table
	--		--
	pimNbrSecAddressTable OBJECT-TYPE		pimNbrSecAddressTable OBJECT-TYPE
	SYNTAX SEQUENCE OF PimNbrSecAddressEntry		SYNTAX SEQUENCE OF PimNbrSecAddressEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The (conceptual) table listing the secondary addresses		"The (conceptual) table listing the secondary addresses
	skipping to change at page 31, line 34 ¶		skipping to change at page 40, line 16 ¶
	pimSGRPFRouteProtocol IANAipRouteProtocol,		pimSGRPFRouteProtocol IANAipRouteProtocol,
	pimSGRPFRouteAddress InetAddress,		pimSGRPFRouteAddress InetAddress,
	pimSGRPFRoutePrefixLength InetAddressPrefixLength,		pimSGRPFRoutePrefixLength InetAddressPrefixLength,
	pimSGRPFRouteMetricPref Unsigned32,		pimSGRPFRouteMetricPref Unsigned32,
	pimSGRPFRouteMetric Unsigned32,		pimSGRPFRouteMetric Unsigned32,
	pimSGSPTBit TruthValue,		pimSGSPTBit TruthValue,
	pimSGKeepaliveTimer TimeTicks,		pimSGKeepaliveTimer TimeTicks,
	pimSGDRRegisterState INTEGER,		pimSGDRRegisterState INTEGER,
	pimSGDRRegisterStopTimer TimeTicks,		pimSGDRRegisterStopTimer TimeTicks,
	pimSGRPRegisterPMBRAddressType InetAddressType,		pimSGRPRegisterPMBRAddressType InetAddressType,
	pimSGRPRegisterPMBRAddress InetAddress		pimSGRPRegisterPMBRAddress InetAddress,
			pimSGUpstreamPruneState INTEGER,
			pimSGUpstreamPruneLimitTimer TimeTicks,
			pimSGOriginatorState INTEGER,
			pimSGSourceActiveTimer TimeTicks,
			pimSGStateRefreshTimer TimeTicks
	}		}
	pimSGAddressType OBJECT-TYPE		pimSGAddressType OBJECT-TYPE
	SYNTAX InetAddressType		SYNTAX InetAddressType
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The address type of the source and multicast group for this		"The address type of the source and multicast group for this
	entry."		entry."
	::= { pimSGEntry 1 }		::= { pimSGEntry 1 }
	skipping to change at page 36, line 45 ¶		skipping to change at page 45, line 31 ¶
	SYNTAX InetAddress (SIZE (0|4|16|20))		SYNTAX InetAddress (SIZE (0|4|16|20))
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The IP address of the first PIM Multicast Border Router to		"The IP address of the first PIM Multicast Border Router to
	send a Register message with the Border bit set. The		send a Register message with the Border bit set. The
	InetAddressType is given by the		InetAddressType is given by the
	pimSGRPRegisterPMBRAddressType object."		pimSGRPRegisterPMBRAddressType object."
	::= { pimSGEntry 22 }		::= { pimSGEntry 22 }
			pimSGUpstreamPruneState OBJECT-TYPE
			SYNTAX INTEGER {
			forwarding (1),
			ackpending (2),
			pruned (3)
			}
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"Whether the local router has pruned itself from the tree.
			This corresponds to the state of the upstream prune (S,G)
			state machine in the PIM-DM specification. This object is
			used only by PIM-DM."
			REFERENCE "RFC 3973 section 4.4.1"
			::= { pimSGEntry 23 }
			pimSGUpstreamPruneLimitTimer OBJECT-TYPE
			SYNTAX TimeTicks
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"The time remaining before the local router may send a (S,G)
			Prune message on pimSGRPFIfIndex. This timer is called the
			(S,G) Prune Limit Timer in the PIM-DM specification. This
			object is zero if the timer is not running. This object is
			used only by PIM-DM."
			REFERENCE "RFC 2973 section 4.8"
			::= { pimSGEntry 24 }
			pimSGOriginatorState OBJECT-TYPE
			SYNTAX INTEGER {
			notOriginator (1),
			originator (2)
			}
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"Whether the router is an originator for an (S,G) message
			flow. This corresponds to the state of the per-(S,G)
			Originator state machine in the PIM-DM specification. This
			object is used only by PIM-DM."
			REFERENCE "RFC 3973 section 4.5.2"
			::= { pimSGEntry 25 }
			pimSGSourceActiveTimer OBJECT-TYPE
			SYNTAX TimeTicks
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"If pimSGOriginatorState is 'originator', this is the time
			remaining before the local router reverts to a notOriginator
			state. Otherwise, this is zero. This timer is called the
			Source Active Timer in the PIM-DM specification. This
			object is used only by PIM-DM."
			REFERENCE "RFC 3973 section 4.8"
			::= { pimSGEntry 26 }
			pimSGStateRefreshTimer OBJECT-TYPE
			SYNTAX TimeTicks
			MAX-ACCESS read-only
			STATUS current
			DESCRIPTION
			"If pimSGOriginatorState is 'originator', this is the time
			remaining before the local router sends a State Refresh
			message. Otherwise, this is zero. This timer is called the
			State Refresh Timer in the PIM-DM specification. This
			object is used only by PIM-DM."
			REFERENCE "RFC 3973 section 4.8"
			::= { pimSGEntry 27 }
	--		--
	-- The PIM (S,G,I) State Table		-- The PIM (S,G,I) State Table
	--		--
	pimSGITable OBJECT-TYPE		pimSGITable OBJECT-TYPE
	SYNTAX SEQUENCE OF PimSGIEntry		SYNTAX SEQUENCE OF PimSGIEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The (conceptual) table listing the interface-specific (S,G)		"The (conceptual) table listing the interface-specific (S,G)
	skipping to change at page 38, line 29 ¶		skipping to change at page 48, line 37 ¶
	noInfo (1),		noInfo (1),
	join (2),		join (2),
	prunePending (3)		prunePending (3)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The state resulting from (S,G) Join/Prune messages		"The state resulting from (S,G) Join/Prune messages
	received on this interface. This corresponds to the state		received on this interface. This corresponds to the state
	of the downstream per-interface (S,G) state machine in the		of the downstream per-interface (S,G) state machine in the
	PIM-SM specification."		PIM-SM and PIM-DM specification."
	REFERENCE "I-D.ietf-pim-sm-v2-new section 4.5.3"		REFERENCE "I-D.ietf-pim-sm-v2-new section 4.5.3 and RFC 3973 section
			4.4.2"
	::= { pimSGIEntry 4 }		::= { pimSGIEntry 4 }
	pimSGIPrunePendingTimer OBJECT-TYPE		pimSGIPrunePendingTimer OBJECT-TYPE
	SYNTAX TimeTicks		SYNTAX TimeTicks
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The time remaining before the local router acts on an (S,G)		"The time remaining before the local router acts on an (S,G)
	Prune message received on this interface, during which the		Prune message received on this interface, during which the
	router is waiting to see whether another downstream router		router is waiting to see whether another downstream router
	skipping to change at page 38, line 44 ¶		skipping to change at page 49, line 4 ¶
	SYNTAX TimeTicks		SYNTAX TimeTicks
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The time remaining before the local router acts on an (S,G)		"The time remaining before the local router acts on an (S,G)
	Prune message received on this interface, during which the		Prune message received on this interface, during which the
	router is waiting to see whether another downstream router		router is waiting to see whether another downstream router
	will override the Prune message. This timer is called the		will override the Prune message. This timer is called the
	(S,G) Prune-Pending Timer in the PIM-SM specification. This		(S,G) Prune-Pending Timer in the PIM-SM specification. This
	object is zero if the timer is not running."		object is zero if the timer is not running."
	REFERENCE "I-D.ietf-pim-sm-v2-new section 4.5.3 and 4.5.4"		REFERENCE "I-D.ietf-pim-sm-v2-new section 4.5.3 and 4.5.4"
	::= { pimSGIEntry 5 }		::= { pimSGIEntry 5 }
	pimSGIJoinExpiryTimer OBJECT-TYPE		pimSGIJoinExpiryTimer OBJECT-TYPE
	SYNTAX TimeTicks		SYNTAX TimeTicks
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The time remaining before (S,G) Join state for this		"The time remaining before (S,G) Join state for this
	interface expires. This timer is called the (S,G) Join		interface expires. This timer is called the (S,G) Join
	Expiry Timer in the PIM-SM specification. This object is		Expiry Timer in the PIM-SM specification. This object is
	zero if the timer is not running. A value of 'FFFFFFFF'h		zero if the timer is not running. A value of 'FFFFFFFF'h
	indicates an infinite expiry time."		indicates an infinite expiry time. This timer is called the
	REFERENCE "I-D.ietf-pim-sm-v2-new section 4.10"		(S,G) Prune Timer in the PIM-DM specification."
			REFERENCE "I-D.ietf-pim-sm-v2-new section 4.10 and RFC 3973 section
			4.8"
	::= { pimSGIEntry 6 }		::= { pimSGIEntry 6 }
	pimSGIAssertState OBJECT-TYPE		pimSGIAssertState OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	noInfo (1),		noInfo (1),
	iAmAssertWinner (2),		iAmAssertWinner (2),
	iAmAssertLoser (3)		iAmAssertLoser (3)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	skipping to change at page 56, line 46 ¶		skipping to change at page 67, line 8 ¶
	--		--
	pimNeighborLoss NOTIFICATION-TYPE		pimNeighborLoss NOTIFICATION-TYPE
	OBJECTS { pimNeighborUpTime }		OBJECTS { pimNeighborUpTime }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A pimNeighborLoss trap signifies the loss of an adjacency		"A pimNeighborLoss trap signifies the loss of an adjacency
	with a neighbor. This trap should be generated when the		with a neighbor. This trap should be generated when the
	neighbor timer expires, and the router has no other		neighbor timer expires, and the router has no other
	neighbors on the same interface with the same IP version and		neighbors on the same interface with the same IP version and
	a lower IP address than itself."		a lower IP address than itself.
	::= { pimTraps 1 }
	pimUnexpectedRegisterAddressType OBJECT-TYPE
	SYNTAX InetAddressType
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"The address type stored in pimUnexpectedRegisterOrigin,
	pimUnexpectedRegisterGroup and pimUnexpectedRegisterRp.
	If no unexpected Register messages have been received, then
	this object is set to unknown(0)."
	::= { pimTraps 2 }
	pimUnexpectedRegisterOrigin OBJECT-TYPE
	SYNTAX InetAddress (SIZE (0|4|8|16|20))
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"The source address of the last unexpected Register message
	received by this device."
	::= { pimTraps 3 }
	pimUnexpectedRegisterGroup OBJECT-TYPE
	SYNTAX InetAddress (SIZE (0|4|8|16|20))
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"The IP multicast group address to which the last unexpected
	Register message received by this device was addressed."
	::= { pimTraps 4 }
	pimUnexpectedRegisterRp OBJECT-TYPE		This notification is generated whenever the counter
	SYNTAX InetAddress (SIZE (0|4|8|16|20))		pimNeighborLossCount is incremented, subject
	MAX-ACCESS read-only		to the rate limit specified by pimNeighborLossPeriod."
	STATUS current		REFERENCE "I-D.ietf-pim-sm-v2-new section 4.3.2"
	DESCRIPTION		::= { pimTraps 1 }
	"The RP address to which the last unexpected Register
	message received by this device was delivered."
	::= { pimTraps 5 }
	pimUnexpectedRegister NOTIFICATION-TYPE		pimInvalidRegister NOTIFICATION-TYPE
	OBJECTS { pimGroupMappingPimMode,		OBJECTS { pimGroupMappingPimMode,
	pimUnexpectedRegisterAddressType,		pimInvalidRegisterAddressType,
	pimUnexpectedRegisterOrigin,		pimInvalidRegisterOrigin,
	pimUnexpectedRegisterGroup,		pimInvalidRegisterGroup,
	pimUnexpectedRegisterRp		pimInvalidRegisterRp
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A pimUnexpectedRegister trap signifies that an unexpected		"A pimInvalidRegister trap signifies that an invalid PIM
	Register message was received by this device. This		Register message was received by this device.
	indicates that the originating router and this router have
	different Group to RP mappings.
	This trap may also signify that this router believes the
	group address to be within the SSM range, but the origin
	of the Register has implied ASM usage by sending this
	Register message.
	If the local router has one or more Group to RP mappings
	for this group, then the object pimGroupMappingPimMode
	specifies the mapping currently being used (the one with
	the lowest value for pimGroupMappingPrecedence).
	If the local router has no Group to RP mapping for this
	group, them the object pimGroupMappingPimMode is absent.
	This trap may indicate a transient condition while new RP
	mappings are propagating through the network. If it
	occurs repeatedly over an extended period, then there is a
	persisting configuration error that requires correction.
	The effect is that multicast data is being discarded,
	because this router discards the unexpected Register
	messages. The discarded data is from a source directly
	connected to pimUnexpectedRegisterOrigin, and is addressed
	to pimUnexpectedRegisterGroup.
	The condition that causes this trap can occur very		This notification is generated whenever the counter
	frequently. Routers may choose to limit the rate at which		pimInvalidRegisterMsgsRcvd is incremented, subject to the
	pimUnexpectedRegister is sent."		rate limit specified by pimInvalidRegisterTrapPeriod."
	REFERENCE "I-D.ietf-pim-sm-v2-new section 4.4.2"		REFERENCE "I-D.ietf-pim-sm-v2-new section 4.4.2"
	::= { pimTraps 6 }		::= { pimTraps 2 }
	pimUnexpectedJoinPruneAddressType OBJECT-TYPE
	SYNTAX InetAddressType
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"The address type stored in pimUnexpectedJoinPruneOrigin,
	pimUnexpectedJoinPruneGroup and pimUnexpectedJoinPrune.
	If no unexpected Join/Prune messages have been received,
	this object is set to unknown(0)."
	::= { pimTraps 7 }
	pimUnexpectedJoinPruneOrigin OBJECT-TYPE
	SYNTAX InetAddress (SIZE (0|4|8|16|20))
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"The source address of the last unexpected Join/Prune
	message received by this device."
	::= { pimTraps 8 }
	pimUnexpectedJoinPruneGroup OBJECT-TYPE
	SYNTAX InetAddress (SIZE (0|4|8|16|20))
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"The IP multicast group address carried in the last
	unexpected Join/Prune message received by this device."
	::= { pimTraps 9 }
	pimUnexpectedJoinPruneRp OBJECT-TYPE
	SYNTAX InetAddress (SIZE (0|4|8|16|20))
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"The RP address carried in the last unexpected Join/Prune
	message received by this device."
	::= { pimTraps 10 }
	pimUnexpectedJoinPrune NOTIFICATION-TYPE		pimInvalidJoinPrune NOTIFICATION-TYPE
	OBJECTS { pimGroupMappingPimMode,		OBJECTS { pimGroupMappingPimMode,
	pimUnexpectedJoinPruneAddressType,		pimInvalidJoinPruneAddressType,
	pimUnexpectedJoinPruneOrigin,		pimInvalidJoinPruneOrigin,
	pimUnexpectedJoinPruneGroup,		pimInvalidJoinPruneGroup,
	pimUnexpectedJoinPruneRp,		pimInvalidJoinPruneRp,
	pimNeighborUpTime		pimNeighborUpTime
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A pimUnexpectedJoinPrune trap signifies that an		"A pimInvalidJoinPrune trap signifies that an invalid PIM
	unexpected Join/Prune message was received by this device.		Join/Prune message was received by this device.
	This indicates that this router and one of its neighbors
	have different Group to RP mappings.
	This trap may also signify that this router believes the
	group address to be within the SSM range, but the origin
	of the JoinPrune has implied ASM usage by sending this
	Join/Prune(*,G).
	If the local router has one or more Group to RP mappings
	for this group, then the object pimGroupMappingPimMode
	specifies the mapping currently being used (the one with
	the lowest value for pimGroupMappingPrecedence).
	If the local router has no Group to RP mapping for this
	group, them the object pimGroupMappingPimMode is absent.
	If the neighbor that sent this Join/Prune is known, then
	it is identified by pimNeighborUpTime. Otherwise
	pimNeighborUpTime is absent.
	This trap may indicate a transient condition while new RP
	mappings are propagating through the network. If it
	occurs repeatedly over an extended period, then there is a
	persisting configuration error that requires correction.
	The effect is that ASM multicast data will not reach
	listeners below the neighbor identified by pimNeighborUpTime
	because this router will ignore the Join/Prune request.
	The condition that causes this trap can occur very		This notification is generated whenever the counter
	frequently. Routers may choose to limit the rate at which		pimInvalidJoinPruneMsgsRcvd is incremented, subject to the
	pimUnexpectedJoinPrune is sent."		rate limit specified by pimInvalidJoinPruneTrapPeriod."
	REFERENCE "I-D.ietf-pim-sm-v2-new section 4.5.2"		REFERENCE "I-D.ietf-pim-sm-v2-new section 4.5.2"
	::= { pimTraps 11 }		::= { pimTraps 3 }
	pimRPMappingChangeType OBJECT-TYPE
	SYNTAX INTEGER { newMapping(1),
	deletedMapping(2),
	modifiedOldMapping(3),
	modifiedNewMapping(4),
	highestPrecedenceOldMapping(5),
	highestPrecedenceNewMapping(6)
	}
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"The operation that resulted in the most recent
	pimRPMappingChange notification.
	o newMapping indicates that a new mapping has been added
	into the pimGroupMappingTable, and that this new entry is
	now the highest precedence mapping for the group.
	o deletedMapping indicates that a mapping has been
	deleted from the pimGroupMappingTable, and that the
	deleted entry was the highest precedence mapping for the
	group. If there are other entries for this group, then
	this is immediately followed by an additional notification
	of type highestPrecedenceNewMapping.
	o modifiedOldMapping indicates that the mapping that had the
	highest precedence is being modified. This is
	immediately followed by an additional notification of type
	modifiedNewMapping or highestPrecedenceNewMapping
	containing the new RP address.
	o modifiedNewMapping indicates the mapping that has the
	highest precedence has just been modified. This
	immediately follows a notification of type
	modifiedOldMapping or highestPrecedenceOldMapping.
	o highestPrecedenceOldMapping is similar to
	modifiedOldMapping, but the old mapping entry is not being
	modified. This notification states that it is no longer
	the active mapping, because another mapping now has the
	highest precedence. This is immediately followed by an
	additional notification of type newMapping or
	modifiedNewMapping containing the new RP address.
	o highestPrecedenceNewMapping is similar to
	modifiedNewMapping, but the new mapping entry has not been
	modified. This notification states that an existing entry
	is now the active mapping, because another mapping has
	been deleted or reduced in precedence. This notification
	immediately follows a notification of type deletedMapping
	or modifiedOldMapping."
	::= { pimTraps 12 }
	pimRPMappingChange NOTIFICATION-TYPE		pimRPMappingChange NOTIFICATION-TYPE
	OBJECTS { pimGroupMappingPimMode,		OBJECTS { pimGroupMappingPimMode,
	pimGroupMappingPrecedence,		pimGroupMappingPrecedence
	pimRPMappingChangeType
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A pimRPMappingChange trap signifies a change in the active		"A pimRPMappingChange trap signifies a change to the active
	RP Mapping on this device. The type of change is indicated		RP mapping on this device.
	by pimRPMappingChangeType.
	Not all changes to the pimGroupMappingTable cause a
	pimRPMappingChange trap. Only those changes that modify the
	pimGroupMappingEntry with the highest precedence for a
	group (lowest value of pimGroupMappingPrecedence) cause
	traps.
	Traps with pimRPMappingChangeType set to deletedMapping,
	modifiedOldMapping or highestPrecedenceOldMapping always
	contain an old RP mapping that is about to be replaced.
	Traps with pimRPMappingChangeType set to newMapping,
	modifiedNewMapping or highestPrecedenceNewMapping always
	contain the new RP mapping that is now in use.
	The condition that causes this trap can occur frequently.		This notification is generated whenever the counter
	Routers may choose to limit the rate at which		pimRPMappingChangeCount is incremented, subject to the
	pimRPMappingChange is sent."		rate limit specified by pimRPMappingChangeTrapPeriod."
	::= { pimTraps 13 }		::= { pimTraps 4 }
	pimDRElection NOTIFICATION-TYPE		pimInterfaceElection NOTIFICATION-TYPE
	OBJECTS { pimInterfaceDR }		OBJECTS { pimInterfaceAddressType,
			pimInterfaceAddress }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A pimDRElection trap signifies that a new DR has been		"A pimInterfaceElection trap signifies that a new DR or DF
	elected on a network.		has been elected on a network.
	This trap is only sent if the router is elected as the new
	DR, or if the router was the DR before this election.
	A router may choose not to send this trap until it has sent		This notification is generated whenever the counter
	a periodic Hello on this interface. At the time when the		pimInterfaceElectionsWinCount is incremented, subject to the
	first periodic Hello is sent, a router may choose to		rate limit specified by pimInterfaceElectionTrapPeriod."
	send a pimDRElection trap if it is the DR at that time.		REFERENCE "I-D.ietf-pim-sm-v2-new section 4.3.2 and
	This suppresses misleading pimDRElection traps during router		I-D.ietf-pim-bidir section 3.5.2"
	startup and reboot."		::= { pimTraps 5 }
	REFERENCE "I-D.ietf-pim-sm-v2-new section 4.3.2"
	::= { pimTraps 14 }
	--		--
	-- Conformance Information		-- Conformance Information
	--		--
	pimMIBConformance OBJECT IDENTIFIER ::= { pimStdMIB 2 }		pimMIBConformance OBJECT IDENTIFIER ::= { pimStdMIB 2 }
	pimMIBCompliances OBJECT IDENTIFIER ::= { pimMIBConformance 1 }		pimMIBCompliances OBJECT IDENTIFIER ::= { pimMIBConformance 1 }
	pimMIBGroups OBJECT IDENTIFIER ::= { pimMIBConformance 2 }		pimMIBGroups OBJECT IDENTIFIER ::= { pimMIBConformance 2 }
	--		--
	skipping to change at page 67, line 25 ¶		skipping to change at page 73, line 25 ¶
	pimStaticRPPrecedenceGroup OBJECT-GROUP		pimStaticRPPrecedenceGroup OBJECT-GROUP
	OBJECTS { pimStaticRPPrecedence }		OBJECTS { pimStaticRPPrecedence }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A collection of objects to allow fine control of		"A collection of objects to allow fine control of
	interactions between static RP configuration and		interactions between static RP configuration and
	dynamically acquired group to RP mappings."		dynamically acquired group to RP mappings."
	::= { pimMIBGroups 10 }		::= { pimMIBGroups 10 }
	pimNetMgmtNotificationObjects OBJECT-GROUP		pimNetMgmtNotificationObjects OBJECT-GROUP
	OBJECTS { pimUnexpectedRegisterAddressType,		OBJECTS { pimInvalidRegisterTrapPeriod,
	pimUnexpectedRegisterOrigin,		pimInvalidRegisterMsgsRcvd,
	pimUnexpectedRegisterGroup,		pimInvalidRegisterAddressType,
	pimUnexpectedRegisterRp,		pimInvalidRegisterOrigin,
	pimUnexpectedJoinPruneAddressType,		pimInvalidRegisterGroup,
	pimUnexpectedJoinPruneOrigin,		pimInvalidRegisterRp,
	pimUnexpectedJoinPruneGroup,		pimInvalidJoinPruneTrapPeriod,
	pimUnexpectedJoinPruneRp,		pimInvalidJoinPruneMsgsRcvd,
	pimRPMappingChangeType		pimInvalidJoinPruneAddressType,
			pimInvalidJoinPruneOrigin,
			pimInvalidJoinPruneGroup,
			pimInvalidJoinPruneRp,
			pimRPMappingTrapPeriod,
			pimRPMappingChangeCount,
			pimInterfaceElectionTrapPeriod,
			pimInterfaceElectionWinCount
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Objects required by notification for signaling PIM network		"A collection of objects to support notification of PIM
	management events."		network management events."
	::= { pimMIBGroups 11 }		::= { pimMIBGroups 11 }
	pimNetMgmtNotificationGroup NOTIFICATION-GROUP		pimNetMgmtNotificationGroup NOTIFICATION-GROUP
	NOTIFICATIONS { pimUnexpectedRegister,		NOTIFICATIONS { pimInvalidRegister,
	pimUnexpectedJoinPrune,		pimInvalidJoinPrune,
	pimRPMappingChange,		pimRPMappingChange,
	pimDRElection		pimInterfaceElection
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A collection of notifications for signaling PIM network		"A collection of notifications for signaling PIM network
	management events."		management events."
	::= { pimMIBGroups 12 }		::= { pimMIBGroups 12 }
	END		pimDiagnosticsGroup OBJECT-GROUP
			OBJECTS { pimInAsserts,
			pimOutAsserts,
			pimLastAssertInterface,
			pimLastAssertGroupAddressType,
			pimLastAssertGroupAddress,
			pimLastAssertSourceAddressType,
			pimLastAssertSourceAddress,
			pimNeighborLossTrapPeriod,
			pimNeighborLossCount
			}
			STATUS current
			DESCRIPTION
			"Objects providing additonal diagnostics related to a PIM
			router."
			::= { pimMIBGroups 13 }
			pimDmGroup OBJECT-GROUP
			OBJECTS {
			pimRefreshInterval,
			pimInterfacePruneLimitInterval,
			pimInterfaceGraftRetryInterval,
			pimInterfaceSRPriorityEnabled,
			pimNeighborSRCapable,
			pimSGUpstreamPruneState,
			pimSGUpstreamPruneLimitTimer,
			pimSGOriginatorState,
			pimSGSourceActiveTimer,
			pimSGStateRefreshTimer
			}
			STATUS current
			DESCRIPTION
			"A collection of objects required for management of PIM
			Dense Mode (PIM-DM) function."
			REFERENCE "RFC 3973"
			::= { pimMIBGroups 14 }
			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 or disrupts		multicast routing behavior in a way that prevents, disrupts, or
	services provided by the network, including (but not limited to)		subverts services provided by the network, including (but not limited
	multicast data traffic delivery.		to) multicast data traffic delivery. For example, attacks can be
	The following tables and objects may also be used to modify multicast
	routing behavior in order to intercept or subvert any information
	that is carried by the network. 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		pimKeepalivePeriod pimRegisterSuppressionTime
	pimRegisterSuppressionTime		pimNeighborLossTrapPeriod
	pimInterfaceTable		pimInvalidRegisterTrapPeriod
	pimInterfaceEntry		pimInvalidJoinPruneTrapPeriod pimRPMappingTrapPeriod
			pimInterfaceElectionTrapPeriod pimRefreshInterval
			pimInterfaceTable pimInterfaceEntry
			pimInterfaceIfIndex pimInterfaceIPVersion
	pimInterfaceHelloInterval		pimInterfaceHelloInterval
	pimInterfaceTrigHelloInterval		pimInterfaceTrigHelloInterval
	pimInterfaceJoinPruneInterval		pimInterfaceJoinPruneInterval
	pimInterfaceDFElectionRobustness		pimInterfaceDFElectionRobustness pimInterfaceHelloHoldtime
			pimInterfaceJoinPruneHoldtime
	pimInterfacePropagationDelay		pimInterfacePropagationDelay
	pimInterfaceOverrideInterval		pimInterfaceOverrideInterval pimInterfaceDRPriority
	pimInterfaceDomainBorder		pimInterfaceDomainBorder pimInterfaceStatus
	pimInterfaceStatus
	pimInterfaceStubInterface		pimInterfaceStubInterface
	pimStaticRPTable		pimInterfacePruneLimitInterval pimStaticRPTable
	pimStaticRPEntry		pimStaticRPEntry pimStaticRPAddressType
	pimStaticRPAddressType		pimStaticRPGrpAddress pimStaticRPGrpPrefixLength
	pimStaticRPGrpAddress		pimStaticRPRPAddress pimStaticRPPimMode
	pimStaticRPGrpPrefixLength		pimStaticRPOverrideDynamic pimStaticRPRowStatus
	pimStaticRPRPAddress		pimStaticRPPrecedence pimAnycastRPSetTable
	pimStaticRPPimMode		pimAnycastRPSetEntry pimAnycastRPSetAddressType
	pimStaticRPOverrideDynamic
	pimStaticRPRowStatus
	pimStaticRPPrecedence
	pimAnycastRPSetTable
	pimAnycastRPSetEntry
	pimAnycastRPSetAddressType
	pimAnycastRPSetAnycastAddress		pimAnycastRPSetAnycastAddress
	pimAnycastRPSetRouterAddress		pimAnycastRPSetRouterAddress
	pimAnycastRPSetRowStatus
	pimAnycastRPSetLocalRouter
	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:
	The following tables and objects could be employed to determine the		The following tables and objects could be employed to determine the
	skipping to change at page 69, line 42 ¶		skipping to change at page 76, line 30 ¶
	transported.		transported.
	pimKeepalivePeriod		pimKeepalivePeriod
	pimRegisterSuppressionTime		pimRegisterSuppressionTime
	pimStarGEntries		pimStarGEntries
	pimStarGIEntries		pimStarGIEntries
	pimSGEntries		pimSGEntries
	pimSGIEntries		pimSGIEntries
	pimSGRptEntries		pimSGRptEntries
	pimSGRptIEntries		pimSGRptIEntries
			pimOutAsserts
			pimInAsserts
			pimLastAssertInterface
			pimLastAssertGroupAddressType
			pimLastAssertGroupAddress
			pimLastAssertSourceAddressType
			pimLastAssertSourceAddress
			pimNeighborLossTrapPeriod
			pimNeighborLossCount
			pimInvalidRegisterTrapPeriod
			pimInvalidRegisterMsgsRcvd
			pimInvalidRegisterAddressType
			pimInvalidRegisterOrigin
			pimInvalidRegisterGroup
			pimInvalidRegisterRp
			pimInvalidJoinPruneTrapPeriod
			pimInvalidJoinPruneMsgsRcvd
			pimInvalidJoinPruneAddressType
			pimInvalidJoinPruneOrigin
			pimInvalidJoinPruneGroup
			pimInvalidJoinPruneRp
			pimRPMappingTrapPeriod
			pimRPMappingChangeCount
			pimInterfaceElectionTrapPeriod
			pimInterfaceElectionWinCount
			pimRefreshInterval
	pimInterfaceTable		pimInterfaceTable
	pimInterfaceEntry		pimInterfaceEntry
	pimInterfaceIfIndex		pimInterfaceIfIndex
	pimInterfaceIPVersion		pimInterfaceIPVersion
	pimInterfaceAddressType		pimInterfaceAddressType
	pimInterfaceAddress		pimInterfaceAddress
	pimInterfaceDR		pimInterfaceDR
	pimInterfaceHelloInterval		pimInterfaceHelloInterval
	pimInterfaceTrigHelloInterval		pimInterfaceTrigHelloInterval
	pimInterfaceJoinPruneInterval		pimInterfaceJoinPruneInterval
	skipping to change at page 70, line 20 ¶		skipping to change at page 77, line 34 ¶
	pimInterfaceDRPriority		pimInterfaceDRPriority
	pimInterfaceLanDelayEnabled		pimInterfaceLanDelayEnabled
	pimInterfaceEffectPropagDelay		pimInterfaceEffectPropagDelay
	pimInterfaceEffectOverrideIvl		pimInterfaceEffectOverrideIvl
	pimInterfaceSuppressionEnabled		pimInterfaceSuppressionEnabled
	pimInterfaceBidirCapable		pimInterfaceBidirCapable
	pimInterfaceDRPriorityEnabled		pimInterfaceDRPriorityEnabled
	pimInterfaceDomainBorder		pimInterfaceDomainBorder
	pimInterfaceStatus		pimInterfaceStatus
	pimInterfaceStubInterface		pimInterfaceStubInterface
			pimInterfacePruneLimitInterval
			pimInterfaceSRPriorityEnabled
	pimNeighborTable		pimNeighborTable
	pimNeighborEntry		pimNeighborEntry
	pimNeighborIfIndex		pimNeighborIfIndex
	pimNeighborAddressType		pimNeighborAddressType
	pimNeighborAddress		pimNeighborAddress
	pimNeighborUpTime		pimNeighborUpTime
	pimNeighborExpiryTime		pimNeighborExpiryTime
	pimNeighborLanPruneDelayPresent		pimNeighborLanPruneDelayPresent
	pimNeighborPropagationDelay		pimNeighborPropagationDelay
	pimNeighborOverrideInterval		pimNeighborOverrideInterval
	pimNeighborTBit		pimNeighborTBit
	pimNeighborGenerationIDPresent		pimNeighborGenerationIDPresent
	pimNeighborGenerationIDValue		pimNeighborGenerationIDValue
	pimNeighborBidirCapable		pimNeighborBidirCapable
	pimNeighborDRPriorityPresent		pimNeighborDRPriorityPresent
	pimNeighborDRPriority		pimNeighborDRPriority
			pimNeighborSRCapable
	pimNbrSecAddressTable		pimNbrSecAddressTable
	pimNbrSecAddressEntry		pimNbrSecAddressEntry
	pimNbrSecAddressIfIndex		pimNbrSecAddressIfIndex
	pimNbrSecAddressType		pimNbrSecAddressType
	pimNbrSecAddressPrimary		pimNbrSecAddressPrimary
	pimNbrSecAddress		pimNbrSecAddress
	pimStarGTable		pimStarGTable
	pimStarGEntry		pimStarGEntry
	pimStarGAddressType		pimStarGAddressType
	pimStarGGrpAddress		pimStarGGrpAddress
	skipping to change at page 72, line 6 ¶		skipping to change at page 79, line 23 ¶
	pimSGRPFRouteAddress		pimSGRPFRouteAddress
	pimSGRPFRoutePrefixLength		pimSGRPFRoutePrefixLength
	pimSGRPFRouteMetricPref		pimSGRPFRouteMetricPref
	pimSGRPFRouteMetric		pimSGRPFRouteMetric
	pimSGSPTBit		pimSGSPTBit
	pimSGKeepaliveTimer		pimSGKeepaliveTimer
	pimSGDRRegisterState		pimSGDRRegisterState
	pimSGDRRegisterStopTimer		pimSGDRRegisterStopTimer
	pimSGRPRegisterPMBRAddressType		pimSGRPRegisterPMBRAddressType
	pimSGRPRegisterPMBRAddress		pimSGRPRegisterPMBRAddress
			pimSGUpstreamPruneState
			pimSGUpstreamPruneLimitTimer
			pimSGOriginatorState
			pimSGSourceActiveTimer
			pimSGStateRefreshTimer
	pimSGITable		pimSGITable
	pimSGIEntry		pimSGIEntry
	pimSGIIfIndex		pimSGIIfIndex
	pimSGIUpTime		pimSGIUpTime
	pimSGILocalMembership		pimSGILocalMembership
	pimSGIJoinPruneState		pimSGIJoinPruneState
	pimSGIPrunePendingTimer		pimSGIPrunePendingTimer
	pimSGIJoinExpiryTimer		pimSGIJoinExpiryTimer
	pimSGIAssertState		pimSGIAssertState
	pimSGIAssertTimer		pimSGIAssertTimer
	skipping to change at page 73, line 24 ¶		skipping to change at page 80, line 46 ¶
	pimAnycastRPSetLocalRouter		pimAnycastRPSetLocalRouter
	pimGroupMappingTable		pimGroupMappingTable
	pimGroupMappingEntry		pimGroupMappingEntry
	pimGroupMappingOrigin		pimGroupMappingOrigin
	pimGroupMappingAddressType		pimGroupMappingAddressType
	pimGroupMappingGrpAddress		pimGroupMappingGrpAddress
	pimGroupMappingGrpPrefixLength		pimGroupMappingGrpPrefixLength
	pimGroupMappingRPAddress		pimGroupMappingRPAddress
	pimGroupMappingPimMode		pimGroupMappingPimMode
	pimGroupMappingPrecedence		pimGroupMappingPrecedence
	pimUnexpectedRegisterAddressType
	pimUnexpectedRegisterOrigin		There is also a specific danger arising from the notification
	pimUnexpectedRegisterGroup		pimInvalidRegister. This is originated by devices that receive an
	pimUnexpectedRegisterRp		incorrect unicast-encapsulted multicast data packet, which poses a
	pimUnexpectedJoinPruneAddressType		clear danger of propagating a DoS (Denial of Service) attack from the
	pimUnexpectedJoinPruneOrigin		data or control plane to the network management plane. The following
	pimUnexpectedJoinPruneGroup		steps are taken to guard against this.
	pimUnexpectedJoinPruneRp
	pimRPMappingChangeType		1. The notification is disabled by default. The writeable field
			pimInvalidRegisterTrapPeriod must be set in order to enable it.
			2. The syntax of pimInvalidRegisterTrapPeriod prevents any given
			device from originating the notification more frequently than
			once every 10 seconds.
			3. The counter pimInvalidRegisterMsgsRcvd provides equivalent
			function to the notification. Management applications are
			encouraged to monitor this counter in preference to enabling the
			notification.
			The same measures are taken in respect of pimInvalidJoinPrune, though
			as this notification can only arise as a result of non-routable
			control packets, the risk is not so acute.
	SNMP versions prior to SNMPv3 did not include adequate security.		SNMP versions prior to SNMPv3 did not include adequate security.
	Even if the network itself is secure (for example by using IPSec),		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		even then, there is no control as to who on the secure network is
	allowed to access and GET/SET (read/change/create/delete) the objects		allowed to access and GET/SET (read/change/create/delete) the objects
	in this MIB module.		in this MIB module.
	It is RECOMMENDED that implementers consider the security features as		It is RECOMMENDED that implementers consider the security features as
	provided by the SNMPv3 framework (see [RFC3410], section 8),		provided by the SNMPv3 framework (see [RFC3410], section 8),
	including full support for the SNMPv3 cryptographic mechanisms (for		including full support for the SNMPv3 cryptographic mechanisms (for
	skipping to change at page 74, line 18 ¶		skipping to change at page 82, line 6 ¶
	requested to assign { mib-2 XXX } to the PIM-STD-MIB module specified		requested to assign { mib-2 XXX } to the PIM-STD-MIB module specified
	in this document.		in this document.
	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.
	8. References		8. References
	8.1 Normative References		8.1 Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 2434,		IANA Considerations Section in RFCs", BCP 26, RFC 2434,
	skipping to change at page 74, line 46 ¶		skipping to change at page 82, line 35 ¶
	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
			Independent Multicast - Dense Mode (PIM-DM): Protocol
			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.
	[I-D.ietf-pim-sm-v2-new]		[I-D.ietf-pim-sm-v2-new]
	Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,		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)",		Protocol Specification (Revised)",
	draft-ietf-pim-sm-v2-new-11 (work in progress),		draft-ietf-pim-sm-v2-new-11 (work in progress),
	October 2004.		October 2004.
	[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-07 (work in progress),		PIM)", draft-ietf-pim-bidir-07 (work in progress),
	March 2005.		March 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-05 (work in progress),		draft-ietf-pim-sm-bsr-05 (work in progress),
	February 2005.		February 2005.
	[I-D.ietf-pim-anycast-rp]		[I-D.ietf-pim-anycast-rp]
	Farinacci, D., and Cai, Y., "Anycast-RP using PIM",		Farinacci, D., and Cai, Y., "Anycast-RP using PIM",
	draft-ietf-pim-anycast-rp-04 (work in progress),		draft-ietf-pim-anycast-rp-04 (work in progress),
	August 2005.		August 2005.
	[RFC3569] Bhattacharyya, S., "An Overview of Source-Specific		[I-D.mcwalter-ip-mcast-mib]
	Multicast (SSM)", RFC 3569, July 2003.		McWalter, D., Thaler, D., and Kessler, A.,
			"IP Multicast MIB" draft-mcwalter-ip-mcast-mib-01,
	[RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous		(work in progress), December 2005.
	Point (RP) Address in an IPv6 Multicast Address",
	RFC 3956, November 2004.
	8.2 Informative References		8.2 Informative References
	[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
	"Introduction and Applicability Statements for Internet-
	Standard Management Framework", RFC 3410, December 2002.
	[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.
	[I-D.mcwalter-ip-mcast-mib]		[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
	McWalter, D., Thaler, D., and Kessler, A.,		"Introduction and Applicability Statements for Internet-
	"IP Multicast MIB" draft-mcwalter-ip-mcast-mib-00,		Standard Management Framework", RFC 3410, December 2002.
	(work in progress), September 2005.
	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
	skipping to change at page 77, line 41 ¶		skipping to change at page 85, line 41 ¶
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,		ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Copyright Statement		Copyright Statement
	Copyright (C) The Internet Society (2005). This document is subject		Copyright (C) The Internet Society (2006). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and		to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.		except as set forth therein, the authors retain all their rights.
	Acknowledgment		Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is currently provided by the
	Internet Society.		Internet Society.
End of changes. 68 change blocks.
	347 lines changed or deleted		731 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/