< draft-ietf-l3vpn-mpls-vpn-mib-06.txt		draft-ietf-l3vpn-mpls-vpn-mib-07.txt >
	IETF Internet Draft Thomas D. Nadeau		IETF Internet Draft Thomas D. Nadeau
	Expires: August 2005 Cisco Systems, Inc.		Expires: October 2005 Cisco Systems, Inc.
	Document: draft-ietf-l3vpn-mpls-vpn-mib-06.txt		Document: draft-ietf-l3vpn-mpls-vpn-mib-07.txt
	Harmen Van Der Linde		Harmen Van Der Linde
	AT&T		AT&T
	Editors		Editors
	February 2005		April 2005
	MPLS/BGP Layer 3 Virtual Private Network		MPLS/BGP Layer 3 Virtual Private Network
	Management Information Base		Management Information Base
	Status of this Memo		Status of this Memo
	Internet-Drafts are working documents of the Internet Engineering		By submitting this Internet-Draft, each author represents that
	Task Force (IETF), its areas, and its working groups. Note that other		any applicable patent or other IPR claims of which he or she is
	groups may also distribute working documents as Internet-Drafts.		aware 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.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are working documents of the Internet Engineering
	and may be updated, replaced, or obsoleted by other documents at any		Task Force (IETF), its areas, and its working groups. Note that other
	time. It is inappropriate to use Internet-Drafts as reference		groups may also distribute working documents as Internet-Drafts.
	material or to cite them other than a "work in progress."
	The list of current Internet-Drafts can be accessed at		Internet-Drafts are draft documents valid for a maximum of six months
	http://www.ietf.org/1id-abstracts.html		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."
	The list of Internet-Draft Shadow Directories can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/shadow.html		http://www.ietf.org/1id-abstracts.html
	By submitting this Internet-Draft, I certify that any applicable		The list of Internet-Draft Shadow Directories can be accessed at
	patent or other IPR claims of which I am aware have been disclosed, or		http://www.ietf.org/shadow.html.
	will be disclosed, and any of which I become aware will be disclosed,
	in accordance with RFC 3668.
	Abstract		Abstract
	This memo defines an portion of the Management		This memo defines an portion of the Management
	Information Base (MIB) for use with network management protocols		Information Base (MIB) for use with network management protocols
	in the Internet community. In particular, it describes managed		in the Internet community. In particular, it describes managed
	objects to configure and/or monitor Multi-protocol Label		objects to configure and/or monitor Multi-protocol Label
	Switching Layer-3 Virtual Private Networks on a		Switching Layer-3 Virtual Private Networks on a
	Multi-Protocol Label Switching (MPLS) Label Switching Router		Multi-Protocol Label Switching (MPLS) Label Switching Router
	(LSR) supporting this feature.		(LSR) supporting this feature.
	Contents		Contents
	1.0 Abstract..........................................................2		1. Abstract..........................................................2
	2.0 Introduction......................................................2		2. Introduction......................................................2
	3.0 Terminology.......................................................3		3. Terminology.......................................................3
	4.0 The SNMP Management Framework.....................................3		4. The Internet-Standard Management Framework........................3
	5.0 Assumptions and Prerequisites.....................................3		5. Assumptions and Prerequisites.....................................3
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205		6. Brief Description of MIB Objects..................................4
			6. mplsL3VpnVrfTable................................................4
	6.0 Brief Description of MIB Objects..................................4		6. mplsL3VpnIfConfTable.............................................4
	6.1 mplsL3VpnVrfTable................................................4		6. mplsL3VpnVrfPerfTable............................................5
	6.2 mplsL3VpnIfConfTable.............................................4		6. mplsL3VpnVrfRouteTable...........................................5
	6.3 mplsL3VpnVrfPerfTable............................................5		6. mplsVpnVrfRTTable................................................5
	6.4 mplsL3VpnVrfRouteTable...........................................5		7. Example of MPLS L3VPN Setup.......................................5
	6.5 MplsVpnVrfRTTable................................................5		8. MPLS-L3VPN-MIB Module Definition..................................6
	7.0 Example of MPLS L3VPN Setup.......................................5		9. Acknowledgements.................................................37
	8.0 MPLS-L3VPN-MIB Module Definition..................................6		10. Intellectual Property Statement.................................37
	9.0 Acknowledgements.................................................37		11. References......................................................37
	10.0 Intellectual Property Statement.................................37
	11.0 References......................................................37
	11.1 Normative References............................................37		11.1 Normative References............................................37
	11.2 Informative References..........................................37		11.2 Informative References..........................................37
	12.0 Editors' Addresses..............................................40		12. Editors' Addresses..............................................40
	13.0 Contributors' Addresses.........................................40		13. Contributors' Addresses.........................................40
	14.0 Dedication......................................................41		14. Dedication......................................................41
	15.0 Full Copyright Statement........................................41		15. Full Copyright Statement........................................41
	16.0 Security Considerations.........................................41		16. Security Considerations.........................................41
	17. Intellectual Property Notice....................................41		17. Intellectual Property Statement.................................41
	18.0 IANA Considerations.............................................41		18. IANA Considerations.............................................41
	18.1 IANA Considerations for MPLS-L3VPN-MIB..........................41		18.1 IANA Considerations for MPLS-L3VPN-MIB..........................41
	2.0 Introduction		2. Introduction
	This memo defines an portion of the Management		This memo defines an portion of the Management
	Information Base (MIB) for use with network management protocols		Information Base (MIB) for use with network management protocols
	in the Internet community. In particular, it describes managed		in the Internet community. In particular, it describes managed
	objects to configure and/or monitor Multi-protocol Label		objects to configure and/or monitor Multi-protocol Label
	Switching Layer-3 Virtual Private Networks on a		Switching Layer-3 Virtual Private Networks on a
	Multi-Protocol Label Switching (MPLS) Label Switching Router		Multi-Protocol Label Switching (MPLS) Label Switching Router
	(LSR) supporting this feature.		(LSR) supporting this feature.
			This document adopts the definitions, acronyms and mechanisms
			described in [RFC2547bis]. Unless otherwise stated, the mechanisms of
			[RFC2547bis] apply and will not be re-described here.
	Comments should be made directly to the MPLS mailing list at		Comments should be made directly to the MPLS mailing list at
	mpls@uu.net and the Layer-3 VPN (L3VPN) WG at l3vpn@ietf.org.		mpls@uu.net and the Layer-3 VPN (L3VPN) WG at l3vpn@ietf.org.
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
	NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and		NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in		"OPTIONAL" in this document are to be interpreted as described in
	RFC 2119, reference [RFC2119].		[RFC2119].
	3.0 Terminology		3. Terminology
	This document uses terminology from the document describing the MPLS		This document uses terminology from the document describing the MPLS
	architecture [MPLSArch] and from the document describing MPLS Layer-3		architecture [RFC3031] and from the document describing MPLS Layer-3
	VPNs (L3VPN) [MPLSBGPVPN], as well as the MPLS architecture		VPNs (L3VPN) [RFC2547bis], as well as the MPLS architecture
	[RFC3031].		[RFC3031].
	Throughout this document, the use of the terms "Provider Edge (PE)		Throughout this document, the use of the terms "Provider Edge (PE)
	and Customer Edge (CE) or PE/CE" will be replaced by PE in all cases		and Customer Edge (CE) or PE/CE" will be replaced by PE in all cases
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	except when a network device is a CE when used in the carrier of		except when a network device is a CE when used in the carrier of
	carriers model.		carriers model.
	4.0 The SNMP Management Framework		4. The Internet-Standard Management Framework
	For a detailed overview of the documents that describe the current		For a detailed overview of the documents that describe the current
	Internet-Standard Management Framework, please refer to section 7 of		Internet-Standard Management Framework, please refer to section 7 of
	RFC 3410 [RFC3410].		RFC 3410 [RFC3410].
	Managed objects are accessed via a virtual information store, termed		Managed objects are accessed via a virtual information store, termed
	the Management Information Base or MIB. MIB objects are generally		the Management Information Base or MIB. MIB objects are generally
	accessed through the Simple Network Management Protocol (SNMP).		accessed through the Simple Network Management Protocol (SNMP).
	Objects in the MIB are defined using the mechanisms defined in the		Objects in the MIB are defined using the mechanisms defined in the
	Structure of Management Information (SMI). This memo specifies a MIB		Structure of Management Information (SMI). This memo specifies a MIB
	module that is compliant to the SMIv2, which is described in STD 58,		module that is compliant to the SMIv2, which is described in STD 58,
	RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580		RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
	[RFC2580].		[RFC2580].
	5.0 Assumptions and Prerequisites		5. Assumptions and Prerequisites
	It is assumed that certain things are configured and operational in		It is assumed that certain things are configured and operational in
	order for the tables and objects described in this MIB to function		order for the tables and objects described in this MIB to function
	correctly. These things are outlined below:		correctly. These things are outlined below:
	- MPLS in general, must be configured and operational.		- MPLS in general, must be configured and operational.
	- LDP paths or traffic engineered tunnels [RFC3812] should be		- LDP paths or traffic engineered tunnels [RFC3812] should be
	configured between PEs and CEs.		configured between PEs and CEs.
	6.0 Brief Description of MIB Objects		6. Brief Description of MIB Objects
	The following subsections describe the purpose of each of the objects		The following subsections describe the purpose of each of the objects
	contained in the MPLS-VPN-MIB.		contained in the MPLS-L3VPN-STD-MIB.
	6.1 mplsL3VpnVrfTable		6.1 mplsL3VpnVrfTable
	This table represents the MPLS L3VPNs that are configured.		This table represents the MPLS L3VPNs that are configured.
	A Network Management System (NMS) or SNMP agent creates an		A Network Management System (NMS) or SNMP agent creates an
	entry in this table for every MPLS L3VPN configured on		entry in this table for every MPLS L3VPN configured on
	the LSR being examined. The VPR that is configured at		the LSR being examined. The VRF that is configured at
	a particular device represents an instance of some VPN, but		a particular device represents an instance of some VPN, but
	not the entire VPN (unless it is the only VRF, of course).		not the entire VPN (unless it is the only VRF, of course).
	The collective set of VRF instances comprises the actual		The collective set of VRF instances comprises the actual
	VPN. This information is typically only known in its entirety		VPN. This information is typically only known in its entirety
	at the NMS. That is, specific devices generally only know		at the NMS. That is, specific devices generally only know
	of their local VRF information, but not that of other LSRs'		of their local VRF information, but not that of other LSRs'
	VRFs.		VRFs.
	6.2 mplsL3VpnIfConfTable		6.2 mplsL3VpnIfConfTable
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	This table represents the MPLS L3VPN-enabled interfaces		This table represents the MPLS L3VPN-enabled interfaces
	that are associated with a specific VRF as represented in		that are associated with a specific VRF as represented in
	the aforementioned mplsL3VpnVrfTable. Each entry in this table		the aforementioned mplsL3VpnVrfTable. Each entry in this table
	corresponds to an entry in the Interfaces MIB. In addition,		corresponds to an entry in the Interfaces MIB. In addition,
	each entry extends its corresponding entry in the Interface		each entry extends its corresponding entry in the Interface
	MIB to contain specific MPLS L3VPN information. Due to this		MIB to contain specific MPLS L3VPN information. Due to this
	correspondence, certain objects such as traffic counters		correspondence, certain objects such as traffic counters
	are not found in this MIB to avoid overlap, but instead		are not found in this MIB to avoid overlap, but instead
	are found in the Interfaces MIB [RFC2863].		are found in the Interfaces MIB [RFC2863].
	6.3 mplsL3VpnVrfPerfTable		6.3 mplsL3VpnVrfPerfTable
	This table contains objects to measure the performance of		This table contains objects to measure the performance of
	MPLS L3VPNs and augments the mplsL3VpnVrfConfTable. High		MPLS L3VPNs and augments the mplsL3VpnVrfTable. High
	capacity counters are provided for objects that are likely		capacity counters are provided for objects that are likely
	to wrap around quickly on objects such as high-speed interface		to wrap around quickly on objects such as high-speed interface
	counters.		counters.
	6.4 mplsL3VpnVrfRouteTable		6.4 mplsL3VpnVrfRouteTable
	The table contains the objects necessary to configure and monitor		The table contains the objects necessary to configure and monitor
	routes used by a particular VRF. This includes a cross-connect		routes used by a particular VRF. This includes a cross-connect
	pointer into the MPLS-LSR-STD-MIB's mplsXCTable, which may be		pointer into the MPLS-LSR-STD-MIB's mplsXCTable, which may be
	used to refer that entry to its label stack used to label		used to refer that entry to its label stack used to label
	switch that entry.		switch that entry.
	6.5 MplsVpnVrfRTTable		6.5 MplsVpnVrfRTTable
	The table contains the objects necessary to configure and monitor		The table contains the objects necessary to configure and monitor
	route targets for a particular VRF.		route targets for a particular VRF.
	7.0 Example of MPLS L3VPN Setup		7. Example of MPLS L3VPN Setup
	In this section, we provide a brief example of using the MIB		In this section, we provide a brief example of using the MIB
	objects described in the following section. While this example		objects described in the following section. While this example
	is not meant to illustrate every nuance of the MIB, it is intended		is not meant to illustrate every nuance of the MIB, it is intended
	as an aid to understanding some of the key concepts. It is our		as an aid to understanding some of the key concepts. It is our
	intent that it is read only after the reader has gone through		intent that it is read only after the reader has gone through
	the MIB itself.		the MIB itself.
	This configuration is under the assumption that 1) MPLS has been		This configuration is under the assumption that 1) MPLS has been
	pre-configured in the network, through enabling LDP or RSVP-TE.		pre-configured in the network, through enabling LDP or RSVP-TE.
	2) OSPF or ISIS has been pre-configured. 3) BGP sessions have been		2) OSPF or ISIS has been pre-configured. 3) BGP sessions have been
	established between PEs.		established between PEs.
	Defining the VRF, the route target and route distinguisher:		Defining the VRF, the route target and route distinguisher:
	In mplsL3VpnVrfTable:		In mplsL3VpnVrfTable:
	{		{
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	mplsL3VpnVrfName = "RED",		mplsL3VpnVrfName = "RED",
	mplsL3VpnVrfDescription = "Intranet of Company ABC",		mplsL3VpnVrfDescription = "Intranet of Company ABC",
	mplsL3VpnVrfRD = "100:1", -- octet string		mplsL3VpnVrfRD = "100:1", -- octet string
	mplsL3VpnVrfRowStatus = createAndGo(4)		mplsL3VpnVrfRowStatus = createAndGo(4)
	}		}
	In mplsL3VpnVrfRouteTTable:		In mplsL3VpnVrfRouteTable:
	{		{
	mplsL3VpnVrfRTRowStatus."Red"."100:1".import = createAndGo,		mplsL3VpnVrfRTRowStatus."Red"."100:1".import = createAndGo,
	mplsL3VpnVrfRTRowStatus."Red"."100:1".export = createAndGo		mplsL3VpnVrfRTRowStatus."Red"."100:1".export = createAndGo
	}		}
	8.0 MPLS-L3VPN-STD-MIB Module Definition		8. MPLS-L3VPN-STD-MIB Module Definition
	MPLS-L3VPN-STD-MIB DEFINITIONS ::= BEGIN		MPLS-L3VPN-STD-MIB DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,		MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
	Integer32, Counter32, Unsigned32,		Integer32, Counter32, Unsigned32, Gauge32
	Gauge32
	FROM SNMPv2-SMI -- [RFC2578]		FROM SNMPv2-SMI -- [RFC2578]
	MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP		MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
	FROM SNMPv2-CONF -- [RFC2580]		FROM SNMPv2-CONF -- [RFC2580]
	TEXTUAL-CONVENTION, TruthValue, RowStatus,		TEXTUAL-CONVENTION, TruthValue, RowStatus,
	TimeStamp, StorageType		TimeStamp, StorageType
	FROM SNMPv2-TC -- [RFC2579]		FROM SNMPv2-TC -- [RFC2579]
	InterfaceIndex, InterfaceIndexOrZero		InterfaceIndex, InterfaceIndexOrZero
	FROM IF-MIB -- [RFC2863]		FROM IF-MIB -- [RFC2863]
	VPNIdOrZero		VPNIdOrZero
	FROM VPN-TC-STD-MIB		FROM VPN-TC-STD-MIB
	SnmpAdminString		SnmpAdminString
	FROM SNMP-FRAMEWORK-MIB -- [RFC3411]		FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
	IANAipRouteProtocol		IANAipRouteProtocol
	FROM IANA-RTPROTO-MIB		FROM IANA-RTPROTO-MIB -- [RTPROTO]
	InetAddress, InetAddressType,		InetAddress, InetAddressType,
	InetAddressPrefixLength,		InetAddressPrefixLength,
	InetAutonomousSystemNumber		InetAutonomousSystemNumber
	FROM INET-ADDRESS-MIB -- [RFC3291]		FROM INET-ADDRESS-MIB -- [RFC4001]
	mplsStdMIB		mplsStdMIB
	FROM MPLS-TC-STD-MIB -- [RFC3811]		FROM MPLS-TC-STD-MIB -- [RFC3811]
	MplsIndexType		MplsIndexType
	FROM MPLS-LSR-STD-MIB -- [RFC3813]		FROM MPLS-LSR-STD-MIB -- [RFC3813]
	;		;
	mplsL3VpnMIB MODULE-IDENTITY		mplsL3VpnMIB MODULE-IDENTITY
	LAST-UPDATED "200502011200Z" -- 01 February 2005 12:00:00 GMT		LAST-UPDATED "200504011200Z" -- 01 April 2005 12:00:00 GMT
	ORGANIZATION "IETF Layer-3 Virtual Private		ORGANIZATION "IETF Layer-3 Virtual Private
	Networks Working Group."		Networks Working Group."
	CONTACT-INFO		CONTACT-INFO
	" Thomas D. Nadeau		" Thomas D. Nadeau
	tnadeau@cisco.com		tnadeau@cisco.com
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	Harmen van der Linde		Harmen van der Linde
	hvdl@att.com		hvdl@att.com
	Luyuan Fang
	luyuanfang@att.com
	Stephen Brannon
	Fabio M. Chiussi
	fabio@bell-labs.com
	Joseph Dube
	Martin Tatham
	martin.tatham@bt.com
	Comments and discussion to l3vpn@ietf.org"		Comments and discussion to l3vpn@ietf.org"
	DESCRIPTION		DESCRIPTION
	"This MIB contains managed object definitions for the		"This MIB contains managed object definitions for the
	Layer-3 Multiprotocol Label Switching Virtual		Layer-3 Multiprotocol Label Switching Virtual
	Private Networks.		Private Networks.
	Copyright (C) The Internet Society (2004). This		Copyright (C) The Internet Society (2005). This
	version of this MIB module is part of RFCXXX; see		version of this MIB module is part of RFCXXX; see
	the RFC itself for full legal notices."		the RFC itself for full legal notices."
	-- Revision history.		-- Revision history.
	REVISION		REVISION
	"200502011200Z" -- 01 February 2005 12:00:00 GMT		"200504011200Z" -- 01 April 2005 12:00:00 GMT
	DESCRIPTION		DESCRIPTION
	"Initial version. Published as RFC xxxx." -- RFC-editor pls fill in xxx		"Initial version. Published as RFC xxxx." -- RFC-editor pls fill in xxx
	::= { mplsStdMIB xxxx } -- assigned by IANA, see section 18.1 for details		::= { mplsStdMIB 9999 } -- assigned by IANA, see section 18.1 for details
	-- Textual Conventions.		-- Textual Conventions.
	MplsL3VpnName ::= TEXTUAL-CONVENTION		MplsL3VpnName ::= TEXTUAL-CONVENTION
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An identifier that is assigned to each MPLS/BGP VPN and		"An identifier that is assigned to each MPLS/BGP VPN and
	is used to uniquely identify it. This is assigned by the		is used to uniquely identify it. This is assigned by the
	system operator or NMS and SHOULD be unique throughout		system operator or NMS and SHOULD be unique throughout
	the MPLS domain. If this is the case, then this identifier		the MPLS domain. If this is the case, then this identifier
	can then be used at any LSR within a specific MPLS domain		can then be used at any LSR within a specific MPLS domain
	to identify this MPLS/BGP VPN. It may also be possible to		to identify this MPLS/BGP VPN. It may also be possible to
	preserve the uniqueness of this identifier across MPLS		preserve the uniqueness of this identifier across MPLS
	domain boundaries, in which case this identifier can then		domain boundaries, in which case this identifier can then
	be used to uniquely identify MPLS/BGP VPNs on a more global		be used to uniquely identify MPLS/BGP VPNs on a more global
	basis. This object MAY be set to the VPN ID as defined in		basis. This object MAY be set to the VPN ID as defined in
	RFC 2685."		RFC 2685."
	REFERENCE		REFERENCE
	"RFC 2685 Fox B., et al, 'Virtual Private		"RFC 2685 Fox B., et al, 'Virtual Private
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	Networks Identifier', September 1999."		Networks Identifier', September 1999."
	SYNTAX OCTET STRING (SIZE (0..31))		SYNTAX OCTET STRING (SIZE (0..31))
	MplsL3VpnRouteDistinguisher ::= TEXTUAL-CONVENTION		MplsL3VpnRouteDistinguisher ::= TEXTUAL-CONVENTION
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Syntax for a route distinguisher and route target		"Syntax for a route distinguisher and route target
	as defined in RFC2547."		as defined in [RFC2547bis]."
	REFERENCE		REFERENCE
	"Rosen, E., Rekhter, Y., et al., 'BGP/MPLS VPNs',		"[RFC2547bis]"
	RFC2547, March 1999."
	SYNTAX OCTET STRING(SIZE (0..256))		SYNTAX OCTET STRING(SIZE (0..256))
	MplsL3VpnRtType ::= TEXTUAL-CONVENTION		MplsL3VpnRtType ::= TEXTUAL-CONVENTION
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Used to define the type of a route target usage.		"Used to define the type of a route target usage.
	Route targets can be specified to be imported,		Route targets can be specified to be imported,
	exported or both. For a complete definition of a		exported or both. For a complete definition of a
	route target see RFC2547."		route target see [RFC2547bis]."
	REFERENCE		REFERENCE
	"Rosen, E., Rekhter, Y., et al., 'BGP/MPLS VPNs',		"[RFC2547bis]"
	RFC2547, March 1999."
	SYNTAX INTEGER { import(1), export(2), both(3) }		SYNTAX INTEGER { import(1), export(2), both(3) }
	-- Top level components of this MIB.		-- Top level components of this MIB.
	mplsL3VpnNotifications OBJECT IDENTIFIER ::= { mplsL3VpnMIB 0 }		mplsL3VpnNotifications OBJECT IDENTIFIER ::= { mplsL3VpnMIB 0 }
	mplsL3VpnObjects OBJECT IDENTIFIER ::= { mplsL3VpnMIB 1 }		mplsL3VpnObjects OBJECT IDENTIFIER ::= { mplsL3VpnMIB 1 }
	mplsL3VpnScalars OBJECT IDENTIFIER ::= { mplsL3VpnObjects 1 }		mplsL3VpnScalars OBJECT IDENTIFIER ::= { mplsL3VpnObjects 1 }
	mplsL3VpnConf OBJECT IDENTIFIER ::= { mplsL3VpnObjects 2 }		mplsL3VpnConf OBJECT IDENTIFIER ::= { mplsL3VpnObjects 2 }
	mplsL3VpnPerf OBJECT IDENTIFIER ::= { mplsL3VpnObjects 3 }		mplsL3VpnPerf OBJECT IDENTIFIER ::= { mplsL3VpnObjects 3 }
	mplsL3VpnRoute OBJECT IDENTIFIER ::= { mplsL3VpnObjects 4 }		mplsL3VpnRoute OBJECT IDENTIFIER ::= { mplsL3VpnObjects 4 }
	mplsL3VpnConformance OBJECT IDENTIFIER ::= { mplsL3VpnMIB 3 }		mplsL3VpnConformance OBJECT IDENTIFIER ::= { mplsL3VpnMIB 2 }
	--		--
	-- Scalar Objects		-- Scalar Objects
	--		--
	mplsL3VpnConfiguredVrfs OBJECT-TYPE		mplsL3VpnConfiguredVrfs OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of VRFs which are configured on this node."		"The number of VRFs which are configured on this node."
	::= { mplsL3VpnScalars 1 }		::= { mplsL3VpnScalars 1 }
	mplsL3VpnActiveVrfs OBJECT-TYPE		mplsL3VpnActiveVrfs OBJECT-TYPE
	SYNTAX Gauge32		SYNTAX Gauge32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	DESCRIPTION		DESCRIPTION
	"The number of VRFs which are active on this node.		"The number of VRFs which are active on this node.
	That is, those VRFs whose corresponding mplsL3VpnVrfOperStatus		That is, those VRFs whose corresponding mplsL3VpnVrfOperStatus
	object value is equal to operational (1)."		object value is equal to operational (1)."
	::= { mplsL3VpnScalars 2 }		::= { mplsL3VpnScalars 2 }
	mplsL3VpnConnectedInterfaces OBJECT-TYPE		mplsL3VpnConnectedInterfaces OBJECT-TYPE
	SYNTAX Gauge32		SYNTAX Gauge32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of interfaces connected to a VRF."		"Total number of interfaces connected to a VRF."
	::= { mplsL3VpnScalars 3 }		::= { mplsL3VpnScalars 3 }
	mplsL3VpnNotificationEnable OBJECT-TYPE		mplsL3VpnNotificationEnable OBJECT-TYPE
	SYNTAX TruthValue		SYNTAX TruthValue
	MAX-ACCESS read-write		MAX-ACCESS read-write
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"If this object is true, then it enables the		"If this object is true, then it enables the
	generation of all notifications defined in		generation of all notifications defined in
	this MIB. This object's value should be		this MIB. This object's value should be
	preserved across agent re-boots."		preserved across agent re-boots."
	REFERENCE		REFERENCE
	"See also RFC3413 for explanation that		"See also [RFC3413] for explanation that
	notifications are under the ultimate control of the		notifications are under the ultimate control of the
	MIB modules in this document."		MIB modules in this document."
	DEFVAL { false }		DEFVAL { false }
	::= { mplsL3VpnScalars 4 }		::= { mplsL3VpnScalars 4 }
	mplsL3VpnVrfConfMaxPossRts OBJECT-TYPE		mplsL3VpnVrfConfMaxPossRts OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	skipping to change at page 9, line 4 ¶		skipping to change at page 8, line 51 ¶
	be allowed by the device."		be allowed by the device."
	::= { mplsL3VpnScalars 5 }		::= { mplsL3VpnScalars 5 }
	mplsL3VpnVrfConfRteMxThrshTime OBJECT-TYPE		mplsL3VpnVrfConfRteMxThrshTime OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	UNITS "seconds"		UNITS "seconds"
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Denotes the interval in seconds, at which the route max threshold		"Denotes the interval in seconds, at which the route max threshold
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	notification may be re-issued after the maximum value has been		notification may be re-issued after the maximum value has been
	exceeded (or has been reached if mplsL3VpnVrfConfMaxRoutes and		exceeded (or has been reached if mplsL3VpnVrfConfMaxRoutes and
	mplsL3VpnVrfConfHighRteThresh are equal) and the initial		mplsL3VpnVrfConfHighRteThresh are equal) and the initial
	notification has been issued. This value is intended to prevent		notification has been issued. This value is intended to prevent
	continuous generation of notifications by an agent in the event		continuous generation of notifications by an agent in the event
	that routes are continually added to a VRF after it has reached		that routes are continually added to a VRF after it has reached
	its maximum value. If this value is set to 0, the agent should		its maximum value. If this value is set to 0, the agent should
	only issue a single notification at the time that the maxium		only issue a single notification at the time that the maxium
	threshold has been reached, and should not issue any more		threshold has been reached, and should not issue any more
	notifications until the value of routes has fallen below the		notifications until the value of routes has fallen below the
	skipping to change at page 9, line 29 ¶		skipping to change at page 9, line 23 ¶
	DEFVAL { 0 }		DEFVAL { 0 }
	::= { mplsL3VpnScalars 6 }		::= { mplsL3VpnScalars 6 }
	mplsL3VpnIllLblRcvThrsh OBJECT-TYPE		mplsL3VpnIllLblRcvThrsh OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-write		MAX-ACCESS read-write
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of illegally received labels above which		"The number of illegally received labels above which
	the mplsNumVrfSecIllglLblThrshExcd notification		the mplsNumVrfSecIllglLblThrshExcd notification
	is issued."		is issued. The persistence of this value mimics
			that of the device's configuration."
	::= { mplsL3VpnScalars 7 }		::= { mplsL3VpnScalars 7 }
	-- VPN Interface Configuration Table		-- VPN Interface Configuration Table
	mplsL3VpnIfConfTable OBJECT-TYPE		mplsL3VpnIfConfTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MplsL3VpnIfConfEntry		SYNTAX SEQUENCE OF MplsL3VpnIfConfEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This table specifies per-interface MPLS capability		"This table specifies per-interface MPLS capability
	skipping to change at page 10, line 4 ¶		skipping to change at page 9, line 52 ¶
	DESCRIPTION		DESCRIPTION
	"An entry in this table is created by an LSR for		"An entry in this table is created by an LSR for
	every interface capable of supporting MPLS L3VPN.		every interface capable of supporting MPLS L3VPN.
	Each entry in this table is meant to correspond to		Each entry in this table is meant to correspond to
	an entry in the Interfaces Table."		an entry in the Interfaces Table."
	INDEX { mplsL3VpnVrfName, mplsL3VpnIfConfIndex }		INDEX { mplsL3VpnVrfName, mplsL3VpnIfConfIndex }
	::= { mplsL3VpnIfConfTable 1 }		::= { mplsL3VpnIfConfTable 1 }
	MplsL3VpnIfConfEntry ::= SEQUENCE {		MplsL3VpnIfConfEntry ::= SEQUENCE {
	mplsL3VpnIfConfIndex InterfaceIndex,		mplsL3VpnIfConfIndex InterfaceIndex,
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	mplsL3VpnIfVpnClassification INTEGER,		mplsL3VpnIfVpnClassification INTEGER,
	mplsL3VpnIfVpnRouteDistProtocol BITS,		mplsL3VpnIfVpnRouteDistProtocol BITS,
	mplsL3VpnIfConfStorageType StorageType,		mplsL3VpnIfConfStorageType StorageType,
	mplsL3VpnIfConfRowStatus RowStatus		mplsL3VpnIfConfRowStatus RowStatus
	}		}
	mplsL3VpnIfConfIndex OBJECT-TYPE		mplsL3VpnIfConfIndex OBJECT-TYPE
	SYNTAX InterfaceIndex		SYNTAX InterfaceIndex
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This is a unique index for an entry in the		"This is a unique index for an entry in the
	mplsL3VpnIfConfTable. A non-zero index for an		mplsL3VpnIfConfTable. A non-zero index for an
	entry indicates the ifIndex for the corresponding		entry indicates the ifIndex for the corresponding
	interface entry in the MPLS-VPN-layer in the ifTable.		interface entry in the MPLS-VPN-layer in the ifTable.
	Note that this table does not necessarily correspond		Note that this table does not necessarily correspond
	one-to-one with all entries in the Interface MIB		one-to-one with all entries in the Interface MIB
	having an ifType of MPLS-layer; rather, only those		having an ifType of MPLS-layer; rather, only those
	which are enabled for MPLS L3VPN functionality."		which are enabled for MPLS L3VPN functionality."
	REFERENCE		REFERENCE
	"RFC 2233 - The Interfaces Group MIB using SMIv2,		"RFC2863"
	McCloghrie, K., and F. Kastenholtz, Nov. 1997"
	::= { mplsL3VpnIfConfEntry 1 }		::= { mplsL3VpnIfConfEntry 1 }
	mplsL3VpnIfVpnClassification OBJECT-TYPE		mplsL3VpnIfVpnClassification OBJECT-TYPE
	SYNTAX INTEGER { carrierOfCarrier (1),		SYNTAX INTEGER { carrierOfCarrier (1),
	enterprise (2),		enterprise (2),
	interProvider (3)		interProvider (3)
	}		}
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	skipping to change at page 11, line 4 ¶		skipping to change at page 10, line 52 ¶
	bgp (1),		bgp (1),
	ospf (2),		ospf (2),
	rip(3),		rip(3),
	isis(4),		isis(4),
	static(5),		static(5),
	other (6)		other (6)
	}		}
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	"Denotes the route distribution protocol across the		"Denotes the route distribution protocol across the
	PE-CE link. Note that more than one routing protocol		PE-CE link. Note that more than one routing protocol
	may be enabled at the same time, thus this object is		may be enabled at the same time, thus this object is
	specified as a bitmask. For example, static(5) and		specified as a bitmask. For example, static(5) and
	ospf(2) are a typical configuration."		ospf(2) are a typical configuration."
	::= { mplsL3VpnIfConfEntry 3 }		::= { mplsL3VpnIfConfEntry 3 }
	mplsL3VpnIfConfStorageType OBJECT-TYPE		mplsL3VpnIfConfStorageType OBJECT-TYPE
	SYNTAX StorageType		SYNTAX StorageType
	MAX-ACCESS read-create		MAX-ACCESS read-create
	skipping to change at page 11, line 43 ¶		skipping to change at page 11, line 39 ¶
	delete a row in this table. Rows in this		delete a row in this table. Rows in this
	table signify that the specified interface is		table signify that the specified interface is
	associated with this VRF. If the row creation		associated with this VRF. If the row creation
	operation succeeds, the interface will have been		operation succeeds, the interface will have been
	associated with the specified VRF, otherwise the		associated with the specified VRF, otherwise the
	agent MUST not allow the association. If the agent		agent MUST not allow the association. If the agent
	only allows read-only operations on this table, it		only allows read-only operations on this table, it
	MUST create entries in this table as they are created		MUST create entries in this table as they are created
	on the device. When a row in this		on the device. When a row in this
	table is in active(1) state, no objects in that row		table is in active(1) state, no objects in that row
	can be modified by the agent except		can be modified except mplsL3VpnIfConfStorageType and
	mplsL3VpnIfConfStorageType and mplsL3VpnIfConfRowStatus."		mplsL3VpnIfConfRowStatus."
	::= { mplsL3VpnIfConfEntry 5 }		::= { mplsL3VpnIfConfEntry 5 }
	-- VRF Configuration Table		-- VRF Configuration Table
	mplsL3VpnVrfTable OBJECT-TYPE		mplsL3VpnVrfTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MplsL3VpnVrfEntry		SYNTAX SEQUENCE OF MplsL3VpnVrfEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This table specifies per-interface MPLS L3VPN		"This table specifies per-interface MPLS L3VPN
	VRF Table capability and associated information.		VRF Table capability and associated information.
	Entries in this table define VRF routing instances		Entries in this table define VRF routing instances
	associated with MPLS/VPN interfaces. Note that		associated with MPLS/VPN interfaces. Note that
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	multiple interfaces can belong to the same VRF		multiple interfaces can belong to the same VRF
	instance. The collection of all VRF instances		instance. The collection of all VRF instances
	comprises an actual VPN."		comprises an actual VPN."
	::= { mplsL3VpnConf 2 }		::= { mplsL3VpnConf 2 }
	mplsL3VpnVrfEntry OBJECT-TYPE		mplsL3VpnVrfEntry OBJECT-TYPE
	SYNTAX MplsL3VpnVrfEntry		SYNTAX MplsL3VpnVrfEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	skipping to change at page 12, line 30 ¶		skipping to change at page 12, line 27 ¶
	interface."		interface."
	INDEX { mplsL3VpnVrfName }		INDEX { mplsL3VpnVrfName }
	::= { mplsL3VpnVrfTable 1 }		::= { mplsL3VpnVrfTable 1 }
	MplsL3VpnVrfEntry ::= SEQUENCE {		MplsL3VpnVrfEntry ::= SEQUENCE {
	mplsL3VpnVrfName MplsL3VpnName,		mplsL3VpnVrfName MplsL3VpnName,
	mplsL3VpnVrfVpnId VPNIdOrZero,		mplsL3VpnVrfVpnId VPNIdOrZero,
	mplsL3VpnVrfDescription SnmpAdminString,		mplsL3VpnVrfDescription SnmpAdminString,
	mplsL3VpnVrfRD MplsL3VpnRouteDistinguisher,		mplsL3VpnVrfRD MplsL3VpnRouteDistinguisher,
	mplsL3VpnVrfCreationTime TimeStamp,		mplsL3VpnVrfCreationTime TimeStamp,
	mplsL3VpnVrfOperStatus INTEGER,		mplsL3VpnVrfOperStatus INTEGER,
	mplsL3VpnVrfActiveInterfaces Unsigned32,		mplsL3VpnVrfActiveInterfaces Gauge32,
	mplsL3VpnVrfAssociatedInterfaces Unsigned32,		mplsL3VpnVrfAssociatedInterfaces Unsigned32,
	mplsL3VpnVrfConfMidRteThresh Unsigned32,		mplsL3VpnVrfConfMidRteThresh Unsigned32,
	mplsL3VpnVrfConfHighRteThresh Unsigned32,		mplsL3VpnVrfConfHighRteThresh Unsigned32,
	mplsL3VpnVrfConfMaxRoutes Unsigned32,		mplsL3VpnVrfConfMaxRoutes Unsigned32,
	mplsL3VpnVrfConfLastChanged TimeStamp,		mplsL3VpnVrfConfLastChanged TimeStamp,
	mplsL3VpnVrfConfRowStatus RowStatus,		mplsL3VpnVrfConfRowStatus RowStatus,
			mplsL3VpnVrfConfAdminStatus INTEGER,
	mplsL3VpnVrfConfStorageType StorageType		mplsL3VpnVrfConfStorageType StorageType
	}		}
	mplsL3VpnVrfName OBJECT-TYPE		mplsL3VpnVrfName OBJECT-TYPE
	SYNTAX MplsL3VpnName		SYNTAX MplsL3VpnName
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The human-readable name of this VPN. This MAY		"The human-readable name of this VPN. This MAY
	be equivalent to the RFC2685 VPN-ID, but may		be equivalent to the [RFC2685] VPN-ID, but may
	also vary. If it is set to the VPN ID, it MUST		also vary. If it is set to the VPN ID, it MUST
	be equivalent to the value of mplsL3VpnVrfVpnId.		be equivalent to the value of mplsL3VpnVrfVpnId.
	It is strongly recommended that all sites supporting		It is strongly recommended that all sites supporting
	VRFs that are part of the same VPN use the same		VRFs that are part of the same VPN use the same
	naming convention for VRFs as well as the same VPN		naming convention for VRFs as well as the same VPN
	ID."		ID."
	REFERENCE		REFERENCE
	"RFC 2685 Fox B., et al, `Virtual		"[RFC2685]"
	Private Networks Identifier`, September 1999."
	::= { mplsL3VpnVrfEntry 1 }
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205		::= { mplsL3VpnVrfEntry 1 }
	mplsL3VpnVrfVpnId OBJECT-TYPE		mplsL3VpnVrfVpnId OBJECT-TYPE
	SYNTAX VPNIdOrZero		SYNTAX VPNIdOrZero
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The VPN ID as specified in RFC 2685. If a VPN ID		"The VPN ID as specified in [RFC2685]. If a VPN ID
	has not been specified for this VRF, then this		has not been specified for this VRF, then this
	variable SHOULD be set to an zero-length OCTET		variable SHOULD be set to an zero-length OCTET
	STRING."		STRING."
	::= { mplsL3VpnVrfEntry 2 }		::= { mplsL3VpnVrfEntry 2 }
	mplsL3VpnVrfDescription OBJECT-TYPE		mplsL3VpnVrfDescription OBJECT-TYPE
	SYNTAX SnmpAdminString		SYNTAX SnmpAdminString
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	skipping to change at page 13, line 54 ¶		skipping to change at page 14, line 4 ¶
	mplsL3VpnVrfOperStatus OBJECT-TYPE		mplsL3VpnVrfOperStatus OBJECT-TYPE
	SYNTAX INTEGER { up (1),		SYNTAX INTEGER { up (1),
	down (2)		down (2)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Denotes whether a VRF is operational or not. A VRF is		"Denotes whether a VRF is operational or not. A VRF is
	up(1) when at least one interface associated with the		up(1) when at least one interface associated with the
	VRF, which ifOperStatus is up(1). A VRF is down(2) when:		VRF, which ifOperStatus is up(1). A VRF is down(2) when:
	a. There does not exist at least one interface whose		a. There does not exist at least one interface whose
	ifOperStatus is up(1).		ifOperStatus is up(1).
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	b. There are no interfaces associated with the VRF."		b. There are no interfaces associated with the VRF."
	::= { mplsL3VpnVrfEntry 6 }		::= { mplsL3VpnVrfEntry 6 }
	mplsL3VpnVrfActiveInterfaces OBJECT-TYPE		mplsL3VpnVrfActiveInterfaces OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Gauge32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of interfaces connected to this VRF with		"Total number of interfaces connected to this VRF with
	ifOperStatus = up(1).		ifOperStatus = up(1).
	This counter should be incremented when:
	a. When the ifOperStatus of one of the connected interfaces
	changes from down(2) to up(1).
	b. When an interface with ifOperStatus = up(1) is connected		This value should increase when an interface is associted
	to this VRF.		with the corresponding VRF and its corresponding ifOperStatus
	This counter should be decremented when:		is equal to up(1). If an interface is associated whose
	a. When the ifOperStatus of one of the connected interfaces		ifOperStatus is not up(1), then the value is not incremented
	changes from up(1) to down(2).		until such time as it transitions to this state.
	b. When one of the connected interfaces with
	ifOperStatus = up(1) gets disconnected from this VRF."		This value should be decremented when an interface is
			disassociated with a VRF or the corresponding ifOperStatus
			transitions out of the up(1) state to any other state.
			"
	::= { mplsL3VpnVrfEntry 7 }		::= { mplsL3VpnVrfEntry 7 }
	mplsL3VpnVrfAssociatedInterfaces OBJECT-TYPE		mplsL3VpnVrfAssociatedInterfaces OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Total number of interfaces connected to this VRF		"Total number of interfaces connected to this VRF
	(independent of ifOperStatus type)."		(independent of ifOperStatus type)."
	::= { mplsL3VpnVrfEntry 8 }		::= { mplsL3VpnVrfEntry 8 }
	skipping to change at page 15, line 4 ¶		skipping to change at page 15, line 7 ¶
	::= { mplsL3VpnVrfEntry 9 }		::= { mplsL3VpnVrfEntry 9 }
	mplsL3VpnVrfConfHighRteThresh OBJECT-TYPE		mplsL3VpnVrfConfHighRteThresh OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Denotes high-level water marker for the number of		"Denotes high-level water marker for the number of
	routes which this VRF may hold."		routes which this VRF may hold."
	DEFVAL { 0 }		DEFVAL { 0 }
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	::= { mplsL3VpnVrfEntry 10 }		::= { mplsL3VpnVrfEntry 10 }
	mplsL3VpnVrfConfMaxRoutes OBJECT-TYPE		mplsL3VpnVrfConfMaxRoutes OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Denotes maximum number of routes which this VRF is		"Denotes maximum number of routes which this VRF is
	configured to hold. This value MUST be less than or		configured to hold. This value MUST be less than or
	equal to mplsL3VpnVrfConfMaxPossRts unless it is set		equal to mplsL3VpnVrfConfMaxPossRts unless it is set
	skipping to change at page 15, line 38 ¶		skipping to change at page 15, line 38 ¶
	VRF parameters defined in this table or addition or		VRF parameters defined in this table or addition or
	deletion of interfaces associated with this VRF."		deletion of interfaces associated with this VRF."
	::= { mplsL3VpnVrfEntry 12 }		::= { mplsL3VpnVrfEntry 12 }
	mplsL3VpnVrfConfRowStatus OBJECT-TYPE		mplsL3VpnVrfConfRowStatus OBJECT-TYPE
	SYNTAX RowStatus		SYNTAX RowStatus
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This variable is used to create, modify, and/or		"This variable is used to create, modify, and/or
	delete a row in this table."		delete a row in this table.
			When a row in this table is in active(1) state, no
			objects in that row can be modified except
			mplsL3VpnVrfConfAdminStatus, mplsL3VpnVrfConfRowStatus
			and mplsL3VpnVrfConfStorageType."
	::= { mplsL3VpnVrfEntry 13 }		::= { mplsL3VpnVrfEntry 13 }
			mplsL3VpnVrfConfAdminStatus OBJECT-TYPE
			SYNTAX INTEGER {
			up(1), -- ready to pass packets
			down(2), -- can't pass packets
			testing(3) -- in some test mode
			}
			MAX-ACCESS read-create
			STATUS current
			DESCRIPTION
			"Indicates the desired operational status of this
			VRF."
			::= { mplsL3VpnVrfEntry 14 }
	mplsL3VpnVrfConfStorageType OBJECT-TYPE		mplsL3VpnVrfConfStorageType OBJECT-TYPE
	SYNTAX StorageType		SYNTAX StorageType
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The storage type for this VPN VRF entry.		"The storage type for this VPN VRF entry.
	Conceptual rows having the value 'permanent'		Conceptual rows having the value 'permanent'
	need not allow write-access to any columnar		need not allow write-access to any columnar
	objects in the row."		objects in the row."
	REFERENCE		REFERENCE
	"See RFC2579."		"See RFC2579."
	DEFVAL { volatile }		DEFVAL { volatile }
	::= { mplsL3VpnVrfEntry 14 }		::= { mplsL3VpnVrfEntry 15 }
	-- MplsL3VpnVrfRTTable		-- MplsL3VpnVrfRTTable
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	mplsL3VpnVrfRTTable OBJECT-TYPE		mplsL3VpnVrfRTTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MplsL3VpnVrfRTEntry		SYNTAX SEQUENCE OF MplsL3VpnVrfRTEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This table specifies per-VRF route target association.		"This table specifies per-VRF route target association.
	Each entry identifies a connectivity policy supported		Each entry identifies a connectivity policy supported
	as part of a VPN."		as part of a VPN."
	::= { mplsL3VpnConf 3 }		::= { mplsL3VpnConf 3 }
	mplsL3VpnVrfRTEntry OBJECT-TYPE		mplsL3VpnVrfRTEntry OBJECT-TYPE
	SYNTAX MplsL3VpnVrfRTEntry		SYNTAX MplsL3VpnVrfRTEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table is created by an LSR for		"An entry in this table is created by an LSR for
	each route target configured for a VRF supporting		each route target configured for a VRF supporting
	a MPLS L3VPN instance. The indexing provides an		a MPLS L3VPN instance. The indexing provides an
	ordering per-VRF instance. See RFC2547 for a		ordering per-VRF instance. See [RFC2547bis] for a
	complete definition of a route target."		complete definition of a route target."
	INDEX { mplsL3VpnVrfName, mplsL3VpnVrfRTIndex,		INDEX { mplsL3VpnVrfName, mplsL3VpnVrfRTIndex,
	mplsL3VpnVrfRTType }		mplsL3VpnVrfRTType }
	::= { mplsL3VpnVrfRTTable 1 }		::= { mplsL3VpnVrfRTTable 1 }
	MplsL3VpnVrfRTEntry ::= SEQUENCE {		MplsL3VpnVrfRTEntry ::= SEQUENCE {
	mplsL3VpnVrfRTIndex Unsigned32,		mplsL3VpnVrfRTIndex Unsigned32,
	mplsL3VpnVrfRTType MplsL3VpnRtType,		mplsL3VpnVrfRTType MplsL3VpnRtType,
	mplsL3VpnVrfRT MplsL3VpnRouteDistinguisher,		mplsL3VpnVrfRT MplsL3VpnRouteDistinguisher,
	mplsL3VpnVrfRTDescr SnmpAdminString,		mplsL3VpnVrfRTDescr SnmpAdminString,
	skipping to change at page 17, line 5 ¶		skipping to change at page 17, line 27 ¶
	::= { mplsL3VpnVrfRTEntry 2 }		::= { mplsL3VpnVrfRTEntry 2 }
	mplsL3VpnVrfRTType OBJECT-TYPE		mplsL3VpnVrfRTType OBJECT-TYPE
	SYNTAX MplsL3VpnRtType		SYNTAX MplsL3VpnRtType
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The route target distribution type."		"The route target distribution type."
	::= { mplsL3VpnVrfRTEntry 3 }		::= { mplsL3VpnVrfRTEntry 3 }
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	mplsL3VpnVrfRT OBJECT-TYPE		mplsL3VpnVrfRT OBJECT-TYPE
	SYNTAX MplsL3VpnRouteDistinguisher		SYNTAX MplsL3VpnRouteDistinguisher
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The route target distribution policy."		"The route target distribution policy."
	DEFVAL { "" }		DEFVAL { "" }
	::= { mplsL3VpnVrfRTEntry 4 }		::= { mplsL3VpnVrfRTEntry 4 }
	mplsL3VpnVrfRTDescr OBJECT-TYPE		mplsL3VpnVrfRTDescr OBJECT-TYPE
	skipping to change at page 17, line 33 ¶		skipping to change at page 18, line 4 ¶
	::= { mplsL3VpnVrfRTEntry 5 }		::= { mplsL3VpnVrfRTEntry 5 }
	mplsL3VpnVrfRTRowStatus OBJECT-TYPE		mplsL3VpnVrfRTRowStatus OBJECT-TYPE
	SYNTAX RowStatus		SYNTAX RowStatus
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This variable is used to create, modify, and/or		"This variable is used to create, modify, and/or
	delete a row in this table. When a row in this		delete a row in this table. When a row in this
	table is in active(1) state, no objects in that row		table is in active(1) state, no objects in that row
	can be modified by the agent except		can be modified except mplsL3VpnVrfRTRowStatus."
	mplsL3VpnVrfRTRowStatus."
	::= { mplsL3VpnVrfRTEntry 6 }		::= { mplsL3VpnVrfRTEntry 6 }
	mplsL3VpnVrfRTStorageType OBJECT-TYPE		mplsL3VpnVrfRTStorageType OBJECT-TYPE
	SYNTAX StorageType		SYNTAX StorageType
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The storage type for this VPN RT entry.		"The storage type for this VPN RT entry.
	Conceptual rows having the value 'permanent'		Conceptual rows having the value 'permanent'
	need not allow write-access to any columnar		need not allow write-access to any columnar
	skipping to change at page 18, line 4 ¶		skipping to change at page 18, line 27 ¶
	"See RFC2579."		"See RFC2579."
	DEFVAL { volatile }		DEFVAL { volatile }
	::= { mplsL3VpnVrfRTEntry 7 }		::= { mplsL3VpnVrfRTEntry 7 }
	-- VRF Security Table		-- VRF Security Table
	mplsL3VpnVrfSecTable OBJECT-TYPE		mplsL3VpnVrfSecTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MplsL3VpnVrfSecEntry		SYNTAX SEQUENCE OF MplsL3VpnVrfSecEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	DESCRIPTION		DESCRIPTION
	"This table specifies per MPLS L3VPN VRF Table		"This table specifies per MPLS L3VPN VRF Table
	security-related counters."		security-related counters."
	::= { mplsL3VpnConf 6 }		::= { mplsL3VpnConf 6 }
	mplsL3VpnVrfSecEntry OBJECT-TYPE		mplsL3VpnVrfSecEntry OBJECT-TYPE
	SYNTAX MplsL3VpnVrfSecEntry		SYNTAX MplsL3VpnVrfSecEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	skipping to change at page 19, line 5 ¶		skipping to change at page 19, line 27 ¶
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The value of sysUpTime on the most recent occasion at		"The value of sysUpTime on the most recent occasion at
	which any one or more of this entry's counters suffered		which any one or more of this entry's counters suffered
	a discontinuity. If no such discontinuities have		a discontinuity. If no such discontinuities have
	occurred since the last re-initialization of the local		occurred since the last re-initialization of the local
	management subsystem, then this object contains a zero		management subsystem, then this object contains a zero
	value."		value."
	::= { mplsL3VpnVrfSecEntry 2 }		::= { mplsL3VpnVrfSecEntry 2 }
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	-- VRF Performance Table		-- VRF Performance Table
	mplsL3VpnVrfPerfTable OBJECT-TYPE		mplsL3VpnVrfPerfTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MplsL3VpnVrfPerfEntry		SYNTAX SEQUENCE OF MplsL3VpnVrfPerfEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This table specifies per MPLS L3VPN VRF Table performance		"This table specifies per MPLS L3VPN VRF Table performance
	information."		information."
	::= { mplsL3VpnPerf 1 }		::= { mplsL3VpnPerf 1 }
	skipping to change at page 19, line 31 ¶		skipping to change at page 19, line 51 ¶
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table is created by an LSR for		"An entry in this table is created by an LSR for
	every VRF capable of supporting MPLS L3VPN."		every VRF capable of supporting MPLS L3VPN."
	AUGMENTS { mplsL3VpnVrfEntry }		AUGMENTS { mplsL3VpnVrfEntry }
	::= { mplsL3VpnVrfPerfTable 1 }		::= { mplsL3VpnVrfPerfTable 1 }
	MplsL3VpnVrfPerfEntry ::= SEQUENCE {		MplsL3VpnVrfPerfEntry ::= SEQUENCE {
	mplsL3VpnVrfPerfRoutesAdded Counter32,		mplsL3VpnVrfPerfRoutesAdded Counter32,
	mplsL3VpnVrfPerfRoutesDeleted Counter32,		mplsL3VpnVrfPerfRoutesDeleted Counter32,
	mplsL3VpnVrfPerfCurrNumRoutes Unsigned32,		mplsL3VpnVrfPerfCurrNumRoutes Gauge32,
	mplsL3VpnVrfPerfRoutesDropped Counter32,		mplsL3VpnVrfPerfRoutesDropped Counter32,
	mplsL3VpnVrfPerfDiscTime TimeStamp		mplsL3VpnVrfPerfDiscTime TimeStamp
	}		}
	mplsL3VpnVrfPerfRoutesAdded OBJECT-TYPE		mplsL3VpnVrfPerfRoutesAdded OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates the number of routes added to this VPN/VRF		"Indicates the number of routes added to this VPN/VRF
	skipping to change at page 20, line 4 ¶		skipping to change at page 20, line 29 ¶
	::= { mplsL3VpnVrfPerfEntry 1 }		::= { mplsL3VpnVrfPerfEntry 1 }
	mplsL3VpnVrfPerfRoutesDeleted OBJECT-TYPE		mplsL3VpnVrfPerfRoutesDeleted OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates the number of routes removed from this VPN/VRF.		"Indicates the number of routes removed from this VPN/VRF.
	Discontinuities in the value of this counter can occur		Discontinuities in the value of this counter can occur
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	at re-initialization of the management system, and at		at re-initialization of the management system, and at
	other times as indicated by the value of		other times as indicated by the value of
	mplsL3VpnVrfPerfDiscTime."		mplsL3VpnVrfPerfDiscTime."
	::= { mplsL3VpnVrfPerfEntry 2 }		::= { mplsL3VpnVrfPerfEntry 2 }
	mplsL3VpnVrfPerfCurrNumRoutes OBJECT-TYPE		mplsL3VpnVrfPerfCurrNumRoutes OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Gauge32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates the number of routes currently used by this VRF.		"Indicates the number of routes currently used by this
			VRF."
	Discontinuities in the value of this counter can occur
	at re-initialization of the management system, and at
	other times as indicated by the value of
	mplsL3VpnVrfPerfDiscTime."
	::= { mplsL3VpnVrfPerfEntry 3 }		::= { mplsL3VpnVrfPerfEntry 3 }
	mplsL3VpnVrfPerfRoutesDropped OBJECT-TYPE		mplsL3VpnVrfPerfRoutesDropped OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This counter should be incremented when the number of routes		"This counter should be incremented when the number of routes
	contained by the specified VRF exceeds or attempts to exceed		contained by the specified VRF exceeds or attempts to exceed
	the maximum allowed value as indicated by		the maximum allowed value as indicated by
	skipping to change at page 21, line 4 ¶		skipping to change at page 21, line 25 ¶
	DESCRIPTION		DESCRIPTION
	"The value of sysUpTime on the most recent occasion at		"The value of sysUpTime on the most recent occasion at
	which any one or more of this entry's counters suffered		which any one or more of this entry's counters suffered
	a discontinuity. If no such discontinuities have		a discontinuity. If no such discontinuities have
	occurred since the last re-initialization of the local		occurred since the last re-initialization of the local
	management subsystem, then this object contains a zero		management subsystem, then this object contains a zero
	value."		value."
	::= { mplsL3VpnVrfPerfEntry 5 }		::= { mplsL3VpnVrfPerfEntry 5 }
	-- VRF Routing Table		-- VRF Routing Table
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	mplsL3VpnVrfRteTable OBJECT-TYPE		mplsL3VpnVrfRteTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MplsL3VpnVrfRteEntry		SYNTAX SEQUENCE OF MplsL3VpnVrfRteEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This table specifies per-interface MPLS L3VPN VRF Table		"This table specifies per-interface MPLS L3VPN VRF Table
	routing information. Entries in this table define VRF routing		routing information. Entries in this table define VRF routing
	entries associated with the specified MPLS/VPN interfaces. Note		entries associated with the specified MPLS/VPN interfaces. Note
	that this table contains both BGP and IGP routes, as both may		that this table contains both BGP and IGP routes, as both may
	appear in the same VRF."		appear in the same VRF."
	REFERENCE		REFERENCE
	"1. RFC 1213 Section 6.6, The IP Group.		"[RFC2096]"
	2. RFC 2096 "
	::= { mplsL3VpnRoute 1 }		::= { mplsL3VpnRoute 1 }
	mplsL3VpnVrfRteEntry OBJECT-TYPE		mplsL3VpnVrfRteEntry OBJECT-TYPE
	SYNTAX MplsL3VpnVrfRteEntry		SYNTAX MplsL3VpnVrfRteEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table is created by an LSR for every route		"An entry in this table is created by an LSR for every route
	present configured (either dynamically or statically) within		present configured (either dynamically or statically) within
	the context of a specific VRF capable of supporting MPLS/BGP		the context of a specific VRF capable of supporting MPLS/BGP
	VPN. The indexing provides an ordering of VRFs per-VPN		VPN. The indexing provides an ordering of VRFs per-VPN
	interface.		interface.
	Implementors need to be aware that if the value of		Implementors need to be aware that there are quite a few
	the mplsL3VpnVrfName (an OID) has more		index objects which together can exceed the size allowed
	that 111 sub-identifiers, then OIDs of column		for an OID. So immplementors must make sure that OIDs of
	instances in this table will have more than 128		column instances in this table will have no more than 128
	sub-identifiers and cannot be accessed using SNMPv1,		sub-identifiers, otherwise they cannot be accessed using
	SNMPv2c, or SNMPv3."		SNMPv1, SNMPv2c, or SNMPv3."
	INDEX { mplsL3VpnVrfName,		INDEX { mplsL3VpnVrfName,
	mplsL3VpnVrfRteInetCidrDestType,		mplsL3VpnVrfRteInetCidrDestType,
	mplsL3VpnVrfRteInetCidrDest,		mplsL3VpnVrfRteInetCidrDest,
	mplsL3VpnVrfRteInetCidrPfxLen,		mplsL3VpnVrfRteInetCidrPfxLen,
	mplsL3VpnVrfRteInetCidrPolicy,		mplsL3VpnVrfRteInetCidrPolicy,
	mplsL3VpnVrfRteInetCidrNHopType,		mplsL3VpnVrfRteInetCidrNHopType,
	mplsL3VpnVrfRteInetCidrNextHop		mplsL3VpnVrfRteInetCidrNextHop
	}		}
	::= { mplsL3VpnVrfRteTable 1 }		::= { mplsL3VpnVrfRteTable 1 }
	MplsL3VpnVrfRteEntry ::= SEQUENCE {		MplsL3VpnVrfRteEntry ::= SEQUENCE {
	mplsL3VpnVrfRteInetCidrDestType InetAddressType,		mplsL3VpnVrfRteInetCidrDestType InetAddressType,
	mplsL3VpnVrfRteInetCidrDest InetAddress,		mplsL3VpnVrfRteInetCidrDest InetAddress,
	mplsL3VpnVrfRteInetCidrPfxLen InetAddressPrefixLength,		mplsL3VpnVrfRteInetCidrPfxLen InetAddressPrefixLength,
	mplsL3VpnVrfRteInetCidrPolicy OBJECT IDENTIFIER,		mplsL3VpnVrfRteInetCidrPolicy OBJECT IDENTIFIER,
	mplsL3VpnVrfRteInetCidrNHopType InetAddressType,		mplsL3VpnVrfRteInetCidrNHopType InetAddressType,
	mplsL3VpnVrfRteInetCidrNextHop InetAddress,		mplsL3VpnVrfRteInetCidrNextHop InetAddress,
	mplsL3VpnVrfRteInetCidrIfIndex InterfaceIndexOrZero,		mplsL3VpnVrfRteInetCidrIfIndex InterfaceIndexOrZero,
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	mplsL3VpnVrfRteInetCidrType INTEGER,		mplsL3VpnVrfRteInetCidrType INTEGER,
	mplsL3VpnVrfRteInetCidrProto IANAipRouteProtocol,		mplsL3VpnVrfRteInetCidrProto IANAipRouteProtocol,
	mplsL3VpnVrfRteInetCidrAge Gauge32,		mplsL3VpnVrfRteInetCidrAge Gauge32,
	mplsL3VpnVrfRteInetCidrNextHopAS InetAutonomousSystemNumber,		mplsL3VpnVrfRteInetCidrNextHopAS InetAutonomousSystemNumber,
	mplsL3VpnVrfRteInetCidrMetric1 Integer32,		mplsL3VpnVrfRteInetCidrMetric1 Integer32,
	mplsL3VpnVrfRteInetCidrMetric2 Integer32,		mplsL3VpnVrfRteInetCidrMetric2 Integer32,
	mplsL3VpnVrfRteInetCidrMetric3 Integer32,		mplsL3VpnVrfRteInetCidrMetric3 Integer32,
	mplsL3VpnVrfRteInetCidrMetric4 Integer32,		mplsL3VpnVrfRteInetCidrMetric4 Integer32,
	mplsL3VpnVrfRteInetCidrMetric5 Integer32,		mplsL3VpnVrfRteInetCidrMetric5 Integer32,
	mplsL3VpnVrfRteXCPointer MplsIndexType,		mplsL3VpnVrfRteXCPointer MplsIndexType,
	skipping to change at page 22, line 30 ¶		skipping to change at page 22, line 50 ¶
	mplsL3VpnVrfRteInetCidrDestType OBJECT-TYPE		mplsL3VpnVrfRteInetCidrDestType OBJECT-TYPE
	SYNTAX InetAddressType		SYNTAX InetAddressType
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The type of the mplsL3VpnVrfRteInetCidrDest address, as		"The type of the mplsL3VpnVrfRteInetCidrDest address, as
	defined in the InetAddress MIB.		defined in the InetAddress MIB.
	Only those address types that may appear in an actual		Only those address types that may appear in an actual
	routing table are allowed as values of this object."		routing table are allowed as values of this object."
	REFERENCE "RFC 3291"		REFERENCE "RFC4001"
	::= { mplsL3VpnVrfRteEntry 1 }		::= { mplsL3VpnVrfRteEntry 1 }
	mplsL3VpnVrfRteInetCidrDest OBJECT-TYPE		mplsL3VpnVrfRteInetCidrDest OBJECT-TYPE
	SYNTAX InetAddress		SYNTAX InetAddress
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The destination IP address of this route.		"The destination IP address of this route.
	The type of this address is determined by the value of		The type of this address is determined by the value of
	skipping to change at page 23, line 4 ¶		skipping to change at page 23, line 29 ¶
	the bitwise logical-AND of x with the value of the mask		the bitwise logical-AND of x with the value of the mask
	formed from the corresponding index object		formed from the corresponding index object
	mplsL3VpnVrfRteInetCidrPfxLen MUST be		mplsL3VpnVrfRteInetCidrPfxLen MUST be
	equal to x. If not, then the index pair is not		equal to x. If not, then the index pair is not
	consistent and an inconsistentName error must be		consistent and an inconsistentName error must be
	returned on SET or CREATE requests."		returned on SET or CREATE requests."
	::= { mplsL3VpnVrfRteEntry 2 }		::= { mplsL3VpnVrfRteEntry 2 }
	mplsL3VpnVrfRteInetCidrPfxLen OBJECT-TYPE		mplsL3VpnVrfRteInetCidrPfxLen OBJECT-TYPE
	SYNTAX InetAddressPrefixLength (0..128)		SYNTAX InetAddressPrefixLength (0..128)
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates the number of leading one bits which form the		"Indicates the number of leading one bits which form the
	mask to be logical-ANDed with the destination address		mask to be logical-ANDed with the destination address
	before being compared to the value in the		before being compared to the value in the
	mplsL3VpnVrfRteInetCidrDest field.		mplsL3VpnVrfRteInetCidrDest field.
	The values for the index objects		The values for the index objects
	mplsL3VpnVrfRteInetCidrDest and		mplsL3VpnVrfRteInetCidrDest and
	skipping to change at page 23, line 52 ¶		skipping to change at page 24, line 24 ¶
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The type of the mplsL3VpnVrfRteInetCidrNextHop address,		"The type of the mplsL3VpnVrfRteInetCidrNextHop address,
	as defined in the InetAddress MIB.		as defined in the InetAddress MIB.
	Value should be set to unknown(0) for non-remote		Value should be set to unknown(0) for non-remote
	routes.		routes.
	Only those address types that may appear in an actual		Only those address types that may appear in an actual
	routing table are allowed as values of this object."		routing table are allowed as values of this object."
	REFERENCE "RFC 3291"		REFERENCE "RFC4001"
	::= { mplsL3VpnVrfRteEntry 5 }		::= { mplsL3VpnVrfRteEntry 5 }
	mplsL3VpnVrfRteInetCidrNextHop OBJECT-TYPE		mplsL3VpnVrfRteInetCidrNextHop OBJECT-TYPE
	SYNTAX InetAddress		SYNTAX InetAddress
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"On remote routes, the address of the next system en		"On remote routes, the address of the next system en
	route. For non-remote routes, a zero length string.		route. For non-remote routes, a zero length string.
	The type of this address is determined by the value of		The type of this address is determined by the value of
	the mplsL3VpnVrfRteInetCidrNHopType object."		the mplsL3VpnVrfRteInetCidrNHopType object."
	::= { mplsL3VpnVrfRteEntry 6 }		::= { mplsL3VpnVrfRteEntry 6 }
	mplsL3VpnVrfRteInetCidrIfIndex OBJECT-TYPE		mplsL3VpnVrfRteInetCidrIfIndex OBJECT-TYPE
	skipping to change at page 25, line 5 ¶		skipping to change at page 25, line 30 ¶
	Routes which do not result in traffic forwarding or		Routes which do not result in traffic forwarding or
	rejection should not be displayed even if the		rejection should not be displayed even if the
	implementation keeps them stored internally.		implementation keeps them stored internally.
	reject(2) refers to a route which, if matched, discards		reject(2) refers to a route which, if matched, discards
	the message as unreachable and returns a notification		the message as unreachable and returns a notification
	(e.g. ICMP error) to the message sender. This is used		(e.g. ICMP error) to the message sender. This is used
	in some protocols as a means of correctly aggregating		in some protocols as a means of correctly aggregating
	routes.		routes.
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	blackhole(5) refers to a route which, if matched,		blackhole(5) refers to a route which, if matched,
	discards the message silently."		discards the message silently."
	DEFVAL { other }		DEFVAL { other }
	::= { mplsL3VpnVrfRteEntry 8 }		::= { mplsL3VpnVrfRteEntry 8 }
	mplsL3VpnVrfRteInetCidrProto OBJECT-TYPE		mplsL3VpnVrfRteInetCidrProto OBJECT-TYPE
	SYNTAX IANAipRouteProtocol		SYNTAX IANAipRouteProtocol
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	skipping to change at page 25, line 50 ¶		skipping to change at page 26, line 24 ¶
	"The Autonomous System Number of the Next Hop. The		"The Autonomous System Number of the Next Hop. The
	semantics of this object are determined by the		semantics of this object are determined by the
	routing protocol specified in the route's		routing protocol specified in the route's
	mplsL3VpnVrfRteInetCidrProto value. When this		mplsL3VpnVrfRteInetCidrProto value. When this
	object is unknown or not relevant its value should		object is unknown or not relevant its value should
	be set to zero."		be set to zero."
	DEFVAL { 0 }		DEFVAL { 0 }
	::= { mplsL3VpnVrfRteEntry 11 }		::= { mplsL3VpnVrfRteEntry 11 }
	mplsL3VpnVrfRteInetCidrMetric1 OBJECT-TYPE		mplsL3VpnVrfRteInetCidrMetric1 OBJECT-TYPE
	SYNTAX Integer32		SYNTAX Integer32 (-1 | 0..2147483647)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The primary routing metric for this route. The		"The primary routing metric for this route. The
	semantics of this metric are determined by the		semantics of this metric are determined by the
	routing protocol specified in the route's		routing protocol specified in the route's
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	mplsL3VpnVrfRteInetCidrProto value. If this		mplsL3VpnVrfRteInetCidrProto value. If this
	metric is not used, its value should be set to		metric is not used, its value should be set to
	-1."		-1."
	DEFVAL { -1 }		DEFVAL { -1 }
	::= { mplsL3VpnVrfRteEntry 12 }		::= { mplsL3VpnVrfRteEntry 12 }
	mplsL3VpnVrfRteInetCidrMetric2 OBJECT-TYPE		mplsL3VpnVrfRteInetCidrMetric2 OBJECT-TYPE
	SYNTAX Integer32		SYNTAX Integer32 (-1 | 0..2147483647)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An alternate routing metric for this route. The		"An alternate routing metric for this route. The
	semantics of this metric are determined by the routing		semantics of this metric are determined by the routing
	protocol specified in the route's		protocol specified in the route's
	mplsL3VpnVrfRteInetCidrProto		mplsL3VpnVrfRteInetCidrProto
	value. If this metric is not used, its value should be		value. If this metric is not used, its value should be
	set to -1."		set to -1."
	DEFVAL { -1 }		DEFVAL { -1 }
	::= { mplsL3VpnVrfRteEntry 13 }		::= { mplsL3VpnVrfRteEntry 13 }
	mplsL3VpnVrfRteInetCidrMetric3 OBJECT-TYPE		mplsL3VpnVrfRteInetCidrMetric3 OBJECT-TYPE
	SYNTAX Integer32		SYNTAX Integer32 (-1 | 0..2147483647)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An alternate routing metric for this route. The		"An alternate routing metric for this route. The
	semantics of this metric are determined by the routing		semantics of this metric are determined by the routing
	protocol specified in the route's		protocol specified in the route's
	mplsL3VpnVrfRteInetCidrProto		mplsL3VpnVrfRteInetCidrProto
	value. If this metric is not used, its value should be		value. If this metric is not used, its value should be
	set to -1."		set to -1."
	DEFVAL { -1 }		DEFVAL { -1 }
	::= { mplsL3VpnVrfRteEntry 14 }		::= { mplsL3VpnVrfRteEntry 14 }
	mplsL3VpnVrfRteInetCidrMetric4 OBJECT-TYPE		mplsL3VpnVrfRteInetCidrMetric4 OBJECT-TYPE
	SYNTAX Integer32		SYNTAX Integer32 (-1 | 0..2147483647)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An alternate routing metric for this route. The		"An alternate routing metric for this route. The
	semantics of this metric are determined by the routing		semantics of this metric are determined by the routing
	protocol specified in the route's		protocol specified in the route's
	mplsL3VpnVrfRteInetCidrProto value. If this metric		mplsL3VpnVrfRteInetCidrProto value. If this metric
	is not used, its value should be set to -1."		is not used, its value should be set to -1."
	DEFVAL { -1 }		DEFVAL { -1 }
	::= { mplsL3VpnVrfRteEntry 15 }		::= { mplsL3VpnVrfRteEntry 15 }
	mplsL3VpnVrfRteInetCidrMetric5 OBJECT-TYPE		mplsL3VpnVrfRteInetCidrMetric5 OBJECT-TYPE
	SYNTAX Integer32		SYNTAX Integer32 (-1 | 0..2147483647)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An alternate routing metric for this route. The		"An alternate routing metric for this route. The
	semantics of this metric are determined by the routing		semantics of this metric are determined by the routing
	protocol specified in the route's		protocol specified in the route's
	mplsL3VpnVrfRteInetCidrProto value. If this metric is		mplsL3VpnVrfRteInetCidrProto value. If this metric is
	not used, its value should be set to -1."		not used, its value should be set to -1."
	DEFVAL { -1 }		DEFVAL { -1 }
	::= { mplsL3VpnVrfRteEntry 16 }		::= { mplsL3VpnVrfRteEntry 16 }
	skipping to change at page 27, line 31 ¶		skipping to change at page 28, line 7 ¶
	DESCRIPTION		DESCRIPTION
	"Index into mplsXCTable which identifies which cross		"Index into mplsXCTable which identifies which cross
	connect entry is associated with this VRF route entry		connect entry is associated with this VRF route entry
	by containing the mplsXCIndex of that cross-connect entry.		by containing the mplsXCIndex of that cross-connect entry.
	The string containing the single octet 0x00 indicates that		The string containing the single octet 0x00 indicates that
	a label stack is not associated with this route entry. This		a label stack is not associated with this route entry. This
	can be the case because the label bindings have not yet		can be the case because the label bindings have not yet
	been established, or because some change in the agent has		been established, or because some change in the agent has
	removed them.		removed them.
	When the label stack associated with this VRF route is created		When the label stack associated with this VRF route is created,
	by the agent, it MUST establish the associated cross-connect		it MUST establish the associated cross-connect
	entry in the mplsXCTable and then set that index to the value		entry in the mplsXCTable and then set that index to the value
	of this object. Changes to the cross-connect object in the		of this object. Changes to the cross-connect object in the
	mplsXCTable MUST automatically be be reflected the value of		mplsXCTable MUST automatically be be reflected the value of
	this object. If this object represents a static routing entry,		this object. If this object represents a static routing entry,
	then the manager must ensure that this entry is also maintained		then the manager must ensure that this entry is also maintained
	consistently in the corresponding mplsXCTable as well."		consistently in the corresponding mplsXCTable as well."
	REFERENCE		REFERENCE
	"RFC 3813 - Multiprotocol Label Switching (MPLS) Label Switching		"RFC 3813 - Multiprotocol Label Switching (MPLS) Label Switching
	Router (LSR) Management Information base (MIB), C. Srinivasan,		Router (LSR) Management Information base (MIB), C. Srinivasan,
	A. Vishwanathan, and T. Nadeau, June 2004"		A. Vishwanathan, and T. Nadeau, June 2004"
	skipping to change at page 28, line 5 ¶		skipping to change at page 28, line 32 ¶
	SYNTAX RowStatus		SYNTAX RowStatus
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The row status variable, used according to row		"The row status variable, used according to row
	installation and removal conventions.		installation and removal conventions.
	A row entry cannot be modified when the status is		A row entry cannot be modified when the status is
	marked as active(1)."		marked as active(1)."
	::= { mplsL3VpnVrfRteEntry 18 }		::= { mplsL3VpnVrfRteEntry 18 }
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	-- MPLS L3VPN Notifications		-- MPLS L3VPN Notifications
			mplsL3VpnVrfUp NOTIFICATION-TYPE
	mplsVrfIfUp NOTIFICATION-TYPE
	OBJECTS { mplsL3VpnIfConfRowStatus,		OBJECTS { mplsL3VpnIfConfRowStatus,
	mplsL3VpnVrfOperStatus		mplsL3VpnVrfOperStatus
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This notification is generated when:		"This notification is generated when:
	a. The ifOperStatus of an interface associated with a VRF		a. The ifOperStatus of an interface associated with
	changes to the up(1) state.		a VRF changes to the up(1) state.
	b. When an interface with ifOperStatus = up(1) is		b. When an interface with ifOperStatus = up(1) is
	associated with a VRF."		associated with a VRF."
	::= { mplsL3VpnNotifications 1 }		::= { mplsL3VpnNotifications 1 }
	mplsVrfIfDown NOTIFICATION-TYPE		mplsL3VpnVrfDown NOTIFICATION-TYPE
	OBJECTS { mplsL3VpnIfConfRowStatus,		OBJECTS { mplsL3VpnIfConfRowStatus,
	mplsL3VpnVrfOperStatus		mplsL3VpnVrfOperStatus
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This notification is generated when:		"This notification is generated when:
	a. The ifOperStatus of an interface associated with a VRF		a. The ifOperStatus of an interface associated with a VRF
	changes to the down(1) state.		changes to the down(1) state.
	b. When an interface with ifOperStatus = up(1) state is		b. When an interface with ifOperStatus = up(1) state is
	disassociated with a VRF."		disassociated with a VRF."
	::= { mplsL3VpnNotifications 2 }		::= { mplsL3VpnNotifications 2 }
	mplsNumVrfRouteMidThreshExceeded NOTIFICATION-TYPE		mplsL3VpnVrfRouteMidThreshExceeded NOTIFICATION-TYPE
	OBJECTS { mplsL3VpnVrfPerfCurrNumRoutes,		OBJECTS { mplsL3VpnVrfPerfCurrNumRoutes,
	mplsL3VpnVrfConfMidRteThresh		mplsL3VpnVrfConfMidRteThresh
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This notification is generated when the number of routes		"This notification is generated when the number of routes
	contained by the specified VRF exceeds the value indicated by		contained by the specified VRF exceeds the value indicated by
	mplsL3VpnVrfMidRouteThreshold. A single notification MUST be		mplsL3VpnVrfMidRouteThreshold. A single notification MUST be
	generated when this threshold is exceeded, and no other		generated when this threshold is exceeded, and no other
	notifications of this type should be issued until the value		notifications of this type should be issued until the value
	of mplsL3VpnVrfPerfCurrNumRoutes has fallen below that of		of mplsL3VpnVrfPerfCurrNumRoutes has fallen below that of
	mplsL3VpnVrfConfMidRteThresh."		mplsL3VpnVrfConfMidRteThresh."
	::= { mplsL3VpnNotifications 3 }		::= { mplsL3VpnNotifications 3 }
	mplsNumVrfRouteMaxThreshExceeded NOTIFICATION-TYPE		mplsL3VpnVrfNumVrfRouteMaxThreshExceeded NOTIFICATION-TYPE
	OBJECTS { mplsL3VpnVrfPerfCurrNumRoutes,		OBJECTS { mplsL3VpnVrfPerfCurrNumRoutes,
	mplsL3VpnVrfConfHighRteThresh		mplsL3VpnVrfConfHighRteThresh
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This notification is generated when the number of routes		"This notification is generated when the number of routes
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	contained by the specified VRF exceeds or attempts to exceed		contained by the specified VRF exceeds or attempts to exceed
	the maximum allowed value as indicated by		the maximum allowed value as indicated by
	mplsL3VpnVrfMaxRouteThreshold. In cases where		mplsL3VpnVrfMaxRouteThreshold. In cases where
	mplsL3VpnVrfConfHighRteThresh is set to the same value		mplsL3VpnVrfConfHighRteThresh is set to the same value
	as mplsL3VpnVrfConfMaxRoutes, mplsL3VpnVrfConfHighRteThresh		as mplsL3VpnVrfConfMaxRoutes, mplsL3VpnVrfConfHighRteThresh
	need not be exceeded; rather, just reached for this notification		need not be exceeded; rather, just reached for this notification
	to be issued.		to be issued.
	Note that mplsL3VpnVrfConfRteMxThrshTime denotes the interval		Note that mplsL3VpnVrfConfRteMxThrshTime denotes the interval
	at which the this notification will be re-issued after the		at which the this notification will be re-issued after the
	maximum value has been exceeded (or reached if		maximum value has been exceeded (or reached if
	skipping to change at page 29, line 27 ¶		skipping to change at page 30, line 4 ¶
	mplsL3VpnVrfConfMaxRoutes and mplsL3VpnVrfConfHighRteThresh are		mplsL3VpnVrfConfMaxRoutes and mplsL3VpnVrfConfHighRteThresh are
	equal) and the initial notification has been issued. This value		equal) and the initial notification has been issued. This value
	is intended to prevent continuous generation of notifications by		is intended to prevent continuous generation of notifications by
	an agent in the event that routes are continually added to a VRF		an agent in the event that routes are continually added to a VRF
	after it has reached its maximum value. The default value is 0		after it has reached its maximum value. The default value is 0
	minutes. If this value is set to 0, the agent should only issue		minutes. If this value is set to 0, the agent should only issue
	a single notification at the time that the maximum threshold has		a single notification at the time that the maximum threshold has
	been reached, and should not issue any more notifications until		been reached, and should not issue any more notifications until
	the value of routes has fallen below the configured threshold		the value of routes has fallen below the configured threshold
	value."		value."
	::= { mplsL3VpnNotifications 4 }		::= { mplsL3VpnNotifications 4 }
	mplsNumVrfSecIllglLblThrshExcd NOTIFICATION-TYPE		mplsL3VpnNumVrfSecIllglLblThrshExcd NOTIFICATION-TYPE
	OBJECTS { mplsL3VpnVrfSecIllegalLblVltns }		OBJECTS { mplsL3VpnVrfSecIllegalLblVltns }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This notification is generated when the number of illegal		"This notification is generated when the number of illegal
	label violations on a VRF as indicated by		label violations on a VRF as indicated by
	mplsL3VpnVrfSecIllegalLblVltns has exceeded		mplsL3VpnVrfSecIllegalLblVltns has exceeded
	mplsL3VpnIllLblRcvThrsh. The threshold is not		mplsL3VpnIllLblRcvThrsh. The threshold is not
	included in the varbind here because the value of		included in the varbind here because the value of
	mplsL3VpnVrfSecIllegalLblVltns should be one greater than		mplsL3VpnVrfSecIllegalLblVltns should be one greater than
	the threshold at the time this notification is issued."		the threshold at the time this notification is issued."
	::= { mplsL3VpnNotifications 5 }		::= { mplsL3VpnNotifications 5 }
	mplsNumVrfRouteMaxThreshCleared NOTIFICATION-TYPE		mplsL3VpnNumVrfRouteMaxThreshCleared NOTIFICATION-TYPE
	OBJECTS { mplsL3VpnVrfPerfCurrNumRoutes,		OBJECTS { mplsL3VpnVrfPerfCurrNumRoutes,
	mplsL3VpnVrfConfHighRteThresh		mplsL3VpnVrfConfHighRteThresh
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This notification is generated only after the number of routes		"This notification is generated only after the number of routes
	contained by the specified VRF exceeds or attempts to exceed		contained by the specified VRF exceeds or attempts to exceed
	the maximum allowed value as indicated by		the maximum allowed value as indicated by
	mplsVrfMaxRouteThreshold, and then falls below this value. The		mplsVrfMaxRouteThreshold, and then falls below this value. The
	emission of this notification informs the operator that the		emission of this notification informs the operator that the
	error condition has been cleared without the operator having to		error condition has been cleared without the operator having to
	query the device.		query the device.
	Note that mplsL3VpnVrfConfRteMxThrshTime denotes the interval at		Note that mplsL3VpnVrfConfRteMxThrshTime denotes the interval at
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	which the the mplsNumVrfRouteMaxThreshExceeded notification will		which the the mplsNumVrfRouteMaxThreshExceeded notification will
	be re-issued after the maximum value has been exceeded (or		be re-issued after the maximum value has been exceeded (or
	reached if mplsL3VpnVrfConfMaxRoutes and		reached if mplsL3VpnVrfConfMaxRoutes and
	mplsL3VpnVrfConfHighRteThresh are equal) and the initial		mplsL3VpnVrfConfHighRteThresh are equal) and the initial
	notification has been issued. Therefore,		notification has been issued. Therefore,
	the generation of this notification should also be emitted with		the generation of this notification should also be emitted with
	this same frequency (assuming that the error condition is		this same frequency (assuming that the error condition is
	cleared). Specifically, if the error condition is reached and		cleared). Specifically, if the error condition is reached and
	cleared several times during the period of time specified in		cleared several times during the period of time specified in
	mplsL3VpnVrfConfRteMxThrshTime, only a single notification will		mplsL3VpnVrfConfRteMxThrshTime, only a single notification will
	skipping to change at page 30, line 53 ¶		skipping to change at page 31, line 33 ¶
	mplsL3VpnVrfGroup,		mplsL3VpnVrfGroup,
	mplsL3VpnIfGroup,		mplsL3VpnIfGroup,
	mplsL3VpnPerfGroup,		mplsL3VpnPerfGroup,
	mplsL3VpnVrfRteGroup,		mplsL3VpnVrfRteGroup,
	mplsL3VpnVrfRTGroup,		mplsL3VpnVrfRTGroup,
	mplsL3VpnSecGroup,		mplsL3VpnSecGroup,
	mplsL3VpnNotificationGroup		mplsL3VpnNotificationGroup
	}		}
	GROUP mplsL3VpnPerfRouteGroup		GROUP mplsL3VpnPerfRouteGroup
	DESCRIPTION "This group is only mandatory for LSRs that wish to		DESCRIPTION "This group is only mandatory for LSRs that
	support tracking the number of routes attempted to		support tracking the number of routes attempted
	be added to VRFs."		to be added to VRFs."
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	OBJECT mplsL3VpnIfConfRowStatus		OBJECT mplsL3VpnIfConfRowStatus
	SYNTAX RowStatus { active(1), notInService(2) }		SYNTAX RowStatus { active(1), notInService(2) }
	WRITE-SYNTAX RowStatus { active(1), notInService(2),		WRITE-SYNTAX RowStatus { active(1), notInService(2),
	createAndGo(4), destroy(6)		createAndGo(4), destroy(6)
	}		}
	DESCRIPTION "Support for createAndWait and notReady is		DESCRIPTION "Support for createAndWait and notReady is
	not required."		not required."
	OBJECT mplsL3VpnVrfConfRowStatus		OBJECT mplsL3VpnVrfConfRowStatus
	skipping to change at page 31, line 37 ¶		skipping to change at page 32, line 19 ¶
	}		}
	DESCRIPTION "Support for createAndWait and notReady is		DESCRIPTION "Support for createAndWait and notReady is
	not required."		not required."
	::= { mplsL3VpnCompliances 1 }		::= { mplsL3VpnCompliances 1 }
	--		--
	-- ReadOnly Compliance		-- ReadOnly Compliance
	--		--
	mplsL3VpnModuleReadOnlyComplianc MODULE-COMPLIANCE		mplsL3VpnModuleReadOnlyCompliance MODULE-COMPLIANCE
	STATUS current		STATUS current
	DESCRIPTION "Compliance requirement for implementations that only		DESCRIPTION "Compliance requirement for implementations that only
	provide read-only support for L3-MPLS-VPN-STD-MIB.		provide read-only support for L3-MPLS-VPN-STD-MIB.
	Such devices can then be monitored but cannot be		Such devices can then be monitored but cannot be
	configured using this MIB module.		configured using this MIB module.
	"		"
	MODULE -- this module		MODULE -- this module
	MANDATORY-GROUPS { mplsL3VpnScalarGroup,		MANDATORY-GROUPS { mplsL3VpnScalarGroup,
	mplsL3VpnVrfGroup,		mplsL3VpnVrfGroup,
	mplsL3VpnIfGroup,		mplsL3VpnIfGroup,
	mplsL3VpnPerfGroup,		mplsL3VpnPerfGroup,
	mplsL3VpnVrfRteGroup,		mplsL3VpnVrfRteGroup,
	mplsL3VpnVrfRTGroup,		mplsL3VpnVrfRTGroup,
	mplsL3VpnSecGroup,		mplsL3VpnSecGroup,
	mplsL3VpnNotificationGroup		mplsL3VpnNotificationGroup
	}		}
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	GROUP mplsL3VpnPerfRouteGroup		GROUP mplsL3VpnPerfRouteGroup
	DESCRIPTION "This group is only mandatory for LSRs that wish to		DESCRIPTION "This group is only mandatory for LSRs that
	support tracking the number of routes attempted to		support tracking the number of routes attempted to
	be added to VRFs."		be added to VRFs."
	OBJECT mplsL3VpnIfConfRowStatus		OBJECT mplsL3VpnIfConfRowStatus
	SYNTAX RowStatus { active(1), notInService(2) }		SYNTAX RowStatus { active(1) }
	WRITE-SYNTAX RowStatus { active(1), notInService(2),		MIN-ACCESS read-only
	createAndGo(4), destroy(6)		DESCRIPTION "Write access is not required."
	}
	DESCRIPTION "Support for createAndWait and notReady is not
	required."
	OBJECT mplsL3VpnVrfConfRowStatus		OBJECT mplsL3VpnVrfConfRowStatus
	SYNTAX RowStatus { active(1), notInService(2) }		SYNTAX RowStatus { active(1) }
	WRITE-SYNTAX RowStatus { active(1), notInService(2),		MIN-ACCESS read-only
	createAndGo(4), destroy(6)		DESCRIPTION "Write access is not required."
	}
	DESCRIPTION "Support for createAndWait and notReady is not
	required."
	OBJECT mplsL3VpnVrfRTRowStatus		OBJECT mplsL3VpnVrfRTRowStatus
	SYNTAX RowStatus { active(1), notInService(2) }		SYNTAX RowStatus { active(1) }
	WRITE-SYNTAX RowStatus { active(1), notInService(2),		MIN-ACCESS read-only
	createAndGo(4), destroy(6)		DESCRIPTION "Write access is not required."
	}
	DESCRIPTION "Support for createAndWait and notReady is not
	required."
	OBJECT mplsL3VpnIfVpnClassification		OBJECT mplsL3VpnIfVpnClassification
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnIfVpnRouteDistProtocol		OBJECT mplsL3VpnIfVpnRouteDistProtocol
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnIfConfStorageType		OBJECT mplsL3VpnIfConfStorageType
	skipping to change at page 33, line 5 ¶		skipping to change at page 33, line 29 ¶
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnVrfVpnId		OBJECT mplsL3VpnVrfVpnId
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnVrfDescription		OBJECT mplsL3VpnVrfDescription
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	OBJECT mplsL3VpnVrfRD		OBJECT mplsL3VpnVrfRD
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnVrfConfMidRteThresh		OBJECT mplsL3VpnVrfConfMidRteThresh
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnVrfConfHighRteThresh		OBJECT mplsL3VpnVrfConfHighRteThresh
	MIN-ACCESS read-only		MIN-ACCESS read-only
	skipping to change at page 34, line 4 ¶		skipping to change at page 34, line 30 ¶
	OBJECT mplsL3VpnVrfRteInetCidrNextHopAS		OBJECT mplsL3VpnVrfRteInetCidrNextHopAS
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnVrfRteInetCidrMetric1		OBJECT mplsL3VpnVrfRteInetCidrMetric1
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnVrfRteInetCidrMetric2		OBJECT mplsL3VpnVrfRteInetCidrMetric2
	MIN-ACCESS read-only		MIN-ACCESS read-only
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnVrfRteInetCidrMetric3		OBJECT mplsL3VpnVrfRteInetCidrMetric3
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnVrfRteInetCidrMetric4		OBJECT mplsL3VpnVrfRteInetCidrMetric4
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnVrfRteInetCidrMetric5		OBJECT mplsL3VpnVrfRteInetCidrMetric5
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnVrfRteXCPointer		OBJECT mplsL3VpnVrfRteXCPointer
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."		DESCRIPTION "Write access is not required."
	OBJECT mplsL3VpnVrfRteInetCidrStatus		OBJECT mplsL3VpnVrfRteInetCidrStatus
	SYNTAX RowStatus { active(1), notInService(2) }		SYNTAX RowStatus { active(1) }
	WRITE-SYNTAX RowStatus { active(1), notInService(2),		MIN-ACCESS read-only
	createAndGo(4), destroy(6)		DESCRIPTION "Write access is not required."
	}
	DESCRIPTION "Support for createAndWait and notReady is not
	required."
	::= { mplsL3VpnCompliances 2 }		::= { mplsL3VpnCompliances 2 }
	-- Units of conformance.		-- Units of conformance.
	mplsL3VpnScalarGroup OBJECT-GROUP		mplsL3VpnScalarGroup OBJECT-GROUP
	OBJECTS { mplsL3VpnConfiguredVrfs,		OBJECTS { mplsL3VpnConfiguredVrfs,
	mplsL3VpnActiveVrfs,		mplsL3VpnActiveVrfs,
	mplsL3VpnConnectedInterfaces,		mplsL3VpnConnectedInterfaces,
	mplsL3VpnNotificationEnable,		mplsL3VpnNotificationEnable,
	mplsL3VpnVrfConfMaxPossRts,		mplsL3VpnVrfConfMaxPossRts,
	mplsL3VpnVrfConfRteMxThrshTime,		mplsL3VpnVrfConfRteMxThrshTime,
	skipping to change at page 35, line 4 ¶		skipping to change at page 35, line 27 ¶
	DESCRIPTION		DESCRIPTION
	"Collection of scalar objects required for MPLS VPN		"Collection of scalar objects required for MPLS VPN
	management."		management."
	::= { mplsL3VpnGroups 1 }		::= { mplsL3VpnGroups 1 }
	mplsL3VpnVrfGroup OBJECT-GROUP		mplsL3VpnVrfGroup OBJECT-GROUP
	OBJECTS { mplsL3VpnVrfVpnId,		OBJECTS { mplsL3VpnVrfVpnId,
	mplsL3VpnVrfDescription,		mplsL3VpnVrfDescription,
	mplsL3VpnVrfRD,		mplsL3VpnVrfRD,
	mplsL3VpnVrfCreationTime,		mplsL3VpnVrfCreationTime,
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	mplsL3VpnVrfOperStatus,		mplsL3VpnVrfOperStatus,
	mplsL3VpnVrfActiveInterfaces,		mplsL3VpnVrfActiveInterfaces,
	mplsL3VpnVrfAssociatedInterfaces,		mplsL3VpnVrfAssociatedInterfaces,
	mplsL3VpnVrfConfMidRteThresh,		mplsL3VpnVrfConfMidRteThresh,
	mplsL3VpnVrfConfHighRteThresh,		mplsL3VpnVrfConfHighRteThresh,
	mplsL3VpnVrfConfMaxRoutes,		mplsL3VpnVrfConfMaxRoutes,
	mplsL3VpnVrfConfLastChanged,		mplsL3VpnVrfConfLastChanged,
	mplsL3VpnVrfConfRowStatus,		mplsL3VpnVrfConfRowStatus,
			mplsL3VpnVrfConfAdminStatus,
	mplsL3VpnVrfConfStorageType		mplsL3VpnVrfConfStorageType
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Collection of objects needed for MPLS VPN VRF		"Collection of objects needed for MPLS VPN VRF
	management."		management."
	::= { mplsL3VpnGroups 2 }		::= { mplsL3VpnGroups 2 }
	mplsL3VpnIfGroup OBJECT-GROUP		mplsL3VpnIfGroup OBJECT-GROUP
	OBJECTS { mplsL3VpnIfVpnClassification,		OBJECTS { mplsL3VpnIfVpnClassification,
	skipping to change at page 36, line 4 ¶		skipping to change at page 36, line 30 ¶
	OBJECTS { mplsL3VpnVrfPerfRoutesDropped,		OBJECTS { mplsL3VpnVrfPerfRoutesDropped,
	mplsL3VpnVrfPerfDiscTime		mplsL3VpnVrfPerfDiscTime
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Collection of objects needed to track MPLS VPN		"Collection of objects needed to track MPLS VPN
	routing table dropped routes."		routing table dropped routes."
	::= { mplsL3VpnGroups 5 }		::= { mplsL3VpnGroups 5 }
	mplsL3VpnSecGroup OBJECT-GROUP		mplsL3VpnSecGroup OBJECT-GROUP
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	OBJECTS { mplsL3VpnVrfSecIllegalLblVltns,		OBJECTS { mplsL3VpnVrfSecIllegalLblVltns,
	mplsL3VpnVrfSecDiscontinuityTime }		mplsL3VpnVrfSecDiscontinuityTime }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Collection of objects needed for MPLS VPN		"Collection of objects needed for MPLS VPN
	security-related information."		security-related information."
	::= { mplsL3VpnGroups 7 }		::= { mplsL3VpnGroups 7 }
	mplsL3VpnVrfRteGroup OBJECT-GROUP		mplsL3VpnVrfRteGroup OBJECT-GROUP
	OBJECTS {		OBJECTS {
	skipping to change at page 36, line 30 ¶		skipping to change at page 37, line 4 ¶
	mplsL3VpnVrfRteInetCidrAge,		mplsL3VpnVrfRteInetCidrAge,
	mplsL3VpnVrfRteInetCidrNextHopAS,		mplsL3VpnVrfRteInetCidrNextHopAS,
	mplsL3VpnVrfRteInetCidrMetric1,		mplsL3VpnVrfRteInetCidrMetric1,
	mplsL3VpnVrfRteInetCidrMetric2,		mplsL3VpnVrfRteInetCidrMetric2,
	mplsL3VpnVrfRteInetCidrMetric3,		mplsL3VpnVrfRteInetCidrMetric3,
	mplsL3VpnVrfRteInetCidrMetric4,		mplsL3VpnVrfRteInetCidrMetric4,
	mplsL3VpnVrfRteInetCidrMetric5,		mplsL3VpnVrfRteInetCidrMetric5,
	mplsL3VpnVrfRteXCPointer,		mplsL3VpnVrfRteXCPointer,
	mplsL3VpnVrfRteInetCidrStatus		mplsL3VpnVrfRteInetCidrStatus
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Objects required for VRF route table management."		"Objects required for VRF route table management."
	::= { mplsL3VpnGroups 8 }		::= { mplsL3VpnGroups 8 }
	mplsL3VpnVrfRTGroup OBJECT-GROUP		mplsL3VpnVrfRTGroup OBJECT-GROUP
	OBJECTS { mplsL3VpnVrfRTDescr,		OBJECTS { mplsL3VpnVrfRTDescr,
	mplsL3VpnVrfRT,		mplsL3VpnVrfRT,
	mplsL3VpnVrfRTRowStatus,		mplsL3VpnVrfRTRowStatus,
	mplsL3VpnVrfRTStorageType		mplsL3VpnVrfRTStorageType
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Objects required for VRF route target management."		"Objects required for VRF route target management."
	::= { mplsL3VpnGroups 9 }		::= { mplsL3VpnGroups 9 }
	mplsL3VpnNotificationGroup NOTIFICATION-GROUP		mplsL3VpnNotificationGroup NOTIFICATION-GROUP
	NOTIFICATIONS { mplsVrfIfUp,		NOTIFICATIONS { mplsL3VpnVrfUp,
	mplsVrfIfDown,		mplsL3VpnVrfDown,
	mplsNumVrfRouteMidThreshExceeded,		mplsL3VpnVrfRouteMidThreshExceeded,
	mplsNumVrfRouteMaxThreshExceeded,		mplsL3VpnVrfNumVrfRouteMaxThreshExceeded,
	mplsNumVrfSecIllglLblThrshExcd,		mplsL3VpnNumVrfSecIllglLblThrshExcd,
	mplsNumVrfRouteMaxThreshCleared		mplsL3VpnNumVrfRouteMaxThreshCleared
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Objects required for MPLS VPN notifications."		"Objects required for MPLS VPN notifications."
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	::= { mplsL3VpnGroups 10 }		::= { mplsL3VpnGroups 10 }
	END		END
	9.0 Acknowledgments		-- End of MPLS-VPN-MIB
			9. Acknowledgments
	This document has benefited from discussions and input from		This document has benefited from discussions and input from
	Bill Fenner, Gerald Ash, Sumit Mukhopadhyay, Mike Piecuch,		Bill Fenner, Gerald Ash, Sumit Mukhopadhyay, Mike Piecuch,
	and Joan Weiss.		and Joan Weiss.
	10.0 Intellectual Property Considerations		10. Intellectual Property Statement
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	intellectual property or other rights that might be claimed to per-		Intellectual Property Rights or other rights that might be claimed to
	tain to the implementation or use of the technology described in this		pertain to the implementation or use of the technology described in
	document or the extent to which any license under such rights might		this document or the extent to which any license under such rights
	or might not be available; neither does it represent that it has made		might or might not be available; nor does it represent that it has
	any effort to identify any such rights. Information on the IETF's		made any independent effort to identify any such rights. Information
	procedures with respect to rights in standards-track and standards-		on the procedures with respect to rights in RFC documents can be
	related documentation can be found in BCP-11. Copies of claims of		found in BCP 78 and BCP 79.
	rights made available for publication and any assurances of licenses
	to be made available, or the result of an attempt made to obtain a		Copies of IPR disclosures made to the IETF Secretariat and any
	general license or permission for the use of such proprietary rights		assurances of licenses to be made available, or the result of an
	by implementers or users of this specification can be obtained from		attempt made to obtain a general license or permission for the use of
	the IETF Secretariat.		such proprietary rights by implementers or users of this
			specification can be obtained from the IETF on-line IPR repository at
			http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any		The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary		copyrights, patents or patent applications, or other proprietary
	rights which may cover technology that may be required to practice		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF Executive		this standard. Please address the information to the IETF at ietf-
	Director.		ipr@ietf.org.
	14.0 References		11. References
	14.1 Normative References		11.1 Normative References
	[RFC2547] Rosen, E., Rekhter, Y., et al., "BGP/MPLS VPNs",		[RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
	RFC2547, March 1999.		Requirement Levels", BCP 14, RFC2119, March 1997.
			[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
			Conventions and for Multiprotocol Label Switching (MPLS)
			Management", RFC 3811, June 2004.
			[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
			Label Switching Architecture", RFC 3031, January 2001.
	[RFC2547bis] Rosen, E., Rekhter, Y., et al., "BGP/MPLS		[RFC2547bis] Rosen, E., Rekhter, Y., et al., "BGP/MPLS
	VPNs", Internet Draft <draft-l3vpn-rfc2547bis-01.txt>,		VPNs", Internet Draft <draft-l3vpn-rfc2547bis-01.txt>,
	September 2003.		September 2003.
	[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.
	[MPLSArch] Rosen, E., Viswanathan, A., and R. Callon,
	"Multiprotocol Label Switching Architecture",
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	RFC3031, January 2001.
	[RFC2685] Fox B., et al, "Virtual Private Networks		[RFC2685] Fox B., et al, "Virtual Private Networks
	Identifier", RFC 2685, September 1999.		Identifier", RFC 2685, September 1999.
			[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
			Architecture for Describing Simple Network Management
			Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
			December 2002.
	[RFC3813] Srinivasan, C., Viswanathan, A. and T.		[RFC3813] Srinivasan, C., Viswanathan, A. and T.
	Nadeau, "MPLS Multiprotocol Label Switching		Nadeau, "MPLS Multiprotocol Label Switching
	(MPLS) Label Switch Router Management		(MPLS) Label Switch Router Management
	Information Base ", RFC 3813, June 2004		Information Base ", RFC 3813, June 2004
	[RFC3812] C. Srinivasan, A. Viswanathan, and T. Nadeau, "MPLS		[RFC3812] C. Srinivasan, A. Viswanathan, and T. Nadeau, "MPLS
	Traffic Engineering Management Information Base ",		Traffic Engineering Management Information Base ",
	RFC 3812, June 2004		RFC 3812, June 2004
	[RFC2096] Baker, F., "IP Forwarding Table MIB", RFC2096,		[RFC2096] Baker, F., "IP Forwarding Table MIB",
	January 1997.		Request for Comments 2096, January 1997.
	[VPNTCMIB] B. Schliesser, and T. Nadeau, "Definition of		[VPNTCMIB] B. Schliesser, and T. Nadeau, "Definition of
	Textual Conventions for Provider Provisioned		Textual Conventions for Provider Provisioned
	Virtual Private Network (PPVPN) Management.",		Virtual Private Network (PPVPN) Management.",
	Internet Draft <draft-ietf-l3vpn-tc-mib-03.txt>,		Internet Draft <draft-ietf-l3vpn-tc-mib-03.txt>,
	May 2004.		May 2004.
	[RFC3291] Daniele, M., Haberman, B., Routhier, S., Schoenwaelder,		[RFC4001] Daniele, M., et al., "Textual Conventions for Internet
	J., "Textual Conventions for Internet Network Addresses",		Network Addresses", RFC4001, February 2005.
	RFC 3291, May 2002.
	-- RFC Ed : An update to RFC 3291 is in the works, in the case that
	-- draft-ietf-ops-rfc3291bis is published before or at the same
	-- time as this document, please update this reference and the two
	-- citations in the document. Afterwards, please remove this note.
	[RFC2863] McCloghrie, K., and Kastenholz, F., "The Interfaces Group		[RFC2863] McCloghrie, K., and Kastenholz, F., "The Interfaces Group
	MIB", RFC 2863, June 2000.		MIB", RFC 2863, June 2000.
	[2011upd] Routhier, S., "Management Information Base for the
	Internet Protocol (IP),
	draft-ietf-ipv6-rfc2011-update-02.txt, February 2003.
	[RTPROTO] IANA, "IP Route Protocol MIB",		[RTPROTO] IANA, "IP Route Protocol MIB",
	http://www.iana.org/assignments/ianaiprouteprotocol-mib,		http://www.iana.org/assignments/ianaiprouteprotocol-mib,
	September 2000.		September 2000.
	[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,		[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
	J., Rose, M., and S. Waldbusser, "Structure of		J., Rose, M., and S. Waldbusser, "Structure of
	Management Information Version 2 (SMIv2)", STD 58, RFC		Management Information Version 2 (SMIv2)", STD 58, RFC
	2578, April 1999.		2578, April 1999.
	[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205		[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
			Rose, M. and S. Waldbusser, "Textual Conventions for
			SMIv2", STD 58, RFC 2579, April 1999.
	14.2 Informative References		[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
			Rose, M. and S. Waldbusser, "Conformance Statements for
			SMIv2", STD 58, RFC 2580, April 1999.
	[RFC2026] S. Bradner, "The Internet Standards Process --		11.2 Informative References
	Revision 3", RFC 2026, October 1996.
	[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,		[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
	"Introduction and Applicability Statements for		"Introduction and Applicability Statements for
	Internet-Standard Management Framework", RFC 3410,		Internet-Standard Management Framework", RFC 3410,
	December 2002.		December 2002.
	[RFC3413] Levi, D., Meyer, P., Stewart, B.,		[RFC3413] Levi, D., Meyer, P., Stewart, B.,
	"SNMP Applications", RFC 3413, December 2002.		"SNMP Applications", RFC 3413, December 2002.
	12.0 Editors' Addresses		[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an
			IANA Considerations Section in RFCs", BCP 26, RFC 2434,
			October 1998.
			12. Editors' Addresses
	Thomas D. Nadeau		Thomas D. Nadeau
	Cisco Systems, Inc.		Cisco Systems, Inc.
	300 Beaverbrook Drive		300 Beaverbrook Drive
	Boxborough, MA		Boxborough, MA
	Phone: +1-978-936-1470		Phone: +1-978-936-1470
	Email: tnadeau@cisco.com		Email: tnadeau@cisco.com
	Harmen van der Linde		Harmen van der Linde
	AT&T - Layer-2/Layer-3 NM Architecture and Operations Planning		AT&T - Layer-2/Layer-3 NM Architecture and Operations Planning
	Room C2-3C34		Room C2-3C34
	200 Laurel Ave		200 Laurel Ave
	Middletown, NJ 07748		Middletown, NJ 07748
	Tel: +1-732-420-1916		Tel: +1-732-420-1916
	Email: hvdl@att.com		Email: hvdl@att.com
	13.0 Contributors' Addresses		13. Contributors' Addresses
	Luyuan Fang Martin Tatham		Luyuan Fang Martin Tatham
	AT&T British Telecom		AT&T British Telecom
	200 Laurel Ave BT Adastal Park,		200 Laurel Ave BT Adastal Park,
	Middletown, NJ 07748 Martlesham Heath,		Middletown, NJ 07748 Martlesham Heath,
	Phone: +1-732-420-1921 Ipswich, IP5 3RE		Phone: +1-732-420-1921 Ipswich, IP5 3RE
	Email: luyuanfang@att.com UK		Email: luyuanfang@att.com UK
	Tel: +44 1473 606349		Tel: +44 1473 606349
	Fax: +44 1473 606727		Fax: +44 1473 606727
	Email: martin.tatham@bt.com		Email: martin.tatham@bt.com
	Fabio M. Chiussi Joseph Dube		Fabio M. Chiussi Joseph Dube
	Bell Laboratories, Avici Systems, Inc.		Bell Laboratories, Avici Systems, Inc.
	Lucent Technologies 101 Billerica Avenue		Lucent Technologies 101 Billerica Avenue
	101 Crawfords Corner Road North Billerica, MA 01862		101 Crawfords Corner Road North Billerica, MA 01862
	Room 4D-521		Room 4D-521
	Holmdel, NJ 07733		Holmdel, NJ 07733
	Phone: +1-732-949-2407		Phone: +1-732-949-2407
	Email: fabio@bell-labs.com		Email: fabio@bell-labs.com
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205		14. Dedication
	14.0 Dedication
	Steve Brannon passed away suddenly on January 30, 2001. We would like		Steve Brannon passed away suddenly on January 30, 2001. We would like
	to dedicate our efforts in this area and this document to his memory.		to dedicate our efforts in this area and this document to his memory.
	15.0 Full Copyright Statement		15. Full Copyright Statement
	Copyright (C) The Internet Society (2004). This document is subject		Copyright (C) The Internet Society (2005). This document is
	to the rights, licenses and restrictions contained in BCP 78 and		subject to the rights, licenses and restrictions contained in BCP
	except as set forth therein, the authors retain all their rights.		78, and except as set forth therein, the authors retain all their
			rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET		REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
			PARTICULAR PURPOSE.
	16.0 Security Considerations		16. Security Considerations
	It is clear that these MIB modules are potentially useful for		It is clear that these MIB modules are potentially useful for
	monitoring of MPLS LSRs supporting L3 MPLS VPN. This		monitoring of MPLS LSRs supporting L3 MPLS VPN. This
	MIB module can also be used for configuration of certain objects,		MIB module can also be used for configuration of certain objects,
	and anything that can be configured can be incorrectly configured,		and anything that can be configured can be incorrectly configured,
	with potentially disastrous results.		with potentially disastrous results.
	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
	skipping to change at page 41, line 4 ¶		skipping to change at page 41, line 46 ¶
	interfaces and configuration. Unauthorized access to objects		interfaces and configuration. Unauthorized access to objects
	in these tables, could result in disruption of traffic on the		in these tables, could result in disruption of traffic on the
	network. This is especially true if these VRFs have been		network. This is especially true if these VRFs have been
	previously provisioned and are in use. The use of stronger		previously provisioned and are in use. The use of stronger
	mechanisms such as SNMPv3 security should be considered where		mechanisms such as SNMPv3 security should be considered where
	possible. Specifically,		possible. Specifically,
	SNMPv3 VACM and USM MUST be used with any v3 agent which		SNMPv3 VACM and USM MUST be used with any v3 agent which
	implements this MIB module. Administrators should consider		implements this MIB module. Administrators should consider
	whether read access to these objects should be allowed,		whether read access to these objects should be allowed,
	since read access may be undesirable under certain		since read access may be undesirable under certain
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	circumstances.		circumstances.
	Some of the readable objects in this MIB module (i.e., objects with a		Some of the readable objects in this MIB module (i.e., objects with a
	MAX-ACCESS other than not-accessible) may be considered sensitive or		MAX-ACCESS other than not-accessible) may be considered sensitive or
	vulnerable in some network environments. It is thus important to		vulnerable in some network environments. It is thus important to
	control even GET and/or NOTIFY access to these objects and possibly		control even GET and/or NOTIFY access to these objects and possibly
	to even encrypt the values of these objects when sending them over		to even encrypt the values of these objects when sending them over
	the network via SNMP. These are the tables and objects and their		the network via SNMP. These are the tables and objects and their
	sensitivity/vulnerability:		sensitivity/vulnerability:
	skipping to change at page 41, line 44 ¶		skipping to change at page 42, line 35 ¶
	authentication and privacy).		authentication and privacy).
	Further, deployment of SNMP versions prior to SNMPv3 is NOT		Further, deployment of SNMP versions prior to SNMPv3 is NOT
	RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to		RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
	enable cryptographic security. It is then a customer/operator		enable cryptographic security. It is then a customer/operator
	responsibility to ensure that the SNMP entity giving access to an		responsibility to ensure that the SNMP entity giving access to an
	instance of this MIB module, is properly configured to give access		instance of this MIB module, is properly configured to give access
	to the objects only to those principals (users) that have legitimate		to the objects only to those principals (users) that have legitimate
	rights to indeed GET or SET (change/create/delete) them.		rights to indeed GET or SET (change/create/delete) them.
	17. Intellectual Property Statement
	The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.
	Copies of IPR disclosures made to the IETF Secretariat and any
	assurances of licenses to be made available, or the result of an
	Internet Draft MPLS-L3VPN-STD-MIB February 1, 205
	attempt made to obtain a general license or permission for the use of
	such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at ietf-
	ipr@ietf.org.
	18. IANA Considerations		18. IANA Considerations
	As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB		As described in MPLS-TC-STD-MIB [RFC3811], MPLS related
	[MPLSTCMIB], MPLS related standards track MIB modules should be		standards track MIB modules should be rooted under the mplsStdMIB
	rooted under the mplsStdMIB subtree. There is one MPLS-related		subtree. There is one MPLS-related
	MIB module contained in this document. Each of the following "IANA		MIB module contained in this document. Each of the following "IANA
	Considerations" subsections requests IANA for a new assignment under		Considerations" subsections requests IANA for a new assignment under
	the mplsStdMIB subtree. New assignments can only be made via a		the mplsStdMIB subtree. New assignments can only be made via a
	Standards Action as specified in [RFC2434].		Standards Action as specified in [RFC2434].
	18.1. IANA Considerations for MPLS-L3VPN-STD-MIB		18.1. IANA Considerations for MPLS-L3VPN-STD-MIB
	The IANA is requested to assign { mplsStdMIB 11 } to the		The IANA is requested to assign { mplsStdMIB 11 } to the
	MPLS-L3VPN-STD-MIB module specified in this document.		MPLS-L3VPN-STD-MIB module specified in this document.
End of changes. 147 change blocks.
	375 lines changed or deleted		251 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/