draft-ietf-mpls-tp-te-mib-08.txt		draft-ietf-mpls-tp-te-mib-09.txt
	Network Working Group		Network Working Group
	INTERNET-DRAFT M.Venkatesan		INTERNET-DRAFT M.Venkatesan
	Intended Status: Standards Track Dell Inc.		Intended Status: Standards Track Dell Inc.
	Expires: November 7, 2014 Kannan KV Sampath		Expires: March 26, 2015 Kannan KV Sampath
	Redeem		Redeem
	Sam K. Aldrin		Sam K. Aldrin
	Huawei Technologies		Huawei Technologies
	Thomas D. Nadeau		Thomas D. Nadeau
	Brocade		Brocade
	May 6, 2014		September 22, 2014
	MPLS-TP Traffic Engineering (TE) Management Information Base (MIB)		MPLS-TP Traffic Engineering (TE) Management Information Base (MIB)
	draft-ietf-mpls-tp-te-mib-08.txt		draft-ietf-mpls-tp-te-mib-09.txt
	Abstract		Abstract
	This memo defines a portion of the Management Information Base (MIB)		This memo defines a portion of the Management Information Base (MIB)
	for use with network management protocols in the Internet community.		for use with network management protocols in the Internet community.
	In particular, it describes additional managed objects of Tunnels,		In particular, it describes additional managed objects of Tunnels,
	Identifiers, Label Switching Router and Textual conventions to		Identifiers, Label Switching Router and Textual conventions to
	support Multiprotocol Label Switching (MPLS) MIB modules for		support Multiprotocol Label Switching (MPLS) MIB modules for
	transport networks.		transport networks.
	skipping to change at page 1, line 48		skipping to change at page 1, line 48
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on November 7, 2014.		This Internet-Draft will expire on March 26, 2015.
	Copyright and License Notice		Copyright and License Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 38		skipping to change at page 2, line 38
	5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6		5. Feature List . . . . . . . . . . . . . . . . . . . . . . . . . 6
	6. Brief description of MIB modules . . . . . . . . . . . . . . . 7		6. Brief description of MIB modules . . . . . . . . . . . . . . . 7
	6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 7		6.1. mplsTunnelExtNodeConfigTable . . . . . . . . . . . . . . . 7
	6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 8		6.2. mplsTunnelExtNodeIpMapTable . . . . . . . . . . . . . . . . 8
	6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 8		6.3. mplsTunnelExtNodeIccMapTable . . . . . . . . . . . . . . . 8
	6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 9		6.4. mplsTunnelExtTable . . . . . . . . . . . . . . . . . . . . 9
	6.5 MPLS-TC-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9		6.5 MPLS-TC-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9
	6.6 MPLS-ID-STD-MIB . . . . . . . . . . . . . . . . . . . . . . 9		6.6 MPLS-ID-STD-MIB . . . . . . . . . . . . . . . . . . . . . . 9
	6.7 MPLS-LSR-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9		6.7 MPLS-LSR-EXT-STD-MIB . . . . . . . . . . . . . . . . . . . . 9
	7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 9		7. MIB Module Interdependencies . . . . . . . . . . . . . . . . . 9
	8. Dependencies between MIB Module Tables . . . . . . . . . . . . 10		8. Dependencies between MIB Module Tables . . . . . . . . . . . . 11
	9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 11		9. Example of MPLS-TP Tunnel Setup . . . . . . . . . . . . . . . . 12
	9.1. Example of MPLS-TP static co-routed bidirectional tunnel		9.1. Example of MPLS-TP static co-routed bidirectional tunnel
	setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 13		setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
	9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 13		9.1.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 14
	9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 13		9.1.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 14
	9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 14		9.1.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 15
	9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 14		9.1.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 15
	9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 15		9.1.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 16
	9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 15		9.1.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 16
	9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 15		9.1.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 16
	9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 15		9.1.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 16
	9.2. Example of MPLS-TP static associated bidirectional tunnel		9.2. Example of MPLS-TP static associated bidirectional tunnel
	setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 16		setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
	9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 16		9.2.1. Forward direction mplsTunnelEntry . . . . . . . . . . . 17
	9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 17		9.2.2. Forward direction mplsTunnelExtEntry . . . . . . . . . 18
	9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 17		9.2.3. Forward direction mplsOutSegmentTable . . . . . . . . . 18
	9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 17		9.2.4. Forward direction mplsXCEntry . . . . . . . . . . . . . 18
	9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 18		9.2.5. Forward direction mplsXCExtEntry . . . . . . . . . . . 19
	9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 18		9.2.6. Reverse direction mplsTunnelEntry . . . . . . . . . . . 19
	9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 19		9.2.7. Reverse direction mplsTunnelExtEntry . . . . . . . . . 20
	9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 19		9.2.8. Reverse direction mplsInSegmentEntry . . . . . . . . . 20
	9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 19		9.2.9. Reverse direction mplsXCEntry . . . . . . . . . . . . . 20
	9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 20		9.2.10. Reverse direction mplsXCExtEntry . . . . . . . . . . . 21
	9.3. Example of MPLS-TP signaled co-routed bidirectional		9.3. Example of MPLS-TP signaled co-routed bidirectional
	tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 20		tunnel setup . . . . . . . . . . . . . . . . . . . . . . . 21
	9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 20		9.3.1. mplsTunnelEntry . . . . . . . . . . . . . . . . . . . . 21
	9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 21		9.3.2. mplsTunnelExtEntry . . . . . . . . . . . . . . . . . . 22
	9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 22		9.3.3. Forward direction mplsOutSegmentEntry . . . . . . . . . 23
	9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 22		9.3.4. Reverse direction mplsInSegmentEntry . . . . . . . . . 23
	9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 22		9.3.5. Forward direction mplsXCEntry . . . . . . . . . . . . . 23
	9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 22		9.3.6. Reverse direction mplsXCEntry . . . . . . . . . . . . . 23
	9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 22		9.3.7. Forward direction mplsXCExtEntry . . . . . . . . . . . 23
	9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 22		9.3.8. Reverse direction mplsXCExtEntry . . . . . . . . . . . 23
	10. MPLS Textual Convention Extension MIB definitions . . . . . . 22		10. MPLS Textual Convention Extension MIB definitions . . . . . . 23
	11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 25		11. MPLS Identifier MIB definitions . . . . . . . . . . . . . . . 26
	12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 30		12. MPLS LSR Extension MIB definitions . . . . . . . . . . . . . . 31
	13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 35		13. MPLS Tunnel Extension MIB definitions . . . . . . . . . . . . 36
	14. Security Consideration . . . . . . . . . . . . . . . . . . . . 53		14. Security Consideration . . . . . . . . . . . . . . . . . . . . 54
	15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54		15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55
	15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 54		15.1. IANA Considerations for MPLS-TC-EXT-STD-MIB . . . . . . . 55
	15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 54		15.2. IANA Considerations for MPLS-ID-STD-MIB . . . . . . . . . 55
	15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 54		15.3. IANA Considerations for MPLS-LSR-EXT-STD-MIB . . . . . . . 55
	15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 55		15.4. IANA Considerations for MPLS-TE-EXT-STD-MIB . . . . . . . 56
	16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 55		16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56
	16.1. Normative References . . . . . . . . . . . . . . . . . . . 55		16.1. Normative References . . . . . . . . . . . . . . . . . . . 56
	16.2. Informative References . . . . . . . . . . . . . . . . . 55		16.2. Informative References . . . . . . . . . . . . . . . . . 56
	17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 56		17. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57
	18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 56		18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 57
	1. Introduction		1. Introduction
	This memo defines a portion of the Management Information Base (MIB) for		This memo defines a portion of the Management Information Base (MIB) for
	use with network management protocols in the Internet community. In		use with network management protocols in the Internet community. In
	particular, it describes additional managed objects of Tunnels,		particular, it describes additional managed objects of Tunnels,
	Identifiers, Label Switching Router and Textual conventions to support		Identifiers, Label Switching Router and Textual conventions to support
	Multiprotocol Label Switching (MPLS) MIB modules for transport networks.		Multiprotocol Label Switching (MPLS) MIB modules for transport networks.
	MIB modules defined in this document extends the existing MPLS MIB		MIB modules defined in this document extends the existing MPLS MIB
	objects in such a way that they support MPLS-TP and Non-MPLS-TP networks		objects in such a way that they support MPLS-TP and Non-MPLS-TP networks
	skipping to change at page 8, line 12		skipping to change at page 8, line 12
	The mplsTunnelExtNodeConfigTable is used to assign a local identifier		The mplsTunnelExtNodeConfigTable is used to assign a local identifier
	for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID		for a given ICC_Operator_ID::Node_ID or Global_ID::Node_ID
	combination as defined in [RFC6923] and [RFC6370] respectively. The		combination as defined in [RFC6923] and [RFC6370] respectively. The
	CC is a string of two alphabetic characters represented with upper		CC is a string of two alphabetic characters represented with upper
	case letters (i.e., A-Z). The ICC is a string of one to six		case letters (i.e., A-Z). The ICC is a string of one to six
	characters, each character being either alphabetic (i.e. A-Z) or		characters, each character being either alphabetic (i.e. A-Z) or
	numeric (i.e. 0-9) characters. Alphabetic characters in the ICC		numeric (i.e. 0-9) characters. Alphabetic characters in the ICC
	should be represented with upper case letters. In the IP compatible		should be represented with upper case letters. In the IP compatible
	mode, Global_ID::Node_ID, is used to uniquely identify a node. For		mode, Global_ID::Node_ID, is used to uniquely identify a node. For
	each ICC_Operator_ID::Node_ID or Global_ID::Node_ID, there is a		each ICC_Operator_ID::Node_ID or Global_ID::Node_ID, there is a
	unique entry in the table representing a node. Every node is assigned		unique entry in the table representing a node. As the regular TE
	a local identifier within a range of 0 to 16777215. This local		tunnels use IP address as LSR ID, the local identifier should be
	identifier is used for indexing into mplsTunnelTable as		below the first valid IP address, which is 16777216[1.0.0.0]. Every
			node is assigned a local identifier within a range of 0 to 16777215.
			This local identifier is used for indexing into mplsTunnelTable as
	mplsTunnelIngressLSRId and mplsTunnelEgressLSRId.		mplsTunnelIngressLSRId and mplsTunnelEgressLSRId.
	For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel		For IP compatible environment, MPLS-TP tunnel is indexed by Tunnel
	Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination		Index, Tunnel Instance, Source Global_ID, Source Node_ID, Destination
	Global_ID and Destination Node_ID.		Global_ID and Destination Node_ID.
	For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index,		For ICC based environment, MPLS-TP tunnel is indexed by Tunnel Index,
	Tunnel Instance, Source CC, Source ICC, Source Node_ID, Destination		Tunnel Instance, Source CC, Source ICC, Source Node_ID, Destination
	CC, Destination ICC and Destination Node_ID.		CC, Destination ICC and Destination Node_ID.
	As mplsTunnelTable is indexed by mplsTunnelIndex,		As mplsTunnelTable is indexed by mplsTunnelIndex,
	mplsTunnelInstance, mplsTunnelIngressLSRId, and		mplsTunnelInstance, mplsTunnelIngressLSRId, and
	mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be		mplsTunnelEgressLSRId, the MPLS-TP tunnel identifiers cannot be
	used directly.		used directly.
	The mplsTunnelExtNodeConfigTable will be used to store an entry for		The mplsTunnelExtNodeConfigTable will be used to store an entry for
	ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local		ICC_Operator_ID::Node_ID or Global_ID::Node_ID with a local
	identifier to be used as LSR ID in mplsTunnelTable. As the regular TE		identifier to be used as LSR ID in mplsTunnelTable.
	tunnels use IP address as LSR ID, the local identifier should be
	below the first valid IP address, which is 16777216[1.0.0.0].
	6.2. mplsTunnelExtNodeIpMapTable		6.2. mplsTunnelExtNodeIpMapTable
	The read-only mplsTunnelExtNodeIpMapTable is used to query the local		The read-only mplsTunnelExtNodeIpMapTable is used to query the local
	identifier assigned and stored in mplsTunnelExtNodeConfigTable for		identifier assigned and stored in mplsTunnelExtNodeConfigTable for
	a given Global_ID::Node_ID. In order to query the local identifier,		a given Global_ID::Node_ID. In order to query the local identifier,
	in the IP compatible mode, this table is indexed with		in the IP compatible mode, this table is indexed with
	Global_ID::Node_ID. In the IP compatible mode for a TP tunnel,		Global_ID::Node_ID. In the IP compatible mode for a TP tunnel,
	Global_ID::Node_ID is used.		Global_ID::Node_ID is used.
	skipping to change at page 9, line 21		skipping to change at page 9, line 21
	while indexing mplsTunnelTable.		while indexing mplsTunnelTable.
	6.4. mplsTunnelExtTable		6.4. mplsTunnelExtTable
	This table sparsely extends the mplsTunnelTable in order to support		This table sparsely extends the mplsTunnelTable in order to support
	MPLS-TP tunnels with additional objects. All the additional		MPLS-TP tunnels with additional objects. All the additional
	attributes specific to supporting TP tunnel are contained in this		attributes specific to supporting TP tunnel are contained in this
	extended table and could be accessed with the mplsTunnelTable		extended table and could be accessed with the mplsTunnelTable
	indices.		indices.
			The gmplsTunnelReversePerfTable [RFC4802] should be used to provide
			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.
	6.5 MPLS-TC-EXT-STD-MIB		6.5 MPLS-TC-EXT-STD-MIB
	This MIB module contains Textual Conventions for LSPs of MPLS based		This MIB module contains Textual Conventions for LSPs of MPLS based
	transport networks.		transport networks.
	6.6 MPLS-ID-STD-MIB		6.6 MPLS-ID-STD-MIB
	This MIB module contains generic object definitions for MPLS Traffic		This MIB module contains generic object definitions for MPLS Traffic
	Engineering in transport networks.		Engineering in transport networks.
	skipping to change at page 33, line 29		skipping to change at page 34, line 29
	::= { mplsXCExtEntry 1 }		::= { mplsXCExtEntry 1 }
	mplsXCExtOppositeDirXCPtr OBJECT-TYPE		mplsXCExtOppositeDirXCPtr OBJECT-TYPE
	SYNTAX RowPointer		SYNTAX RowPointer
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object indicates the pointer to the opposite		"This object indicates the pointer to the opposite
	direction XC entry. This object cannot be modified if		direction XC entry. This object cannot be modified if
	mplsXCRowStatus for the corresponding entry in the		mplsXCRowStatus for the corresponding entry in the
	mplsXCTable is active(1)."		mplsXCTable is active(1). If this pointer is not set or
			removed, mplsXCOperStatus should be set to down(2)."
	REFERENCE		REFERENCE
	"1. Multiprotocol Label Switching (MPLS) Label Switching		"1. Multiprotocol Label Switching (MPLS) Label Switching
	Router (LSR) Management Information Base (MIB), RFC 3813."		Router (LSR) Management Information Base (MIB), RFC 3813."
	::= { mplsXCExtEntry 2 }		::= { mplsXCExtEntry 2 }
	mplsLsrExtCompliances		mplsLsrExtCompliances
	OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 }		OBJECT IDENTIFIER ::= { mplsLsrExtConformance 1 }
	mplsLsrExtGroups		mplsLsrExtGroups
	OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 }		OBJECT IDENTIFIER ::= { mplsLsrExtConformance 2 }
End of changes. 12 change blocks.
	57 lines changed or deleted		63 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/