draft-ietf-mpls-lsr-mib-07.txt		draft-ietf-mpls-lsr-mib-08.txt
	Network Working Group Cheenu Srinivasan		Network Working Group Cheenu Srinivasan
	Internet Draft Tachion Networks, Inc.		Internet Draft Parama Networks, Inc.
	Expires: July 2001		Expires: July 2002
	Arun Viswanathan		Arun Viswanathan
	Force10 Networks, Inc.		Force10 Networks, Inc.
	Thomas D. Nadeau		Thomas D. Nadeau
	Cisco Systems, Inc.		Cisco Systems, Inc.
	January 2001
	MPLS Label Switch Router Management Information Base Using SMIv2		January 2002
	draft-ietf-mpls-lsr-mib-07.txt		Multiprotocol Label Switching (MPLS) Label Switch Router (LSR)
			Management Information Base
			draft-ietf-mpls-lsr-mib-08.txt
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC 2026.		all provisions of Section 10 of RFC 2026.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 38		skipping to change at page 1, line 40
	documents at any time. It is inappropriate to use Internet-		documents at any time. It is inappropriate to use Internet-
	Drafts as reference material or to cite them other than as "work		Drafts as reference material or to cite them other than as "work
	in progress."		in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	Table of Contents		Abstract
	1. Abstract............................................2
	2. Introduction........................................2
	3. Terminology.........................................2
	4. The SNMP Management Framework.......................3
	4.1. Object Definitions..................................4
	5. Feature Checklist...................................4
	6. Outline.............................................5
	6.1. Summary of LSR MIB..................................5
	7. Brief Description of MIB Objects....................6
	7.1. mplsInterfaceConfTable..............................6
	7.2. mplsInterfacePerfTable..............................6
	7.3. mplsInSegmentTable..................................6
	7.4. mplsInSegmentPerfTable..............................7
	7.5. mplsOutSegmentTable.................................7
	7.6. mplsOutSegmentPerfTable............................7
	7.7. mplsXCTable........................................7
	7.8. mplsLabelStackTable................................8
	7.9. mplsTrafficParamTable..............................8
	8. Example of LSP Setup...............................8
	9. Application of the Interface Group to MPLS........10
	9.1. Support of the MPLS Layer by ifTable..............10
	10. The Use of RowPointer.............................12
	11. MPLS Label Switch Router MIB Definitions..........12
	12. Security Considerations...........................49
	13. Acknowledgments...................................50
	14. References........................................50
	15. Authors' Addresses................................53
	16. Full Copyright Statement..........................53
	1. Abstract
	This memo defines an experimental portion of the Management
	Information Base (MIB) for use with network management protocols
	in the Internet community. In particular, it describes managed
	objects for modeling a Multi-Protocol Label Switching (MPLS)
	[MPLSArch, MPLSFW] Label Switch Router (LSR).
	Note: There have been no changes to this document. This is only an		This memo defines a portion of the Management Information Base
	update to prevent the document from expiring while in IESG review.		(MIB) for use with network management protocols in the Internet
			community. In particular, it describes managed objects for
			modeling a Multiprotocol Label Switching (MPLS) Label Switch
			Router (LSR).
	2. Introduction		Table of Contents
	This memo defines an experimental portion of the Management		1. Introduction .............................................. 2
	Information Base (MIB) for use with network management protocols		2. Terminology ............................................... 2
	in the Internet community. In particular, it describes managed		3. The SNMP Management Framework ............................. 3
	objects for modeling a Multi-Protocol Label Switching (MPLS)		4. Feature Checklist ......................................... 4
	[MPLSArch, MPLSFW] Label Switch Router (LSR).		5. Outline ................................................... 5
			5.1. Summary of LSR MIB ..................................... 5
			6. Brief Description of MIB Objects .......................... 6
			6.1. mplsInterfaceConfTable ................................. 6
			6.2. mplsInterfacePerfTable ................................. 6
			6.3. mplsInSegmentTable ..................................... 6
			6.4. mplsInSegmentPerfTable ................................. 7
			6.5. mplsOutSegmentTable .................................... 7
			6.6. mplsOutSegmentPerfTable ................................ 7
			6.7. mplsXCTable ............................................ 7
			6.8. mplsLabelStackTable .................................... 8
			6.9. mplsTrafficParamTable .................................. 8
			7. Example of LSP Setup ...................................... 8
			8. Application of the Interface Group to MPLS ................ 10
			8.1. Support of the MPLS Layer by ifTable ................... 10
			9. The Use of RowPointer ..................................... 12
			10. MPLS Label Switch Router MIB Definitions ................. 12
			11. Security Considerations .................................. 48
			12. Acknowledgments .......................................... 49
			13. References ............................................... 49
			14. Authors' Addresses ....................................... 51
			15. Full Copyright Statement ................................. 52
	Comments should be made directly to the MPLS mailing list at		1. Introduction
	mpls@uu.net.
	This memo does not, in its draft form, specify a standard for the		This memo defines a portion of the Management Information Base
	Internet community.		(MIB) for use with network management protocols in the Internet
			community. In particular, it describes managed objects for
			modeling a Multi-Protocol Label Switching (MPLS) [RFC3031] Label
			Switch Router (LSR).
	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 [BCP14].		RFC 2119, reference [RFC2119].
	3. Terminology		2. Terminology
	This document uses terminology from the document describing the		This document uses terminology from the document describing the
	MPLS architecture [MPLSArch]. A label switched path (LSP) is		MPLS architecture [RFC3031]. A label switched path (LSP) is
	modeled as a connection consisting of one or more incoming		modeled as a connection consisting of one or more incoming
	segments (in-segments) and/or one or more outgoing segments (out-		segments (in-segments) and/or one or more outgoing segments (out-
	segments) at a label switch router (LSR). The association or		segments) at a label switch router (LSR). The association or
	interconnection of the in-segments and out-segments is		interconnection of the in-segments and out-segments is
	accomplished by using a cross-connect. We use the terminology		accomplished by using a cross-connect. We use the terminology
	"connection" and "LSP" interchangeably where the meaning is clear		"connection" and "LSP" interchangeably where the meaning is clear
	from the context.		from the context.
	4. The SNMP Management Framework		3. The SNMP Management Framework
	The SNMP Management Framework presently consists of five major		The SNMP Management Framework presently consists of five major
	components:		components:
	- An overall architecture, described in RFC 2271 [SNMPArch].		- An overall architecture, described in RFC 2571 [RFC2571].
	- Mechanisms for describing and naming objects and events for the		- Mechanisms for describing and naming objects and events for the
	purpose of management. The first version of this Structure of		purpose of management. The first version of this Structure of
	Management Information (SMI) is called SMIv1 and described in		Management Information (SMI) is called SMIv1 and described in
	RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215		STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD
	[SNMPv1Traps]. The second version, called SMIv2, is described		16, RFC 1215 [RFC1215]. The second version, called SMIv2, is
	in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904		described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579
	[SNMPv2Conf].		[RFC2579] and STD 58, RFC 2580 [RFC2580].
	- Message protocols for transferring management information. The		- Message protocols for transferring management information. The
	first version of the SNMP message protocol is called SNMPv1		first version of the SNMP message protocol is called SNMPv1
	and described in RFC 1157 [SNMPv1]. A second version of the		and described in STD 15, RFC 1157 [RFC1157]. A second version
	SNMP message protocol, which is not an Internet standards		of the SNMP message protocol, which is not an Internet
	track protocol, is called SNMPv2c and described in RFC 1901		standards track protocol, is called SNMPv2c and described in
	[SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the		RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version
	message protocol is called SNMPv3 and described in RFC 1906		of the message protocol is called SNMPv3 and described in RFC
	[SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM].		1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
	- Protocol operations for accessing management information. The		- Protocol operations for accessing management information. The
	first set of protocol operations and associated PDU formats is		first set of protocol operations and associated PDU formats is
	described in RFC 1157 [SNMPv1]. A second set of protocol		described in STD 15, RFC 1157 [RFC1157]. A second set of
	operations and associated PDU formats is described in RFC 1905		protocol operations and associated PDU formats is described in
	[SNMPv2PO].		RFC 1905 [RFC1905].
	- A set of fundamental applications described in RFC 2273
	[SNMPv3App] and the view-based access control mechanism
	described in RFC 2575 [SNMPv3VACM].
	Managed objects are accessed via a virtual information store,		- A set of fundamental applications described in RFC 2573
	termed the Management Information Base or MIB. Objects in the MIB		[RFC2573] and the view-based access control mechanism
	are defined using the mechanisms defined in the SMI. This memo		described in RFC 2575 [RFC2575].
	specifies a MIB module that is compliant to the SMIv2. A MIB
	conforming to the SMIv1 can be produced through the appropriate
	translations. The resulting translated MIB must be semantically
	equivalent, except where objects or events are omitted because no
	translation is possible (use of Counter64). Some machine-readable
	information in SMIv2 will be converted into textual descriptions
	in SMIv1 during the translation process. However, this loss of
	machine-readable information is not considered to change the
	semantics of the MIB.
	4.1. Object Definitions		A more detailed introduction to the current SNMP Management
			Framework can be found in RFC 2570 [RFC2570].
	Managed objects are accessed via a virtual information store,		Managed objects are accessed via a virtual information store,
	termed the Management Information Base or MIB. Objects in the MIB		termed the Management Information Base or MIB. Objects in the MIB
	are defined using the subset of Abstract Syntax Notation One		are defined using the mechanisms defined in the SMI.
	(ASN.1) defined in the SMI. In particular, each object type is
	named by an OBJECT IDENTIFIER, an administratively assigned name.
	The object type together with an object instance serves to
	uniquely identify a specific instantiation of the object. For
	human convenience, we often use a textual string, termed the
	descriptor, to also refer to the object type.
	5. Feature Checklist		This memo specifies a MIB module that is compliant to the SMIv2.
			A MIB conforming to the SMIv1 can be produced through the
			appropriate translations. The resulting translated MIB must be
			semantically equivalent, except where objects or events are
			omitted because no translation is possible (use of Counter64).
			Some machine readable information in SMIv2 will be converted into
			textual descriptions in SMIv1 during the translation process.
			However, this loss of machine readable information is not
			considered to change the semantics of the MIB.
			4. Feature Checklist
	The MPLS label switch router MIB (LSR-MIB) is designed to satisfy		The MPLS label switch router MIB (LSR-MIB) is designed to satisfy
	the following requirements and constraints:		the following requirements and constraints:
	- The MIB supports both manually configured LSPs as well as those		- The MIB supports both manually configured LSPs as well as those
	configured via any MPLS signaling protocol.		configured via any MPLS signaling protocol.
	- The MIB supports the enabling and disabling of MPLS capability		- The MIB supports the enabling and disabling of MPLS capability
	on MPLS capable interfaces of an LSR.		on MPLS capable interfaces of an LSR.
	- The MIB allows resource sharing between two or more LSPs.		- The MIB allows resource sharing between two or more LSPs.
	- Both per-platform and per-interface label spaces are supported.		- Both per-platform and per-interface label spaces are supported.
	- MPLS packets can be forwarded solely based on an incoming top		- MPLS packets can be forwarded solely based on an incoming top
	label [MPLSArch, LblStk].		label [RFC3031, RFC3032].
	- Support is provided for next-hop resolution when the outgoing		- Support is provided for next-hop resolution when the outgoing
	interface is a shared media interface. In the point-to-		interface is a shared media interface. In the point-to-
	multipoint case, each outgoing segment can reside on a		multipoint case, each outgoing segment can reside on a
	different shared media interface.		different shared media interface.
	- The MIB supports point-to-point, point-to-multipoint and		- The MIB supports point-to-point, point-to-multipoint and
	multipoint-to-point connections at an LSR.		multipoint-to-point connections at an LSR.
	- For multipoint-to-point connections all outgoing packets can		- For multipoint-to-point connections all outgoing packets can
	skipping to change at page 5, line 18		skipping to change at page 5, line 4
	- In the point-to-multipoint case each outgoing connection can		- In the point-to-multipoint case each outgoing connection can
	have a distinct label stack including the top label.		have a distinct label stack including the top label.
	- All the members of a point-to-multipoint connection can share		- All the members of a point-to-multipoint connection can share
	the resources allocated for the ingress segments.		the resources allocated for the ingress segments.
	- The MIB provides cross-connect capability to "pop" an incoming		- The MIB provides cross-connect capability to "pop" an incoming
	label and forward the packet with the remainder of the label		label and forward the packet with the remainder of the label
	stack unchanged and without pushing any labels ("pop-and-go")		stack unchanged and without pushing any labels ("pop-and-go")
	[LblStk].		[RFC3032].
	- The MIB supports persistent as well as non-persistent LSPs.		- The MIB supports persistent as well as non-persistent LSPs.
	- Performance counters are provided for in-segments and out-		- Performance counters are provided for in-segments and out-
	segments as well as for measuring MPLS performance on a per-		segments as well as for measuring MPLS performance on a per-
	interface basis.		interface basis.
	6. Outline		5. Outline
	Configuring LSPs through an LSR involves the following steps:		Configuring LSPs through an LSR involves the following steps:
	- Enabling MPLS on MPLS capable interfaces.		- Enabling MPLS on MPLS capable interfaces.
	- Configuring in-segments and out-segments.		- Configuring in-segments and out-segments.
	- Setting up the cross-connect table to associate segments and/or		- Setting up the cross-connect table to associate segments and/or
	to indicate connection origination and termination.		to indicate connection origination and termination.
	- Optionally specifying label stack actions.		- Optionally specifying label stack actions.
	- Optionally specifying segment traffic parameters.		- Optionally specifying segment traffic parameters.
	6.1. Summary of LSR MIB		5.1. Summary of LSR MIB
	The MIB objects for performing these actions consist of the		The MIB objects for performing these actions consist of the
	following tables:		following tables:
	- The interface configuration table (mplsInterfaceConfTable),		- The interface configuration table (mplsInterfaceConfTable),
	which is used for enabling the MPLS protocol on MPLS-capable		which is used for enabling the MPLS protocol on MPLS-capable
	interfaces.		interfaces.
	- The in-segment (mplsInSegmentTable) and out-segment		- The in-segment (mplsInSegmentTable) and out-segment
	(mplsOutSegmentTable) tables, which are used for configuring		(mplsOutSegmentTable) tables, which are used for configuring
	skipping to change at page 6, line 24		skipping to change at page 6, line 10
	used for specifying LSP-related traffic parameters.		used for specifying LSP-related traffic parameters.
	Further, the MPLS in-segment and out-segment performance tables,		Further, the MPLS in-segment and out-segment performance tables,
	mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the		mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the
	objects necessary to measure the performance of LSPs, and		objects necessary to measure the performance of LSPs, and
	mplsInterfacePerfTable has objects to measure MPLS performance on		mplsInterfacePerfTable has objects to measure MPLS performance on
	a per-interface basis.		a per-interface basis.
	These tables are described in the subsequent sections.		These tables are described in the subsequent sections.
	7. Brief Description of MIB Objects		6. Brief Description of MIB Objects
	Sections 7.1-7.2 describe objects pertaining to MPLS-capable		Sections 6.1-6.2 describe objects pertaining to MPLS-capable
	interfaces of an LSR. The objects described in Sections 7.3-7.8,		interfaces of an LSR. The objects described in Sections 6.3-6.8,
	were derived from the Incoming Label Map (ILM) and Next Hop Label		were derived from the Incoming Label Map (ILM) and Next Hop Label
	Forwarding Entry (NHLFE) as specified in the MPLS architecture		Forwarding Entry (NHLFE) as specified in the MPLS architecture
	document [MPLSArch]. Section 7.9 describes objects for specifying		document [RFC3031]. Section 6.9 describes objects for specifying
	traffic parameters for in and out segments. It is appropriate to		traffic parameters for in and out segments. It is appropriate to
	note that the in-segment, out-segment, and cross-connect tables		note that the in-segment, out-segment, and cross-connect tables
	were modeled after similar tables found in [ATOMMIB].		were modeled after similar tables found in [RFC2515].
	7.1. mplsInterfaceConfTable		6.1. mplsInterfaceConfTable
	This table represents the interfaces that are MPLS capable. An		This table represents the interfaces that are MPLS capable. An
	LSR creates an entry in this table for every MPLS capable		LSR creates an entry in this table for every MPLS capable
	interface on that LSR.		interface on that LSR.
	7.2. mplsInterfacePerfTable		6.2. mplsInterfacePerfTable
	This table contains objects to measure the MPLS performance of		This table contains objects to measure the MPLS performance of
	MPLS capable interfaces and is an AUGMENT to		MPLS capable interfaces and is an AUGMENT to
	mplsInterfaceConfTable. High capacity counters are provided for		mplsInterfaceConfTable. High capacity counters are provided for
	objects that are likely to wrap around quickly on high-speed		objects that are likely to wrap around quickly on high-speed
	interfaces.		interfaces.
	7.3. mplsInSegmentTable		6.3. mplsInSegmentTable
	This table contains a description of the incoming MPLS segments to		This table contains a description of the incoming MPLS segments to
	an LSR and their associated parameters.		an LSR and their associated parameters.
	The administrative and operational status objects for this table		The administrative and operational status objects for this table
	are used to control packet transmission on this segment. If		are used to control packet transmission on this segment. If
	either the administrative and operational status objects for this		either the administrative and operational status objects for this
	table are set to 'down', this implies that packets will not be		table are set to 'down', this implies that packets will not be
	forwarded. Likewise, if the values are set to 'up' this implies		forwarded. Likewise, if the values are set to 'up' this implies
	that packets are forwarded. These values are particularly useful		that packets are forwarded. These values are particularly useful
	in cases where multi-point connections utilize a single cross-		in cases where multi-point connections utilize a single cross-
	connect and the administrator wishes to disable some, but not all		connect and the administrator wishes to disable some, but not all
	of the streams. In these cases, the administrator may set the		of the streams. In these cases, the administrator may set the
	administrative status object to 'down' on some of the in-segments.		administrative status object to 'down' on some of the in-segments.
	7.4. mplsInSegmentPerfTable		6.4. mplsInSegmentPerfTable
	The MPLS In-Segment Performance Table has objects to measure the		The MPLS In-Segment Performance Table has objects to measure the
	performance of an incoming segment configured on an LSR. It is an		performance of an incoming segment configured on an LSR. It is an
	AUGMENT to mplsInSegmentTable. High capacity counters are		AUGMENT to mplsInSegmentTable. High capacity counters are
	provided for objects that are likely to wrap around quickly on		provided for objects that are likely to wrap around quickly on
	high-speed interfaces.		high-speed interfaces.
	7.5. mplsOutSegmentTable		6.5. mplsOutSegmentTable
	The Out-Segment Table contains a description of the outgoing MPLS		The Out-Segment Table contains a description of the outgoing MPLS
	segments at an LSR and their associated parameters.		segments at an LSR and their associated parameters.
	The administrative and operational status objects for this table		The administrative and operational status objects for this table
	are used to control packet transmission on this segment. If		are used to control packet transmission on this segment. If
	either the administrative and operational status objects are set		either the administrative and operational status objects are set
	to 'down', this implies that packets will not be forwarded.		to 'down', this implies that packets will not be forwarded.
	Likewise, if the values are set to 'up' this implies that packets		Likewise, if the values are set to 'up' this implies that packets
	are forwarded. These values are particularly useful in cases		are forwarded. These values are particularly useful in cases
	where multicast connections utilize a single cross-connect and the		where multicast connections utilize a single cross-connect and the
	administrator wishes to disable some, but not all of the streams.		administrator wishes to disable some, but not all of the streams.
	In these cases, the administrator may set the administrative		In these cases, the administrator may set the administrative
	status object to 'down' on some of the out-segments.		status object to 'down' on some of the out-segments.
	7.6. mplsOutSegmentPerfTable		6.6. mplsOutSegmentPerfTable
	The MPLS Out-Segment Table contains objects to measure the		The MPLS Out-Segment Table contains objects to measure the
	performance of an outgoing segment configured on an LSR. It is an		performance of an outgoing segment configured on an LSR. It is an
	AUGMENT to mplsOutSegmentTable. High capacity counters are		AUGMENT to mplsOutSegmentTable. High capacity counters are
	provided for objects that are likely to wrap around quickly on		provided for objects that are likely to wrap around quickly on
	high-speed interfaces.		high-speed interfaces.
	7.7. mplsXCTable		6.7. mplsXCTable
	The mplsXCTable specifies information for associating segments		The mplsXCTable specifies information for associating segments
	together in order to instruct the LSR to switch between the		together in order to instruct the LSR to switch between the
	specified segments. It supports point-to-point, point-to-multi-		specified segments. It supports point-to-point, point-to-multi-
	point and multi-point-to-point connections.		point and multi-point-to-point connections.
	The administrative and operational status objects for this table		The administrative and operational status objects for this table
	imply control of packet forwarding to and from a XCEntry. When		imply control of packet forwarding to and from a XCEntry. When
	the administrative and operational status objects are set to		the administrative and operational status objects are set to
	'down' for example, this implies that the specified XCEntry will		'down' for example, this implies that the specified XCEntry will
	not forward packets. Likewise, when either is set to 'up' this		not forward packets. Likewise, when either is set to 'up' this
	implies that packets will be forwarded.		implies that packets will be forwarded.
	7.8. mplsLabelStackTable		6.8. mplsLabelStackTable
	The mplsLabelStackTable specifies the label stack to be pushed		The mplsLabelStackTable specifies the label stack to be pushed
	onto a packet, beneath the top label. Entries to this table are		onto a packet, beneath the top label. Entries to this table are
	referred to from mplsXCTable.		referred to from mplsXCTable.
	7.9. mplsTrafficParamTable		6.9. mplsTrafficParamTable
	The mplsTrafficParamTable contains objects for specifying the		The mplsTrafficParamTable contains objects for specifying the
	traffic parameters of in-segments and out-segments. Entries in		traffic parameters of in-segments and out-segments. Entries in
	this table are referred to from mplsInSegmentTable and		this table are referred to from mplsInSegmentTable and
	mplsOutSegmentTable.		mplsOutSegmentTable.
	8. Example of LSP Setup		7. Example of LSP Setup
	In this section we provide a brief example of using the MIB		In this section we provide a brief example of setting up an LSP
	objects described in section 11. to set up an LSP. While this		using the MIB objects described in section 10. While this example
	example is not meant to illustrate every nuance of the MIB, it is		is not meant to illustrate every nuance of the MIB, it is intended
	intended as an aid to understanding some of the key concepts. It		as an aid to understanding some of the key concepts. It is meant
	is meant to be read after going through the MIB itself.		to be read after going through the MIB itself.
	Suppose that one would like to manually create a best-effort,		Suppose that one would like to manually create a best-effort,
	unidirectional LSP. Assume that the LSP enters the LSR via MPLS		unidirectional LSP. Assume that the LSP enters the LSR via MPLS
	interface A with ifIndex 12 and exits the LSR via MPLS interface B		interface A with ifIndex 12 and exits the LSR via MPLS interface B
	with ifIndex 13. Let us assume that we do not wish to have a		with ifIndex 13. Let us assume that we do not wish to have a
	label stack beneath the top label on the outgoing labeled packets.		label stack beneath the top label on the outgoing labeled packets.
	The following example illustrates which rows and corresponding		The following example illustrates which rows and corresponding
	objects might be created to accomplish this.		objects might be created to accomplish this.
	First, the traffic parameter entries must be set-up for both		First, the traffic parameter entries must be set-up for both
	skipping to change at page 10, line 19		skipping to change at page 10, line 7
	mplsLabelStackIndex = 0, -- only a single		mplsLabelStackIndex = 0, -- only a single
	-- outgoing label		-- outgoing label
	mplsXCRowStatus = createAndGo(4)		mplsXCRowStatus = createAndGo(4)
	}		}
	Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex		Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex
	objects will automatically be populated with the value 2 when		objects will automatically be populated with the value 2 when
	these segments are referred to from the corresponding cross-		these segments are referred to from the corresponding cross-
	connect entry.		connect entry.
	9. Application of the Interface Group to MPLS		8. Application of the Interface Group to MPLS
	The Interfaces Group of MIB II defines generic managed objects for		The Interfaces Group of MIB II defines generic managed objects for
	managing interfaces. This memo contains the media-specific		managing interfaces. This memo contains the media-specific
	extensions to the Interfaces Group for managing MPLS interfaces.		extensions to the Interfaces Group for managing MPLS interfaces.
	This memo assumes the interpretation of the Interfaces Group to be		This memo assumes the interpretation of the Interfaces Group to be
	in accordance with [IFMIB] which states that the interfaces table		in accordance with [RFC2863] which states that the interfaces
	(ifTable) contains information on the managed resource's		table (ifTable) contains information on the managed resource's
	interfaces and that each sub-layer below the internetwork layer of		interfaces and that each sub-layer below the internetwork layer of
	a network interface is considered an interface. Thus, the MPLS		a network interface is considered an interface. Thus, the MPLS
	interface is represented as an entry in the ifTable. The inter-		interface is represented as an entry in the ifTable. The inter-
	relation of entries in the ifTable is defined by Interfaces Stack		relation of entries in the ifTable is defined by Interfaces Stack
	Group defined in [IFMIB].		Group defined in [RFC2863].
	When using MPLS interfaces, the interface stack table might appear		When using MPLS interfaces, the interface stack table might appear
	as follows:		as follows:
	+----------------------------------------+		+----------------------------------------+
	| MPLS-interface ifType = mpls(166) +		| MPLS-interface ifType = mpls(166) +
	+----------------------------------------+		+----------------------------------------+
	| Underlying Layer... +		| Underlying Layer... +
	+----------------------------------------+		+----------------------------------------+
	In the above diagram, "Underlying Layer..." refers to the ifIndex		In the above diagram, "Underlying Layer..." refers to the ifIndex
	of any interface type, which has been defined for MPLS		of any interface type, which has been defined for MPLS
	interworking. Examples include ATM, Frame Relay, Ethernet, etc.		interworking. Examples include ATM, Frame Relay, Ethernet, etc.
	9.1. Support of the MPLS Layer by ifTable		8.1. Support of the MPLS Layer by ifTable
	Some specific interpretations of ifTable for the MPLS layer		Some specific interpretations of ifTable for the MPLS layer
	follow.		follow.
	Object Use for the MPLS layer		Object Use for the MPLS layer
	ifIndex Each MPLS interface is represented by an ifEntry.		ifIndex Each MPLS interface is represented by an ifEntry.
	ifDescr Description of the MPLS interface.		ifDescr Description of the MPLS interface.
	ifType The value that is allocated for MPLS is 166.		ifType The value that is allocated for MPLS is 166.
	ifSpeed The total bandwidth in bits per second for use by		ifSpeed The total bandwidth in bits per second for use by
	the MPLS layer.		the MPLS layer.
	ifPhysAddress Unused.		ifPhysAddress Unused.
	ifAdminStatus This variable indicates the administrator's intent		ifAdminStatus This variable indicates the administrator's intent
	as to whether MPLS should be enabled, disabled, or		as to whether MPLS should be enabled, disabled, or
	running in some diagnostic testing mode on this		running in some diagnostic testing mode on this
	interface. Also see [IFMIB].		interface. Also see [RFC2863].
	ifOperStatus This value reflects the actual or operational		ifOperStatus This value reflects the actual or operational
	status of MPLS on this interface.		status of MPLS on this interface.
	ifLastChange See [IFMIB].		ifLastChange See [RFC2863].
	ifInOctets The number of received octets over the interface,		ifInOctets The number of received octets over the interface,
	i.e., the number of received, octets received as		i.e., the number of received, octets received as
	labeled packets.		labeled packets.
	ifOutOctets The number of transmitted octets over the		ifOutOctets The number of transmitted octets over the
	interface, i.e., the number of octets transmitted		interface, i.e., the number of octets transmitted
	as labeled packets.		as labeled packets.
	ifInErrors The number of labeled packets dropped due to		ifInErrors The number of labeled packets dropped due to
	uncorrectable errors.		uncorrectable errors.
	ifInUnknownProtos		ifInUnknownProtos
	The number of received packets discarded during		The number of received packets discarded during
	packet header validation, including packets with		packet header validation, including packets with
	unrecognized label values.		unrecognized label values.
	ifOutErrors See [IFMIB].		ifOutErrors See [RFC2863].
	ifName Textual name (unique on this system) of the		ifName Textual name (unique on this system) of the
	interface or an octet string of zero length.		interface or an octet string of zero length.
	ifLinkUpDownTrapEnable		ifLinkUpDownTrapEnable
	Default is disabled (2).		Default is disabled (2).
	ifConnectorPresent		ifConnectorPresent
	Set to false (2).		Set to false (2).
	ifHighSpeed See [IFMIB].		ifHighSpeed See [RFC2863].
	ifHCInOctets The 64-bit version of ifInOctets; supported if		ifHCInOctets The 64-bit version of ifInOctets; supported if
	required by the compliance statements in [IFMIB].		required by the compliance statements in [RFC2863].
	ifHCOutOctets The 64-bit version of ifOutOctets; supported if		ifHCOutOctets The 64-bit version of ifOutOctets; supported if
	required by the compliance statements in [IFMIB].		required by the compliance statements in [RFC2863].
	ifAlias The non-volatile 'alias' name for the interface as		ifAlias The non-volatile 'alias' name for the interface as
	specified by a network manager.		specified by a network manager.
	ifCounterDiscontinuityTime		ifCounterDiscontinuityTime
	See [IFMIB].		See [RFC2863].
	10. The Use of RowPointer		9. The Use of RowPointer
	RowPointer is a textual convention used to identify a conceptual		RowPointer is a textual convention used to identify a conceptual
	row in an SNMP Table by pointing to one of its objects. In this		row in an SNMP Table by pointing to one of its objects. In this
	MIB, it is used in mplsInSegmentTable and mplsOutSegmentTable		MIB, it is used in mplsInSegmentTable and mplsOutSegmentTable
	for the following purposes. First, it indicates a particular		for the following purposes. First, it indicates a particular
	traffic parameter table. An example of such a table is		traffic parameter table. An example of such a table is
	mplsTrafficParamTable. Second, it is used to indicate a specific		mplsTrafficParamTable. Second, it is used to indicate a specific
	instance of a traffic parameter entry that is associated with a		instance of a traffic parameter entry that is associated with a
	given in-segment or out-segment entry. In the in-segment and out-		given in-segment or out-segment entry. In the in-segment and out-
	segment tables, the trafficParamPtr SHOULD point to the first		segment tables, the trafficParamPtr SHOULD point to the first
	column of the appropriate conceptual row.		column of the appropriate conceptual row.
	11. MPLS Label Switch Router MIB Definitions		10. MPLS Label Switch Router MIB Definitions
	MPLS-LSR-MIB DEFINITIONS ::= BEGIN		MPLS-LSR-MIB DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,		MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
	experimental, Integer32, Counter32, Unsigned32,		Integer32, Counter32, Unsigned32, Counter64, Gauge32
	Counter64, Gauge32
	FROM SNMPv2-SMI		FROM SNMPv2-SMI
	MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP		MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
	FROM SNMPv2-CONF		FROM SNMPv2-CONF
			TruthValue, RowStatus, StorageType, RowPointer,
	TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType,		TimeStamp
	RowPointer, TimeStamp
	FROM SNMPv2-TC		FROM SNMPv2-TC
	InterfaceIndex, InterfaceIndexOrZero		InterfaceIndex, InterfaceIndexOrZero
	FROM IF-MIB		FROM IF-MIB
			mplsMIB, MplsLSPID, MplsLabel, MplsBitRate, MplsBurstSize,
			MplsInitialCreationSource
			FROM MPLS-TC-MIB
	AddressFamilyNumbers		AddressFamilyNumbers
	FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB		FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB
	InetAddressIPv4, InetAddressIPv6, InetAddressType		InetAddressIPv4, InetAddressIPv6, InetAddressType
	FROM INET-ADDRESS-MIB;		FROM INET-ADDRESS-MIB
			;
	mplsLsrMIB MODULE-IDENTITY		mplsLsrMIB MODULE-IDENTITY
	LAST-UPDATED "200007121200Z" -- 12 July 2000 12:00:00 EST		LAST-UPDATED "200201041200Z" -- 4 January 2002 12:00:00 GMT
	ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"		ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
	CONTACT-INFO		CONTACT-INFO
	" Cheenu Srinivasan		"
	Postal: Tachion Networks, Inc.		Cheenu Srinivasan
	Monmouth Park Corporate Center I		Postal: Parama Networks, Inc.
	Building C, 185 Monmouth Parkway		1030 Broad Street
	West Long Branch, NJ 07764		Shrewsbury, NJ 07702
	Tel: +1-732-542-7750 x1234		Tel: +1-732-544-9120 x731
	Email: cheenu@tachion.com		Email: cheenu@paramanet.com
	Arun Viswanathan		Arun Viswanathan
	Postal: Force10 Networks, Inc.		Postal: Force10 Networks, Inc.
	1440 McCarthy Blvd		1440 McCarthy Blvd
	Milpitas, CA 95035		Milpitas, CA 95035
	Tel: +1-408-571-3516		Tel: +1-408-571-3516
	Email: arun@force10networks.com		Email: arun@force10networks.com
	Thomas D. Nadeau		Thomas D. Nadeau
	Postal: Cisco Systems, Inc.		Postal: Cisco Systems, Inc.
	250 Apollo Drive		250 Apollo Drive
	Chelmsford, MA 01824		Chelmsford, MA 01824
	Tel: +1-978-244-3051		Tel: +1-978-244-3051
	Email: tnadeau@cisco.com"		Email: tnadeau@cisco.com
			"
	DESCRIPTION		DESCRIPTION
	"This MIB contains managed object definitions for the		"This MIB contains managed object definitions for the
	Multiprotocol Label Switching (MPLS) Router as		Multiprotocol Label Switching (MPLS) Router as
	defined in: Rosen, E., Viswanathan, A., and R.		defined in: Rosen, E., Viswanathan, A., and R.
	Callon, Multiprotocol Label Switching Architecture,		Callon, Multiprotocol Label Switching Architecture,
	Internet Draft <draft-ietf-mpls-arch-06.txt>,		RFC 3031, January 2001."
	August 1999."
	-- Revision history.		-- Revision history.
	REVISION		REVISION
	"200007121200Z" -- 12 July 2000 12:00:00 EST		"200201041200Z" -- 4 January 2002 12:00:00 GMT
	DESCRIPTION
	"Seventh draft version. Fix minor compilation errors."
	REVISION
	"200007071200Z" -- 07 July 2000 12:00:00 EST
	DESCRIPTION
	"Sixth draft version. Made minor typographical corrections
	noted from WG mailing list during second working group last
	call."
	REVISION
	"200004261200Z" -- 26 April 2000 12:00:00 EST
	DESCRIPTION
	"Fifth draft version. Made minor typographical corrections
	noted from WG mailing list."
	REVISION
	"200004211200Z" -- 21 April 2000 12:00:00 EST
	DESCRIPTION
	"Fourth draft version. Made corrections from WG Last
	Call comments."
	REVISION
	"200003061200Z" -- 6 March 2000 12:00:00 EST
	DESCRIPTION
	"Third draft version."
	REVISION
	"200002161200Z" -- 16 February 2000 12:00:00 EST
	DESCRIPTION
	"Second draft version."
	REVISION
	"199906161200Z" -- 16 June 1999 12:00:00 EST
	DESCRIPTION
	"Initial draft version."
	::= { experimental 96 }
	MplsLSPID ::= TEXTUAL-CONVENTION
	STATUS current
	DESCRIPTION
	"An identifier that is assigned to each LSP and is
	used to uniquely identify it. This is assigned at
	the head end of the LSP and can be used by all LSRs
	to identify this LSP. This value is piggybacked by
	the signaling protocol when this LSP is signaled
	within the network. This identifier can then be
	used at each LSR to identify which labels are being
	swapped to other labels for this LSP. For IPv4
	addresses this results in a 6-octet long cookie."
	SYNTAX OCTET STRING (SIZE (0..31))
	MplsLabel ::= TEXTUAL-CONVENTION
	STATUS current
	DESCRIPTION
	"This value represents an MPLS label. Note that the
	contents of a label field are interpreted in an
	interface-type specific fashion. For example, the
	20-bit wide label carried in the MPLS shim header is
	contained in bits 0-19 and bits 20-31 must be zero.
	The frame relay label can be either 10 or 23 bits
	wide depending on the size of the DLCI field and
	bits 10-31, or 23-31 must be zero, respectively.
	For an ATM interface, bits 0-15 must be interpreted
	as the VCI, bits 16-23 as the VPI and bits 24-31
	must be zero. Note that the permissible label
	values are also a function of the interface type.
	For example, the value 3 has special semantics in
	the control plane for an MPLS shim header label and
	is not a valid label value in the data path."
	REFERENCE
	"1. MPLS Label Stack Encoding, Rosen et al, draft-
	ietf-mpls-label-encaps-07.txt, March 2000.
	2. Use of Label Switching on Frame Relay Networks,
	Conta et al, draft-ietf-mpls-fr-03.txt, Nov.
	1998.
	3. MPLS using LDP and ATM VC switching, Davie et al,
	draft-ietf-mpls-atm-02.txt, April 1999."
	SYNTAX Unsigned32 (0..4294967295)
	MplsBitRate ::= TEXTUAL-CONVENTION
	DISPLAY-HINT "d"
	STATUS current
	DESCRIPTION
	"An estimate of bandwidth in units of 1,000 bits per
	second. If this object reports a value of 'n' then
	the rate of the object is somewhere in the range of
	'n-500' to 'n+499'. For objects which do not vary in
	bitrate, or for those where no accurate estimation
	can be made, this object should contain the nominal
	bitrate."
	SYNTAX Integer32 (1..2147483647)
	MplsBurstSize ::= TEXTUAL-CONVENTION
	DISPLAY-HINT "d"
	STATUS current
	DESCRIPTION
	"The number of octets of MPLS data that the stream
	may send back-to-back without concern for policing."
	SYNTAX Integer32 (1..2147483647)
	MplsObjectOwner ::= TEXTUAL-CONVENTION
	STATUS current
	DESCRIPTION		DESCRIPTION
	"The entity which owns the object in question."		"Initial revision, published as part of RFC XXXX."
	SYNTAX INTEGER {		::= { mplsMIB 2 }
	other(1),
	snmp(2),
	ldp(3),
	rsvp(4),
	crldp(5),
	policyAgent(6),
	unknown (7)
	}
	-- Top level components of this MIB.		-- Top level components of this MIB.
	-- Tables, Scalars		-- Tables, Scalars
	mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrMIB 1 }		mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrMIB 1 }
			-- Notifications
	mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrMIB 2 }		mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrMIB 2 }
	mplsLsrNotifyPrefix OBJECT IDENTIFIER ::= { mplsLsrNotifications 0 }		mplsLsrNotifyPrefix OBJECT IDENTIFIER ::= { mplsLsrNotifications 0 }
	-- conformance		-- conformance
	mplsLsrConformance OBJECT IDENTIFIER ::= { mplsLsrMIB 3 }		mplsLsrConformance OBJECT IDENTIFIER ::= { mplsLsrMIB 3 }
	-- MPLS Interface Configuration Table.		-- MPLS Interface Configuration Table.
	mplsInterfaceConfTable OBJECT-TYPE		mplsInterfaceConfTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MplsInterfaceConfEntry		SYNTAX SEQUENCE OF MplsInterfaceConfEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	skipping to change at page 16, line 37		skipping to change at page 14, line 13
	"This table specifies per-interface MPLS capability		"This table specifies per-interface MPLS capability
	and associated information."		and associated information."
	::= { mplsLsrObjects 1 }		::= { mplsLsrObjects 1 }
	mplsInterfaceConfEntry OBJECT-TYPE		mplsInterfaceConfEntry OBJECT-TYPE
	SYNTAX MplsInterfaceConfEntry		SYNTAX MplsInterfaceConfEntry
	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
	every interface capable of supporting MPLS. The		every interface capable of supporting MPLS. Each
	entry with index 0 represents the per-platform label		entry in this table will exist only if a
	space and contains parameters that apply to all		corresponding entry in ifTable exists. If the
	interfaces that participate in the per-platform		associated entry in ifTable is deleted, the
	label space. Other entries defined in this table		corresponding entry in this table must also be
	represent additional MPLS interfaces that may		deleted shortly thereafter. The entry with index 0
	participate in either the per-platform or per-		represents the per-platform label space and contains
	interface label spaces, or both. Additional		parameters that apply to all interfaces that
	information about label space participation of an		participate in the per-platform label space. Other
	interface is provided in the description clause of		entries defined in this table represent additional
			MPLS interfaces that may participate in either the
			per-platform or per-interface label spaces, or both.
			Additional information about label space
			participation of an interface is provided in the
			description clause of
	mplsInterfaceLabelParticipationType."		mplsInterfaceLabelParticipationType."
	INDEX { mplsInterfaceConfIndex }		INDEX { mplsInterfaceConfIndex }
	::= { mplsInterfaceConfTable 1 }		::= { mplsInterfaceConfTable 1 }
	MplsInterfaceConfEntry ::= SEQUENCE {		MplsInterfaceConfEntry ::= SEQUENCE {
	mplsInterfaceConfIndex InterfaceIndexOrZero,		mplsInterfaceConfIndex InterfaceIndexOrZero,
	mplsInterfaceLabelMinIn MplsLabel,		mplsInterfaceLabelMinIn MplsLabel,
	mplsInterfaceLabelMaxIn MplsLabel,		mplsInterfaceLabelMaxIn MplsLabel,
	mplsInterfaceLabelMinOut MplsLabel,		mplsInterfaceLabelMinOut MplsLabel,
	mplsInterfaceLabelMaxOut MplsLabel,		mplsInterfaceLabelMaxOut MplsLabel,
	mplsInterfaceTotalBandwidth MplsBitRate,		mplsInterfaceTotalBandwidth MplsBitRate,
	mplsInterfaceAvailableBandwidth MplsBitRate,		mplsInterfaceAvailableBandwidth MplsBitRate,
	mplsInterfaceLabelParticipationType BITS,		mplsInterfaceLabelParticipationType BITS
	mplsInterfaceConfStorageType StorageType
	}		}
	mplsInterfaceConfIndex OBJECT-TYPE		mplsInterfaceConfIndex OBJECT-TYPE
	SYNTAX InterfaceIndexOrZero		SYNTAX InterfaceIndexOrZero
	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
	MplsInterfaceConfTable. A non-zero index for an		MplsInterfaceConfTable. A non-zero index for an
	entry indicates the ifIndex for the corresponding		entry indicates the ifIndex for the corresponding
	interface entry in of the MPLS-layer in the ifTable.		interface entry in of the MPLS-layer in the ifTable.
	Note that the per-platform label space may apply to		Note that the per-platform label space may apply to
	several interfaces, and therefore the configuration		several interfaces, and therefore the configuration
	of the per-platform label space interface parameters		of the per-platform label space interface parameters
	will apply to all of the interfaces that are		will apply to all of the interfaces that are
	participating in the per-platform label space."		participating in the per-platform label space."
	REFERENCE		REFERENCE
	"RFC 2233 - The Interfaces Group MIB using SMIv2,		"RFC 2863 - The Interfaces Group MIB, McCloghrie, K.,
	McCloghrie, K., and F. Kastenholtz, Nov. 1997"		and F. Kastenholtz, June 2000"
	::= { mplsInterfaceConfEntry 1 }		::= { mplsInterfaceConfEntry 1 }
	mplsInterfaceLabelMinIn OBJECT-TYPE		mplsInterfaceLabelMinIn OBJECT-TYPE
	SYNTAX MplsLabel		SYNTAX MplsLabel
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This is the minimum value of an MPLS label that this		"This is the minimum value of an MPLS label that this
	LSR is willing to receive on this interface."		LSR is willing to receive on this interface."
	::= { mplsInterfaceConfEntry 2 }		::= { mplsInterfaceConfEntry 2 }
	skipping to change at page 18, line 26		skipping to change at page 16, line 5
	LSR is willing to send on this interface."		LSR is willing to send on this interface."
	::= { mplsInterfaceConfEntry 5 }		::= { mplsInterfaceConfEntry 5 }
	mplsInterfaceTotalBandwidth OBJECT-TYPE		mplsInterfaceTotalBandwidth OBJECT-TYPE
	SYNTAX MplsBitRate		SYNTAX MplsBitRate
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This value indicates the total amount of usable		"This value indicates the total amount of usable
	bandwidth on this interface and is specified in		bandwidth on this interface and is specified in
	kilobits per second (Kbps). This variable is		kilobits per second (Kbps). This variable is not
	not applicable when applied to the interface with		applicable when applied to the interface with index
	index 0."		0. When this value cannot be measured, this value
			should contain the nominal bandwidth."
	::= { mplsInterfaceConfEntry 6 }		::= { mplsInterfaceConfEntry 6 }
	mplsInterfaceAvailableBandwidth OBJECT-TYPE		mplsInterfaceAvailableBandwidth OBJECT-TYPE
	SYNTAX MplsBitRate		SYNTAX MplsBitRate
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This value indicates the total amount of available		"This value indicates the total amount of available
	bandwidth available on this interface and is		bandwidth available on this interface and is
	specified in kilobits per second (Kbps). This		specified in kilobits per second (Kbps). This value
	value is calculated as the difference between the		is calculated as the difference between the amount
	amount of bandwidth currently in use and that		of bandwidth currently in use and that specified in
	specified in mplsInterfaceTotalBandwidth. This		mplsInterfaceTotalBandwidth. This variable is not
	variable is not applicable when applied to the		applicable when applied to the interface with index
	interface with index 0."		0. When this value cannot be measured, this value
			should contain the nominal bandwidth."
	::= { mplsInterfaceConfEntry 7 }		::= { mplsInterfaceConfEntry 7 }
	mplsInterfaceLabelParticipationType OBJECT-TYPE		mplsInterfaceLabelParticipationType OBJECT-TYPE
	SYNTAX BITS {		SYNTAX BITS {
	perPlatform (0),		perPlatform (0),
	perInterface (1)		perInterface (1)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	skipping to change at page 19, line 21		skipping to change at page 16, line 52
	mplsInterfaceLabelMinOut, and		mplsInterfaceLabelMinOut, and
	mplsInterfaceLabelMaxOut for this entry reflect the		mplsInterfaceLabelMaxOut for this entry reflect the
	label ranges for this interface. If only the		label ranges for this interface. If only the
	perPlatform(0) bit is set, then the value of		perPlatform(0) bit is set, then the value of
	mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn,		mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn,
	mplsInterfaceLabelMinOut, and		mplsInterfaceLabelMinOut, and
	mplsInterfaceLabelMaxOut for this entry must be		mplsInterfaceLabelMaxOut for this entry must be
	identical to the instance of these objects with		identical to the instance of these objects with
	index 0."		index 0."
	REFERENCE		REFERENCE
	"Multiprotocol Label Switching, Rosen et al, draft-ietf-mpls-		"Rosen, E., Viswanathan, A., and R. Callon,
	arch-06.txt, August 1999."		Multiprotocol Label Switching Architecture, RFC
			3031, January 2001."
	::= { mplsInterfaceConfEntry 8 }		::= { mplsInterfaceConfEntry 8 }
	mplsInterfaceConfStorageType OBJECT-TYPE
	SYNTAX StorageType
	MAX-ACCESS read-create
	STATUS current
	DESCRIPTION
	"The storage type for this entry."
	::= { mplsInterfaceConfEntry 9 }
	-- End of mplsInterfaceConfTable		-- End of mplsInterfaceConfTable
	-- MPLS Interface Performance Table.		-- MPLS Interface Performance Table.
	mplsInterfacePerfTable OBJECT-TYPE		mplsInterfacePerfTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MplsInterfacePerfEntry		SYNTAX SEQUENCE OF MplsInterfacePerfEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This table provides MPLS performance information on		"This table provides MPLS performance information on
	a per-interface basis."		a per-interface basis."
	::= { mplsLsrObjects 2 }		::= { mplsLsrObjects 2 }
	mplsInterfacePerfEntry OBJECT-TYPE		mplsInterfacePerfEntry OBJECT-TYPE
	skipping to change at page 20, line 22		skipping to change at page 17, line 46
	-- outgoing direction		-- outgoing direction
	mplsInterfaceOutLabelsUsed Gauge32,		mplsInterfaceOutLabelsUsed Gauge32,
	mplsInterfaceOutFragments Counter32		mplsInterfaceOutFragments Counter32
	}		}
	mplsInterfaceInLabelsUsed OBJECT-TYPE		mplsInterfaceInLabelsUsed OBJECT-TYPE
	SYNTAX Gauge32		SYNTAX Gauge32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object counts the number of labels		"This object counts the number of labels that are in
	that are in use at this point in time on this		use at this point in time on this interface in the
	interface in the incoming direction. If the interface		incoming direction. If the interface participates in
	participates in the per-platform label space only,		the per-platform label space only, then this
	then this instance of this object MUST be identical		instance of this object MUST be identical with the
	with the instance with index 0. If the interface		instance with index 0. If the interface participates
	participates in the per-interface label space, then this		in the per-interface label space, then this instance
	this instance of this object MUST represent the number of		of this object MUST represent the number of of per-
	of per-interface labels that are in use at this point in		interface labels that are in use at this point in
	time on this interface."		time on this interface."
	::= { mplsInterfacePerfEntry 1 }		::= { mplsInterfacePerfEntry 1 }
	mplsInterfaceFailedLabelLookup OBJECT-TYPE		mplsInterfaceFailedLabelLookup OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object counts the number of labeled packets		"This object counts the number of labeled packets
	that have been received on this interface and were		that have been received on this interface and were
	discarded because there was no matching cross-connect		discarded because there was no matching cross-
	entry. This object MUST count on a per-interface basis		connect entry. This object MUST count on a per-
	regardless of which label space the interface participates		interface basis regardless of which label space the
	in."		interface participates in."
	::= { mplsInterfacePerfEntry 2 }		::= { mplsInterfacePerfEntry 2 }
	mplsInterfaceOutLabelsUsed OBJECT-TYPE		mplsInterfaceOutLabelsUsed OBJECT-TYPE
	SYNTAX Gauge32		SYNTAX Gauge32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object counts the number of top-most labels in the		"This object counts the number of top-most labels in
	outgoing label stacks that are in use at this point		the outgoing label stacks that are in use at this
	in time on this interface. This object		point in time on this interface. This object MUST
	MUST count on a per-interface basis regardless of		count on a per-interface basis regardless of which
	which label space the interface participates in."		label space the interface participates in."
	::= { mplsInterfacePerfEntry 3 }		::= { mplsInterfacePerfEntry 3 }
	mplsInterfaceOutFragments OBJECT-TYPE		mplsInterfaceOutFragments OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object counts the number of outgoing MPLS		"This object counts the number of outgoing MPLS
	packets that required fragmentation before		packets that required fragmentation before
	transmission on this interface. This object		transmission on this interface. This object MUST
	transmission on this interface. This object		count on a per-interface basis regardless of which
	MUST count on a per-interface basis regardless of		label space the interface participates in."
	which label space the interface participates in."
	::= { mplsInterfacePerfEntry 4 }		::= { mplsInterfacePerfEntry 4 }
	-- In-segment table.		-- In-segment table.
	mplsInSegmentTable OBJECT-TYPE		mplsInSegmentTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MplsInSegmentEntry		SYNTAX SEQUENCE OF MplsInSegmentEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This table contains a collection of incoming		"This table contains a collection of incoming
	skipping to change at page 21, line 44		skipping to change at page 19, line 18
	SYNTAX MplsInSegmentEntry		SYNTAX MplsInSegmentEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table represents one incoming		"An entry in this table represents one incoming
	segment. An entry can be created by a network		segment. An entry can be created by a network
	administrator or an SNMP agent, or an MPLS signaling		administrator or an SNMP agent, or an MPLS signaling
	protocol. The creator of the entry is denoted by		protocol. The creator of the entry is denoted by
	mplsInSegmentOwner. An entry in this table is		mplsInSegmentOwner. An entry in this table is
	indexed by the ifIndex of the incoming interface and		indexed by the ifIndex of the incoming interface and
	the (top) label."		the (top) label. The value of mplsInSegmentRowStatus
			cannot be active(1)unless the ifTable entry
			corresponding to mplsInSegmentIfIndex exists."
	INDEX { mplsInSegmentIfIndex, mplsInSegmentLabel }		INDEX { mplsInSegmentIfIndex, mplsInSegmentLabel }
	::= { mplsInSegmentTable 1 }		::= { mplsInSegmentTable 1 }
	MplsInSegmentEntry ::= SEQUENCE {		MplsInSegmentEntry ::= SEQUENCE {
	mplsInSegmentIfIndex InterfaceIndexOrZero,		mplsInSegmentIfIndex InterfaceIndexOrZero,
	mplsInSegmentLabel MplsLabel,		mplsInSegmentLabel MplsLabel,
	mplsInSegmentNPop Integer32,		mplsInSegmentNPop Integer32,
	mplsInSegmentAddrFamily AddressFamilyNumbers,		mplsInSegmentAddrFamily AddressFamilyNumbers,
	mplsInSegmentXCIndex Integer32,		mplsInSegmentXCIndex Unsigned32,
	mplsInSegmentOwner MplsObjectOwner,		mplsInSegmentOwner MplsInitialCreationSource ,
	mplsInSegmentTrafficParamPtr RowPointer,		mplsInSegmentTrafficParamPtr RowPointer,
	mplsInSegmentRowStatus RowStatus,		mplsInSegmentRowStatus RowStatus,
	mplsInSegmentStorageType StorageType		mplsInSegmentStorageType StorageType
	}		}
	mplsInSegmentIfIndex OBJECT-TYPE		mplsInSegmentIfIndex OBJECT-TYPE
	SYNTAX InterfaceIndexOrZero		SYNTAX InterfaceIndexOrZero
	MAX-ACCESS accessible-for-notify		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
	MplsInSegmentTable. This value represents the		MplsInSegmentTable. This value represents the
	interface index for the incoming MPLS interface. A		interface index for the incoming MPLS interface. A
	value of zero represents an incoming label from the		value of zero represents an incoming label from the
	per-platform label space. In this case, the		per-platform label space. In this case, the
	mplsInSegmentLabel is interpreted to be an MPLS-type		mplsInSegmentLabel is interpreted to be an MPLS-type
	label."		label."
	::= { mplsInSegmentEntry 1 }		::= { mplsInSegmentEntry 1 }
	mplsInSegmentLabel OBJECT-TYPE		mplsInSegmentLabel OBJECT-TYPE
	SYNTAX MplsLabel		SYNTAX MplsLabel
	MAX-ACCESS accessible-for-notify		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The incoming label for this segment."		"The incoming label for this segment."
	::= { mplsInSegmentEntry 2 }		::= { mplsInSegmentEntry 2 }
	mplsInSegmentNPop OBJECT-TYPE		mplsInSegmentNPop OBJECT-TYPE
	SYNTAX Integer32 (1..2147483647)		SYNTAX Integer32 (1..2147483647)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of labels to pop from the incoming		"The number of labels to pop from the incoming
	packet. Normally only the top label is popped from		packet. Normally only the top label is popped from
	the packet and used for all switching decisions for		the packet and used for all switching decisions for
	that packet. Note that technologies which do not		that packet. Note that technologies which do not
	support label popping should set this value to its		support label popping should set this value to its
	default value of 1."		default value of 1. This object cannot be modified
			if mplsInSegmentRowStatus is active(1)."
	DEFVAL { 1 }		DEFVAL { 1 }
	::= { mplsInSegmentEntry 3 }		::= { mplsInSegmentEntry 3 }
	mplsInSegmentAddrFamily OBJECT-TYPE		mplsInSegmentAddrFamily OBJECT-TYPE
	SYNTAX AddressFamilyNumbers		SYNTAX AddressFamilyNumbers
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The IANA address family [IANAFamily] of the incoming		"The IANA address family [IANAFamily] of the incoming
	packet. A value of other(0) indicates that the		packet. A value of other(0) indicates that the
	family type is either unknown or undefined."		family type is either unknown or undefined. This
			object cannot be modified if mplsInSegmentRowStatus
			is active(1)."
	DEFVAL { other }		DEFVAL { other }
	::= { mplsInSegmentEntry 4 }		::= { mplsInSegmentEntry 4 }
	mplsInSegmentXCIndex OBJECT-TYPE		mplsInSegmentXCIndex OBJECT-TYPE
	SYNTAX Integer32 (0..2147483647)		SYNTAX Unsigned32 (0..4294967295)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Index into mplsXCTable which identifies which cross-		"Index into mplsXCTable which identifies which cross-
	connect entry this segment is part of. A value of		connect entry this segment is part of. A value of
	zero indicates that this entry is not referred to by		zero indicates that this entry is not referred to by
	any cross-connect entry. When a cross-connect entry		any cross-connect entry. When a cross-connect entry
	is created which this in-segment is a part of, this		is created which this in-segment is a part of, this
	object is automatically updated to reflect the value		object is automatically updated to reflect the value
	of mplsXCIndex of that cross-connect entry."		of mplsXCIndex of that cross-connect entry."
	DEFVAL { 0 }		DEFVAL { 0 }
	::= { mplsInSegmentEntry 5 }		::= { mplsInSegmentEntry 5 }
	mplsInSegmentOwner OBJECT-TYPE		mplsInSegmentOwner OBJECT-TYPE
	SYNTAX MplsObjectOwner		SYNTAX MplsInitialCreationSource
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Denotes the entity that created and is responsible		"Denotes the entity that created and is responsible
	for managing this segment."		for managing this segment. This object cannot be
			modified if mplsInSegmentRowStatus is active(1)."
	DEFVAL { unknown }		DEFVAL { unknown }
	::= { mplsInSegmentEntry 6 }		::= { mplsInSegmentEntry 6 }
	mplsInSegmentTrafficParamPtr OBJECT-TYPE		mplsInSegmentTrafficParamPtr OBJECT-TYPE
	SYNTAX RowPointer		SYNTAX RowPointer
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This variable represents a pointer to the traffic		"This variable represents a pointer to the traffic
	parameter specification for this in-segment. This		parameter specification for this in-segment. This
	value may point at an entry in the		value may point at an entry in the
	mplsTrafficParamTable to indicate which		mplsTrafficParamTable to indicate which
	mplsTrafficParamEntry is to be assigned to this		mplsTrafficParamEntry is to be assigned to this
	segment. This value may optionally point at an		segment. This value may optionally point at an
	externally defined traffic parameter specification		externally defined traffic parameter specification
	table. A value of zero-dot-zero indicates best-effort		table. A value of zero-dot-zero indicates best-effort
	treatment. By having the same value of this object,		treatment. By having the same value of this object,
	two or more segments can indicate resource sharing."		two or more segments can indicate resource sharing.
			This object cannot be modified if
			mplsInSegmentRowStatus is active(1)."
	::= { mplsInSegmentEntry 7 }		::= { mplsInSegmentEntry 7 }
	mplsInSegmentRowStatus OBJECT-TYPE		mplsInSegmentRowStatus 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."
	::= { mplsInSegmentEntry 8 }		::= { mplsInSegmentEntry 8 }
	mplsInSegmentStorageType OBJECT-TYPE		mplsInSegmentStorageType OBJECT-TYPE
	SYNTAX StorageType		SYNTAX StorageType
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This variable indicates the storage type for this		"This variable indicates the storage type for this
	object."		object. This object cannot be modified if
			mplsInSegmentRowStatus is active(1). If this
			variable is set to readOnly(5), and the
			corresponding TFIB entry is removed, then the agent
			must remove this row shortly thereafter."
	::= { mplsInSegmentEntry 9 }		::= { mplsInSegmentEntry 9 }
	-- End of mplsInSegmentTable		-- End of mplsInSegmentTable
	-- In-segment performance table.		-- In-segment performance table.
	mplsInSegmentPerfTable OBJECT-TYPE		mplsInSegmentPerfTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MplsInSegmentPerfEntry		SYNTAX SEQUENCE OF MplsInSegmentPerfEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	skipping to change at page 26, line 8		skipping to change at page 23, line 45
	DESCRIPTION		DESCRIPTION
	"The total number of octets received. This is the 64		"The total number of octets received. This is the 64
	bit version of mplsInSegmentOctets."		bit version of mplsInSegmentOctets."
	::= { mplsInSegmentPerfEntry 5 }		::= { mplsInSegmentPerfEntry 5 }
	mplsInSegmentPerfDiscontinuityTime OBJECT-TYPE		mplsInSegmentPerfDiscontinuityTime OBJECT-TYPE
	SYNTAX TimeStamp		SYNTAX TimeStamp
	MAX-ACCESS read-only		MAX-ACCESS read-only
	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
	which any one or more of this segment's Counter32 or		at which any one or more of this segment's Counter32
	Counter64 suffered a discontinuity. If no such		or Counter64 suffered a discontinuity. If no such
	discontinuities have occurred since the last re-		discontinuities have occurred since the last re-
	initialization of the local management subsystem, then		initialization of the local management subsystem,
	this object contains a zero value."		then this object contains a zero value."
	::= { mplsInSegmentPerfEntry 6 }		::= { mplsInSegmentPerfEntry 6 }
	-- End of mplsInSegmentPerfTable.		-- End of mplsInSegmentPerfTable.
	-- Out-segment table.		-- Out-segment table.
	mplsOutSegmentIndexNext OBJECT-TYPE		mplsOutSegmentIndexNext OBJECT-TYPE
	SYNTAX Integer32 (0..2147483647)		SYNTAX Unsigned32 (0..4294967295)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object contains the next appropriate value to		"This object contains the next appropriate value to
	be used for mplsOutSegmentIndex when creating		be used for mplsOutSegmentIndex when creating
	entries in the mplsOutSegmentTable. If the number		entries in the mplsOutSegmentTable. If the number
	of unassigned entries is exhausted, this object will		of unassigned entries is exhausted, this object will
	take on the value of 0. To obtain the		take on the value of 0. To obtain the
	mplsOutSegmentIndex value for a new entry, the		mplsOutSegmentIndex value for a new entry, the
	manager must first issue a management protocol		manager must first issue a management protocol
	skipping to change at page 27, line 11		skipping to change at page 24, line 46
	mplsOutSegmentEntry OBJECT-TYPE		mplsOutSegmentEntry OBJECT-TYPE
	SYNTAX MplsOutSegmentEntry		SYNTAX MplsOutSegmentEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table represents one outgoing		"An entry in this table represents one outgoing
	segment. An entry can be created by a network		segment. An entry can be created by a network
	administrator or an SNMP agent, or an MPLS signaling		administrator or an SNMP agent, or an MPLS signaling
	protocol. The object mplsOutSegmentOwner indicates		protocol. The object mplsOutSegmentOwner indicates
	the creator of this entry."		the creator of this entry. The value of
			mplsOutSegmentRowStatus cannot be active(1)unless
			the ifTable entry corresponding to
			mplsOutSegmentIfIndex exists."
	INDEX { mplsOutSegmentIndex }		INDEX { mplsOutSegmentIndex }
	::= { mplsOutSegmentTable 1 }		::= { mplsOutSegmentTable 1 }
	MplsOutSegmentEntry ::= SEQUENCE {		MplsOutSegmentEntry ::= SEQUENCE {
	mplsOutSegmentIndex Integer32,		mplsOutSegmentIndex Unsigned32,
	mplsOutSegmentIfIndex InterfaceIndex,		mplsOutSegmentIfIndex InterfaceIndex,
	mplsOutSegmentPushTopLabel TruthValue,		mplsOutSegmentPushTopLabel TruthValue,
	mplsOutSegmentTopLabel MplsLabel,		mplsOutSegmentTopLabel MplsLabel,
	mplsOutSegmentNextHopIpAddrType InetAddressType,		mplsOutSegmentNextHopIpAddrType InetAddressType,
	mplsOutSegmentNextHopIpv4Addr InetAddressIPv4,		mplsOutSegmentNextHopIpv4Addr InetAddressIPv4,
	mplsOutSegmentNextHopIpv6Addr InetAddressIPv6,		mplsOutSegmentNextHopIpv6Addr InetAddressIPv6,
	mplsOutSegmentXCIndex Integer32,		mplsOutSegmentXCIndex Unsigned32,
	mplsOutSegmentOwner MplsObjectOwner,		mplsOutSegmentOwner MplsInitialCreationSource ,
	mplsOutSegmentTrafficParamPtr RowPointer,		mplsOutSegmentTrafficParamPtr RowPointer,
	mplsOutSegmentRowStatus RowStatus,		mplsOutSegmentRowStatus RowStatus,
	mplsOutSegmentStorageType StorageType		mplsOutSegmentStorageType StorageType
	}		}
	mplsOutSegmentIndex OBJECT-TYPE		mplsOutSegmentIndex OBJECT-TYPE
	SYNTAX Integer32(0..2147483647)		SYNTAX Unsigned32(0..2147483647)
	MAX-ACCESS accessible-for-notify		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This value contains a unique index for this row.		"This value contains a unique index for this row.
	While a value of 0 is not valid as an index for this		While a value of 0 is not valid as an index for this
	row it can be supplied as a valid value to index		row it can be supplied as a valid value to index
	mplsXCTable to access entries for which no out-		mplsXCTable to access entries for which no out-
	segment has been configured."		segment has been configured."
	::= { mplsOutSegmentEntry 1 }		::= { mplsOutSegmentEntry 1 }
	mplsOutSegmentIfIndex OBJECT-TYPE		mplsOutSegmentIfIndex OBJECT-TYPE
	SYNTAX InterfaceIndex		SYNTAX InterfaceIndexOrZero
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This value contains the interface index of the		"This value must contain the interface index of the
	outgoing interface."		outgoing interface. This object may only take the
			value of 0 during the create-and-wait row creation
			operation if the management station has not yet set
			the value of this object. This object cannot be
			modified if mplsOutSegmentRowStatus is active(1).
			The mplsOutSegmentRowStatus cannot be set to
			active(1) until this object is set to a value
			corresponding to a valid ifEntry."
			DEFVAL { 0 }
	::= { mplsOutSegmentEntry 2 }		::= { mplsOutSegmentEntry 2 }
	mplsOutSegmentPushTopLabel OBJECT-TYPE		mplsOutSegmentPushTopLabel OBJECT-TYPE
	SYNTAX TruthValue		SYNTAX TruthValue
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This value indicates whether or not a top label		"This value indicates whether or not a top label
	should be pushed onto the outgoing packet's label		should be pushed onto the outgoing packet's label
	stack. The value of this variable must be set to		stack. The value of this variable MUST be set to
	true if the outgoing interface does not support pop-		true if the outgoing interface does not support pop-
	and-go (for example an ATM interface) or if it is a		and-go (for example an ATM interface) or if it is a
	tunnel origination. Note that it is considered an		tunnel origination. Note that it is considered an
	error in the case that mplsOutSegmentPushTopLabel is		error in the case that mplsOutSegmentPushTopLabel is
	set to false, but the cross-connect entry which		set to false, but the cross-connect entry which
	refers to this out-segment has a non-zero		refers to this out-segment has a non-zero
	mplsLabelStackIndex. The LSR MUST ensure that this		mplsLabelStackIndex. The LSR MUST ensure that this
	situation does not happen "		situation does not happen. This object cannot be
			modified if mplsOutSegmentRowStatus is active(1)."
	::= { mplsOutSegmentEntry 3 }		::= { mplsOutSegmentEntry 3 }
	mplsOutSegmentTopLabel OBJECT-TYPE		mplsOutSegmentTopLabel OBJECT-TYPE
	SYNTAX MplsLabel		SYNTAX MplsLabel
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"If mplsOutSegmentPushTopLabel is true then this		"If mplsOutSegmentPushTopLabel is true then this
	represents the label that should be pushed onto the		represents the label that should be pushed onto the
	top of the outgoing packet's label stack."		top of the outgoing packet's label stack. Otherwise
			this value SHOULD be set to 0 by the management
			station and MUST be ignored by the agent. This
			object cannot be modified if mplsOutSegmentRowStatus
			is active(1)."
			DEFVAL { 0 }
	::= { mplsOutSegmentEntry 4 }		::= { mplsOutSegmentEntry 4 }
	mplsOutSegmentNextHopIpAddrType OBJECT-TYPE		mplsOutSegmentNextHopIpAddrType OBJECT-TYPE
	SYNTAX InetAddressType		SYNTAX InetAddressType
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates whether the next hop address is IPv4 or		"Indicates whether the next hop address is IPv4 or
	IPv6. Note that a value of unknown (0) is valid		IPv6. Note that a value of unknown (0) is valid
	only when the outgoing interface is of type point-to-		only when the outgoing interface is of type point-to-
	point."		point. This object cannot be modified if
			mplsOutSegmentRowStatus is active(1)."
	DEFVAL { unknown }		DEFVAL { unknown }
	::= { mplsOutSegmentEntry 5 }		::= { mplsOutSegmentEntry 5 }
	mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE		mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE
	SYNTAX InetAddressIPv4		SYNTAX InetAddressIPv4
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"IPv4 Address of the next hop. Its value is		"IPv4 Address of the next hop. Its value is
	significant only when		significant only when
	mplsOutSegmentNextHopIpAddrType is ipV4 (1),		mplsOutSegmentNextHopIpAddrType is ipV4 (1),
	otherwise it should return a value of 0."		otherwise it SHOULD return a value of 0. This object
			cannot be modified if mplsOutSegmentRowStatus is
			active(1)."
	::= { mplsOutSegmentEntry 6 }		::= { mplsOutSegmentEntry 6 }
	mplsOutSegmentNextHopIpv6Addr OBJECT-TYPE		mplsOutSegmentNextHopIpv6Addr OBJECT-TYPE
	SYNTAX InetAddressIPv6		SYNTAX InetAddressIPv6
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"IPv6 address of the next hop. Its value is		"IPv6 address of the next hop. Its value is
	significant only when		significant only when
	mplsOutSegmentNextHopIpAddrType is ipV6 (2),		mplsOutSegmentNextHopIpAddrType is ipV6 (2),
	otherwise it should return a value of 0."		otherwise it SHOULD return a value of 0. This object
			cannot be modified if mplsOutSegmentRowStatus is
			active(1)."
	::= { mplsOutSegmentEntry 7 }		::= { mplsOutSegmentEntry 7 }
	mplsOutSegmentXCIndex OBJECT-TYPE		mplsOutSegmentXCIndex OBJECT-TYPE
	SYNTAX Integer32 (0..2147483647)		SYNTAX Unsigned32 (0..4294967295)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Index into mplsXCTable which identifies which cross-		"Index into mplsXCTable which identifies which cross-
	connect entry this segment is part of. A value of		connect entry this segment is part of. A value of
	zero indicates that this entry is not referred to by		zero indicates that this entry is not referred to by
	any cross-connect entry. When a cross-connect entry		any cross-connect entry. When a cross-connect entry
	is created which this out-segment is a part of, this		is created which this out-segment is a part of, this
	object is automatically updated to reflect the value		object is automatically updated to reflect the value
	of mplsXCIndex of that cross-connect entry."		of mplsXCIndex of that cross-connect entry."
	DEFVAL { 0 }		DEFVAL { 0 }
	::= { mplsOutSegmentEntry 8 }		::= { mplsOutSegmentEntry 8 }
	mplsOutSegmentOwner OBJECT-TYPE		mplsOutSegmentOwner OBJECT-TYPE
	SYNTAX MplsObjectOwner		SYNTAX MplsInitialCreationSource
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Denotes the entity which created and is responsible		"Denotes the entity which created and is responsible
	for managing this segment."		for managing this segment. This object cannot be
			modified if mplsOutSegmentRowStatus is active(1)."
	DEFVAL { unknown }		DEFVAL { unknown }
	::= { mplsOutSegmentEntry 9 }		::= { mplsOutSegmentEntry 9 }
	mplsOutSegmentTrafficParamPtr OBJECT-TYPE		mplsOutSegmentTrafficParamPtr OBJECT-TYPE
	SYNTAX RowPointer		SYNTAX RowPointer
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This variable represents a pointer to the traffic		"This variable represents a pointer to the traffic
	parameter specification for this out-segment. This		parameter specification for this out-segment. This
	value may point at an entry in the		value may point at an entry in the
	mplsTrafficParamTable to indicate which		mplsTrafficParamTable to indicate which
	mplsTrafficParamEntry is to be assigned to this		mplsTrafficParamEntry is to be assigned to this
	segment. This value may optionally point at an		segment. This value may optionally point at an
	externally defined traffic parameter specification		externally defined traffic parameter specification
	table. A value of zero-dot-zero indicates best-		table. A value of zero-dot-zero indicates best-
	effort treatment. By having the same value of this		effort treatment. By having the same value of this
	object, two or more segments can indicate resource		object, two or more segments can indicate resource
	sharing."		sharing. This object cannot be modified if
			mplsOutSegmentRowStatus is active(1)."
	::= { mplsOutSegmentEntry 10 }		::= { mplsOutSegmentEntry 10 }
	mplsOutSegmentRowStatus OBJECT-TYPE		mplsOutSegmentRowStatus OBJECT-TYPE
	SYNTAX RowStatus		SYNTAX RowStatus
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"For creating, modifying, and deleting this row."		"For creating, modifying, and deleting this row."
	::= { mplsOutSegmentEntry 11 }		::= { mplsOutSegmentEntry 11 }
	mplsOutSegmentStorageType OBJECT-TYPE		mplsOutSegmentStorageType OBJECT-TYPE
	SYNTAX StorageType		SYNTAX StorageType
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This variable indicates the storage type for this		"This variable indicates the storage type for this
	object."		object. This object cannot be modified if
			mplsOutSegmentRowStatus is active(1). If this
			variable is set to readOnly(5), and the
			corresponding TFIB entry is removed, then the agent
			must remove this row shortly thereafter."
	::= { mplsOutSegmentEntry 12 }		::= { mplsOutSegmentEntry 12 }
	-- End of mplsOutSegmentTable		-- End of mplsOutSegmentTable
	-- Out-segment performance table.		-- Out-segment performance table.
	mplsOutSegmentPerfTable OBJECT-TYPE		mplsOutSegmentPerfTable OBJECT-TYPE
	SYNTAX SEQUENCE OF MplsOutSegmentPerfEntry		SYNTAX SEQUENCE OF MplsOutSegmentPerfEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	skipping to change at page 32, line 16		skipping to change at page 30, line 32
	DESCRIPTION		DESCRIPTION
	"Total number of octets sent. This is the 64 bit		"Total number of octets sent. This is the 64 bit
	version of mplsOutSegmentOctets."		version of mplsOutSegmentOctets."
	::= { mplsOutSegmentPerfEntry 5 }		::= { mplsOutSegmentPerfEntry 5 }
	mplsOutSegmentPerfDiscontinuityTime OBJECT-TYPE		mplsOutSegmentPerfDiscontinuityTime OBJECT-TYPE
	SYNTAX TimeStamp		SYNTAX TimeStamp
	MAX-ACCESS read-only		MAX-ACCESS read-only
	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
	which any one or more of this segment's Counter32 or		at which any one or more of this segment's Counter32
	Counter64 suffered a discontinuity. If no such		or Counter64 suffered a discontinuity. If no such
	discontinuities have occurred since the last re-		discontinuities have occurred since the last re-
	initialization of the local management subsystem, then		initialization of the local management subsystem,
	this object contains a zero value."		then this object contains a zero value."
	::= { mplsOutSegmentPerfEntry 6 }		::= { mplsOutSegmentPerfEntry 6 }
	-- End of mplsOutSegmentPerfTable.		-- End of mplsOutSegmentPerfTable.
	-- Cross-connect table.		-- Cross-connect table.
	mplsXCIndexNext OBJECT-TYPE		mplsXCIndexNext OBJECT-TYPE
	SYNTAX Integer32 (0..2147483647)		SYNTAX Unsigned32 (0..4294967295)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object contains an appropriate value to be used		"This object contains an appropriate value to be used
	for mplsXCIndex when creating entries in the		for mplsXCIndex when creating entries in the
	mplsXCTable. The value 0 indicates that no		mplsXCTable. The value 0 indicates that no
	unassigned entries are available. To obtain the		unassigned entries are available. To obtain the
	value of mplsXCIndex for a new entry in the		value of mplsXCIndex for a new entry in the
	mplsXCTable, the manager issues a management		mplsXCTable, the manager issues a management
	protocol retrieval operation to obtain the current		protocol retrieval operation to obtain the current
	skipping to change at page 33, line 51		skipping to change at page 32, line 16
	where LSPs are terminated with incoming label equal		where LSPs are terminated with incoming label equal
	to 0, should have mplsInSegmentIfIndex = 0 as well,		to 0, should have mplsInSegmentIfIndex = 0 as well,
	but can be distinguished from originating LSPs		but can be distinguished from originating LSPs
	because the mplsOutSegmentIfIndex = 0. The		because the mplsOutSegmentIfIndex = 0. The
	mplsOutSegmentIfIndex MUST only be set to 0 in		mplsOutSegmentIfIndex MUST only be set to 0 in
	cases of terminating LSPs.		cases of terminating LSPs.
	An entry can be created by a network administrator		An entry can be created by a network administrator
	or by an SNMP agent as instructed by an MPLS		or by an SNMP agent as instructed by an MPLS
	signaling protocol."		signaling protocol."
	INDEX { mplsXCIndex, mplsInSegmentIfIndex,		INDEX {
			mplsXCIndex,
			mplsInSegmentIfIndex,
	mplsInSegmentLabel,		mplsInSegmentLabel,
	mplsOutSegmentIndex }		mplsOutSegmentIndex
			}
	::= { mplsXCTable 1 }		::= { mplsXCTable 1 }
	MplsXCEntry ::= SEQUENCE {		MplsXCEntry ::= SEQUENCE {
	mplsXCIndex Integer32,		mplsXCIndex Unsigned32,
	mplsXCLspId MplsLSPID,		mplsXCLspId MplsLSPID,
	mplsXCLabelStackIndex Integer32,		mplsXCLabelStackIndex Unsigned32,
	mplsXCIsPersistent TruthValue,		mplsXCIsPersistent TruthValue,
	mplsXCOwner MplsObjectOwner,		mplsXCOwner MplsInitialCreationSource ,
	mplsXCRowStatus RowStatus,		mplsXCRowStatus RowStatus,
	mplsXCStorageType StorageType,		mplsXCStorageType StorageType,
	mplsXCAdminStatus INTEGER,		mplsXCAdminStatus INTEGER,
	mplsXCOperStatus INTEGER		mplsXCOperStatus INTEGER
	}		}
	mplsXCIndex OBJECT-TYPE		mplsXCIndex OBJECT-TYPE
	SYNTAX Integer32 (1..2147483647)		SYNTAX Unsigned32 (1..2147483647)
	MAX-ACCESS accessible-for-notify		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Primary index for the conceptual row identifying		"Primary index for the conceptual row identifying a
	a group of cross-connect segments."		group of cross-connect segments."
	::= { mplsXCEntry 1 }		::= { mplsXCEntry 1 }
	mplsXCLspId OBJECT-TYPE		mplsXCLspId OBJECT-TYPE
	SYNTAX MplsLSPID		SYNTAX MplsLSPID
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This value identifies the label switched path that		"This value identifies the label switched path that
	this cross-connect entry belongs to."		this cross-connect entry belongs to. This object
			cannot be modified if mplsXCRowStatus is active(1)."
	::= { mplsXCEntry 2 }		::= { mplsXCEntry 2 }
	mplsXCLabelStackIndex OBJECT-TYPE		mplsXCLabelStackIndex OBJECT-TYPE
	SYNTAX Integer32 (0..2147483647)		SYNTAX Unsigned32 (0..4294967295)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Primary index into mplsLabelStackTable identifying a		"Primary index into mplsLabelStackTable identifying a
	stack of labels to be pushed beneath the top label.		stack of labels to be pushed beneath the top label.
	Note that the top label identified by the out-		Note that the top label identified by the out-
	segment ensures that all the components of a		segment ensures that all the components of a
	multipoint-to-point connection have the same		multipoint-to-point connection have the same
	outgoing label. A value of 0 indicates that no		outgoing label. A value of 0 indicates that no
	labels are to be stacked beneath the top label."		labels are to be stacked beneath the top label. This
			object cannot be modified if mplsXCRowStatus is
			active(1)."
	::= { mplsXCEntry 3 }		::= { mplsXCEntry 3 }
	mplsXCIsPersistent OBJECT-TYPE		mplsXCIsPersistent OBJECT-TYPE
	SYNTAX TruthValue		SYNTAX TruthValue
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Denotes whether or not this cross-connect entry and		"Denotes whether or not this cross-connect entry and
	associated in- and out-segments should be restored		associated in- and out-segments should be restored
	automatically after failures. This value MUST be		automatically after failures. This value MUST be
	set to false in cases where this cross-connect entry		set to false in cases where this cross-connect entry
	was created by a signaling protocol."		was created by a signaling protocol. This object
			cannot be modified if mplsXCRowStatus is active(1)."
	DEFVAL { false }		DEFVAL { false }
	::= { mplsXCEntry 4 }		::= { mplsXCEntry 4 }
	mplsXCOwner OBJECT-TYPE		mplsXCOwner OBJECT-TYPE
	SYNTAX MplsObjectOwner		SYNTAX MplsInitialCreationSource
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Denotes the entity that created and is responsible		"Denotes the entity that created and is responsible
	for managing this cross-connect."		for managing this cross-connect. This object cannot
			be modified if mplsXCRowStatus is active(1)."
	::= { mplsXCEntry 5 }		::= { mplsXCEntry 5 }
	mplsXCRowStatus OBJECT-TYPE		mplsXCRowStatus OBJECT-TYPE
	SYNTAX RowStatus		SYNTAX RowStatus
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"For creating, modifying, and deleting this row."		"For creating, modifying, and deleting this row."
	::= { mplsXCEntry 6 }		::= { mplsXCEntry 6 }
	mplsXCStorageType OBJECT-TYPE		mplsXCStorageType OBJECT-TYPE
	SYNTAX StorageType		SYNTAX StorageType
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Defines the storage type for this object."		"Defines the storage type for this object. This
			object cannot be modified if mplsXCRowStatus is
			active(1). If this variable is set to readOnly(5),
			and the corresponding TFIB entry is removed, then
			the agent must remove this row shortly thereafter."
	::= { mplsXCEntry 7 }		::= { mplsXCEntry 7 }
	mplsXCAdminStatus OBJECT-TYPE		mplsXCAdminStatus OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	up(1), -- ready to pass packets		up(1), -- ready to pass packets
	down(2),		down(2),
	testing(3) -- in some test mode		testing(3) -- in some test mode
	}		}
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	skipping to change at page 36, line 31		skipping to change at page 35, line 9
	-- Label stack table.		-- Label stack table.
	mplsMaxLabelStackDepth OBJECT-TYPE		mplsMaxLabelStackDepth OBJECT-TYPE
	SYNTAX Integer32 (1..2147483647)		SYNTAX Integer32 (1..2147483647)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The maximum stack depth supported by this LSR."		"The maximum stack depth supported by this LSR."
	::= { mplsLsrObjects 10 }		::= { mplsLsrObjects 10 }
	mplsLabelStackIndexNext OBJECT-TYPE		mplsLabelStackIndexNext OBJECT-TYPE
	SYNTAX Integer32 (0..2147483647)		SYNTAX Unsigned32 (0..4294967295)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object contains an appropriate value to be used		"This object contains an appropriate value to be used
	for mplsLabelStackIndex when creating entries in the		for mplsLabelStackIndex when creating entries in the
	mplsLabelStackTable. The value 0 indicates that no		mplsLabelStackTable. The value 0 indicates that no
	unassigned entries are available. To obtain an		unassigned entries are available. To obtain an
	mplsLabelStackIndex value for a new entry, the		mplsLabelStackIndex value for a new entry, the
	manager issues a management protocol retrieval		manager issues a management protocol retrieval
	operation to obtain the current value of this		operation to obtain the current value of this
	skipping to change at page 37, line 25		skipping to change at page 35, line 52
	DESCRIPTION		DESCRIPTION
	"An entry in this table represents one label which is		"An entry in this table represents one label which is
	to be pushed onto an outgoing packet, beneath the		to be pushed onto an outgoing packet, beneath the
	top label. An entry can be created by a network		top label. An entry can be created by a network
	administrator or by an SNMP agent as instructed by		administrator or by an SNMP agent as instructed by
	an MPLS signaling protocol."		an MPLS signaling protocol."
	INDEX { mplsLabelStackIndex, mplsLabelStackLabelIndex }		INDEX { mplsLabelStackIndex, mplsLabelStackLabelIndex }
	::= { mplsLabelStackTable 1 }		::= { mplsLabelStackTable 1 }
	MplsLabelStackEntry ::= SEQUENCE {		MplsLabelStackEntry ::= SEQUENCE {
	mplsLabelStackIndex Integer32,		mplsLabelStackIndex Unsigned32,
	mplsLabelStackLabelIndex Integer32,		mplsLabelStackLabelIndex Unsigned32,
	mplsLabelStackLabel MplsLabel,		mplsLabelStackLabel MplsLabel,
	mplsLabelStackRowStatus RowStatus,		mplsLabelStackRowStatus RowStatus,
	mplsLabelStackStorageType StorageType		mplsLabelStackStorageType StorageType
	}		}
	mplsLabelStackIndex OBJECT-TYPE		mplsLabelStackIndex OBJECT-TYPE
	SYNTAX Integer32 (1..2147483647)		SYNTAX Unsigned32 (1..2147483647)
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Primary index for this row identifying a stack of		"Primary index for this row identifying a stack of
	labels to be pushed on an outgoing packet, beneath		labels to be pushed on an outgoing packet, beneath
	the top label."		the top label."
	::= { mplsLabelStackEntry 1 }		::= { mplsLabelStackEntry 1 }
	mplsLabelStackLabelIndex OBJECT-TYPE		mplsLabelStackLabelIndex OBJECT-TYPE
	SYNTAX Integer32 (1..2147483647)		SYNTAX Unsigned32 (1..2147483647)
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Secondary index for this row identifying one label		"Secondary index for this row identifying one label
	of the stack. Note that an entry with a smaller		of the stack. Note that an entry with a smaller
	mplsLabelStackLabelIndex would refer to a label		mplsLabelStackLabelIndex would refer to a label
	higher up the label stack and would be popped at a		higher up the label stack and would be popped at a
	downstream LSR before a label represented by a		downstream LSR before a label represented by a
	higher mplsLabelStackLabelIndex at a downstream		higher mplsLabelStackLabelIndex at a downstream
	LSR."		LSR."
	skipping to change at page 38, line 27		skipping to change at page 37, line 4
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"For creating, modifying, and deleting this row."		"For creating, modifying, and deleting this row."
	::= { mplsLabelStackEntry 4 }		::= { mplsLabelStackEntry 4 }
	mplsLabelStackStorageType OBJECT-TYPE		mplsLabelStackStorageType OBJECT-TYPE
	SYNTAX StorageType		SYNTAX StorageType
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Defines the storage type for this object."		"Defines the storage type for this object. If this
			variable is set to readOnly(5), and the
			corresponding TFIB entry is removed, then the agent
			must remove this row shortly thereafter."
	::= { mplsLabelStackEntry 5 }		::= { mplsLabelStackEntry 5 }
	-- End of mplsLabelStackTable		-- End of mplsLabelStackTable
	-- Traffic Parameter table.		-- Traffic Parameter table.
	mplsTrafficParamIndexNext OBJECT-TYPE		mplsTrafficParamIndexNext OBJECT-TYPE
	SYNTAX Integer32 (0..2147483647)		SYNTAX Unsigned32 (0..4294967295)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object contains an appropriate value which will		"This object contains an appropriate value which will
	be used for mplsTrafficParamIndex when creating		be used for mplsTrafficParamIndex when creating
	entries in the mplsTrafficParamTable. The value 0		entries in the mplsTrafficParamTable. The value 0
	indicates that no unassigned entries are available.		indicates that no unassigned entries are available.
	To obtain the mplsTrafficParamIndex value for a new		To obtain the mplsTrafficParamIndex value for a new
	entry, the manager issues a management protocol		entry, the manager issues a management protocol
	retrieval operation to obtain the current value of		retrieval operation to obtain the current value of
	skipping to change at page 39, line 27		skipping to change at page 38, line 6
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table represents the TrafficParam		"An entry in this table represents the TrafficParam
	objects for one or more in or out segments. A		objects for one or more in or out segments. A
	single entry can be pointed to by multiple segments		single entry can be pointed to by multiple segments
	indicating resource sharing."		indicating resource sharing."
	INDEX { mplsTrafficParamIndex }		INDEX { mplsTrafficParamIndex }
	::= { mplsTrafficParamTable 1 }		::= { mplsTrafficParamTable 1 }
	MplsTrafficParamEntry ::= SEQUENCE {		MplsTrafficParamEntry ::= SEQUENCE {
	mplsTrafficParamIndex Integer32,		mplsTrafficParamIndex Unsigned32,
	mplsTrafficParamMaxRate MplsBitRate,		mplsTrafficParamMaxRate MplsBitRate,
	mplsTrafficParamMeanRate MplsBitRate,		mplsTrafficParamMeanRate MplsBitRate,
	mplsTrafficParamMaxBurstSize MplsBurstSize,		mplsTrafficParamMaxBurstSize MplsBurstSize,
	mplsTrafficParamRowStatus RowStatus,		mplsTrafficParamRowStatus RowStatus,
	mplsTrafficParamStorageType StorageType		mplsTrafficParamStorageType StorageType
	}		}
	mplsTrafficParamIndex OBJECT-TYPE		mplsTrafficParamIndex OBJECT-TYPE
	SYNTAX Integer32 (1..2147483647)		SYNTAX Unsigned32 (1..2147483647)
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Uniquely identifies this row of the table. Note		"Uniquely identifies this row of the table. Note
	that zero represents an invalid index."		that zero represents an invalid index."
	::= { mplsTrafficParamEntry 1 }		::= { mplsTrafficParamEntry 1 }
	mplsTrafficParamMaxRate OBJECT-TYPE		mplsTrafficParamMaxRate OBJECT-TYPE
	SYNTAX MplsBitRate		SYNTAX MplsBitRate
	UNITS "kilobits per second"		UNITS "kilobits per second"
	skipping to change at page 40, line 33		skipping to change at page 39, line 13
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"For creating, modifying, and deleting this row."		"For creating, modifying, and deleting this row."
	::= { mplsTrafficParamEntry 5 }		::= { mplsTrafficParamEntry 5 }
	mplsTrafficParamStorageType OBJECT-TYPE		mplsTrafficParamStorageType 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 object."		"The storage type for this object. If this variable
			is set to readOnly(5), and the corresponding TFIB
			entry is removed, then the agent must remove this
			row shortly thereafter."
	::= { mplsTrafficParamEntry 6 }		::= { mplsTrafficParamEntry 6 }
	-- End of mplsTrafficParamTable		-- End of mplsTrafficParamTable
	-- Notification Configuration		-- Notification Configuration
	mplsXCTrapEnable OBJECT-TYPE		mplsXCTrapEnable 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 set to true(1), then it enables
	generation of mplsXCUp and mplsXCDown traps,		the emission of mplsXCUp and mplsXCDown
	otherwise these traps are not emitted."		notifications; otherwise these notifications are not
			emitted."
	DEFVAL { false }		DEFVAL { false }
	::= { mplsLsrObjects 15 }		::= { mplsLsrObjects 15 }
	-- Cross-connect.		-- Cross-connect.
	mplsXCUp NOTIFICATION-TYPE		mplsXCUp NOTIFICATION-TYPE
	OBJECTS { mplsXCIndex,		OBJECTS {
	mplsInSegmentIfIndex,		mplsXCOperStatus, -- start of range
	mplsInSegmentLabel,		mplsXCOperStatus -- end of range
	mplsOutSegmentIndex,		}
	mplsXCAdminStatus,
	mplsXCOperStatus }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This notification is generated when a		"This notification is generated when the
	mplsXCOperStatus object for one of the configured		mplsXCOperStatus object for one or more contiguous
	cross-connect entries is about to leave the down		entries in mplsXCTable are about to enter the up(1)
	state and transition into some other state (but not		state from some other. The included values of
	into the notPresent state). This other state is		mplsXCOperStatus MUST both be set equal to this
	indicated by the included value of		other state. The two instances of mplsXCOperStatus
	mplsXCOperStatus."		in this notification indicate the range of indexes
			that are affected. Note that all the indexes of the
			two ends of the range can be derived from the
			instance identifiers of these two objects. For
			cases where a contiguous range of cross-connects
			have transitioned into the up(1) state at roughly
			the same time, the device SHOULD issue a single
			notification for each range of contiguous indexes in
			an effort to minimize the emission of a large number
			of notifications. If a notification has to be
			issued for just a single cross-connect entry, then
			the instance identifier (and values) of the two
			mplsXCOperStatus objects MUST be the identical."
	::= { mplsLsrNotifyPrefix 1 }		::= { mplsLsrNotifyPrefix 1 }
	mplsXCDown NOTIFICATION-TYPE		mplsXCDown NOTIFICATION-TYPE
	OBJECTS { mplsXCIndex,		OBJECTS {
	mplsInSegmentIfIndex,		mplsXCOperStatus, -- start of range
	mplsInSegmentLabel,		mplsXCOperStatus -- end of range
	mplsOutSegmentIndex,		}
	mplsXCAdminStatus,
	mplsXCOperStatus }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This notification is generated when a		" This notification is generated when the
	mplsXCOperStatus object for one of the configured		mplsXCOperStatus object for one or more contiguous
	cross-connect entries is about to enter the down		entries in mplsXCTable are about to enter the
	state from some other state (but not from the		down(2) state from some other. The included values
	notPresent state). This other state is indicated by		of mplsXCOperStatus MUST both be set equal to this
	the included value of mplsXCOperStatus."		other state. The two instances of mplsXCOperStatus
			in this notification indicate the range of indexes
			that are affected. Note that all the indexes of the
			two ends of the range can be derived from the
			instance identifiers of these two objects. For
			cases where a contiguous range of cross-connects
			have transitioned into the down(2) state at roughly
			the same time, the device SHOULD issue a single
			notification for each range of contiguous indexes in
			an effort to minimize the emission of a large number
			of notifications. If a notification has to be
			issued for just a single cross-connect entry, then
			the instance identifier (and values) of the two
			mplsXCOperStatus objects MUST be the identical."
	::= { mplsLsrNotifyPrefix 2 }		::= { mplsLsrNotifyPrefix 2 }
	-- End of notifications.		-- End of notifications.
	-- Module compliance.		-- Module compliance.
	mplsLsrGroups		mplsLsrGroups
	OBJECT IDENTIFIER ::= { mplsLsrConformance 1 }		OBJECT IDENTIFIER ::= { mplsLsrConformance 1 }
	mplsLsrCompliances		mplsLsrCompliances
	skipping to change at page 42, line 11		skipping to change at page 41, line 17
	DESCRIPTION		DESCRIPTION
	"Compliance statement for agents that support the		"Compliance statement for agents that support the
	MPLS LSR MIB."		MPLS LSR MIB."
	MODULE -- this module		MODULE -- this module
	-- The mandatory groups have to be implemented		-- The mandatory groups have to be implemented
	-- by all LSRs. However, they may all be supported		-- by all LSRs. However, they may all be supported
	-- as read-only objects in the case where manual		-- as read-only objects in the case where manual
	-- configuration is unsupported.		-- configuration is unsupported.
	MANDATORY-GROUPS { mplsInSegmentGroup,		MANDATORY-GROUPS {
			mplsInSegmentGroup,
	mplsOutSegmentGroup,		mplsOutSegmentGroup,
	mplsXCGroup,		mplsXCGroup,
	mplsInterfaceGroup,		mplsInterfaceGroup,
	mplsPerfGroup,		mplsPerfGroup,
	mplsSegmentDiscontinuityGroup }		mplsSegmentDiscontinuityGroup
			}
	GROUP mplsHCInSegmentPerfGroup		GROUP mplsHCInSegmentPerfGroup
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for those in-segment		"This group is mandatory for those in-segment
	entries for which the object		entries for which the object
	mplsInSegmentOutOctets wraps around too		mplsInSegmentOutOctets wraps around too
	quickly."		quickly."
	GROUP mplsHCOutSegmentPerfGroup		GROUP mplsHCOutSegmentPerfGroup
	DESCRIPTION		DESCRIPTION
	skipping to change at page 42, line 46		skipping to change at page 42, line 4
	-- Depending on whether the device implements		-- Depending on whether the device implements
	-- persistent cross-connects or not one of the		-- persistent cross-connects or not one of the
	-- following two groups is mandatory.		-- following two groups is mandatory.
	GROUP mplsXCIsPersistentGroup		GROUP mplsXCIsPersistentGroup
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for devices which		"This group is mandatory for devices which
	support persistent cross-connects. The		support persistent cross-connects. The
	following constraints apply: mplsXCIsPersistent		following constraints apply: mplsXCIsPersistent
	must at least be read-only returning true(2)."		must at least be read-only returning true(2)."
	GROUP mplsXCIsNotPersistentGroup		GROUP mplsXCIsNotPersistentGroup
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for devices which		"This group is mandatory for devices which
	support non-persistent cross-connects. The		support non-persistent cross-connects. The
	following constraints apply: mplsXCIsPersistent		following constraints apply: mplsXCIsPersistent
	must at least be read-only returning false(1)."		must at least be read-only returning false(1)."
	-- mplsInterfaceConfTable
	OBJECT mplsInterfaceConfStorageType
	SYNTAX INTEGER { other(1) }
	MIN-ACCESS read-only
	DESCRIPTION
	"Only other(1) needs to be supported."
	-- mplsInSegmentTable		-- mplsInSegmentTable
	OBJECT mplsInSegmentXCIndex		OBJECT mplsInSegmentXCIndex
	DESCRIPTION		DESCRIPTION
	"Write access is not required."		"Write access is not required."
	OBJECT mplsInSegmentNPop		OBJECT mplsInSegmentNPop
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"Write access if not required. This object		"Write access is not required. This object
	should be set to 1 if it is read-only."		should be set to 1 if it is read-only."
	OBJECT mplsInSegmentAddrFamily		OBJECT mplsInSegmentAddrFamily
	DESCRIPTION		DESCRIPTION
	"Write access is not required. A <value of		"Write access is not required. A <value of
	other(0) should be supported because there may		other(0) should be supported because there may
	be cases where the agent may not know about or		be cases where the agent may not know about or
	support any address types."		support any address types."
	OBJECT mplsInSegmentStorageType		OBJECT mplsInSegmentStorageType
	skipping to change at page 44, line 22		skipping to change at page 43, line 20
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"Write access is not required."		"Write access is not required."
	OBJECT mplsOutSegmentNextHopIpv6Addr		OBJECT mplsOutSegmentNextHopIpv6Addr
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"Write access is not required."		"Write access is not required."
	OBJECT mplsOutSegmentRowStatus		OBJECT mplsOutSegmentRowStatus
	SYNTAX INTEGER { active(1), notInService(2),		SYNTAX INTEGER {
	createAndGo(4), destroy(6) }		active(1),
			notInService(2),
			createAndGo(4),
			destroy(6)
			}
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The notReady(3) and createAndWait(5) states need		"The notReady(3) and createAndWait(5) states need
	not be supported."		not be supported."
	OBJECT mplsOutSegmentStorageType		OBJECT mplsOutSegmentStorageType
	SYNTAX INTEGER { other(1) }		SYNTAX INTEGER { other(1) }
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"Only other(1) needs to be supported."		"Only other(1) needs to be supported."
	skipping to change at page 44, line 51		skipping to change at page 44, line 4
	OBJECT mplsXCIsPersistent		OBJECT mplsXCIsPersistent
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"Write access is not required."		"Write access is not required."
	OBJECT mplsXCAdminStatus		OBJECT mplsXCAdminStatus
	SYNTAX INTEGER { up(1), down(2) }		SYNTAX INTEGER { up(1), down(2) }
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"A value of testing(3) need not be supported."		"A value of testing(3) need not be supported."
	OBJECT mplsXCOperStatus		OBJECT mplsXCOperStatus
	SYNTAX INTEGER { up(1), down(2) }		SYNTAX INTEGER { up(1), down(2) }
	DESCRIPTION		DESCRIPTION
	"Only up(1) and down(2) need to be supported."		"Only up(1) and down(2) need to be supported."
	OBJECT mplsXCRowStatus		OBJECT mplsXCRowStatus
	SYNTAX INTEGER { active(1),		SYNTAX INTEGER {
			active(1),
	notInService(2),		notInService(2),
	createAndGo(4),		createAndGo(4),
	destroy(6) }		destroy(6)
			}
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"The notReady(3) and createAndWait(5) states need		"The notReady(3) and createAndWait(5) states need
	not be supported."		not be supported."
	OBJECT mplsXCStorageType		OBJECT mplsXCStorageType
	SYNTAX INTEGER { other(1) }		SYNTAX INTEGER { other(1) }
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"Only other(1) needs to be supported."		"Only other(1) needs to be supported."
	::= { mplsLsrCompliances 1 }		::= { mplsLsrCompliances 1 }
	-- Units of conformance.		-- Units of conformance.
	mplsInterfaceGroup OBJECT-GROUP		mplsInterfaceGroup OBJECT-GROUP
	OBJECTS { mplsInterfaceLabelMinIn,		OBJECTS {
			mplsInterfaceLabelMinIn,
	mplsInterfaceLabelMaxIn,		mplsInterfaceLabelMaxIn,
	mplsInterfaceLabelMinOut,		mplsInterfaceLabelMinOut,
	mplsInterfaceLabelMaxOut,		mplsInterfaceLabelMaxOut,
	mplsInterfaceTotalBandwidth,		mplsInterfaceTotalBandwidth,
	mplsInterfaceAvailableBandwidth,		mplsInterfaceAvailableBandwidth,
	mplsInterfaceLabelParticipationType,		mplsInterfaceLabelParticipationType
	mplsInterfaceConfStorageType
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Collection of objects needed for MPLS interface		"Collection of objects needed for MPLS interface
	configuration and performance information."		configuration and performance information."
	::= { mplsLsrGroups 1 }		::= { mplsLsrGroups 1 }
	mplsInSegmentGroup OBJECT-GROUP		mplsInSegmentGroup OBJECT-GROUP
	OBJECTS { mplsInSegmentNPop,		OBJECTS {
			mplsInSegmentNPop,
	mplsInSegmentAddrFamily,		mplsInSegmentAddrFamily,
	mplsInSegmentXCIndex,		mplsInSegmentXCIndex,
	mplsInSegmentOctets,		mplsInSegmentOctets,
	mplsInSegmentDiscards,		mplsInSegmentDiscards,
	mplsInSegmentOwner,		mplsInSegmentOwner,
	mplsInSegmentRowStatus,		mplsInSegmentRowStatus,
	mplsInSegmentStorageType,		mplsInSegmentStorageType,
	mplsInSegmentTrafficParamPtr		mplsInSegmentTrafficParamPtr
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Collection of objects needed to implement an in-		"Collection of objects needed to implement an in-
	segment."		segment."
	::= { mplsLsrGroups 2 }		::= { mplsLsrGroups 2 }
	mplsOutSegmentGroup OBJECT-GROUP		mplsOutSegmentGroup OBJECT-GROUP
	OBJECTS { mplsOutSegmentIndexNext,		OBJECTS {
			mplsOutSegmentIndexNext,
	mplsOutSegmentIfIndex,		mplsOutSegmentIfIndex,
	mplsOutSegmentPushTopLabel,		mplsOutSegmentPushTopLabel,
	mplsOutSegmentTopLabel,		mplsOutSegmentTopLabel,
	mplsOutSegmentNextHopIpAddrType,		mplsOutSegmentNextHopIpAddrType,
	mplsOutSegmentNextHopIpv4Addr,		mplsOutSegmentNextHopIpv4Addr,
	mplsOutSegmentNextHopIpv6Addr,		mplsOutSegmentNextHopIpv6Addr,
	mplsOutSegmentXCIndex,		mplsOutSegmentXCIndex,
	mplsOutSegmentOwner,		mplsOutSegmentOwner,
	mplsOutSegmentOctets,		mplsOutSegmentOctets,
	mplsOutSegmentDiscards,		mplsOutSegmentDiscards,
	skipping to change at page 46, line 35		skipping to change at page 45, line 41
	mplsOutSegmentStorageType,		mplsOutSegmentStorageType,
	mplsOutSegmentTrafficParamPtr		mplsOutSegmentTrafficParamPtr
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Collection of objects needed to implement an out-		"Collection of objects needed to implement an out-
	segment."		segment."
	::= { mplsLsrGroups 3 }		::= { mplsLsrGroups 3 }
	mplsXCGroup OBJECT-GROUP		mplsXCGroup OBJECT-GROUP
	OBJECTS { mplsXCIndexNext,		OBJECTS {
			mplsXCIndexNext,
	mplsXCLabelStackIndex,		mplsXCLabelStackIndex,
	mplsXCOwner,		mplsXCOwner,
	mplsXCAdminStatus,		mplsXCAdminStatus,
	mplsXCOperStatus,		mplsXCOperStatus,
	mplsXCRowStatus,		mplsXCRowStatus,
	mplsXCTrapEnable,		mplsXCTrapEnable,
	mplsXCStorageType		mplsXCStorageType
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	skipping to change at page 47, line 9		skipping to change at page 46, line 16
	mplsXCOptionalGroup OBJECT-GROUP		mplsXCOptionalGroup OBJECT-GROUP
	OBJECTS { mplsXCLspId }		OBJECTS { mplsXCLspId }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Collection of optional objects for implementing		"Collection of optional objects for implementing
	a cross-connect entry."		a cross-connect entry."
	::= { mplsLsrGroups 5 }		::= { mplsLsrGroups 5 }
	mplsPerfGroup OBJECT-GROUP		mplsPerfGroup OBJECT-GROUP
	OBJECTS { mplsInSegmentOctets,		OBJECTS {
			mplsInSegmentOctets,
	mplsInSegmentPackets,		mplsInSegmentPackets,
	mplsInSegmentErrors,		mplsInSegmentErrors,
	mplsInSegmentDiscards,		mplsInSegmentDiscards,
	mplsOutSegmentOctets,		mplsOutSegmentOctets,
	mplsOutSegmentPackets,		mplsOutSegmentPackets,
	mplsOutSegmentDiscards,		mplsOutSegmentDiscards,
	mplsInterfaceInLabelsUsed,		mplsInterfaceInLabelsUsed,
	mplsInterfaceFailedLabelLookup,		mplsInterfaceFailedLabelLookup,
	mplsInterfaceOutFragments,		mplsInterfaceOutFragments,
	mplsInterfaceOutLabelsUsed		mplsInterfaceOutLabelsUsed
	skipping to change at page 47, line 49		skipping to change at page 47, line 7
	OBJECTS { mplsOutSegmentHCOctets }		OBJECTS { mplsOutSegmentHCOctets }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Object(s) providing performance information		"Object(s) providing performance information
	specific to out-segments for which the object		specific to out-segments for which the object
	mplsInterfaceOutOctets wraps around too		mplsInterfaceOutOctets wraps around too
	quickly."		quickly."
	::= { mplsLsrGroups 8 }		::= { mplsLsrGroups 8 }
	mplsTrafficParamGroup OBJECT-GROUP		mplsTrafficParamGroup OBJECT-GROUP
	OBJECTS { mplsTrafficParamIndexNext,		OBJECTS {
			mplsTrafficParamIndexNext,
	mplsTrafficParamMaxRate,		mplsTrafficParamMaxRate,
	mplsTrafficParamMeanRate,		mplsTrafficParamMeanRate,
	mplsTrafficParamMaxBurstSize,		mplsTrafficParamMaxBurstSize,
	mplsTrafficParamRowStatus,		mplsTrafficParamRowStatus,
	mplsTrafficParamStorageType		mplsTrafficParamStorageType
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Object(s) required for supporting QoS resource		"Object(s) required for supporting QoS resource
	reservation."		reservation."
	skipping to change at page 48, line 29		skipping to change at page 47, line 38
	mplsXCIsNotPersistentGroup OBJECT-GROUP		mplsXCIsNotPersistentGroup OBJECT-GROUP
	OBJECTS { mplsXCIsPersistent }		OBJECTS { mplsXCIsPersistent }
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Objects needed to support non-persistent cross-		"Objects needed to support non-persistent cross-
	connects."		connects."
	::= { mplsLsrGroups 11 }		::= { mplsLsrGroups 11 }
	mplsLabelStackGroup OBJECT-GROUP		mplsLabelStackGroup OBJECT-GROUP
	OBJECTS {mplsLabelStackLabel,		OBJECTS {
			mplsLabelStackLabel,
	mplsLabelStackRowStatus,		mplsLabelStackRowStatus,
	mplsLabelStackStorageType,		mplsLabelStackStorageType,
	mplsMaxLabelStackDepth,		mplsMaxLabelStackDepth,
	mplsLabelStackIndexNext }		mplsLabelStackIndexNext
			}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Objects needed to support label stacking."		"Objects needed to support label stacking."
	::= { mplsLsrGroups 12 }		::= { mplsLsrGroups 12 }
	mplsSegmentDiscontinuityGroup OBJECT-GROUP		mplsSegmentDiscontinuityGroup OBJECT-GROUP
	OBJECTS { mplsInSegmentPerfDiscontinuityTime,		OBJECTS {
			mplsInSegmentPerfDiscontinuityTime,
	mplsOutSegmentPerfDiscontinuityTime		mplsOutSegmentPerfDiscontinuityTime
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	" A collection of objects providing information		" A collection of objects providing information
	specific to segment discontinuities.."		specific to segment discontinuities.."
	::= { mplsLsrGroups 13 }		::= { mplsLsrGroups 13 }
	mplsLsrNotificationGroup NOTIFICATION-GROUP		mplsLsrNotificationGroup NOTIFICATION-GROUP
	NOTIFICATIONS { mplsXCUp,		NOTIFICATIONS {
	mplsXCDown }		mplsXCUp,
			mplsXCDown
			}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Set of notifications implemented in this module.		"Set of notifications implemented in this module.
	None is mandatory."		None is mandatory."
	::= { mplsLsrGroups 14 }		::= { mplsLsrGroups 14 }
	END		END
	12. Security Considerations		11. Security Considerations
	It is clear that this MIB is potentially useful for monitoring of		It is clear that this MIB is potentially useful for monitoring of
	MPLS LSRs. This MIB can also be used for configuration of certain		MPLS LSRs. This MIB can also be used for configuration of certain
	objects, and anything that can be configured can be incorrectly		objects, and anything that can be configured can be incorrectly
	configured, with potentially disastrous results.		configured, with potentially disastrous results.
	At this writing, no security holes have been identified beyond		At this writing, no security holes have been identified beyond
	those that SNMP Security [SNMPArch] is itself intended to address.		those that SNMP Security [RFC2571] is itself intended to address.
	These relate to primarily controlled access to sensitive		These relate to primarily controlled access to sensitive
	information and the ability to configure a device - or which might		information and the ability to configure a device - or which might
	result from operator error, which is beyond the scope of any		result from operator error, which is beyond the scope of any
	security architecture.		security architecture.
	There are a number of management objects defined in this MIB which		There are a number of management objects defined in this MIB which
	have a MAX-ACCESS clause of read-write and/or read-create. Such		have a MAX-ACCESS clause of read-write and/or read-create. Such
	objects may be considered sensitive or vulnerable in some network		objects may be considered sensitive or vulnerable in some network
	environments. The support for SET operations in a non-secure		environments. The support for SET operations in a non-secure
	environment without proper protection can have a negative effect		environment without proper protection can have a negative effect
	on network operations. The use of SNMP Version 3 is recommended		on network operations. The use of SNMP Version 3 is recommended
	over prior versions, for configuration control, as its security		over prior versions, for configuration control, as its security
	model is improved.		model is improved.
	SNMPv1 or SNMPv2 are by themselves not a secure environment. Even		SNMPv1 or SNMPv2 are by themselves not a secure environment. Even
	if the network itself is secure (for example by using IPSec		if the network itself is secure (for example by using IPSec
	[IPSEC]), there is no control as to who on the secure network is		[RFC2401]), there is no control as to who on the secure network is
	allowed to access and GET/SET (read/change/create/delete) the		allowed to access and GET/SET (read/change/create/delete) the
	objects in this MIB. It is recommended that the implementers		objects in this MIB. It is recommended that the implementers
	consider the security features as provided by the SNMPv3		consider the security features as provided by the SNMPv3
	framework. Specifically, the use of the User-based Security Model		framework. Specifically, the use of the User-based Security Model
	[SNMPv3USM] and the View-based Access Control [SNMPv3VACM] is		[RFC2574] and the View-based Access Control [RFC2575] is
	recommended. It is then a customer/user responsibility to ensure		recommended. It is then a customer/user responsibility to ensure
	that the SNMP entity giving access to an instance of this MIB is		that the SNMP entity giving access to an instance of this MIB is
	properly configured to give access to the objects only to those		properly configured to give access to the objects only to those
	principals (users) that have legitimate rights to indeed GET or		principals (users) that have legitimate rights to indeed GET or
	SET (change/create/delete) them.		SET (change/create/delete) them.
	There are a number of managed objects in this MIB that may contain		There are a number of managed objects in this MIB that may contain
	information that may be sensitive from a business perspective, in		information that may be sensitive from a business perspective, in
	that they represent a customer's interface to the MPLS network.		that they represent a customer's interface to the MPLS network.
	Allowing uncontrolled access to these objects could result in		Allowing uncontrolled access to these objects could result in
	malicious and unwanted disruptions of network traffic or incorrect		malicious and unwanted disruptions of network traffic or incorrect
	configurations for these customers. There are no objects that are		configurations for these customers. There are no objects that are
	particularly sensitive in their own right, such as passwords or		particularly sensitive in their own right, such as passwords or
	monetary amounts.		monetary amounts.
	13. Acknowledgments		12. Acknowledgments
	We wish to thank Ron Bonica, Adrian Farrel, Eric Gray, Tim		We wish to thank Ron Bonica, Adrian Farrel, Eric Gray, Tim
	Mancour, Keith McCloghrie, Bala Rajagopalan, Dan Tappan,		Mancour, Keith McCloghrie, Bala Rajagopalan, Dan Tappan, Vasanthi
	Vasanthi Thirumalai, Joseph Benoit and Joan Cucchiara.		Thirumalai, Joseph Benoit and Joan Cucchiara.
	14. References
	[MPLSArch] Rosen, E., Viswanathan, A., and R. Callon,
	"Multiprotocol Label Switching Architecture",
	Internet Draft <draft-ietf-mpls-arch-06.txt>,
	August 1999.
	[MPLSFW] Callon, R., Doolan, P., Feldman, N., Fredette, A.,
	Swallow, G., and A. Viswanathan, "A Framework for
	Multiprotocol Label Switching", Internet Draft
	<draft-ietf-mpls-framework-05.txt>, September 1999.
	[LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,		13. References
	Federokow, G., Li, T., and A. Conta, "MPLS Label
	Stack Encoding", Internet Draft <draft-ietf-mpls-
	label-encaps-07.txt>, September 1999.
	[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",		[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
	RFC 1700, October 1994. See also:		RFC 1700, October 1994. See also:
	http://www.isi.edu/in-notes/iana/assignments/smi-		http://www.isi.edu/in-notes/iana/assignments/smi-
	numbers		numbers
	[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS		[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
	FAMILY NUMBERS,(http://www.isi.edu/in-		FAMILY NUMBERS,(http://www.isi.edu/in-
	notes/iana/assignements/address-family-numbers),		notes/iana/assignements/address-family-numbers),
	for MIB see:		for MIB see:
	ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib		ftp://ftp.isi.edu/mib/iana.mib/ianaaddressfamilynum
			bers.mib
	[SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An		[TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C,
	Architecture for Describing SNMP Management		Viswanathan, A. and H. Sjostrand, "Definition of
	Frameworks", RFC 2271, January 1998.		Textual Conventions and OBJECT-IDENTITIES for Multi-
			Protocol Label Switching (MPLS) Management",
			Internet Draft <draft-ietf-mpls-tc-mib-03.txt>,
			January 2002.
	[SMIv1] Rose, M., and K. McCloghrie, "Structure and		[RFC1155] Rose, M., and K. McCloghrie, "Structure and
	Identification of Management Information for TCP/IP-		Identification of Management Information for TCP/IP-
	based Internets", RFC 1155, May 1990.		based Internets", RFC 1155, May 1990.
	[SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB		[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
	Definitions", RFC 1212, March 1991.		"Simple Network Management Protocol", RFC 1157, May
			1990.
	[SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use		[RFC1215] M. Rose, "A Convention for Defining Traps for use
	with the SNMP", RFC 1215, March 1991.		with the SNMP", RFC 1215, March 1991.
	[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,		[RFC1901] Case, J., McCloghrie, K., Rose, M., and S.
	"Message Processing and Dispatching for the Simple		Waldbusser, "Introduction to Community-based
	Network Management Protocol (SNMP)", RFC 2572,		SNMPv2", RFC 1901, January 1996.
	April 1999.
	[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
	Model (USM) for version 3 of the Simple Network
	Management Protocol (SNMPv3)", RFC 2574, April
	1999.
	[RFC1905] Case, J., McCloghrie, K., Rose, M., and S.		[RFC1905] Case, J., McCloghrie, K., Rose, M., and S.
	Waldbusser, "Protocol Operations for Version 2 of		Waldbusser, "Protocol Operations for Version 2 of
	the Simple Network Management Protocol (SNMPv2)",		the Simple Network Management Protocol (SNMPv2)",
	RFC 1905, January 1996.		RFC 1905, January 1996.
	[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3		[RFC1906] Case, J., McCloghrie, K., Rose, M., and S.
	Applications", RFC 2573, April 1999.		Waldbusser, "Transport Mappings for Version 2 of
			the Simple Network Management Protocol (SNMPv2)",
			RFC 1906, January 1996.
	[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	based Access Control Model (VACM) for the Simple		Requirement Levels", BCP 14, RFC 2119, March 1997.
	Network Management Protocol (SNMP)", RFC 2575,
	April 1999.		[RFC2863] McCloghrie, K., and F. Kastenholtz, "The Interfaces
			Group MIB using SMIv2", RFC 2863, June 2000
			[RFC2401] Kent, S., and Atkinson, R., "Security Architecture
			for the Internet Protocol", RFC 2401, November
			1998.
			[RFC2515] Tesink, K., "Definitions of Managed Objects for ATM
			Management", RFC 2515, Feb. 1999
	[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,		[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
	"Introduction to Version 3 of the Internet-standard		"Introduction to Version 3 of the Internet-standard
	Network Management Framework", RFC 2570, April		Network Management Framework", RFC 2570, April
	1999.		1999.
	[SMIv2] Case, J., McCloghrie, K., Rose, M., and S.		[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
	Waldbusser, "Structure of Management Information		Architecture for Describing SNMP Management
	for Version 2 of the Simple Network Management		Frameworks", RFC 2571, April 1999.
	Protocol (SNMPv2)", RFC 1902, January 1996.
	[SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S.
	Waldbusser, "Textual Conventions for Version 2 of
	the Simple Network Management Protocol (SNMPv2)",
	RFC 1903, SNMP Research, Inc., Cisco Systems, Inc.,
	January 1996.
	[SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S.
	Waldbusser, "Conformance Statements for Version 2
	of the Simple Network Management Protocol
	(SNMPv2)", RFC 1904, January 1996.
	[SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
	"Simple Network Management Protocol", RFC 1157, May
	1990.
	[SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S.
	Waldbusser, "Introduction to Community-based
	SNMPv2", RFC 1901, January 1996.
	[SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S.
	Waldbusser, "Transport Mappings for Version 2 of
	the Simple Network Management Protocol (SNMPv2)",
	RFC 1906, January 1996.
	[SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen,		[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
	"Message Processing and Dispatching for the Simple		"Message Processing and Dispatching for the Simple
	Network Management Protocol (SNMP)", RFC 2272,		Network Management Protocol (SNMP)", RFC 2572,
	January 1998.		April 1999.
	[SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security		[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
			Applications", RFC 2573, April 1999.
			[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
	Model (USM) for version 3 of the Simple Network		Model (USM) for version 3 of the Simple Network
	Management Protocol (SNMPv3)", RFC 2574, April		Management Protocol (SNMPv3)", RFC 2574, April
	1999.		1999.
	[SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S.		[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-
	Waldbusser, "Protocol Operations for Version 2 of
	the Simple Network Management Protocol (SNMPv2)",
	RFC 1905, January 1996.
	[SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
	Applications", RFC 2273, January 1998.
	[SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-
	based Access Control Model (VACM) for the Simple		based Access Control Model (VACM) for the Simple
	Network Management Protocol (SNMP)", RFC 2575,		Network Management Protocol (SNMP)", RFC 2575,
	April 1999.		April 1999.
	[IPSEC] Kent, S., and Atkinson, R., "Security Architecture		[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
	for the Internet Protocol", RFC 2401, November		Case, J., Rose, M., and S. Waldbusser, "Structure
	1998.		of Management Information Version 2 (SMIv2)", STD
			58, RFC 2578, April 1999.
	[IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces		[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
	Group MIB using SMIv2", RFC 2233, Nov. 1997		Case, J., Rose, M., and S. Waldbusser, "Textual
			Conventions for SMIv2", STD 58, RFC 2579, April
			1999.
	[ATOMMIB] Tesink, K., "Definitions of Managed Objects for ATM		[RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M.,
	Management", RFC 2515, Feb. 1999		and J. McManus, "Requirements for Traffic
			Engineering Over MPLS", RFC 2702, September 1999.
	[BCP14] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Case, J., Rose, M., and S. Waldbusser, "Conformance
			Statements for SMIv2", STD 58, RFC 2580, April
			1999.
	15. Authors' Addresses		[RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
			"Multiprotocol Label Switching Architecture", RFC
			3031, January 2001.
			[RFC3032] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,
			Federokow, G., Li, T., and A. Conta, "MPLS Label
			Stack Encoding", RFC 3032, January 2001.
			14. Authors' Addresses
	Cheenu Srinivasan		Cheenu Srinivasan
	Tachion Networks, Inc.		Parama Networks, Inc.
	Monmouth Park Corporate Center I		1030 Broad Street
	Building C, 185 Monmouth Parkway		Shrewsbury, NJ 07702
	West Long Branch, NJ 07764		Phone: +1-732-544-9120 x731
	Phone: +1-732-542-7750 x1234		Email: cheenu@paramanet.com
	Email: cheenu@tachion.com
	Arun Viswanathan		Arun Viswanathan
	Force10 Networks, Inc.		Force10 Networks, Inc.
	1440 McCarthy Blvd		1440 McCarthy Blvd
	Milpitas, CA 95035		Milpitas, CA 95035
	Phone: +1-408-571-3516		Phone: +1-408-571-3516
	Email: arun@force10networks.com		Email: arun@force10networks.com
	Thomas D. Nadeau		Thomas D. Nadeau
	Cisco Systems, Inc.		Cisco Systems, Inc.
	250 Apollo Drive		250 Apollo Drive
	Chelmsford, MA 01824		Chelmsford, MA 01824
	Phone: +1-978-244-3051		Phone: +1-978-244-3051
	skipping to change at page 53, line 29		skipping to change at page 52, line 17
	Phone: +1-408-571-3516		Phone: +1-408-571-3516
	Email: arun@force10networks.com		Email: arun@force10networks.com
	Thomas D. Nadeau		Thomas D. Nadeau
	Cisco Systems, Inc.		Cisco Systems, Inc.
	250 Apollo Drive		250 Apollo Drive
	Chelmsford, MA 01824		Chelmsford, MA 01824
	Phone: +1-978-244-3051		Phone: +1-978-244-3051
	Email: tnadeau@cisco.com		Email: tnadeau@cisco.com
	16. Full Copyright Statement		15. Full Copyright Statement
	Copyright (C) The Internet Society (2000). All Rights Reserved.		Copyright (C) The Internet Society (2001). All Rights Reserved.
	This document and translations of it may be copied and furnished		This document and translations of it may be copied and furnished
	to others, and derivative works that comment on or otherwise		to others, and derivative works that comment on or otherwise
	explain it or assist in its implementation may be prepared,		explain it or assist in its implementation may be prepared,
	copied, published and distributed, in whole or in part, without		copied, published and distributed, in whole or in part, without
	restriction of any kind, provided that the above copyright notice		restriction of any kind, provided that the above copyright notice
	and this paragraph are included on all such copies and derivative		and this paragraph are included on all such copies and derivative
	works. However, this document itself may not be modified in any		works. However, this document itself may not be modified in any
	way, such as by removing the copyright notice or references to the		way, such as by removing the copyright notice or references to the
	Internet Society or other Internet organizations, except as needed		Internet Society or other Internet organizations, except as needed
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/