draft-ietf-ccamp-gmpls-te-mib-00.txt		draft-ietf-ccamp-gmpls-te-mib-01.txt
	CCAMP Working Group Thomas D. Nadeau		CCAMP Working Group Thomas D. Nadeau
	Internet Draft Cisco Systems, Inc.		Internet Draft Cisco Systems, Inc.
	Expires: December 2002		Expires: February 2004
	Cheenu Srinivasan		Cheenu Srinivasan
	Parama Networks, Inc.		Bloomberg L.P.
	Adrian Farrel		Adrian Farrel
	Movaz Networks, Inc.		Old Dog Consulting
	Edward Harrison
	Tim Hall		Tim Hall
			Ed Harrison
	Data Connection Ltd.		Data Connection Ltd.
	June 2002		August 2003
	Generalized Multiprotocol Label Switching (GMPLS) Traffic		Generalized Multiprotocol Label Switching (GMPLS) Traffic
	Engineering Management Information Base		Engineering Management Information Base
	draft-ietf-ccamp-gmpls-te-mib-00.txt		draft-ietf-ccamp-gmpls-te-mib-01.txt
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full		This document is an Internet-Draft and is in full conformance with
	conformance with all provisions of Section 10 of RFC2026.		all provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet		Internet-Drafts are working documents of the Internet Engineering
	Engineering Task Force (IETF), its areas, and its working		Task Force (IETF), its areas, and its working groups. Note that
	groups. Note that other groups may also distribute		other groups may also distribute working documents as Internet-
	working documents as Internet-Drafts.		Drafts.
	Internet-Drafts are draft documents valid for a maximum		Internet-Drafts are draft documents valid for a maximum of six months
	of six months and may be updated, replaced, or obsoleted		and may be updated, replaced, or obsoleted by other documents at any
	by other documents at any time. It is inappropriate to		time. It is inappropriate to use Internet-Drafts as reference
	use Internet-Drafts as reference material or to cite them		material or to cite them other than as "work in progress."
	other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be		The list of Internet-Draft Shadow Directories can be accessed at
	accessed at http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	Abstract		Abstract
	This memo defines an experimental portion of the		This memo defines an experimental portion of the Management
	Management Information Base (MIB) for use with network		Information Base (MIB) for use with network management protocols in
	management protocols in the Internet community. In		the Internet community. In particular, it describes managed objects
	particular, it describes managed objects for Generalized		for Generalized Multiprotocol Label Switching (GMPLS) based traffic
	Multiprotocol Label Switching (GMPLS) [GMPLSArch] based		engineering.
	traffic engineering.
	Nadeau, et al. [Page 1 ]
	Table of Contents		Table of Contents
	1. Changes and Pending Work 2		1. Introduction 2
	1.1. Changes Since the Last Version 2		1.1. Migration Strategy 3
	1.2. Pending Work 3		2. Terminology 3
	2. Introduction 3		3. The SNMP Management Framework 3
	2.1. Migration Strategy 4		4. Outline 4
	3. Terminology 4		4.1. Summary of GMPLS Traffic Engineering MIB Module 4
	4. The SNMP Management Framework 4		5. Brief Description of GMPLS TE MIB Objects 4
	5. Feature List 5		5.1. gmplsTunnelTable 4
	6. Outline 6		5.2. gmplsTunnelHopTable 5
	6.1. Summary of GMPLS Traffic Engineering MIB 6		5.3. gmplsTunnelARHopTable 5
	7. Brief Description of MIB Objects 6		5.4. gmplsTunnelCHopTable 5
	7.1. gmplsTunnelTable 6		5.5. gmplsTunnelErrorTable 5
	7.2. gmplsTunnelHopTable 7		5.6. gmplsTunnelPerfTable 5
	7.3. gmplsTunnelARHopTable 7		6. Cross-referencing to the mplsLabelTable 5
	7.4. gmplsTunnelCHoptable 7		7. Example of GMPLS Tunnel Setup 6
	7.5. gmplsTunnelErrorTable 7		8. GMPLS Traffic Engineering MIB Definitions 8
	7.6. gmplsTunnelPerfTable 7		9. Security Considerations 36
	8. Example of GMPLS Tunnel Setup 8		10. Acknowledgments 37
	9. Cross-referencing to the mplsLabelTable 10		11. References 37
	10. GMPLS Traffic Engineering MIB Definitions 10		11.1. Normative Refenerces 37
	11. Security Considerations 37		11.2. Informational References 39
	12. Acknowledgments 38		12. Authors' Addresses 39
	13. References 38		13. Full Copyright Statement 40
	13.1. Normative References 38		14. Intellectual Property Notice 41
	13.2. Informational References 40		15. Changes and Pending Work 41
	14. Authors' Addresses 42		15.1. Pending Work 41
	15. Full Copyright Statement 42
	1. Changes and Pending Work
	This section to be removed before the draft progresses to
	RFC.
	1.1. Changes Since the Last Version
	This is the first version of this draft.
	1.2. Pending Work
	The following work items have been identified for this
	draft. They will be addressed in a future version.
	Nadeau, et al. [Page 2 ]
	- Clarify which objects can be modified when rowStatus
	and adminStatus are set to active
	- Expand conformance statements to give one for
	monitoring only, and one for monitoring and control.
	- Bring references up to date, include all drafts
	referenced from this document, and exclude those that
	are not referenced.
	- Consider a way to expose tunnel head, tunnel tail, and
	tunnel transit entries through distinct indexing or
	tables.
	- Provide support for configuring tunnel resources in
	GMPLS systems. For example, SONET/SDH or G.709. This
	might be done through an arbitrary RowPointer to an
	external MIB.
	- Link Ids in EROs and RROs for use of bundled links.
	- Crankback request and reported information.
	- Control and reporting of upstream and downstream
	Notify Recipients.
	- Add support for control and reporting of GMPLS
	Administrative Status object.
	- Add support for IF_ID control and error reporting.
	- Add support for selection and configuration of restart
	options.
	- Update enumerated types in line with latest GMPLS
	drafts.
	- Resolve ownership of enumerated types that are also
	defined in GMPLS or routing drafts. (See "Ed Note:"
	in text.) These could be owned by IANA, imported from
	another MIB, or manually kept in step here. If they
	are not maintained externally then they are likely to
	diverge and MIB implementations will need to provide
	mappings.
	- Test compile MIBs.
	2. Introduction
	This memo defines an experimental portion of the
	Management Information Base (MIB) for use with network
	Nadeau, et al. [Page 3 ]
	management protocols in the Internet community. In
	particular, it describes managed objects for
	Multiprotocol Label Switching (MPLS) [RFC3031] and
	Generalized Multiprotocol Label Switching (GMPLS)
	[GMPLSArch] based traffic engineering.
	Comments should be made directly to the CCAMP mailing
	list at ccamp@ops.ietf.org.
	This memo does not, in its draft form, specify a standard
	for the Internet community.
	2.1. Migration Strategy
	This MIB extends the traffic engineering MIB defined for
	use with MPLS [TEMIB]. It provides additions for support
	of GMPLS tunnels.
	The companion document modeling and managing GMPLS based
	LSRs [GMPLSLSRMIB] extends MPLS LSR MIB [LSRMIB] with the
	same intentions.
	Textual conventions and OBJECT-IDENTIFIERS are defined in
	[GMPLSTCMIB] and [TCMIB].
	3. Terminology
	This document uses terminology from the MPLS architecture
	document [RFC3031] and Label Switching Router MIB
	[LSRMIB]. It imports constructs from the GMPLS textual
	conventions MIB [GMPLSTCMIB] and from the MPLS textual
	conventions MIB [TCMIB]. Some frequently used terms are
	described next.
	An explicitly routed LSP (ERLSP) is referred to as an
	MPLS tunnel. It consists of one in-segment and/or one
	out-segment at the ingress/egress LSRs, each segment
	being associated with one MPLS interface. These are also
	referred to as tunnel segments.
	Additionally, at an intermediate LSR, we model a
	connection as consisting of one or more in-segments
	and/or one or more out-segments. The binding or
	interconnection between in-segments and out-segments in
	performed using a cross-connect. These objects are
	defined in the GMPLS Label Switching Router MIB
	[GMPLSLSRMIB].
	4. The SNMP Management Framework
	Nadeau, et al. [Page 4 ]
	The SNMP Management Framework presently consists of five
	major components:
	- An overall architecture, described in RFC 2571		1. Introduction
	[RFC2571].
	- Mechanisms for describing and naming objects and		This memo defines a portion of the Management Information Base (MIB)
	events for the purpose of management. The first		for use with network management protocols in the Internet community.
	version of this Structure of Management Information		In particular, it describes managed objects for modeling a
	(SMI) is called SMIv1 and described in STD 16, RFC		Generalized Multi-Protocol Label Switching (GMPLS) [GMPLSArch] based
	1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC		traffic engineering. The tables and objects defined in this document
	1215 [RFC1215]. The second version, called SMIv2, is		extend those defined in the equivalent document for MPLS traffic
	described in STD 58, RFC 2578 [RFC2578], STD 58, RFC		engineering [TEMIB], and management of GMPLS traffic engineering is
	2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].		built on management of MPLS traffic engineering.
	- Message protocols for transferring management		This MIB module should be used in conjunction with the companion
	information. The first version of the SNMP message		document [GMPLSLSRMIB] for GMPLS based traffic engineering
	protocol is called SNMPv1 and described in STD 15, RFC		configuration and management.
	1157 [RFC1157]. A second version of the SNMP message
	protocol, which is not an Internet standards track
	protocol, is called SNMPv2c and described in RFC 1901
	[RFC1901] and RFC 1906 [RFC1906]. The third version
	of the message protocol is called SNMPv3 and described
	in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574
	[RFC2574].
	- Protocol operations for accessing management		Comments should be made direct to the CCAMP mailing list at
	information. The first set of protocol operations and		ccamp@ops.ietf.org.
	associated PDU formats is described in STD 15, RFC
	1157 [RFC1157]. A second set of protocol operations
	and associated PDU formats is described in RFC 1905
	[RFC1905].
	- A set of fundamental applications described in RFC		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	2573 [RFC2573] and the view-based access control		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	mechanism described in RFC 2575 [RFC2575].		document are to be interpreted as described in RFC 2119, reference
			[RFC2119].
	A more detailed introduction to the current SNMP		1.1. Migration Strategy
	Management Framework can be found in RFC 2570 [RFC2570].
	Managed objects are accessed via a virtual information		This MIB extends the traffic engineering MIB defined for use with
	store, termed the Management Information Base or MIB.		MPLS [TEMIB]. It provides additions for support of GMPLS tunnels.
	Objects in the MIB are defined using the mechanisms		The companion document modeling and managing GMPLS based LSRs
	defined in the SMI.		[GMPLSLSRMIB] extends MPLS LSR MIB [LSRMIB] with the same intentions.
	This memo specifies a MIB module that is compliant to the		Textual conventions and OBJECT-IDENTIFIERS are defined in [TCMIB] and
	SMIv2. A MIB conforming to the SMIv1 can be produced		[GMPLSTCMIB].
	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
	Nadeau, et al. [Page 5 ]		2. Terminology
	textual descriptions in SMIv1 during the translation
	process.
	However, this loss of machine readable information is not		This document uses terminology from the MPLS architecture document
	considered to change the semantics of the MIB.		[RFC3031], from the GMPLS architecture document [GMPLSArch], and from
			the MPLS Label Switch Router MIB [LSRMIB]. Some frequently used terms
			are described next.
	5. Feature List		An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It
			consists of in-segment(s) and/or out-segment(s) at the egress/ingress
			LSRs, each segment being associated with one GMPLS enabled interface.
			These are also referred to as tunnel segments.
	The GMPLS traffic engineering MIB is designed to satisfy		Additionally, at an intermediate LSR, we model a connection as
	the following requirements and constraints.		consisting of one or more in-segments and/or one or more out-
			segments. The binding or interconnection between in-segments and out-
			segments in performed using a cross-connect.
	- The MIB extends the MPLS traffic engineering MIB		These segment and cross-connect objects are defined in the MPLS Label
	[TEMIB] to provide support for GMPLS tunnels.		Switch Router MIB [LSRMIB], but see also the GMPLS Label Switch
			Router MIB [GMPLSLSRMIB] for the GMPLS-specific extensions to these
			objects.
	- The MIB supports configuration of point-to-point		3. The SNMP Management Framework
	unidirectional and bidirectional tunnels.
	- Tunnels need not be interfaces, but it is possible to		For a detailed overview of the documents that describe the current
	configure a tunnel as an interface.		Internet-Standard Management Framework, please refer to section 7 of
			RFC 3410 [RFC3410].
	- The MIB supports manually configured tunnels as well		Managed objects are accessed via a virtual information store, termed
	as those set up via a GMPLS signaling protocol.		the Management Information Base or MIB. MIB objects are generally
			accessed through the Simple Network Management Protocol (SNMP).
			Objects in the MIB are defined using the mechanisms defined in the
			Structure of Management Information (SMI). This memo specifies a
			MIB module that is compliant to the SMIv2, which is described in STD
			58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC
			2580 [RFC2580].
	- The MIB supports persistent as well as non-persistent		4. Outline
	tunnels.
	6. Outline		Support for GMPLS traffic-engineered tunnels requires the following
			configuration.
	Support for GMPLS traffic-engineered tunnels requires the		- Setting up tunnels with appropriate MPLS configuration parameters
	following configuration.		using [TEMIB].
			- Extending the tunnels with GMPLS configuration parameters.
			- Configuring tunnel loose and strict source routed hops.
	- Setting up tunnels with appropriate MPLS configuration		These actions may need to be accompanied with corresponding actions
	parameters using [TEMIB].		using [LSRMIB] and [GMPLSLSRMIB] to establish and configure tunnel
			segments, if this is done manually. Also, the in-segment and out-
			segment performance tables, mplsInSegmentPerfTable and
			mplsOutSegmentPerfTable [LSRMIB], should be used to determine
			performance of the tunnels and tunnel segments although it should be
			noted that those tables may not be appropriate for measuring
			performance on some times of GMPLS links.
	- Extending the tunnels with GMPLS configuration		4.1. Summary of GMPLS Traffic Engineering MIB Module
	parameters.
	- Configuring tunnel loose and strict source routed		The MIB objects for performing the actions listed above that cannot
	hops.		be performed solely using the MIB objects defined in [TEMIB] consist
			of the following tables.
	These actions may need to be accompanied with		- Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific
	corresponding actions using [LSRMIB] and [GMPLSLSRMIB] to		tunnel configuration parameters.
	establish and configure tunnel segments, if this is done		- Tunnel specified, actual, and computed hop tables
	manually. Also, the in-segment and out-segment		(gmplsTunnelHopTable, gmplsTunnelARHopTable, and
	performance tables, mplsInSegmentPerfTable and		gmplsTunnelCHopTable) for providing additional configuration of
	mplsOutSegmentPerfTable [LSRMIB], should be used to		strict and loose source routed tunnel hops.
	determine performance of the tunnels and tunnel segments.		- Performance and error reporting tables (gmplsTunnelPerfTable and
			gmplsTunnelErrorTable).
	6.1. Summary of GMPLS Traffic Engineering MIB		These tables are described in the subsequent sections.
	Nadeau, et al. [Page 6 ]		5. Brief Description of GMPLS TE MIB Objects
	The MIB objects for performing these actions consist of
	the following tables.
	- Tunnel Table (gmplsTunnelTable) for providing GMPLS-		The objects described in this section support the functionality
	specific tunnel configuration parameters.		described in [GMPLSRSVPTE] and [GMPLSCRLDP] for GMPLS tunnels.
			The tables support both manually configured and signaled tunnels.
	- Tunnel specified, actual, and computed hop tables		5.1. gmplsTunnelTable
	(gmplsTunnelHopTable, gmplsTunnelARHopTable, and
	gmplsTunnelCHopTable) for providing additional
	configuration of strict and loose source routed tunnel
	hops.
	- Performance and error reporting tables		The gmplsTunnelTable extends the MPLS traffic engineering MIB to
	(gmplsTunnelPerfTable and gmplsTunnelErrorTable).		allow GMPLS tunnels to be created between an LSR and a remote
			endpoint, and existing GMPLS tunnels to be reconfigured or removed.
	These tables are described in the subsequent sections.		Note that we only support point-to-point tunnel segments, although
			multi-point-to-point and point-to-multi-point connections are
			supported by an LSR acting as a cross-connect.
	7. Brief Description of MIB Objects		Each tunnel can thus have one out-segment originating at an LSR
			and/or one in-segment terminating at that LSR.
	The objects described in this section support the		5.2. gmplsTunnelHopTable
	functionality described in [GMPLSRSVPTE] and [GMPLSCRLDP]
	for GMPLS tunnels.
	The tables support both manually configured and signaled		The gmplsTunnelHopTable is used to indicate additional parameters for
	tunnels.		the hops, strict or loose, of a GMPLS tunnel defined in
			gmplsTunnelTable, when it is established using signaling. Multiple
			tunnels may share the same hops by pointing to the same entry in this
			table.
	7.1. gmplsTunnelTable		5.3. gmplsTunnelARHopTable
	The gmplsTunnelTable extends the MPLS traffic engineering		The gmplsTunnelARHopTable is used to indicate the actual hops
	MIB to allow GMPLS tunnels to be created between an LSR		traversed by a tunnel as reported by the signaling protocol after the
	and a remote endpoint, and existing GMPLS tunnels to be		tunnel is setup. The support of this table is optional since not all
	reconfigured or removed. Note that we only support point-		GMPLS signaling protocols support this feature.
	to-point tunnel segments, although multi-point-to-point
	and point-to-multi-point connections are supported by an
	LSR acting as a cross-connect.
	Each tunnel can thus have one out-segment originating at		5.4. gmplsTunnelCHoptable
	an LSR and/or one in-segment terminating at that LSR.
	7.2. gmplsTunnelHopTable		The gmplsTunnelCHopTable lists the actual hops computed by a
			constraint-based routing algorithm based on the gmplsTunnelHopTable.
			The support of this table is optional since not all implementations
			support computation of hop list using a constraint-based routing
			protocol.
	The gmplsTunnelHopTable is used to indicate additional		5.5. gmplsTunnelErrorTable
	parameters for the hops, strict or loose, of a GMPLS
	tunnel defined in gmplsTunnelTable, when it is
	established using signaling. Multiple tunnels may share
	the same hops by pointing to the same entry in this
	table.
	7.3. gmplsTunnelARHopTable		The gmplsTunnelErrorTable provides access to information about the
			last error that occurred on each tunnel known about by the MIB. It
			indicates the nature of the error, when and how it was reported and
			can give recovery advice through a display string.
	Nadeau, et al. [Page 7 ]		5.6. gmplsTunnelPerfTable
	The gmplsTunnelARHopTable is used to indicate the actual
	hops traversed by a tunnel as reported by the signaling
	protocol after the tunnel is setup. The support of this
	table is optional since not all GMPLS signaling protocols
	support this feature.
	7.4. gmplsTunnelCHoptable		gmplsTunnelPerfTable provides additional counters to measure the
			performance of GMPLS tunnels in which packets are visible. It
			supplements the counters in mplsTunnelPerfTable and augments
			gmplsTunnelTable.
	The gmplsTunnelCHopTable lists the actual hops computed		Note that not all counters may be appropriate or available for some
	by a constraint-based routing algorithm based on the		types of tunnel.
	gmplsTunnelHopTable.
	The support of this table is optional since not all		6. Cross-referencing to the mplsLabelTable
	implementations support computation of hop list using a
	constraint-based routing protocol.
	7.5. gmplsTunnelErrorTable		The gmplsLabelTable is found in a MIB module in [GMPLSLSRMIB] and
			provides a way to model labels in a GMPLS system where labels might
			not be simple 32 bit integers.
	The gmplsTunnelErrorTable provides access to information		The hop tables in this document (gmplsHopTable, gmplsCHopTable and
	about the last error that occurred on each tunnel known		gmplsARHopTable) use arbitrary indexes to point to entries in the
	about by the MIB. It indicates the nature of the error,		mplsLabelTable to indicate specific label values.
	when and how it was reported and can give recovery advice
	through a display string.
	7.6. gmplsTunnelPerfTable		Since the primary indexes into gmplsLabelTable are the interface
			index and a simple 32 bit integer (gmplsLabelIndex), in systems where
			the nature of a label is well-known, and where the label can safely
			be encoded as a 32 bit integer (for example a conventional MPLS
			system), the gmplsLabelTable does not need to be supported in the
			code implementation and the index pointers to the gmplsLabelTable
			(gmplsTunnelHopExplicitLabel, gmplsTunnelHopExplicitReverseLabel,
			gmplsTunnelCHopExplicitLabel, gmplsTunnelCHopExplicitReverseLabel,
			gmplsTunnelARHopExplicitLabel, gmplsTunnelARHopExplicitReverseLabel)
			may be replaced with the direct label values.
	gmplsTunnelPerfTable provides additional counters to		This provides both a good way to support legacy systems that
	measure the performance of GMPLS tunnels in which packets		implement the previous version of this MIB [TEMIB], and a significant
	are visible. It supplements the counters in		simplification in GMPLS systems that are limited to a single, simple
	mplsTunnelPerfTable and augments gmplsTunnelTable.		label type.
	Note that not all counters may be appropriate or		Note that gmplsLabelTable supports concatenated labels through the
	available for some types of tunnel.		use of a label sub-index (gmplsLabelSubindex).
	8. Example of GMPLS Tunnel Setup		7. Example of GMPLS Tunnel Setup
	This section contains an example of which MIB objects		This section contains an example of which MIB objects should be
	should be modified to create a GMPLS tunnel. This		modified to create a GMPLS tunnel. This example shows a best effort,
	example shows a best effort, loosely routed,		loosely routed, bidirectional traffic engineered tunnel, which spans
	bidirectional traffic engineered tunnel, which spans two		two hops of a simple network, uses Generalized Label requests with
	hops of a simple network, uses Generalized Label requests		Lambda encoding, has label recording and shared link layer
	with Lambda encoding, has label recording and shared link		protection. Note that these objects should be created on the "head-
	layer protection. Note that these objects should be		end" LSR.
	created on the "head-end" LSR.
	First in the mplsTunnelTable:		First in the mplsTunnelTable:
	{		{
	Nadeau, et al. [Page 8 ]
	mplsTunnelIndex = 1,		mplsTunnelIndex = 1,
	mplsTunnelInstance = 1,		mplsTunnelInstance = 1,
	mplsTunnelIngressLSRId = 123.123.125.1,		mplsTunnelIngressLSRId = 123.123.125.1,
	mplsTunnelEgressLSRId = 123.123.126.1,		mplsTunnelEgressLSRId = 123.123.126.1,
	mplsTunnelName = "My first tunnel",		mplsTunnelName = "My first tunnel",
	mplsTunnelDescr = "Here to there and back again",		mplsTunnelDescr = "Here to there and back again",
	mplsTunnelIsIf = true (1),		mplsTunnelIsIf = true (1),
	mplsTunnelXCPointer = mplsXCIndex.3.0.0.12,		mplsTunnelXCPointer = mplsXCIndex.3.0.0.12,
	mplsTunnelSignallingProto = none (1),		mplsTunnelSignallingProto = none (1),
	mplsTunnelSetupPrio = 0,		mplsTunnelSetupPrio = 0,
	skipping to change at page 10, line ?		skipping to change at page 6, line 52
	mplsTunnelLocalProtectInUse = false (0),		mplsTunnelLocalProtectInUse = false (0),
	mplsTunnelResourcePointer = mplsTunnelResourceIndex.6,		mplsTunnelResourcePointer = mplsTunnelResourceIndex.6,
	mplsTunnelInstancePriority = 1,		mplsTunnelInstancePriority = 1,
	mplsTunnelHopTableIndex = 1,		mplsTunnelHopTableIndex = 1,
	mplsTunnelPrimaryInstance = 0,		mplsTunnelPrimaryInstance = 0,
	mplsTunnelIncludeAnyAffinity = 0,		mplsTunnelIncludeAnyAffinity = 0,
	mplsTunnelIncludeAllAffinity = 0,		mplsTunnelIncludeAllAffinity = 0,
	mplsTunnelExcludeAnyAffinity = 0,		mplsTunnelExcludeAnyAffinity = 0,
	mplsTunnelPathInUse = 1,		mplsTunnelPathInUse = 1,
	mplsTunnelRole = head(1),		mplsTunnelRole = head(1),
	mplsTunnelRowStatus = createAndWait (5)		mplsTunnelRowStatus = createAndWait (5),
	}		}
			In gmplsTunnelTable(1,1,123.123.125.1,123.123.126.1):
	In gmplsTunnelTable(1,1,123.123.123.125.1,123.123.126.1):
	{		{
	gmplsTunnelIsUnnum = true (1),		gmplsTunnelIsUnnum = true (1),
	gmplsTunnelAttributes = labelRecordingRequired (1),		gmplsTunnelAttributes = labelRecordingRequired (1),
	gmplsTunnelLSPEncoding = tunnelLspLambda (8),		gmplsTunnelLSPEncoding = tunnelLspLambda (8),
	gmplsTunnelSwitchingType = lsc (150),		gmplsTunnelSwitchingType = lsc (150),
	gmplsTunnelLinkProtection = shared (2),		gmplsTunnelLinkProtection = shared (2),
	gmplsTunnelGPid = lambda (37),		gmplsTunnelGPid = lambda (37),
	gmplsTunnelDirection = bidirectional (1)		gmplsTunnelDirection = bidirectional (1)
	}		}
	Entries in the mplsTunnelResourceTable,		Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and
	mplsTunnelHopTable and gmplsTunnelHopTable are created		gmplsTunnelHopTable are created and activated at this time.
	and activated at this time.
	In mplsTunnelResourceTable:		In mplsTunnelResourceTable:
	{		{
	mplsTunnelResourceIndex = 6,		mplsTunnelResourceIndex = 6,
	mplsTunnelResourceMaxRate = 0,		mplsTunnelResourceMaxRate = 0,
	mplsTunnelResourceMeanRate = 0,		mplsTunnelResourceMeanRate = 0,
	mplsTunnelResourceMaxBurstSize = 0,		mplsTunnelResourceMaxBurstSize = 0,
	mplsTunnelResourceRowStatus = createAndGo (4)		mplsTunnelResourceRowStatus = createAndGo (4)
	}		}
	The next two instances of mplsTunnelHopEntry are used to		The next two instances of mplsTunnelHopEntry are used to denote the
	denote the hops this tunnel will take across the network.		hops this tunnel will take across the network.
	Nadeau, et al. [Page 9 ]		The following denotes the beginning of the network, or the first hop.
	The following denotes the beginning of the network, or		We have used the fictitious LSR identified by "123.123.125.1" as our
	the first hop. We have used the fictitious LSR identified		example head-end router.
	by "123.123.125.1" as our example head-end router.
	In mplsTunnelHopTable:		In mplsTunnelHopTable:
	{		{
	mplsTunnelHopListIndex = 1,		mplsTunnelHopListIndex = 1,
	mplsTunnelPathOptionIndex = 1,		mplsTunnelPathOptionIndex = 1,
	mplsTunnelHopIndex = 1,		mplsTunnelHopIndex = 1,
	mplsTunnelHopAddrType = ipV4 (1),		mplsTunnelHopAddrType = ipV4 (1),
	mplsTunnelHopIpv4Addr = 123.123.125.1,		mplsTunnelHopIpv4Addr = 123.123.125.1,
	mplsTunnelHopIpv4PrefixLen = 9,		mplsTunnelHopIpv4PrefixLen = 9,
	mplsTunnelHopType = strict (1),		mplsTunnelHopType = strict (1),
	mplsTunnelHopRowStatus = createAndGo (4)		mplsTunnelHopRowStatus = createAndGo (4),
	}		}
	The following denotes the end of the network, or the last		The following denotes the end of the network, or the last hop in our
	hop in our example. We have used the fictitious LSR		example. We have used the fictitious LSR identified by
	identified by "123.123.126.1" as our end router.		"123.123.126.1" as our end router.
	In mplsTunnelHopTable:		In mplsTunnelHopTable:
	{		{
	mplsTunnelHopListIndex = 1,		mplsTunnelHopListIndex = 1,
	mplsTunnelPathOptionIndex = 1,		mplsTunnelPathOptionIndex = 1,
	mplsTunnelHopIndex = 2,		mplsTunnelHopIndex = 2,
	mplsTunnelHopAddrType = ipV4 (1),		mplsTunnelHopAddrType = ipV4 (1),
	mplsTunnelHopIpv4Addr = 123.123.126.1,		mplsTunnelHopIpv4Addr = 123.123.126.1,
	mplsTunnelHopIpv4PrefixLen = 9,		mplsTunnelHopIpv4PrefixLen = 9,
	mplsTunnelHopType = loose (2)		mplsTunnelHopType = loose (2),
	}		}
			Now an associated entry in the gmplsTunnelHopTable is created to
	Now an associated entry in the gmplsTunnelHopTable is		provide additional GMPLS hop configuration indicating that the first
	created to provide additional GMPLS hop configuration		hop is an unnumbered link using explicit forward and reverse labels.
	indicating that the first hop is an unnumbered link using
	explicit forward and reverse labels.
	In gmplsTunnelHopTable(1,1,1):		In gmplsTunnelHopTable(1,1,1):
	{		{
	gmplsTunnelHopUnnumAddrType = unnumberedIpV4(2),		gmplsTunnelHopUnnumAddrType = unnumberedIpV4(2),
	gmplsTunnelHopLabelStatuses = forwardPresent(0)		gmplsTunnelHopLabelStatuses = forwardPresent(0)
	+reversePresent(1),		+reversePresent(1),
	gmplsTunnelHopExplicitLabel = mplsLabelIndex.2756132,		gmplsTunnelHopExplicitLabel = mplsLabelIndex.2756132,
	gmplsTunnelHopExplicitReverseLabel= mplsLabelIndex.65236213		gmplsTunnelHopExplicitReverseLabel= mplsLabelIndex.65236213
	}		}
	No gmplsTunnelHopEntry is created for the second hop as		No gmplsTunnelHopEntry is created for the second hop as it contains
	it contains no special GMPLS features.		no special GMPLS features.
	Finally the mplsTunnelEntry is activated:		Finally the mplsTunnelEntry is activated:
	In mplsTunnelTable(1,1,123.123.123.125.1,123.123.126.1)		In mplsTunnelTable(1,1,123.123.125.1,123.123.126.1)
	{		{
	mplsTunnelRowStatus = active(1)		mplsTunnelRowStatus = active(1)
	}		}
	9. Cross-referencing to the mplsLabelTable		8. GMPLS Traffic Engineering MIB Definitions
	The mplsLabelTable [LSRMIB] provides a way to model
	labels in an MPLS system. The gmplsLabelTable
	[GMPLSLSRMIB] provides extensions to the mplsLabelTable
	for use in a GMPLS system where labels might not be
	simple 32 bit integers.
	The hop tables in this document (gmplsHopTable,
	gmplsCHopTable and gmplsARHopTable) use arbitrary indexes
	to point to entries in the mplsLabelTable to indicate
	specific label values.
	Since the primary indexes into mplsLabelTabel are the
	interface index and a simple 32 bit integer
	(mplsLabelIndex), in systems where the nature of a label
	is well-known, and where the label can safely be encoded
	as a 32 bit integer (for example a conventional MPLS
	system), the mplsLabelTable does not need to be supported
	in the code implementation and the pointers to the
	mplsLabelTable (gmplsTunnelHopExplicitLabel,
	gmplsTunnelHopExplicitReverseLabel,
	gmplsTunnelCHopExplicitLabel,
	gmplsTunnelCHopExplicitReverseLabel,
	gmplsTunnelARHopExplicitLabel,
	gmplsTunnelARHopExplicitReverseLabel) may be replaced
	with the direct label values.
	This provides both a good way to support legacy systems
	that implement the previous version of this MIB [TEMIB],
	and a significant simplification in GMPLS systems that
	are limited to a single, simple label type.
	Note that mplsLabelTable supports concatenated labels
	through the use of a sub-label index (mplsSublabelIndex).
	10. GMPLS Traffic Engineering MIB Definitions
	GMPLS-TE-MIB DEFINITIONS ::= BEGIN		GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,		MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
	experimental, Integer32, Unsigned32, Counter32,		experimental, Integer32, Unsigned32, Counter32,
	Counter64, TimeTicks		Counter64, TimeTicks
	FROM SNMPv2-SMI		FROM SNMPv2-SMI
	MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP		MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
	FROM SNMPv2-CONF		FROM SNMPv2-CONF
	TEXTUAL-CONVENTION, TruthValue, TimeStamp		TEXTUAL-CONVENTION, TruthValue, TimeStamp
	FROM SNMPv2-TC		FROM SNMPv2-TC
	InterfaceIndexOrZero
	FROM IF-MIB
	MplsTunnelIndex, MplsTunnelInstanceIndex
	FROM MPLS-TC-MIB
	GmplsHopUnnumAddrTypes
	FROM GMPLS-TC-MIB
	InetAddressIPv4, InetAddressIPv6		InetAddressIPv4, InetAddressIPv6
	FROM INET-ADDRESS-MIB		FROM INET-ADDRESS-MIB
	;		;
	gmplsTeMIB MODULE-IDENTITY		gmplsTeStdMIB MODULE-IDENTITY
	LAST-UPDATED		LAST-UPDATED
	"200206240900Z" -- 24 June 2002 9:00:00 GMT		"200308190900Z " -- 19 August 2003 9:00:00 GMT"
	ORGANIZATION		ORGANIZATION
	"Common Control And Management Protocols (CCAMP)		"Common Control And Management Protocols (CCAMP)
	Working Group"		Working Group"
	CONTACT-INFO		CONTACT-INFO
	"Thomas D. Nadeau		"Thomas D. Nadeau
	Postal: Cisco Systems, Inc.		Cisco Systems, Inc.
	250 Apollo Drive
	Chelmsford, MA 01824
	Tel: +1-978-244-3051
	Email: tnadeau@cisco.com		Email: tnadeau@cisco.com
	Cheenu Srinivasan		Cheenu Srinivasan
	Postal: Parama Networks, Inc.		Bloomberg L.P.
	1030 Broad Street		Email: cheenu@bloomberg.net
	Shrewsbury, NJ 07702
	Tel: +1-732-544-9120 x731
	Email: cheenu@paramanet.com
	Adrian Farrel		Adrian Farrel
	Postal: Movaz Networks, Inc.		Old Dog Consulting
	7926 Jones Branch Drive		Email: adrian@olddog.co.uk
	McLean, VA 22102
	Tel: +1-703-847-1867
	Email: afarrel@movaz.com
	Edward Harrison		Ed Harrison
	Postal: Data Connection Ltd.		Data Connection Ltd.
	100 Church Street		Email: ed.harrison@dataconnection.com
	Enfield, Middlesex
	EN2 6BQ, United Kingdom
	Tel: +44-20-8366-1177
	Email: eph@dataconnection.com
	Tim Hall		Tim Hall
	Postal: Data Connection Ltd.		Data Connection Ltd.
	100 Church Street		Email: timhall@dataconnection.com
	Enfield, Middlesex
	EN2 6BQ, United Kingdom		Comments about this document should be emailed direct to the
	Tel: +44-20-8366-1177		CCAMP working group mailing list at ccamp@ops.ietf.org"
	Email: timhall@dataconnection.com"
	DESCRIPTION		DESCRIPTION
	"This MIB module contains managed object		"This MIB module contains managed object definitions
	definitions for GMPLS Traffic Engineering		for GMPLS Traffic Engineering (TE).
	(TE)."
	-- Revision history.		Copyright (C) The Internet Society (2003). This
			version of this MIB module is part of RFCXXX; see
			the RFC itself for full legal notices."
			-- Revision history.
	REVISION		REVISION
	"200206240900Z" -- 24 June 2002 9:00:00 GMT		"200308190900Z" -- 19 August 2003 09:00:00 GMT
	DESCRIPTION		DESCRIPTION
	"First revision draft version."		"Initial revision, published as part of RFC XXXX."
	-- Above revision history to be replaced as below		::= { gmplsStdMIB xx }
	-- REVISION "yyyymmddhhmmZ"
	-- DESCRIPTION "Initial version, published as RFC xxxx"
	-- xxxx to be assigned by RFC Editor
	::= { experimental XXX } -- To Be Assigned by IANA
	-- Top level components of this MIB.		-- Top level components of this MIB.
			-- Notifications
			-- no notifications are currently defined.
			gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 }
	-- tables, scalars		-- tables, scalars
	gmplsTeScalars OBJECT IDENTIFIER		gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeMIB 1 }
	::= { gmplsTeMIB 1 }		gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeMIB 2 }
	gmplsTeObjects OBJECT IDENTIFIER
	::= { gmplsTeMIB 2 }
	-- conformance		-- conformance
	gmplsTeConformance OBJECT IDENTIFIER		gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeMIB 3 }
	::= { gmplsTeMIB 3 }
	-- GMPLS Tunnel scalars.		-- GMPLS Tunnel scalars.
	gmplsTunnelsConfigured OBJECT-TYPE		gmplsTunnelsConfigured OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of GMPLS tunnels configured on		"The number of GMPLS tunnels configured on this
	this device. A tunnel is considered		device. A GMPLS tunnel is considered configured if
	configured if an entry for the tunnel		an entry for the tunnel exists in the
	exists in the gmplsTunnelTable and the		gmplsTunnelTable and the associated
	associated mplsTunnelRowStatusis		mplsTunnelRowStatusis active(1)."
	active(1)."
	::= { gmplsTeScalars 1 }		::= { gmplsTeScalars 1 }
	gmplsTunnelActive OBJECT-TYPE		gmplsTunnelActive OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The number of GMPLS tunnels active on this		"The number of GMPLS tunnels active on this device.
	device. A tunnel is considered active if		A GMPLS tunnel is considered active if there is an
	there is an entry in the gmplsTunnelTable		entry in the gmplsTunnelTable and the associated
	and the associated mplsTunnelOperStatus		mplsTunnelOperStatus for the tunnel is up(1)."
	for the tunnel is up(1)."
	::= { gmplsTeScalars 2 }		::= { gmplsTeScalars 2 }
	-- End of GMPLS Tunnel scalars.		-- End of GMPLS Tunnel scalars.
	-- GMPLS tunnel table.		-- GMPLS tunnel table.
	gmplsTunnelTable OBJECT-TYPE		gmplsTunnelTable OBJECT-TYPE
	SYNTAX SEQUENCE OF GmplsTunnelEntry		SYNTAX SEQUENCE OF GmplsTunnelEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The gmplsTunnelTable 'extends' the		"The gmplsTunnelTable 'extends' the mplsTunnelTable.
	mplsTunnelTable. It allows GMPLS tunnels		It allows GMPLS tunnels to be created between an LSR
	to be created between an LSR and a remote		and a remote endpoint, and existing tunnels to be
	endpoint, and existing tunnels to be
	reconfigured or removed.		reconfigured or removed.
	Note that only point-to-point tunnel		Note that only point-to-point tunnel segments are
	segments are supported, although multi-		supported, although multi-point-to-point and point-
	point-to-point and point-to-multi-point		to-multi-point connections are supported by an LSR
	connections are supported by an LSR acting		acting as a cross-connect. Each tunnel can thus have
	as a cross-connect. Each tunnel can thus		one out-segment originating at this LSR and/or one
	have one out-segment originating at this		in-segment terminating at this LSR."
	LSR and/or one in-segment terminating at
	this LSR."
	::= { gmplsTeObjects 1 }		::= { gmplsTeObjects 1 }
	gmplsTunnelEntry OBJECT-TYPE		gmplsTunnelEntry OBJECT-TYPE
	SYNTAX GmplsTunnelEntry		SYNTAX GmplsTunnelEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table in association with		"An entry in this table in association with the
	the corresponding entry in the		corresponding entry in the mplsTunnelTable
	mplsTunnelTable represents a GMPLS tunnel.		represents a GMPLS tunnel.
	An entry can be created by a network		An entry can be created by a network administrator
	administrator or by an SNMP agent as		or by an SNMP agent as instructed by a signaling
	instructed by a signaling protocol."		protocol."
	REFERENCE
	"1. RFC 1700 - Assigned Numbers, Reynolds,
	J. and J. Postel, Oct. 1994"
	INDEX {		INDEX {
	mplsTunnelIndex,		mplsTunnelIndex,
	mplsTunnelInstance,		mplsTunnelInstance,
	mplsTunnelIngressLSRId,		mplsTunnelIngressLSRId,
	mplsTunnelEgressLSRId		mplsTunnelEgressLSRId
	}		}
	::= { gmplsTunnelTable 1 }		::= { gmplsTunnelTable 1 }
	GmplsTunnelEntry ::= SEQUENCE {		GmplsTunnelEntry ::= SEQUENCE {
	gmplsTunnelUnnumIf TruthValue,		gmplsTunnelUnnumIf TruthValue,
	gmplsTunnelAttributes BITS,		gmplsTunnelAttributes BITS,
	gmplsTunnelLSPEncoding INTEGER,		gmplsTunnelLSPEncoding INTEGER,
	gmplsTunnelSwitchingType INTEGER,		gmplsTunnelSwitchingType INTEGER,
	gmplsTunnelLinkProtection BITS,		gmplsTunnelLinkProtection BITS,
	gmplsTunnelGPid Unsigned32,		gmplsTunnelGPid Unsigned32,
	gmplsTunnelSecondary TruthValue,		gmplsTunnelSecondary TruthValue,
	gmplsTunnelDirection INTEGER,		gmplsTunnelDirection INTEGER,
	gmplsTunnelPathComp INTEGER		gmplsTunnelPathComp INTEGER
	skipping to change at page 15, line 19		skipping to change at page 11, line 21
	gmplsTunnelSecondary TruthValue,		gmplsTunnelSecondary TruthValue,
	gmplsTunnelDirection INTEGER,		gmplsTunnelDirection INTEGER,
	gmplsTunnelPathComp INTEGER		gmplsTunnelPathComp INTEGER
	}		}
	gmplsTunnelUnnumIf OBJECT-TYPE		gmplsTunnelUnnumIf 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 tunnel		"Denotes whether or not this tunnel corresponds to an
	corresponds to an unnumbered interface		unnumbered interface represented in the interfaces
	represented in the interfaces group table.		group table.
	This object is only used if mplsTunnelIsIf		This object is only used if mplsTunnelIsIf is set to
	is set to true.		'true'.
	If both this object and the mplsTunnelIsIf		If both this object and the mplsTunnelIsIf object
	object are set to true, the originating LSR		are set to 'true', the originating LSR adds an
	adds an LSP_TUNNEL_INTERFACE_ID object to		LSP_TUNNEL_INTERFACE_ID object to the outgoing Path
	the outgoing Path message. This object		message.
	contains information that is only used by		This object contains information that is only used
	the terminating LSR."		by the terminating LSR."
	REFERENCE		REFERENCE
	"draft-ietf-mpls-crldp-unnum-06.txt -		"1. draft-ietf-mpls-crldp-unnum-06.txt - Signalling
	Signalling Unnumbered Links in CR-LDP,		Unnumbered Links in CR-LDP, Kompella, K., Rekhter, Y.
	Kompella, K., Rekhter, Y. and Kullberg, A.,		and Kullberg, A., June 2002.
	June 2002.		2. Signalling Unnumbered Links in RSVP-TE, Kompella, K.
	draft-ietf-mpls-rsvp-unnum-06.txt -		and Rekhter, Y., RFC 3477, January 2003."
	Signalling Unnumbered Links in RSVP-TE,
	Kompella, K., and Rekhter, Y., June 2002."
	DEFVAL { false }		DEFVAL { false }
	::= { gmplsTunnelEntry 1 }		::= { gmplsTunnelEntry 1 }
	gmplsTunnelAttributes OBJECT-TYPE		gmplsTunnelAttributes OBJECT-TYPE
	SYNTAX BITS {		SYNTAX BITS {
	localProtectionDesired (0),		labelRecordingDesired (0)
	labelRecordingDesired (1),
	seStyleDesired (2)
	}		}
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This bitmask indicates optional parameters		"This bitmask indicates optional parameters for this
	for this tunnel. Some of these bits map		tunnel. These bits should be taken in addition to
	direct to signaled values (for example		those defined in mplsTunnelSessionAttributes in
	SESSION_ATTRIBUTES flags in RSVP-TE).		order to determine the full set of options to be
	Others describe qualities of the tunnel.		signaled (for example SESSION_ATTRIBUTES flags in
			RSVP-TE).
	The following describes these bitfields:		The following describes these bitfields:
	localProtectionDesired
	This flag permits transit routers to use a
	local repair mechanism which may result in
	violation of the explicit route object.
	When a fault is detected on an adjacent
	downstream link or node, a transit router
	can reroute traffic for fast service
	restoration.
	labelRecordingDesired		labelRecordingDesired
	This flag indicates that label information		This flag indicates that label information should be
	should be included when doing a route		included when doing a route record. This bit is not
	record. This bit is not valid unless the		valid unless the recordRoute bit is set."
	recordRoute bit is set.
	seStyleDesired
	This flag indicates that the tunnel ingress
	node may choose to reroute this tunnel
	without tearing it down.
	When signaling uses RSVP, a tunnel egress
	node SHOULD use the SE Style when
	responding with a Resv message."
	REFERENCE		REFERENCE
	"1. RSVP-TE: Extensions to RSVP for LSP		"1. RSVP-TE: Extensions to RSVP for LSP Tunnels,
	Tunnels, Awduche et al, RFC 3209, December		Awduche et al, RFC 3209, December 2001."
	2001."
	DEFVAL { 0 }		DEFVAL { 0 }
	::= { gmplsTunnelEntry 2 }		::= { gmplsTunnelEntry 2 }
	gmplsTunnelLSPEncoding OBJECT-TYPE		gmplsTunnelLSPEncoding OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER (0..255)
			MAX-ACCESS read-create
			STATUS current
			DESCRIPTION
			"This object indicates the encoding of the LSP being
			requested.
			A value of zero indicates that GMPLS signaling is
			not in use. Some objects in this MIB module may be
			of use for MPLS signaling extensions that do not use
			GMPLS signaling. By setting this object to zero, an
			application may indicate that only those objects
			meaningful in MPLS should be examined.
			The values to use are currently defined in
			Generalized Multi-Protocol Label Switching (GMPLS)
			Signaling Functional Description, RFC 3471. Further
			values may be defined in future RFCs.
	tunnelLspPacket (1),		tunnelLspPacket (1),
	tunnelLspEthernet (2),		tunnelLspEthernet (2),
	tunnelLspAnsiEtsiPdh (3),		tunnelLspAnsiEtsiPdh (3),
			-- the value 4 is deprecated
	tunnelLspSdhSonet (5),		tunnelLspSdhSonet (5),
			-- the value 6 is deprecated
	tunnelLspDigitalWrapper (7),		tunnelLspDigitalWrapper (7),
	tunnelLspLambda (8),		tunnelLspLambda (8),
	tunnelLspFiber (9),		tunnelLspFiber (9),
	tunnelLspFiberChannel (11)		-- the value 10 is deprecated
			tunnelLspFiberChannel (11)"
	}		REFERENCE
	MAX-ACCESS read-create		"1. Berger, L., et al., Generalized Multi-Protocol
	STATUS current		Label Switching (GMPLS) Signaling Functional
	DESCRIPTION		Description, RFC 3471, January 2003."
	"This object indicates the encoding of the		DEFVAL { 0 }
	LSP being requested.
	Ed Note: Should these be assigned and
	maintained by IANA?"
	::= { gmplsTunnelEntry 3 }		::= { gmplsTunnelEntry 3 }
	gmplsTunnelSwitchingType OBJECT-TYPE		gmplsTunnelSwitchingType OBJECT-TYPE
	SYNTAX INTEGER (0..2147483647)		SYNTAX INTEGER (0..255)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates the type of switching that should		"Indicates the type of switching that should be
	be performed on a particular link. This		performed on a particular link. This field is needed
	field is needed for links that advertise		for links that advertise more than one type of
	more than one type of switching capability.		switching capability. Values of this object are as
	Values of this field are as the Switching		the Switching Capability field defined in Internet
	Capability field defined in [GMPLS-OSPF]		Draft OSPF Extensions in Support of Generalized
	Ed Note: Should these values be assigned and		MPLS.
	maintained by IANA or imported from another
	MIB?
	Currently the following values are valid:
			Further values may be defined in future RFCs.
	unknown (0),		unknown (0),
	psc1 (1),		psc1 (1),
	psc2 (2),		psc2 (2),
	psc3 (3),		psc3 (3),
	psc4 (4),		psc4 (4),
	l2sc (51),		l2sc (51),
	tdm (100),		tdm (100),
	lsc (150),		lsc (150),
	fsc (200)"		fsc (200)
			This object is only meaningful if
			gmplsTunnelLSPEncoding is not set to 0."
			REFERENCE
			"1. Kompella, K., et al., OSPF Extensions in Support
			of Generalized MPLS, draft-ietf-ccamp-ospf-gmpls-
			extensions-07.txt, May 2002, work in progress.
			2. Berger, L., et al., Generalized Multi-Protocol
			Label Switching (GMPLS) Signaling Functional
			Description, RFC 3471, January 2003."
			DEFVAL { unknown }
	::= { gmplsTunnelEntry 4 }		::= { gmplsTunnelEntry 4 }
	gmplsTunnelLinkProtection OBJECT-TYPE		gmplsTunnelLinkProtection OBJECT-TYPE
	SYNTAX BITS {		SYNTAX BITS {
	extraTraffic(1),		extraTraffic(1),
	unprotected(2),		unprotected(2),
	shared (3),		shared (3),
	dedicatedOneToOne (4),		dedicatedOneToOne (4),
	dedicatedOnePlusOne(5),		dedicatedOnePlusOne(5),
	enhanced(6)		enhanced(6)
	}		}
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This bitmask indicates the level of link		"This bitmask indicates the level of link protection
	protection required. A value of zero (no		required. A value of zero (no bits set) indicates
	bits set) indicates that any protection may		that any protection may be used.
	be used.
	This object is only used if
	gmplsTunnelLSPEncoding is not set to 0.
	The following describes these bitfields:		The following describes these bitfields:
	extraTraffic		extraTraffic
	Indicates that the LSP should use links		Indicates that the LSP should use links that are
	that are protecting other (primary)		protecting other (primary) traffic. Such LSPs may
	traffic. Such LSPs may be preempted when		be preempted when the links carrying the (primary)
	the links carrying the (primary) traffic		traffic being protected fail.
	being protected fail.
	unprotected		unprotected
	Indicates that the LSP should not use any		Indicates that the LSP should not use any link layer
	link layer protection.		protection.
	shared		shared
	Indicates that a shared link layer		Indicates that a shared link layer protection
	protection scheme, such as 1:N		scheme, such as 1:N protection, should be used to
	protection, should be used to support the		support the LSP.
	LSP.
	dedicatedOneToOne		dedicatedOneToOne
	Indicates that a dedicated link layer		Indicates that a dedicated link layer protection
	protection scheme, i.e., 1:1 protection,		scheme, i.e., 1:1 protection, should be used to
	should be used to support the LSP.		support the LSP.
	dedicatedOnePlusOne		dedicatedOnePlusOne
	Indicates that a dedicated link layer		Indicates that a dedicated link layer protection
	protection scheme, i.e., 1+1 protection,		scheme, i.e., 1+1 protection, should be used to
	should be used to support the LSP.		support the LSP.
	enhanced		enhanced
	Indicates that a protection scheme that is		Indicates that a protection scheme that is more
	more reliable than Dedicated 1+1 should be		reliable than Dedicated 1+1 should be used, e.g., 4
	used, e.g., 4 fiber BLSR/MS-SPRING."		fiber BLSR/MS-SPRING.
			This object is only meaningful if
			gmplsTunnelLSPEncoding is not set to 0."
			DEFVAL { 0 }
	::= { gmplsTunnelEntry 5 }		::= { gmplsTunnelEntry 5 }
	gmplsTunnelGPid OBJECT-TYPE		gmplsTunnelGPid OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX INTEGER (0..65535)
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object indicates the payload carried		"This object indicates the payload carried by the
	by the LSP. It is only required when GMPLS		LSP. It is only required when GMPLS will be used for
	will be used for this LSP.		this LSP.
	This object is only used if
	gmplsTunnelLSPEncoding is not set to 0.
	Ed note: Should IANA maintain these values?
	Is there a better way of doing this? Say,
	having an enum for these values, plus
	another bit mask for the ethertypes and a
	flag to tell which to use?
	Currently the following values are valid.		The values to use are currently defined in
			Generalized Multi-Protocol Label Switching (GMPLS)
			Signaling Functional Description, RFC 3471. Further
			values may be defined in future RFCs.
	unknown(0),		unknown(0),
	asynchE4(5),		asynchE4(5),
	asynchDS3T3(6),		asynchDS3T3(6),
	asynchE3(7),		asynchE3(7),
	bitsynchE3(8),		bitsynchE3(8),
	bytesynchE3(9),		bytesynchE3(9),
	asynchDS2T2(10),		asynchDS2T2(10),
	bitsynchDS2T2(11),		bitsynchDS2T2(11),
	asynchE1(13),		asynchE1(13),
	skipping to change at page 19, line 32		skipping to change at page 15, line 18
	sdhSonet(34),		sdhSonet(34),
	digitalwrapper(36),		digitalwrapper(36),
	lambda(37),		lambda(37),
	ansiEtsiPdh (38),		ansiEtsiPdh (38),
	lapsSdh (40),		lapsSdh (40),
	fddi (41),		fddi (41),
	dqdb (42),		dqdb (42),
	fiberChannel3 (43),		fiberChannel3 (43),
	hdlc (44),		hdlc (44),
	ethernetV2DixOnly (45),		ethernetV2DixOnly (45),
	ethernet802dot3Only (46)"		ethernet802dot3Only (46)
			This object is only meaningful if
			gmplsTunnelLSPEncoding is not set to 0."
			REFERENCE
			"1. Berger, L., et al., Generalized Multi-Protocol
			Label Switching (GMPLS) Signaling Functional
			Description, RFC 3471, January 2003."
			DEFVAL { unknown }
	::= { gmplsTunnelEntry 6 }		::= { gmplsTunnelEntry 6 }
	gmplsTunnelSecondary OBJECT-TYPE		gmplsTunnelSecondary OBJECT-TYPE
	SYNTAX TruthValue		SYNTAX TruthValue
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates that the requested LSP is a		"Indicates that the requested LSP is a secondary LSP.
	secondary LSP.
	This object is only used if		This object is only meaningful if
	gmplsTunnelLSPEncoding is not set to 0."		gmplsTunnelLSPEncoding is not set to 0."
	DEFVAL { false }		DEFVAL { false }
	::= { gmplsTunnelEntry 7 }		::= { gmplsTunnelEntry 7 }
	gmplsTunnelDirection OBJECT-TYPE		gmplsTunnelDirection OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	forward (0),		forward (0),
	bidirectional (1)		bidirectional (1)
	}		}
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Whether this tunnel carries forward data		"Whether this tunnel carries forward data (is
	(is unidirectional) or is bidirectional.		unidirectional) or is bidirectional.
	By default, tunnels are unidirectional."		Values of this object other than 'forward' are
			meaningful only if gmplsTunnelLSPEncoding is not set
			to 0."
	DEFVAL { forward }		DEFVAL { forward }
	::= { gmplsTunnelEntry 8 }		::= { gmplsTunnelEntry 8 }
	gmplsTunnelPathComp OBJECT-TYPE		gmplsTunnelPathComp OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	dynamicFull(1),-- CSPF fully computed		dynamicFull(1),-- CSPF fully computed
	explicit(2),-- fully specified path		explicit(2),-- fully specified path
	dynamicPartial(3) -- CSPF partially computed		dynamicPartial(3) -- CSPF partially computed
	}		}
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This value instructs the source node on how		"This value instructs the source node on how to
	to perform path computation on the explicit		perform path computation on the explicit route
	route specified by the associated entries		specified by the associated entries in the
	in the gmplsTunnelHopTable.		gmplsTunnelHopTable.
	dynamicFull		dynamicFull
	The user specifies at least the source and		The user specifies at least the source and
	destination of the path and expects that		destination of the path and expects that the CSPF
	the CSPF will calculate the remainder of		will calculate the remainder of the path.
	the path.
	explicit		explicit
	The user specifies the entire path for the		The user specifies the entire path for the tunnel to
	tunnel to take. This path may contain		take. This path may contain strict or loose hops.
	strict or loose hops. Evaluation of the		Evaluation of the explicit route will be performed
	explicit route will be performed hop by hop		hop by hop through the network.
	through the network.
	dynamicPartial		dynamicPartial
	The user specifies at least the source and		The user specifies at least the source and
	destination of the path and expects that		destination of the path and expects that the CSPF
	the CSPF will calculate the remainder of		will calculate the remainder of the path. The path
	the path. The path computed by CSPF is		computed by CSPF is allowed to be only partially
	allowed to be only partially computed		computed allowing the remainder of the path to be
	allowing the remainder of the path to be
	filled in across the network.		filled in across the network.
	This object deprecates		This object deprecates gmplsTunnelHopEntryPathComp."
	gmplsTunnelHopEntryPathComp."		DEFVAL { dynamicFull }
	DEFVAL { explicit }
	::= { gmplsTunnelEntry 9 }		::= { gmplsTunnelEntry 9 }
	-- End of gmplsTunnelTable		-- End of gmplsTunnelTable
	-- Begin gmplsTunnelHopTable		-- Begin gmplsTunnelHopTable
	gmplsTunnelHopTable OBJECT-TYPE		gmplsTunnelHopTable OBJECT-TYPE
	SYNTAX SEQUENCE OF GmplsTunnelHopEntry		SYNTAX SEQUENCE OF GmplsTunnelHopEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The gmplsTunnelHopTable 'extends' the		"The gmplsTunnelHopTable 'extends' the
	mplsTunnelHopTable. It is used to indicate		mplsTunnelHopTable. It is used to indicate the
	the explicit labels and unnumbered		explicit labels to be used in an explicit path for a
	interface hops to be used for a GMPLS		GMPLS tunnel defined in mplsTunnelTable and
	tunnel defined in mplsTunnelTable and		gmplsTunnelTable, when it is established using
	gmplsTunnelTable, when it is established		signaling. It does not insert new hops, but does
	using signaling. Each row in this table is		define new values for hops defined in
	indexed by mplsTunnelHopListIndex. Each		mplsTunnelHopTable.
	row also has a secondary index
	mplsTunnelHopIndex corresponding to the		Each row in this table is indexed by the same
	next hop that this row corresponds to. The		indexes as mplsTunnelHopTable. It is acceptable for
	first row in the table is the first hop		some rows in mplsTunnelHopTable to have
	after the origination point of the tunnel.		corresponding entries in this table and some to have
	In case we want to specify a particular		no corresponding entry in this table.
	interface on the originating LSR of an
	outgoing tunnel by which we want packets to		The storage type for an entry in this table is
	exit the LSR, we specify this as the first		inherited from mplsTunnelHopStorageType in the
	hop for this tunnel in		corresponding entry in mplsTunnelHopTable.
	gmplsTunnelHopTable."
			The row status of an entry in this table is
			controlled by mplsTunnelHopRowStatus in the
			corresponding entry in mplsTunnelHopTable. That is,
			it is not permitted to create a row in this table,
			nor to modify an existing row, when the
			corresponding mplsTunnelHopRowStatus has value
			active(1)."
	::= { gmplsTeObjects 2 }		::= { gmplsTeObjects 2 }
	gmplsTunnelHopEntry OBJECT-TYPE		gmplsTunnelHopEntry OBJECT-TYPE
	SYNTAX GmplsTunnelHopEntry		SYNTAX GmplsTunnelHopEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table represents a tunnel		"An entry in this table represents additions to a
	hop. An entry is created by a network		tunnel hop defined in mplsTunnelHopEntry. At an
	administrator for signaled an ERLSP to be		ingress to a tunnel an entry in this table is
	set up by a signaling protocol."		created by a network administrator for an ERLSP to
	INDEX { mplsTunnelHopListIndex,		be set up by a signaling protocol. At transit and
			egress nodes an entry in this table may be used to
			represent the explicit path instructions received
			using the signaling protocol."
			INDEX {
			mplsTunnelHopListIndex,
	mplsTunnelHopPathOptionIndex,		mplsTunnelHopPathOptionIndex,
	mplsTunnelHopIndex }		mplsTunnelHopIndex
			}
	::= { gmplsTunnelHopTable 1 }		::= { gmplsTunnelHopTable 1 }
	GmplsTunnelHopEntry ::= SEQUENCE {		GmplsTunnelHopEntry ::= SEQUENCE {
	gmplsTunnelHopUnnumAddrType GmplsHopUnnumAddrTypes,
	gmplsTunnelHopLabelStatuses BITS,		gmplsTunnelHopLabelStatuses BITS,
	gmplsTunnelHopExplicitLabel Unsigned32,		gmplsTunnelHopExplicitLabel Unsigned32,
	gmplsTunnelHopExplicitReverseLabel Unsigned32,		gmplsTunnelHopExplicitReverseLabel Unsigned32,
	gmplsTunnelHopUnnumberedInterface InterfaceIndexOrZero
	}		}
	gmplsTunnelHopUnnumAddrType OBJECT-TYPE
	SYNTAX GmplsHopUnnumAddrTypes
	MAX-ACCESS read-create
	STATUS current
	DESCRIPTION
	"Indicates whether this tunnel hop entry
	uses an unnumbered link and, if so, whether
	it is an Ipv4 or Ipv6 hop. When this
	object is set to unnumberedIfIpV4(2) or
	unnumberedIfIpV6(3), it overrides the value
	of the associated mplsTunnelHopAddrType."
	DEFVAL { numbered }
	::= { gmplsTunnelHopEntry 1 }
	gmplsTunnelHopLabelStatuses OBJECT-TYPE		gmplsTunnelHopLabelStatuses OBJECT-TYPE
	SYNTAX BITS {		SYNTAX BITS {
	forwardPresent (0),		forwardPresent (0),
	reversePresent (1)		reversePresent (1)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This bitmask indicates the presence and		"This bitmask indicates the presence of labels
	status of labels indicated by the		indicated by the gmplsTunnelHopExplicitLabel and
	gmplsTunnelHopExplicitLabel and
	gmplsTunnelHopExplicitReverseLabel objects.		gmplsTunnelHopExplicitReverseLabel objects.
	For the Present bits, a set bit indicates
	that a label is present for this hop in the		For the Present bits, a set bit indicates that a
	route."		label is present for this hop in the route. This
	::= { gmplsTunnelHopEntry 2 }		allows zero to be a valid label value."
			::= { gmplsTunnelHopEntry 1 }
	gmplsTunnelHopExplicitLabel OBJECT-TYPE		gmplsTunnelHopExplicitLabel OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates the row entry in the		"Indicates the row entry in the gmplsLabelTable that
	mplsLabelTabel that defines the explicit		defines the explicit label to use in the explicit
	label to use in the explicit route as the		route as the forward path label at this point. This
	forward path label at this point. This		value only has meaning if the forwardPresent bit of
	value only has meaning if the
	forwardPresent bit of
	gmplsTunnelHopLabelStatuses is set.		gmplsTunnelHopLabelStatuses is set.
			Note that the other indexes in the gmplsLabelTable
			should be interpreted as follows:
			- The gmplsLabelInterface should be zero because
			this label is not tied to any specific interface
			on this LSR
			- The gmplsLabelSubindex is used to represent label
			concatenations. The first (or only) component
			label SHOULD have gmplsLabelSubindex set to zero.
	This variable is only valid for settings of		This variable is only valid for settings of
	gmplsTunnelHopAddrType which may be		mplsTunnelHopAddrType which may be associated with a
	associated with a forward path label.		forward path label.
	Note that in implementations where the		Note that in implementations where the label may be
	label may be encoded within a 32 bit		encoded within a 32 bit integer and where
	integer and where mplsLabelTable is not		gmplsLabelTable is not implemented, this object may
	implemented, this object may directly		directly contain the label value to use."
	contain the label value to use."		::= { gmplsTunnelHopEntry 2 }
	::= { gmplsTunnelHopEntry 3 }
	gmplsTunnelHopExplicitReverseLabel OBJECT-TYPE		gmplsTunnelHopExplicitReverseLabel OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates the row entry in the		"Indicates the row entry in the gmplsLabelTable that
	mplsLabelTabel that defines the explicit		defines the explicit label to use in the explicit
	label to use in the explicit route as the		route as the reverse path label at this point. This
	reverse path label at this point. This		value only has meaning if the reversePresent bit of
	value only has meaning if the
	reversePresent bit of
	gmplsTunnelHopLabelStatuses is set.		gmplsTunnelHopLabelStatuses is set.
	This variable is only valid for settings of		The same rules and notes apply as set out for
	gmplsTunnelHopAddrType which may be		gmplsTunnelHopExplicitLabel."
	associated with a reverse path label.		::= { gmplsTunnelHopEntry 3 }
	Note that in implementations where the
	label may be encoded within a 32 bit
	integer and where mplsLabelTable is not
	implemented, this object may directly
	contain the label value to use."
	::= { gmplsTunnelHopEntry 4 }
	gmplsTunnelHopUnnumberedInterface OBJECT-TYPE
	SYNTAX InterfaceIndexOrZero
	MAX-ACCESS read-create
	STATUS current
	DESCRIPTION
	"Indicates the interface index of the
	unnumbered interface to use when setting up
	the LSP. Only has value when
	gmplsTunnelHopUnnumAddrType is set to
	unnumberedIfIpV4(2) or unnumberedIfIpV6(3)
	in which case the corresponding
	mplsTunnelHopIpv4Addr or
	mplsTunnelHopIpv6Addr variable must contain
	an LSR id."
	::= { gmplsTunnelHopEntry 5 }
	-- End of gmplsTunnelHopTable		-- End of gmplsTunnelHopTable
	-- Tunnel Actual Route Hop table.		-- Tunnel Actual Route Hop table.
	gmplsTunnelARHopTable OBJECT-TYPE		gmplsTunnelARHopTable OBJECT-TYPE
	SYNTAX SEQUENCE OF GmplsTunnelARHopEntry		SYNTAX SEQUENCE OF GmplsTunnelARHopEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The gmplsTunnelARHopTable 'extends' the		"The gmplsTunnelARHopTable 'extends' the
	mplsTunnelARHopTable. It is used to		mplsTunnelARHopTable. It is used to indicate the
	indicate the unnumbered hops, strict or		labels currently in use for a GMPLS tunnel defined
	loose, for a GMPLS tunnel defined in		in mplsTunnelTable and gmplsTunnelTable, as reported
	mplsTunnelTable and gmplsTunnelTable, as		by the signaling protocol. It does not insert new
	reported by the signaling protocol, for the		hops, but does define new values for hops defined in
	outgoing direction of the tunnel. Each row		mplsTunnelARHopTable.
	in this table is indexed by
	mplsTunnelARHopListIndex. Each row also
	has a secondary index mplsTunnelARHopIndex,
	corresponding to the next hop that this row
	corresponds to. The first row in the table
	is the first hop after the origination
	point of the tunnel. In case we want to
	specify a particular interface on the
	originating LSR of an outgoing tunnel by
	which we want packets to exit the LSR, we
	specify this as the first hop for this
	tunnel in gmplsTunnelARHopTable.
	Please note that since the information		Each row in this table is indexed by the same
	necessary to build entries within this		indexes as mplsTunnelARHopTable. It is acceptable
	table is not provided by some signaling		for some rows in mplsTunnelARHopTable to have
	protocols, implementation of this table is		corresponding entries in this table and some to have
	optional. Furthermore, since the		no corresponding entry in this table.
	information in this table is actually
	provided by the signaling protocol after		Note that since the information necessary to build
	the path has been set-up, the entries in		entries within this table is not provided by some
	this table are provided only for		signaling protocols and might not be returned in all
	observation, and hence, all variables in		cases of other signaling protocols, implementation
	this table are accessible exclusively as		of this table and mplsTunnelARHopTable is optional.
	read-only."		Furthermore, since the information in this table is
			actually provided by the signaling protocol after
			the path has been set-up, the entries in this table
			are provided only for observation, and hence, all
			variables in this table are accessible exclusively
			as read-only."
	::= { gmplsTeObjects 3 }		::= { gmplsTeObjects 3 }
	gmplsTunnelARHopEntry OBJECT-TYPE		gmplsTunnelARHopEntry OBJECT-TYPE
	SYNTAX GmplsTunnelARHopEntry		SYNTAX MplsTunnelARHopEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table represents		"An entry in this table represents additions to a
	additional information about a GMPLS tunnel		tunnel hop visible in mplsTunnelARHopEntry. An entry
	hop. An entry is created by the signaling		is created by the signaling protocol for a signaled
	protocol for a signaled ERLSP set up by the		ERLSP set up by the signaling protocol.
	signaling protocol."
	INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex }		At any node on the LSP (ingress, transit or egress)
			Thus at this table and mplsTunnelARHopTable (if the
			tables are supported and if the signaling protocol
			is recording actual route information) contains the
			actual route of the whole tunnel. If the signaling
			protocol is not recording the actual route, this
			table MAY report the information from the
			gmplsTunnelHopTable or the gmplsTunnelCHopTable.
			Note that the recording of actual labels is distinct
			from the recording of the actual route in some
			signaling protocols. This feature is enabled using
			the gmplsTunnelAttributes object."
			INDEX {
			mplsTunnelARHopListIndex,
			mplsTunnelARHopIndex
			}
	::= { gmplsTunnelARHopTable 1 }		::= { gmplsTunnelARHopTable 1 }
	GmplsTunnelARHopEntry ::= SEQUENCE {		GmplsTunnelARHopEntry ::= SEQUENCE {
	gmplsTunnelARHopUnnumAddrType GmplsHopUnnumAddrTypes,
	gmplsTunnelARHopLabelStatuses BITS,		gmplsTunnelARHopLabelStatuses BITS,
	gmplsTunnelARHopExplicitLabel Unsigned32,		gmplsTunnelARHopExplicitLabel Unsigned32,
	gmplsTunnelARHopExplicitReverseLabel Unsigned32,		gmplsTunnelARHopExplicitReverseLabel Unsigned32,
	gmplsTunnelARHopUnnumberedInterface InterfaceIndexOrZero,
	gmplsTunnelARHopProtection BITS		gmplsTunnelARHopProtection BITS
	}		}
	gmplsTunnelARHopUnnumAddrType OBJECT-TYPE
	SYNTAX GmplsHopUnnumAddrTypes
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"Denotes whether this tunnel hop uses
	numbered or unnumbered interfaces.
	If set to unnumberedIfIpV4(2) or
	unnumberedIfIpV6(3) the value overrides the
	value of the associated
	mplsTunnelARHopAddrType."
	DEFVAL { numbered }
	::= { gmplsTunnelARHopEntry 1 }
	gmplsTunnelARHopLabelStatuses OBJECT-TYPE		gmplsTunnelARHopLabelStatuses OBJECT-TYPE
	SYNTAX BITS {		SYNTAX BITS {
	forwardPresent (0),		forwardPresent (0),
	reversePresent (1),		reversePresent (1),
	forwardGlobal (2),		forwardGlobal (2),
	reverseGlobal (3)		reverseGlobal (3)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This bitmask indicates the presence and		"This bitmask indicates the presence and status of
	status of labels indicated by the		labels indicated by the
	gmplsTunnelARHopExplicitLabel and		gmplsTunnelARHopExplicitLabel and
	gmplsTunnelARHopExplicitReverseLabel		gmplsTunnelARHopExplicitReverseLabel objects.
	objects.		For the Present bits, a set bit indicates that a
	For the Present bits, a set bit indicates		label is present for this hop in the route.
	that a label is present for this hop in the		For the Global bits, a set bit indicates that the
	route.		label comes from the Global Label Space. A clear bit
	For the Global bits, a set bit indicates		indicates that this is a Per-Interface label. A
	that the label comes from the Global Label		Global bit only has meaning if the corresponding
	Space. A clear bit indicates that this is		Present bit is set."
	a Per-Interface label. A Global bit only		::= { gmplsTunnelARHopEntry 1 }
	has meaning if the corresponding Present
	bit is set."
	::= { gmplsTunnelARHopEntry 2 }
	gmplsTunnelARHopExplicitLabel OBJECT-TYPE		gmplsTunnelARHopExplicitLabel OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates the row entry in the		"Indicates the row entry in the gmplsLabelTable that
	mplsLabelTabel that defines the label used		defines the label in use as the forward path label
	in the path as forward path at this point.		on the path at this point.
	This value only has meaning if the		This value only has meaning if the forwardPresent
	forwardPresent bit of		bit of gmplsTunnelARHopLabelStatuses is set.
	gmplsTunnelARHopLabelStatuses is set.
	Note that in implementations where the		Note that the other indexes in the gmplsLabelTable
	label may be encoded within a 32 bit		should be interpreted as follows:
	integer and where mplsLabelTable is not		- The gmplsLabelInterface should be zero because
	implemented, this object may directly		this label is not tied to any specific interface
	contain the label value to use."		on this LSR
	::= { gmplsTunnelARHopEntry 3 }		- The gmplsLabelSubindex is used to represent label
			concatenations. The first (or only) component
			label SHOULD have gmplsLabelSubindex set to zero.
			This variable is only valid for settings of
			mplsTunnelARHopAddrType which may be associated with
			a forward path label.
			Note that in implementations where the label may be
			encoded within a 32 bit integer and where
			gmplsLabelTable is not implemented, this object may
			directly contain the label value to use."
			::= { gmplsTunnelARHopEntry 2 }
	gmplsTunnelARHopExplicitReverseLabel OBJECT-TYPE		gmplsTunnelARHopExplicitReverseLabel OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates the row entry in the		"Indicates the row entry in the gmplsLabelTable that
	mplsLabelTabel that defines the label used		defines the label used in the path as reverse path
	in the path as reverse path at this point.		at this point.
	This value only has meaning if the		This value only has meaning if the reversePresent
	reversePresent bit of		bit of gmplsTunnelARHopLabelStatuses is set.
	gmplsTunnelARHopLabelStatuses is set.		The same rules and notes apply as set out for
	Note that in implementations where the		gmplsTunnelARHopExplicitLabel."
	label may be encoded within a 32 bit		::= { gmplsTunnelARHopEntry 3 }
	integer and where mplsLabelTable is not
	implemented, this object may directly
	contain the label value to use."
	::= { gmplsTunnelARHopEntry 4 }
	gmplsTunnelARHopUnnumberedInterface OBJECT-TYPE
	SYNTAX InterfaceIndexOrZero
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"Indicates the interface index of the
	unnumbered interface used when setting up
	the LSP.
	Only has value when
	gmplsTunnelARHopUnnumAddrType is set to
	unnumberedIfIpV4(2) or unnumberedIfIpV6(3)
	in which case the corresponding
	gmplsTunnelARHopIpv4Addr or
	gmplsTunnelARHopIpv6Addr variable must
	contain an LSR id."
	::= { gmplsTunnelARHopEntry 5 }
	gmplsTunnelARHopProtection OBJECT-TYPE		gmplsTunnelARHopProtection OBJECT-TYPE
	SYNTAX BITS {		SYNTAX BITS {
	localAvailable (0),		localAvailable (0),
	localInUse (1)		localInUse (1)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Availability and usage of protection on the		"Availability and usage of protection on the reported
	reported link.		link.
	- localAvailable indicates that the link
	downstream of this node is protected via a		localAvailable
	local repair mechanism. This flag can only		Indicates that the link downstream of this node
	be set if the localProtectionDesired bit		is protected via a local repair mechanism.
	was set in gmplsTunnelAttributes for this		localInUse
	tunnel.		Indicates that a local repair mechanism is in
	- localInUse indicates that a local repair		use to maintain this tunnel (usually in the
	mechanism is in use to maintain this tunnel		face of an outage of the link it was previously
	(usually in the face of an outage of the		routed over)."
	link it was previously routed over)."		::= { gmplsTunnelARHopEntry 4 }
	::= { gmplsTunnelARHopEntry 6 }
	-- End of mplsTunnelARHopTable
			-- End of mplsTunnelARHopTable
	-- Tunnel Computed Hop table.		-- Tunnel Computed Hop table.
	gmplsTunnelCHopTable OBJECT-TYPE		gmplsTunnelCHopTable OBJECT-TYPE
	SYNTAX SEQUENCE OF GmplsTunnelCHopEntry		SYNTAX SEQUENCE OF GmplsTunnelCHopEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The gmplsTunnelCHopTable 'extends' the		"The gmplsTunnelCHopTable 'extends' the
	mplsTunnelCHopTable. It is used to		mplsTunnelCHopTable. It is used to indicate
	indicate additional information about the		additional information about the hops of a GMPLS
	hops of a GMPLS tunnel defined in		tunnel defined in mplsTunnelTable and
	mplsTunnelTable and gmplsTunnelTable, as		gmplsTunnelTable, as computed by a constraint-based
	computed by a constraint-based routing		routing protocol, based on the mplsTunnelHopTable
	protocol, based on the gmplsTunnelHopTable		and the gmplsTunnelHopTable.
	for the outgoing direction of the tunnel.
	Each row in this table is indexed by
	mplsTunnelCHopListIndex. Each row also has
	a secondary index mplsTunnelCHopIndex,
	corresponding to the next hop that this row
	corresponds to. The first row in the table
	is the first hop after the origination
	point of the tunnel. In case we want to
	specify a particular interface on the
	originating LSR of an outgoing tunnel by
	which we want packets to exit the LSR, we
	specify this as the first hop for this
	tunnel in gmplsTunnelCHopTable.
	Please note that since the information		Each row in this table is indexed by the same
	necessary to build entries within this		indexes as mplsTunnelCHopTable. It is acceptable for
	table may not be supported by some LSRs,		some rows in mplsTunnelCHopTable to have
	implementation of this table is optional.		corresponding entries in this table and some to have
	Furthermore, since the information in this		no corresponding entry in this table.
	table is actually provided by routing
	protocol after the path has been computed,		Please note that since the information necessary to
	the entries in this table are provided only		build entries within this table may not be supported
	for observation, and hence, all variables		by some LSRs, implementation of this table is
	in this table are accessible exclusively as		optional.
	read-only."
			Furthermore, since the information in this table is
			actually provided by a path computation component
			after the path has been computed, the entries in
			this table are provided only for observation, and
			hence, all objects in this table are accessible
			exclusively as read-only."
	::= { gmplsTeObjects 4 }		::= { gmplsTeObjects 4 }
	gmplsTunnelCHopEntry OBJECT-TYPE		gmplsTunnelCHopEntry OBJECT-TYPE
	SYNTAX GmplsTunnelCHopEntry		SYNTAX GmplsTunnelCHopEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table represents a tunnel		"An entry in this table represents additions to a
	hop. An entry in this table is created by		computed tunnel hop visible in mplsTunnelCHopEntry.
	a constraint-based routing protocol based		An entry is created by a path computation component
	on the hops specified in the corresponding		based on the hops specified in the corresponding
	mplsTunnelHopTable and		mplsTunnelHopTable and gmplsTunnelHopTable.
	gmplsTunnelHopTable."
	INDEX { mplsTunnelCHopListIndex, mplsTunnelCHopIndex }
	::= { gmplsTunnelCHopTable 1 }
			At a transit LSR this table (if the table is
			supported) MAY contain the path computed by path
			computation engine on (or on behalf of) the transit
			LSR."
			INDEX {
			mplsTunnelCHopListIndex,
			mplsTunnelCHopIndex
			}
			::= { gmplsTunnelCHopTable 1 }
	GmplsTunnelCHopEntry ::= SEQUENCE {		GmplsTunnelCHopEntry ::= SEQUENCE {
	gmplsTunnelCHopUnnumAddrType GmplsHopUnnumAddrTypes,
	gmplsTunnelCHopLabelStatuses BITS,		gmplsTunnelCHopLabelStatuses BITS,
	gmplsTunnelCHopExplicitLabel Unsigned32,		gmplsTunnelCHopExplicitLabel Unsigned32,
	gmplsTunnelCHopExplicitReverseLabel Unsigned32,		gmplsTunnelCHopExplicitReverseLabel Unsigned32,
	gmplsTunnelCHopUnnumberedInterface InterfaceIndexOrZero
	}		}
	gmplsTunnelCHopUnnumAddrType OBJECT-TYPE
	SYNTAX GmplsHopUnnumAddrTypes
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"Denotes whether this tunnel hop uses
	numbered or unnumbered interfaces.
	If set to unnumberedIfIpV4(2) or
	unnumberedIfIpV6(3) the value overrides the
	value of the associated
	mplsTunnelCHopAddrType."
	DEFVAL { numbered }
	::= { gmplsTunnelCHopEntry 1 }
	gmplsTunnelCHopLabelStatuses OBJECT-TYPE		gmplsTunnelCHopLabelStatuses OBJECT-TYPE
	SYNTAX BITS {		SYNTAX BITS {
	forwardPresent (0),		forwardPresent (0),
	reversePresent (1)		reversePresent (1)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This bitmask indicates the presence and		"This bitmask indicates the presence indicated by the
	status of labels indicated by the
	gmplsTunnelCHopExplicitLabel and		gmplsTunnelCHopExplicitLabel and
	gmplsTunnelCHopExplicitReverseLabel		gmplsTunnelCHopExplicitReverseLabel objects.
	objects.		A set bit indicates that a label is present for this
	For the Present bits, a set bit indicates		hop in the route thus allowing zero to be a valid
	that a label is present for this hop in the		label value."
	route."		::= { gmplsTunnelCHopEntry 1 }
	::= { gmplsTunnelCHopEntry 2 }
	gmplsTunnelCHopExplicitLabel OBJECT-TYPE		gmplsTunnelCHopExplicitLabel OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates the row entry in the		"Indicates the row entry in the gmplsLabelTable that
	mplsLabelTabel that defines the explicit		defines the label to use as the forward path label
	label to use in the explicit route as the		on the path at this point.
	forward path label at this point.		This value only has meaning if the forwardPresent
	This value only has meaning if the		bit of gmplsTunnelCHopLabelStatuses is set.
	forwardPresent bit of
	gmplsTunnelCHopLabelStatuses is set.		Note that the other indexes in the gmplsLabelTable
			should be interpreted as follows:
			- The gmplsLabelInterface should be zero because
			this label is not tied to any specific interface
			on this LSR
			- The gmplsLabelSubindex is used to represent label
			concatenations. The first (or only) component
			label SHOULD have gmplsLabelSubindex set to zero.
	This variable is only valid for settings of		This variable is only valid for settings of
	gmplsTunnelCHopAddrType which may be		mplsTunnelCHopAddrType which may be associated with
	associated with a forward path label.		a forward path label.
	Note that in implementations where the
	label may be encoded within a 32 bit
	integer and where mplsLabelTable is not
	implemented, this object may directly
	contain the label value to use."
	::= { gmplsTunnelCHopEntry 3 }
			Note that in implementations where the label may be
			encoded within a 32 bit integer and where
			gmplsLabelTable is not implemented, this object may
			directly contain the label value to use."
			::= { gmplsTunnelCHopEntry 2 }
	gmplsTunnelCHopExplicitReverseLabel OBJECT-TYPE		gmplsTunnelCHopExplicitReverseLabel OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Indicates the row entry in the		"Indicates the row entry in the gmplsLabelTable that
	mplsLabelTabel that defines the explicit		defines the label to use in the path as reverse path
	label to use in the explicit route as the		at this point.
	reverse path label at this point.		This value only has meaning if the reversePresent
	This value only has meaning if the		bit of gmplsTunnelCHopLabelStatuses is set.
	reversePresent bit of		The same rules and notes apply as set out for
	gmplsTunnelCHopLabelStatuses is set.		gmplsTunnelCHopExplicitLabel."
	This variable is only valid for settings of		::= { gmplsTunnelCHopEntry 3 }
	gmplsTunnelCHopAddrType which may be
	associated with a forward path label.
	Note that in implementations where the
	label may be encoded within a 32 bit
	integer and where mplsLabelTable is not
	implemented, this object may directly
	contain the label value to use."
	::= { gmplsTunnelCHopEntry 4 }
	gmplsTunnelCHopUnnumberedInterface OBJECT-TYPE
	SYNTAX InterfaceIndexOrZero
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"Indicates the interface index of the
	unnumbered interface to use when setting up
	the LSP.
	Only has value when
	gmplsTunnelCHopUnnumAddrType is set to
	unnumberedIfIpV4(2) or unnumberedIfIpV6(3)
	in which case the corresponding
	mplsTunnelCHopIpv4Addr or
	mplsTunnelCHopIpv6Addr variable contains an
	LSR id."
	::= { gmplsTunnelCHopEntry 5 }
	-- End of gmplsTunnelCHopTable		-- End of gmplsTunnelCHopTable
	-- GMPLS Tunnel Performance Table.		-- GMPLS Tunnel Reverse Direction Performance Table.
	gmplsTunnelPacketPerfTable OBJECT-TYPE		gmplsTunnelReversePerfTable OBJECT-TYPE
	SYNTAX SEQUENCE OF GmplsTunnelPacketPerfEntry		SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This table provides per-tunnel packet		"This table 'augments' the gmplsTunnelTable to
	performance information."		provides per-tunnel packet performance information
			for the reverse direction of a bidirectional tunnel.
			It can be seen as supplementing the
			mplsTunnelPerfTable which augments the
			mplsTunnelTable."
	::= { gmplsTeObjects 5 }		::= { gmplsTeObjects 5 }
	gmplsTunnelPacketPerfEntry OBJECT-TYPE		gmplsTunnelReversePerfEntry OBJECT-TYPE
	SYNTAX GmplsTunnelPacketPerfEntry		SYNTAX GmplsTunnelReversePerfEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table is created by the		"An entry in this table is created by the LSR for
	LSR for every GMPLS tunnel where packets		every bidirectional GMPLS tunnel where packets are
	are visible to the LSR.		visible to the LSR."
	Its is an extension to gmplsTunnelEntry."
	AUGMENTS { gmplsTunnelEntry }		AUGMENTS { gmplsTunnelEntry }
	::= { gmplsTunnelPacketPerfTable 1 }		::= { gmplsTunnelReversePerfTable 1 }
	GmplsTunnelPacketPerfEntry ::= SEQUENCE {
	gmplsTunnelPacketPerfRvsPackets Counter32,
	gmplsTunnelPacketPerfRvsHCPackets Counter64,
	gmplsTunnelPacketPerfRvsErrors Counter32,
	gmplsTunnelPacketPerfRvsBytes Counter32,
	gmplsTunnelPacketPerfRvsHCBytes Counter64}
	gmplsTunnelPacketPerfRvsPackets OBJECT-TYPE		GmplsTunnelReversePerfEntry ::= SEQUENCE {
			gmplsTunnelReversePerfPackets Counter32,
			gmplsTunnelReversePerfHCPackets Counter64,
			gmplsTunnelReversePerfErrors Counter32,
			gmplsTunnelReversePerfBytes Counter32,
			gmplsTunnelReversePerfHCBytes Counter64
			}
			gmplsTunnelReversePerfPackets OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Number of packets forwarded on the tunnel		"Number of packets forwarded on the tunnel in the
	in the reverse direction if it is		reverse direction if it is bidirectional."
	bidirectional."		::= { gmplsTunnelReversePerfEntry 1 }
	::= { gmplsTunnelPacketPerfEntry 1 }
	gmplsTunnelPacketPerfRvsHCPackets OBJECT-TYPE		gmplsTunnelReversePerfHCPackets OBJECT-TYPE
	SYNTAX Counter64		SYNTAX Counter64
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"High capacity counter for number of packets		"High capacity counter for number of packets
	forwarded on the tunnel in the reverse		forwarded on the tunnel in the reverse direction if
	direction if it is bidirectional."		it is bidirectional."
	::= { gmplsTunnelPacketPerfEntry 2 }		::= { gmplsTunnelReversePerfEntry 2 }
	gmplsTunnelPacketPerfRvsErrors OBJECT-TYPE
			gmplsTunnelReversePerfErrors OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Number of errored packets received on the		"Number of errored packets received on the tunnel in
	tunnel in the reverse direction if it is		the reverse direction if it is bidirectional."
	bidirectional."		::= { gmplsTunnelReversePerfEntry 3 }
	::= { gmplsTunnelPacketPerfEntry 3 }
	gmplsTunnelPacketPerfRvsBytes OBJECT-TYPE		gmplsTunnelReversePerfBytes OBJECT-TYPE
	SYNTAX Counter32		SYNTAX Counter32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Number of bytes forwarded on the tunnel in		"Number of bytes forwarded on the tunnel in the
	the reverse direction if it is		reverse direction if it is bidirectional."
	bidirectional."		::= { gmplsTunnelReversePerfEntry 4 }
	::= { gmplsTunnelPacketPerfEntry 4 }
	gmplsTunnelPacketPerfRvsHCBytes OBJECT-TYPE		gmplsTunnelReversePerfHCBytes OBJECT-TYPE
	SYNTAX Counter64		SYNTAX Counter64
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"High capacity counter for number of bytes		"High capacity counter for number of bytes forwarded
	forwarded on the tunnel in the reverse		on the tunnel in the reverse direction if it is
	direction if it is bidirectional."		bidirectional."
	::= { gmplsTunnelPacketPerfEntry 5 }		::= { gmplsTunnelReversePerfEntry 5 }
	-- End of gmplsTunnelPacketPerfTable
			-- End of gmplsTunnelReversePerfTable
	-- GMPLS Tunnel Error Table.		-- GMPLS Tunnel Error Table.
	gmplsTunnelErrorTable OBJECT-TYPE		gmplsTunnelErrorTable OBJECT-TYPE
	SYNTAX SEQUENCE OF GmplsTunnelErrorEntry		SYNTAX SEQUENCE OF GmplsTunnelErrorEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This table provides per-tunnel information		"This table 'augments' the mplsTunnelTable
	about errors. Errors may be detected
	locally or reported through the signaling		This table provides per-tunnel information about
	protocol."		errors. Errors may be detected locally or reported
			through the signaling protocol.
			Error reporting is not exclusive to GMPLS and this
			table may be applied in MPLS systems."
	::= { gmplsTeObjects 6 }		::= { gmplsTeObjects 6 }
	gmplsTunnelErrorEntry OBJECT-TYPE		gmplsTunnelErrorEntry OBJECT-TYPE
	SYNTAX GmplsTunnelErrorEntry		SYNTAX GmplsTunnelErrorEntry
	MAX-ACCESS not-accessible		MAX-ACCESS not-accessible
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"An entry in this table is created by the		"An entry in this table is created by the LSR for
	LSR for every tunnel where error		every tunnel where error information is visible to
	information is visible to the LSR.		the LSR."
	Its is an extension to gmplsTunnelEntry."		AUGMENTS { mplsTunnelEntry }
	AUGMENTS { gmplsTunnelEntry }
	::= { gmplsTunnelErrorTable 1 }		::= { gmplsTunnelErrorTable 1 }
	GmplsTunnelErrorEntry ::= SEQUENCE {		GmplsTunnelErrorEntry ::= SEQUENCE {
	gmplsTunnelErrorLastError INTEGER,		gmplsTunnelErrorLastErrorType INTEGER,
	gmplsTunnelErrorLastTime TimeStamp,		gmplsTunnelErrorLastTime TimeStamp,
	gmplsTunnelErrorReporterType INTEGER,		gmplsTunnelErrorReporterType INTEGER,
	gmplsTunnelErrorReporterIpv4Addr InetAddressIPv4,		gmplsTunnelErrorReporterIpv4Addr InetAddressIPv4,
	gmplsTunnelErrorReporterIpv6Addr InetAddressIPv6,		gmplsTunnelErrorReporterIpv6Addr InetAddressIPv6,
	gmplsTunnelErrorProtocolCode Unsigned32,		gmplsTunnelErrorCode Unsigned32,
	gmplsTunnelErrorProtocolSubcode Unsigned32,		gmplsTunnelErrorSubcode Unsigned32,
	gmplsTunnelErrorHelpString DisplayString		gmplsTunnelErrorHelpString DisplayString
	}		}
	gmplsTunnelErrorLastError OBJECT-TYPE		gmplsTunnelErrorLastErrorType OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	noError (0),		noError (0),
	unknown (1),		unknown (1),
	localProtocol (2),		localProtocol (2),
	remoteProtocol (3),		remoteProtocol (3),
	configuration (4),		configuration (4),
	pathComputation (5),		pathComputation (5),
	localResources (6)		localResources (6)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The nature of the last error.		"The nature of the last error. Provides
	Protocol errors encompass all errors that		interpretation context for
	may be reported through the protocol and		gmplsTunnelErrorProtocolCode and
	give a wider set of error codes than those		gmplsTunnelErrorProtocolSubcode. A value of noError
	provided here. It may be useful for an		(0) shows that there is no error associated with
	implementation to report locally detected		this tunnel and means that the other objects in this
	errors using the codes provided by the		entry have no meaning."
	signaling protocols to give a better
	diagnosis of the error.
	Values in excess of 32767 are reserved for
	implementation-specific error codes."
	::= { gmplsTunnelErrorEntry 1 }		::= { gmplsTunnelErrorEntry 1 }
	gmplsTunnelErrorLastTime OBJECT-TYPE		gmplsTunnelErrorLastTime OBJECT-TYPE
	SYNTAX TimeStamp		SYNTAX TimeStamp
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The time at which the last error occurred.		"The time at which the last error occurred. This is
	This is presented as the value of SysUpTime		presented as the value of SysUpTime when the error
	when the error occurred or was reported to		occurred or was reported to this node.
	this node.		If gmplsTunnelErrorLastErrorType has the value
	If gmplsTunnelErrorLastError has the value
	noError (0), then this object is ignored."		noError (0), then this object is ignored."
	::= { gmplsTunnelErrorEntry 2 }		::= { gmplsTunnelErrorEntry 2 }
	gmplsTunnelErrorReporterType OBJECT-TYPE		gmplsTunnelErrorReporterType OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	noError (0),		unknown (0),
	unknown (1),		localNode (1),
	localNode (2),		localIpV4 (2),
	localIpV4 (3),		remoteIpV4 (3),
	remoteIpV4 (4),		localIpV6 (4),
	localIpV6 (5),		remoteIpV6 (5)
	remoteIpV6 (6)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The reporter of the last error recorded.		"The reporter of the last error recorded.
	This object is used principally to aid in		This object is used principally to aid in
	interpretation of		interpretation of gmplsTunnelErrorReporterIpv4Addr
	gmplsTunnelErrorReporterIpv4Addr and		and gmplsTunnelErrorReporterIpv6Addr. Where the
	gmplsTunnelErrorReporterIpv6Addr. Where		error has been locally generated and there is no
	the error has been locally generated and		requirement to associate the error with any specific
	there is no requirement to associate the		local address (such as an interface), the value
	error with any specific local address (such		localNode (2) may be used.
	as an interface), the value localNode (2)		If gmplsTunnelErrorLastError has the value noError
	may be used.		(0), then this object is ignored."
	When gmplsTunnelErrorLastError has the
	value noError (0), then this object should
	have the value noError (0) and should be
	ignored."
	::= { gmplsTunnelErrorEntry 3 }		::= { gmplsTunnelErrorEntry 3 }
	gmplsTunnelErrorReporterIpv4Addr OBJECT-TYPE		gmplsTunnelErrorReporterIpv4Addr OBJECT-TYPE
	SYNTAX InetAddressIPv4		SYNTAX InetAddressIPv4
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The address of the node reporting the last		"The address of the node reporting the last error, or
	error, or the address of the resource (such		the address of the resource (such as an interface)
	as an interface) associated with the error.		associated with the error.
			If gmplsTunnelErrorLastErrorType has the value
			noError (0), then this object is ignored.
	This object only has meaning if the object		This object only has meaning if the object
	gmplsTunnelErrorReporterType has value		gmplsTunnelErrorReporterType has value localIpV4 (2)
	localIpV4 (3) or remoteIpV4 (4). Otherwise		or remoteIpV4 (3). Otherwise the object should
	the object should contain the value zero."		contain the value zero and should be ignored."
	::= { gmplsTunnelErrorEntry 4 }		::= { gmplsTunnelErrorEntry 4 }
	gmplsTunnelErrorReporterIpv6Addr OBJECT-TYPE		gmplsTunnelErrorReporterIpv6Addr OBJECT-TYPE
	SYNTAX InetAddressIPv6		SYNTAX InetAddressIPv6,
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The address of the node reporting the last		"The address of the node reporting the last error, or
	error, or the address of the resource (such		the address of the resource (such as an interface)
	as an interface) associated with the error.		associated with the error.
			If gmplsTunnelErrorLastErrorType has the value
			noError (0), then this object is ignored.
	This object only has meaning if the object		This object only has meaning if the object
	gmplsTunnelErrorReporterType has value		gmplsTunnelErrorReporterType has value localIpV6 (4)
	localIpV4 (3) or remoteIpV4 (4). Otherwise		or remoteIpV4 (5). Otherwise the object should
	the object should contain the value zero."		contain the value zero and should be ignored."
	::= { gmplsTunnelErrorEntry 5 }		::= { gmplsTunnelErrorEntry 5 }
	gmplsTunnelErrorProtocolCode OBJECT-TYPE		gmplsTunnelErrorCode OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The primary error code associated with the		"The primary error code associated with the last
	last error and the protocol used to signal		error.
	this tunnel.
	The relevant protocol is indicated by the		The interpretation of this error code depends on the
	gmplsTunnelSignallingProto object."		value of gmplsTunnelErrorLastErrorType. If the value
			of gmplsTunnelErrorLastErrorType is noError (0) the
			value of this object should be 0 and should be
			ignored. If the value of
			gmplsTunnelErrorLastErrorType is localProtocol (2)
			or remoteProtocol (3) the error should be
			interpreted in the context of the signling protocol
			identified by the mplsTunnelSignallingProto object.
			Values in excess 32767 of are not used by signaling
			protocols and may safely be used as implementation-
			specific error codes. "
	::= { gmplsTunnelErrorEntry 6 }		::= { gmplsTunnelErrorEntry 6 }
	gmplsTunnelErrorProtocolSubcode OBJECT-TYPE		gmplsTunnelErrorSubcode OBJECT-TYPE
	SYNTAX Unsigned32		SYNTAX Unsigned32
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The secondary error code associated with		"The secondary error code associated with the last
	the last error and the protocol used to		error and the protocol used to signal this tunnel.
	signal this tunnel.		This value is interprettd in the context of the
	The relevant protocol is indicated by the		value of gmplsTunnelErrorCode.
	gmplsTunnelSignallingProto object."		If the value of gmplsTunnelErrorLastErrorType is
			noError (0) the value of this object should be 0 and
			should be ignored."
	::= { gmplsTunnelErrorEntry 7 }		::= { gmplsTunnelErrorEntry 7 }
	gmplsTunnelErrorHelpString OBJECT-TYPE		gmplsTunnelErrorHelpString OBJECT-TYPE
	SYNTAX DisplayString		SYNTAX DisplayString
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"A textual string containing information		"A textual string containing information about the
	about the last error, recovery actions and		last error, recovery actions and support advice. If
	support advice. If there is no help string		there is no help string this object contains a zero
	this object contains a zero length string."		length string.
			If the value of gmplsTunnelErrorLastErrorType is
			noError (0) this object should contain a zero length
			string, but may contain a help string indicating
			that there is no error."
	::= { gmplsTunnelErrorEntry 8 }		::= { gmplsTunnelErrorEntry 8 }
	-- Module compliance.		-- Module compliance.
	gmplsTeGroups		gmplsTeGroups
	OBJECT IDENTIFIER ::= { gmplsTeConformance 1 }		OBJECT IDENTIFIER ::= { gmplsTeConformance 1 }
	gmplsTeCompliances		gmplsTeCompliances
	OBJECT IDENTIFIER ::= { gmplsTeConformance 2 }		OBJECT IDENTIFIER ::= { gmplsTeConformance 2 }
	gmplsTeModuleCompliance MODULE-COMPLIANCE		gmplsTeModuleCompliance MODULE-COMPLIANCE
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Compliance statement for agents that		"Compliance statement for agents that support the
	support the GMPLS TE MIB."		GMPLS TE MIB."
	MODULE -- this module		MODULE -- this module
	-- The mandatory group has to be implemented by all		-- The mandatory group has to be implemented by all
	-- LSRs that originate/terminate ESLSPs/tunnels.		-- LSRs that originate/terminate ESLSPs/tunnels.
	-- In addition, depending on the type of tunnels		-- In addition, depending on the type of tunnels
	-- supported, other groups become mandatory as		-- supported, other groups become mandatory as
	-- explained below.		-- explained below.
	MANDATORY-GROUPS {		MANDATORY-GROUPS {
	gmplsTunnelGroup,		gmplsTunnelGroup,
	gmplsTunnelScalarGroup		gmplsTunnelScalarGroup
	}		}
	GROUP gmplsTunnelManualGroup		GROUP gmplsTunnelManualGroup
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for devices which		"This group is mandatory for devices which support
	support manual configuration of tunnels, in		manual configuration of tunnels, in addition to
	addition to gmplsTunnelGroup. The		gmplsTunnelGroup. The following constraints apply:
	following constraints apply:
	gmplsTunnelSignallingProto should be at
	least read-only with a value of none(1)."
			gmplsTunnelSignallingProto should be at least read-
			only with a value of none(1)."
	GROUP gmplsTunnelSignaledGroup		GROUP gmplsTunnelSignaledGroup
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for devices which		"This group is mandatory for devices which support
	support signaled tunnel set up, in addition		signaled tunnel set up, in addition to
	to gmplsTunnelGroup. The following		gmplsTunnelGroup. The following constraints apply:
	constraints apply:
	gmplsTunnelSignallingProto should be at		gmplsTunnelSignallingProto should be at least read-
	least read-only returning a value of		only returning a value of ldp(2), or rsvp(3)."
	ldp(2), or rsvp(3)."
	GROUP gmplsTunnelIsNotIntfcGroup		GROUP gmplsTunnelIsNotIntfcGroup
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for devices which		"This group is mandatory for devices which support
	support tunnels that are not interfaces, in		tunnels that are not interfaces, in addition to
	addition to gmplsTunnelGroup. The		gmplsTunnelGroup. The following constraints apply:
	following constraints apply:
	gmplsTunnelIsIf must at least be read-only		gmplsTunnelIsIf must at least be read-only returning
	returning no(0)."		no(0)."
	GROUP gmplsTunnelIsIntfcGroup		GROUP gmplsTunnelIsIntfcGroup
	DESCRIPTION		DESCRIPTION
	"This group is mandatory for devices which		"This group is mandatory for devices which support
	support tunnels that are interfaces, in		tunnels that are interfaces, in addition to
	addition to gmplsTunnelGroup. The		gmplsTunnelGroup. The following constraints apply:
	following constraints apply:
	gmplsTunnelIsUnnum must at least be read-		gmplsTunnelIsUnnum must at least be read-only
	only returning false."		returning false."
	GROUP gmplsTunnelOptionalGroup		GROUP gmplsTunnelOptionalGroup
	DESCRIPTION		DESCRIPTION
	"Objects in this group are optional."		"Objects in this group are optional."
	-- GMPLS Tunnel scalars.		-- GMPLS Tunnel scalars.
	OBJECT gmplsTunnelsConfigured		OBJECT gmplsTunnelsConfigured
	MIN-ACCESS read-only		MIN-ACCESS read-only
	DESCRIPTION		DESCRIPTION
	"Write access is not required."		"Write access is not required."
	skipping to change at page 40, line 33		skipping to change at page 34, line 53
	gmplsTunnelPacketPerfRvsErrors,		gmplsTunnelPacketPerfRvsErrors,
	gmplsTunnelPacketPerfRvsBytes,		gmplsTunnelPacketPerfRvsBytes,
	gmplsTunnelPacketPerfRvsHCBytes,		gmplsTunnelPacketPerfRvsHCBytes,
	gmplsTunnelErrorLastError,		gmplsTunnelErrorLastError,
	gmplsTunnelErrorLastTime,		gmplsTunnelErrorLastTime,
	gmplsTunnelErrorReporterType,		gmplsTunnelErrorReporterType,
	gmplsTunnelErrorReporterIpv4Addr,		gmplsTunnelErrorReporterIpv4Addr,
	gmplsTunnelErrorReporterIpv6Addr,		gmplsTunnelErrorReporterIpv6Addr,
	gmplsTunnelErrorProtocolCode,		gmplsTunnelErrorProtocolCode,
	gmplsTunnelErrorProtocolSubcode,		gmplsTunnelErrorProtocolSubcode,
	gmplsTunnelErrorHelpString}		gmplsTunnelErrorHelpString
			}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Necessary, but not sufficient, set of		"Necessary, but not sufficient, set of objects to
	objects to implement tunnels. In addition,		implement tunnels. In addition, depending on the
	depending on the type of the tunnels		type of the tunnels supported (for example, manually
	supported (for example, manually configured		configured or signaled, persistent or non-
	or signaled, persistent or non-persistent,		persistent, etc.), the following other groups
	etc.), the following other groups defined		defined below are mandatory: gmplsTunnelManualGroup
	below are mandatory: gmplsTunnelManualGroup
	and/or gmplsTunnelSignaledGroup,		and/or gmplsTunnelSignaledGroup,
	gmplsTunnelIsNotIntfcGroup and/or		gmplsTunnelIsNotIntfcGroup and/or
	gmplsTunnelIsIntfcGroup."		gmplsTunnelIsIntfcGroup."
	::= { gmplsTeGroups 1 }		::= { gmplsTeGroups 1 }
	gmplsTunnelManualGroup OBJECT-GROUP		gmplsTunnelManualGroup OBJECT-GROUP
	OBJECTS { gmplsTunnelSignallingProto }		OBJECTS {
			gmplsTunnelSignallingProto
			}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Object(s) needed to implement manually		"Object(s) needed to implement manually configured
	configured tunnels."		tunnels."
	::= { gmplsTeGroups 2 }		::= { gmplsTeGroups 2 }
	gmplsTunnelSignaledGroup OBJECT-GROUP		gmplsTunnelSignaledGroup OBJECT-GROUP
	OBJECTS {		OBJECTS {
	gmplsTunnelLSPEncoding,		gmplsTunnelLSPEncoding,
	gmplsTunnelLinkProtection,		gmplsTunnelLinkProtection,
	gmplsTunnelGPid,		gmplsTunnelGPid,
	gmplsTunnelSecondary,		gmplsTunnelSecondary,
	gmplsTunnelHopUnnumAddrType,		gmplsTunnelHopUnnumAddrType,
	gmplsTunnelHopLabelStatuses,		gmplsTunnelHopLabelStatuses,
	gmplsTunnelHopExplicitLabel,		gmplsTunnelHopExplicitLabel,
	gmplsTunnelHopExplicitReverseLabel,		gmplsTunnelHopExplicitReverseLabel,
	skipping to change at page 41, line 18		skipping to change at page 35, line 35
	gmplsTunnelGPid,		gmplsTunnelGPid,
	gmplsTunnelSecondary,		gmplsTunnelSecondary,
	gmplsTunnelHopUnnumAddrType,		gmplsTunnelHopUnnumAddrType,
	gmplsTunnelHopLabelStatuses,		gmplsTunnelHopLabelStatuses,
	gmplsTunnelHopExplicitLabel,		gmplsTunnelHopExplicitLabel,
	gmplsTunnelHopExplicitReverseLabel,		gmplsTunnelHopExplicitReverseLabel,
	gmplsTunnelHopUnnumberedInterface		gmplsTunnelHopUnnumberedInterface
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Objects needed to implement signaled		"Objects needed to implement signaled tunnels."
	tunnels."
	::= { gmplsTeGroups 3 }		::= { gmplsTeGroups 3 }
	gmplsTunnelScalarGroup OBJECT-GROUP		gmplsTunnelScalarGroup OBJECT-GROUP
	OBJECTS {		OBJECTS {
	gmplsTunnelsConfigured,		gmplsTunnelsConfigured,
	gmplsTunnelActive		gmplsTunnelActive
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Scalar objects needed to implement MPLS		"Scalar objects needed to implement MPLS tunnels."
	tunnels."
	::= { gmplsTeGroups 4 }		::= { gmplsTeGroups 4 }
	gmplsTunnelIsIntfcGroup OBJECT-GROUP		gmplsTunnelIsIntfcGroup OBJECT-GROUP
	OBJECTS { gmplsTunnelIsUnnum }		OBJECTS {
			gmplsTunnelIsUnnum
			}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Objects needed to implement tunnels that		"Objects needed to implement tunnels that are
	are interfaces."		interfaces."
	::= { gmplsTeGroups 5 }		::= { gmplsTeGroups 5 }
	gmplsTunnelIsNotIntfcGroup OBJECT-GROUP		gmplsTunnelIsNotIntfcGroup OBJECT-GROUP
	OBJECTS { gmplsTunnelIsUnnum }		OBJECTS {
			gmplsTunnelIsUnnum
			}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Objects needed to implement tunnels that		"Objects needed to implement tunnels that are not
	are not interfaces."		interfaces."
	::= { gmplsTeGroups 6 }		::= { gmplsTeGroups 6 }
	gmplsTunnelOptionalGroup OBJECT-GROUP		gmplsTunnelOptionalGroup OBJECT-GROUP
	OBJECTS {		OBJECTS {
	gmplsTunnelARHopUnnumAddrType,		gmplsTunnelARHopUnnumAddrType,
	gmplsTunnelARHopLabelStatuses,		gmplsTunnelARHopLabelStatuses,
	gmplsTunnelARHopExplicitLabel,		gmplsTunnelARHopExplicitLabel,
	gmplsTunnelARHopExplicitReverseLabel,		gmplsTunnelARHopExplicitReverseLabel,
	gmplsTunnelCHopUnnumAddrType,		gmplsTunnelCHopUnnumAddrType,
	gmplsTunnelCHopLabelStatuses,		gmplsTunnelCHopLabelStatuses,
	skipping to change at page 42, line 16		skipping to change at page 36, line 33
	gmplsTunnelCHopExplicitReverseLabel,		gmplsTunnelCHopExplicitReverseLabel,
	gmplsTunnelCHopUnnumberedInterface		gmplsTunnelCHopUnnumberedInterface
	}		}
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The objects in this group are optional."		"The objects in this group are optional."
	::= { gmplsTeGroups 7 }		::= { gmplsTeGroups 7 }
	END		END
	11. Security Considerations		9. Security Considerations
	There are a number of management objects defined in this
	MIB that have a MAX-ACCESS clause of read-write and/or
	read-create. Such objects may be considered sensitive or
	vulnerable in some network environments. The support for
	SET operations in a non-secure environment without proper
	protection can have a negative effect on network
	operations.
	There are a number of managed objects in this MIB that		It is clear that the MIB modules described in this document in
	may contain information that may be sensitive from a		association with the MPLS-TE-STD-MIB are potentially useful for
	business perspective, in that they represent a customer's		monitoring of MPLS and GMPLS tunnels. These MIB modules can also be
	interface to the MPLS network.		used for configuration of certain objects, and anything that can be
			configured can be incorrectly configured, with potentially disastrous
			results.
	Allowing uncontrolled access to these objects could		There are a number of management objects defined in these MIB modules
	result in malicious and unwanted disruptions of network		with a MAX-ACCESS clause of read-write and/or read-create. Such
	traffic or incorrect configurations for these customers.		objects may be considered sensitive or vulnerable in some network
	There are no objects that are particularly sensitive in		environments. The support for SET operations in a non-secure
	their own right, such as passwords or monetary amounts.		environment without proper protection can have a negative effect on
			network operations. These are the tables and objects and their
			sensitivity/vulnerability:
	It is thus important to control even GET access to these		o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain
	objects and possibly to even encrypt the values of these		objects to provision GMPLS tunnels interfaces at their ingress
	object when sending them over the network via SNMP. Not		LSRs. Unauthorized write access to objects in these tables, could
	all versions of SNMP provide features for such a secure		result in disruption of traffic on the network. This is especially
	environment.		true if a tunnel has already been established. The use of stronger
			mechanisms such as SNMPv3 security should be considered where
			possible. Specifically, SNMPv3 VACM and USM MUST be used with any
			SNMPv3 agent which implements these MIB modules.
	At this writing, no security holes have been identified		Some of the readable objects in these MIB modules "i.e., objects with
	beyond those that SNMP Security [SNMPArch] is itself		a MAX-ACCESS other than not-accessible" may be considered sensitive
	intended to address. These relate to primarily		or vulnerable in some network environments. It is thus important to
	controlled access to sensitive information and the		control even GET and/or NOTIFY access to these objects and possibly
	ability to configure a device - or which might result		to even encrypt the values of these objects when sending them over
	from operator error, which is beyond the scope of any		the network via SNMP. These are the tables and objects and their
	security architecture.		sensitivity/vulnerability:
	SNMPv1 or SNMPv2 are by themselves not a secure		o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable,
	environment. Even if the network itself is secure (for		gmplsTunnelCHopTable, gmplsTunnelReversePerfTable,
	example by using IPSec [IPSEC]), there is no control as		gmplsTunnelErrorTable collectively show the tunnel network
	to who on the secure network is allowed to access and		topology and status. If an Administrator does not want to reveal
	GET/SET (read/change/create/delete) the objects in this		this information, then these tables should be considered
	MIB. It is recommended that the implementers consider the		sensitive/vulnerable.
	security features as provided by the SNMPv3 framework.
	Specifically, the use of the User-based Security Model
	[SNMPv3USM] and the View-based Access Control
	[SNMPv3VACM] is recommended. It is then a customer/user
	responsibility to ensure that the SNMP entity giving
	access to an instance of this MIB is properly configured
	to give access to the objects only to those principals
	(users) that have legitimate rights to indeed GET or SET
	(change/create/delete) them.
	12. Acknowledgments		SNMP versions prior to SNMPv3 did not include adequate security. Even
			if the network itself is secure "for example by using IPSec", even
			then, there is no control as to who on the secure network is allowed
			to access and GET/SET "read/change/create/delete" the objects in
			these MIB modules. It is RECOMMENDED that implementers consider the
			security features as provided by the SNMPv3 framework "see [RFC3410],
			section 8", including full support for the SNMPv3 cryptographic
			mechanisms "for authentication and privacy".
	This draft is based heavily on [TEMIB]. The authors		Further, deployment of SNMP versions prior to SNMPv3 is NOT
	would like to express their gratitude to all those who		RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
	worked on that earlier MIB.		enable cryptographic security. It is then a customer/operator
			responsibility to ensure that the SNMP entity giving access to an
			instance of this MIB module, is properly configured to give access to
			the objects only to those principals "users" that have legitimate
			rights to indeed GET or SET "change/create/delete" them.
	Thanks also to Tony Zinicola and Jeremy Crossen for their		10. Acknowledgments
	valuable contributions.
	13. References		This draft extends [TEMIB]. The authors would like to express their
			gratitude to all those who worked on that earlier MIB document.
			Thanks also to Tony Zinicola and Jeremy Crossen for their valuable
			contributions during an early implementation.
	13.1. Normative References		11. References
	[RFC1157] Case, J., Fedor, M., Schoffstall, M., and		11.1. Normative References
	J. Davin, "Simple Network Management
	Protocol", RFC 1157, May 1990.
	[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Definitions", RFC 1212, March 1991.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2119] Bradner, S., "Key words for use in RFCs to		[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
	Indicate Requirement Levels", BCP 14, RFC		Case, J., Rose, M., and S. Waldbusser, "Structure
	2119, March 1997.		of Management Information Version 2 (SMIv2)", STD
			58, RFC 2578, April 1999.
	[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder,		[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
	J., Case, J., Rose, M., and S. Waldbusser,		Case, J., Rose, M., and S. Waldbusser, "Textual
	"Textual Conventions for SMIv2", STD 58,		Conventions for SMIv2", STD 58, RFC 2579, April
	RFC 2579, April 1999.		1999.
	[RFC2863] McCloghrie, K. and F. Kastenholtz, "The		[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
	Interfaces Group MIB", RFC 2863, June 2000.		Case, J., Rose, M., and S. Waldbusser, "Conformance
			Statements for SMIv2", STD 58, RFC 2580, April
			1999.
	[RFC3032] Rosen, E., Rekhter, Y., Tappan, D.,		[RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces
	Farinacci, D., Federokow, G., Li, T., and		Group MIB", RFC 2863, June 2000.
	A. Conta, "MPLS Label Stack Encoding", RFC
	3032, January 2001.
	[RFC3036] Anderson, L., Doolan, P., Feldman, N.,		[RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
	Fredette, A., and B. Thomas, "LDP		"Multiprotocol Label Switching Architecture", RFC
	Specification", RFC 3036, January 2001.		3031, January 2001.
	[RSVPTE] Awduche, D., Berger, L., Gan, D., Li, T.,		[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T.,
	Srinivasan, V., and G. Swallow, "RSVP-TE:		Srinivasan, V., and G. Swallow, "RSVP-TE:
	Extensions to RSVP for LSP Tunnels", RFC		Extensions to RSVP for LSP Tunnels", RFC 3209,
	3209, December 2001.		December 2001.
	[CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson,		[RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L.,
	L., Ashwood-Smith, P., Hellstrand, F.,		Ashwood-Smith, P., Hellstrand, F., Sundell, K.,
	Sundell, K., Callon, R., Dantu, R., Wu, L.,		Callon, R., Dantu, R., Wu, L., Doolan, P., Worster,
	Doolan, P., Worster, T., Feldman, N.,		T., Feldman, N., Fredette, A., Girish, M., Gray,
	Fredette, A., Girish, M., Gray, E.,		E., Halpern, J., Heinanen, J., Kilty, T., Malis,
	Halpern, J., Heinanen, J., Kilty, T.,		A., and P. Vaananen, "Constraint-Based LSP Setup
	Malis, A., and P. Vaananen, "Constraint-		using LDP", RFC 3212, December 2001."
	Based LSP Setup using LDP", draft-ietf-mpls-
	cr-ldp-06.txt, November 2001, work in
	progress."
	[GMPLSArch] Ashwood-Smith, P., Awduche, D., Banerjee,		[RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol
	A., Basak, D, Berger, L., Bernstein, G.,		Label Switching (GMPLS) Signaling Functional
	Drake, J., Fan, Y., Fedyk, D., Grammel, D.,		Description", RFC 3471, January 2003.
	Kompella, K., Kullberg, A., Lang, J., Liaw,
	F., Papadimitriou, D., Pendarakis, D.,
	Rajagopalan, B., Rekhter, Y., Saha, D.,
	Sandick, H., Sharma, V., Swallow, G., Tang,
	Z., Yu, J., Zinin, A., Nadeau, T., Mannie,
	E., Generalized Multiprotocol Label
	Switching (GMPLS) Architecture, Internet
	Draft <draft-many-gmpls-architecture-
	01.txt>, March 2001, work in progress.
	[GMPLSSig] Ashwood-Smith, P., Awduche, D., Banerjee,		[RFC3472] Ashwood-Smith, P., Berger, L. (Editors),
	A., Basak, D, Berger, L., Bernstein, G.,		"Generalized MPLS Signaling - CR-LDP Extensions",
	Drake, J., Fan, Y., Fedyk, D., Grammel, D.,		RFC 3472, January 2003.
	Kompella, K., Kullberg, A., Lang,
	Rajagopalan, B., Rekhter, Y., Saha, D.,
	Sharma, V., Swallow, G., Bo Tang, Z.,
	Generalized MPLS - Signaling Functional
	Description, <draft-ietf-mpls-generalized-
	signaling-04.txt>, May 2001, work in
	progress.
	[GMPLSCRLDP] Ashwood-Smith, P., Awduche, D., Banerjee,		[RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling -
	A., Basak, D, Berger, L., Bernstein, G.,		RSVP-TE Extensions", RFC 3473 January 2003.
	Drake, J., Fan, Y., Fedyk, D., Grammel, D.,
	Kompella, K., Kullberg, A., Lang,
	Rajagopalan, B., Rekhter, Y., Saha, D.,
	Sharma, V., Swallow, G., Bo Tang, Z.,
	Generalized MPLS Signaling - CR-LDP
	Extensions, Internet Draft <draft-ietf-mpls-
	generalized-cr-ldp-03.txt>, May 2001, work
	in progress.
	[GMPLSRSVPTE] Ashwood-Smith, P., Awduche, D., Banerjee,		[GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol
	A., Basak, D, Berger, L., Bernstein, G.,		Label Switching (GMPLS) Architecture", Internet
	Drake, J., Fan, Y., Fedyk, D., Grammel, D.,		Draft <draft-many-gmpls-architecture-07.txt>, May
	Kompella, K., Kullberg, A., Lang,		2003, work in progress.
	Rajagopalan, B., Rekhter, Y., Saha, D.,
	Sharma, V., Swallow, G., Bo Tang, Z.,
	Generalized MPLS Signaling - RSVP-TE
	Extensions, Internet Draft <draft-ietf-mpls-
	generalized-rsvp-te-03.txt>, May 2001, work
	in progress.
	[GMPLSSonetSDH] Mannie, E., Ansorge, S., Ashwood-Smith,		[GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors),
	P., Banerjee, A., Berger, L., Bernstein,		"Generalized Multi-Protocol Label Switching
	G., Chiu, A., Drake, J., Fan, Y., Fontana,		Extensions for SONET and SDH Control", Internet
	M., Grammel, G., Heiles, J., Katukam, S.,		Draft <draft-ietf-ccamp-gmpls-sonet-sdh-08.txt>,
	Kompella, K., Lang, J. P., Liaw, F., Lin,		February 2003, work in progress.
	Z., Mack-Crane, B., Papadimitriou, D.,
	Pendarakis, D., Raftelis, M., Rajagopalan,
	B., Rekhter, Y., Saha, D., Sharma, V.,
	Swallow, G., Bo Tang, Z., Varma, E.,
	Vissers, M., Xu, Y., GMPLS Extensions for
	SONET and SDH Control, Internet Draft
	<draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>,
	May 2001, work in progress.
	[TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C,		[TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions of
	Viswanathan, A. and H. Sjostrand,		Textual Conventions for Multiprotocol Label
	"Definition of Textual Conventions and		Switching (MPLS) Management", Internet Draft
	OBJECT-IDENTITIES for Multiprotocol Label		<draft-ietf-mpls-tc-mib-09.txt>, August 2003, work
	Switching (MPLS) Management", Internet		in progress.
	Draft <draft-ietf-mpls-tc-mib-03.txt>,
	January 2002, work in progress.
	[TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A.,		[TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A.,
	"Multiprotocol Label Switching (MPLS)		"Multiprotocol Label Switching (MPLS) Traffic
	Traffic Engineering Management Information		Engineering Management Information Base", Internet
	Base", Internet Draft <draft-ietf-mpls-te-		Draft <draft-ietf-mpls-te-mib-12.txt>, August 2003,
	mib-08.txt>, January 2002, work in		work in progress.
	progress.
	[LSRMIB] Srinivasan, C., Viswanathan, A. and T.
	Nadeau, "MPLS Label Switching Router
	Management Information Base Using SMIv2",
	Internet Draft <draft-ietf-mpls-lsr-mib-
	08.txt>, January 2002, work in progress.
	[GMPLSLSRMIB] Nadeau, T., Srinivasan, C., A., Farrel, A.,
	Hall, T., and Harrison, E., "Generalized
	Multiprotocol Label Switching (GMPLS) Label
	Switching Router Management Information
	Base", draft-ietf-ccamp-gmpls-lsr-mib-
	00.txt, June 2002, work in progress.
	[GMPLS-OSPF] Kompella, K., et al., "OSPF Extensions in
	Support of Generalized MPLS", draft-ietf-
	ccamp-ospf-gmpls-extensions-07.txt, May
	2002, work in progress.
	13.2. Informational References
	[RFC1155] Rose, M., and K. McCloghrie, "Structure and
	Identification of Management Information
	for TCP/IP-based Internets", RFC 1155, May
	1990.
	[RFC1215] M. Rose, "A Convention for Defining Traps
	for use with the SNMP", RFC 1215, March
	1991.
	[RFC1901] Case, J., McCloghrie, K., Rose, M., and S.
	Waldbusser, "Introduction to Community-
	based SNMPv2", RFC 1901, January 1996.
	[RFC1905] Case, J., McCloghrie, K., Rose, M., and S.
	Waldbusser, "Protocol Operations for
	Version 2 of the Simple Network Management
	Protocol (SNMPv2)", RFC 1905, January 1996.
	[RFC1906] 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.
	[RFC2514] Noto, et. al., "Definitions of Textual
	Conventions and OBJECT-IDENTITIES for ATM
	Management", RFC 2514, Feb. 1999
	[RFC2515] K. Tesink, "Definitions of Managed Objects
	for ATM Management", RFC 2515, Feb. 1999
	[RFC2570] Case, J., Mundy, R., Partain, D., and B.
	Stewart, "Introduction to Version 3 of the
	Internet-standard Network Management
	Framework", RFC 2570, April 1999.
	[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen,
	"An Architecture for Describing SNMP
	Management Frameworks", RFC 2571, April
	1999.
	[RFC2572] Case, J., Harrington D., Presuhn R., and B.
	Wijnen, "Message Processing and Dispatching
	for the Simple Network Management Protocol
	(SNMP)", RFC 2572, April 1999.
	[RFC2573] Levi, D., Meyer, P., and B. Stewart,		[LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau,
	"SNMPv3 Applications", RFC 2573, April		"Multiprotocol Label Switching (MPLS) Label
	1999.		Switching Router (LSR) Management Information
			Base", Internet Draft <draft-ietf-mpls-lsr-mib-
			12.txt>, August 2003, work in progress.
	[RFC2574] Blumenthal, U., and B. Wijnen, "User-based		[GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
	Security Model (USM) for version 3 of the		and Harrison, E., "Definitions of Textual
	Simple Network Management Protocol		Conventions for Multiprotocol Label Switching
	(SNMPv3)", RFC 2574, April 1999.		(MPLS) Management", draft-ietf-ccamp-gmpls-te-mib-
			01.txt, August 2003, work in progress.
	[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie,		[GMPLSLSRMIB] Nadeau, T., Srinivasan, C., A., Farrel, A., Hall,
	"View-based Access Control Model (VACM) for		T., and Harrison, E., "Generalized Multiprotocol
	the Simple Network Management Protocol		Label Switching (GMPLS) Label Switching Router
	(SNMP)", RFC 2575, April 1999.		(LSR) Management Information Base", draft-ietf-
			ccamp-gmpls-lsr-mib-01.txt, August 2003, work in
			progress.
	[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder,		[GMPLS-OSPF] Kompella, K., et al., "OSPF Extensions in Support
	J., Case, J., Rose, M., and S. Waldbusser,		of Generalized MPLS", draft-ietf-ccamp-ospf-gmpls-
	"Structure of Management Information		extensions-07.txt, May 2002, work in progress.
	Version 2 (SMIv2)", STD 58, RFC 2578, April
	1999.
	[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder,		11.2. Informational References
	J., Case, J., Rose, M., and S. Waldbusser,
	"Conformance Statements for SMIv2", STD 58,
	RFC 2580, April 1999.
	[RFC3031] Rosen, E., Viswanathan, A., and R. Callon,		[RFC2026] S. Bradner, "The Internet Standards Process --
	"Multiprotocol Label Switching		Revision 3", RFC 2026, October 1996.
	Architecture", RFC 3031, August 1999.
	[RFC3034] Conta, A., Doolan, P., Malis, A., "Use of		[RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP
	Label Switching on Frame Relay Networks		Applications", RFC 3413, December 2002.
	Specification", RFC 3034, January 2001.
	[RFC3035] Davie, B., Lawrence, J., McCloghrie, K.,		[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
	Rosen, E., Swallow, G., Rekhter, Y., and P.		"Introduction and Applicability Statements for
	Doolan, "MPLS using LDP and ATM VC		Internet-Standard Management Framework", RFC 3410,
	switching", RFC 3035, January 2001.		December 2002.
	[IANAFamily] Internet Assigned Numbers Authority (IANA),		[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
	ADDRESS FAMILY NUMBERS.		Architecture for Describing Simple Network
			Management Protocol (SNMP) Management Frameworks",
			RFC 3411, December 2002.
	14. Authors' Addresses		12. Authors' Addresses
	Thomas D. Nadeau		Thomas D. Nadeau
	Cisco Systems, Inc.		Cisco Systems, Inc.
	300 Apollo Drive		300 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
	Cheenu Srinivasan		Cheenu Srinivasan
	Parama Networks, Inc.		Bloomberg L.P.
	1030 Broad Street		499 Park Ave.,
	Shrewsbury, NJ 07702		New York, NY 10022
	Phone: +1-732-544-9120 x731		Phone: +1-212-893-3682
	Email: cheenu@paramanet.com		Email: cheenu@bloomberg.net
	Adrian Farrel		Adrian Farrel
	Movaz Networks, Inc.		Old Dog Consulting
	7926 Jones Branch Drive, Suite 615		Phone: +44-(0)-1978-860944
	McLean VA, 22102 USA		Email: adrian@olddog.co.uk
	Phone: +1-703-847-1867
	Email: afarrel@movaz.com
	Edward Harrison		Tim Hall
	Data Connection Ltd.		Data Connection Ltd.
	100 Church Street		100 Church Street
	Enfield, Middlesex		Enfield, Middlesex
	EN2 6BQ, UK		EN2 6BQ, UK
	Phone: +44 20 8366 1177		Phone: +44 20 8366 1177
	Email: eph@dataconnection.com		Email: timhall@dataconnection.com
	Tim Hall		Ed Harrison
	Data Connection Ltd.		Data Connection Ltd.
	100 Church Street		100 Church Street
	Enfield, Middlesex		Enfield, Middlesex
	EN2 6BQ, UK		EN2 6BQ, UK
	Phone: +44 20 8366 1177		Phone: +44 20 8366 1177
	Email: timhall@dataconnection.com		Email: ed.harrison@dataconnection.com
	15. Full Copyright Statement		13. Full Copyright Statement
	Copyright (C) The Internet Society (2002). All Rights		Copyright (C) The Internet Society (2003). All Rights Reserved.
	Reserved.		This document and translations of it may be copied and furnished to
			others, and derivative works that comment on or otherwise explain it
			or assist in its implementation may be prepared, copied, published
			and distributed, in whole or in part, without restriction of any
			kind, provided that the above copyright notice and this paragraph are
			included on all such copies and derivative works. However, this
			document itself may not be modified in any way, such as by removing
			the copyright notice or references to the Internet Society or other
			Internet organizations, except as needed for the purpose of
			developing Internet standards in which case the procedures for
			copyrights defined in the Internet Standards process must be
			followed, or as required to translate it into languages other than
			English.
	This document and translations of it may be copied and		The limited permissions granted above are perpetual and will not be
	furnished to others, and derivative works that comment on		revoked by the Internet Society or its successors or assigns. This
	or otherwise explain it or assist in its implementation		document and the information contained herein is provided on an "AS
	may be prepared, copied, published and distributed, in		IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
	whole or in part, without restriction of any kind,		FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
	provided that the above copyright notice and this		LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL
	paragraph are included on all such copies and derivative		NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY
	works. However, this document itself may not be modified		OR FITNESS FOR A PARTICULAR PURPOSE.
	in any way, such as by removing the copyright notice or
	references to the Internet Society or other Internet
	organizations, except as needed for the purpose of
	developing Internet standards in which case the
	procedures for copyrights defined in the Internet
	Standards process must be followed, or as required to
	translate it into languages other than English.
	The limited permissions granted above are perpetual and		14. Intellectual Property Notice
	will not be revoked by the Internet Society or its
	successors or assigns. This document and the information		The IETF takes no position regarding the validity or scope of any
	contained herein is provided on an "AS IS" basis and THE		intellectual property or other rights that might be claimed to
	INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE		pertain to the implementation or use of the technology described in
	DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING		this document or the extent to which any license under such rights
	BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		might or might not be available; neither does it represent that it
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY		has made any effort to identify any such rights. Information on the
	IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A		IETF's procedures with respect to rights in standards-track and
	PARTICULAR PURPOSE.		standards-related documentation can be found in BCP-11 [RFC2028].
			Copies of claims of rights made available for publication and any
			assurances of licenses to be made available, or the result of an
			attempt made to obtain a general license or permission for the use
			of such proprietary rights by implementers or users of this
			specification can be obtained from the IETF Secretariat.
			The IETF invites any interested party to bring to its attention any
			copyrights, patents or patent applications, or other proprietary
			rights that may cover technology that may be required to practice
			this standard. Please address the information to the IETF Executive
			Director.
			15. Changes and Pending Work
			This section to be removed before the draft progresses to RFC.
			15.1. Pending Work
			The following work items have been identified for this draft. They
			will be addressed in a future version.
			- Clarify which objects can be modified when rowStatus and
			adminStatus are set to active
			- Sort out conformance statement which is a mess
			- Expand conformance statements to give one for monitoring only,
			and one for monitoring and control.
			- Bring references up to date, include all drafts referenced from
			this document, and exclude those that are not referenced.
			- Consider a way to expose tunnel head, tunnel tail, and tunnel
			transit entries through distinct indexing or tables.
			- Provide support for configuring tunnel resources in GMPLS
			systems. For example, SONET/SDH or G.709. This might be done
			through an arbitrary RowPointer to an external MIB.
			- Link Ids in EROs and RROs for use of bundled links.
			- Crankback request and reported information.
			- Control and reporting of upstream and downstream Notify
			Recipients.
			- Add support for control and reporting of GMPLS Administrative
			Status object.
			- Add support for IF_ID control and error reporting.
			- Add support for selection and configuration of restart options.
			- Update enumerated types in line with latest GMPLS drafts. Examine
			how these can be managed by IANA.
			- Resolve ownership of enumerated types that are also defined in
			GMPLS or routing drafts. These could be owned by IANA, imported
			from another MIB, or manually kept in step here. If they are not
			maintained externally then they are likely to diverge and MIB
			implementations will need to provide mappings.
			- Update examples.
			- Update MIB description in section 5.
			- Update in-line references.
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/