draft-ietf-mpls-tp-mib-management-overview-05.txt		draft-ietf-mpls-tp-mib-management-overview-06.txt
	Network Working Group D. King (Editor)		Network Working Group D. King (Editor)
	Internet-Draft Old Dog Consulting		Internet-Draft Old Dog Consulting
	Intended status: Informational M. Venkatesan (Editor)		Intended status: Informational M. Venkatesan (Editor)
	Expires: February 5, 2012 Aricent		Expires: June 30, 2012 Aricent
	August 5, 2011		January 31, 2012
	Multiprotocol Label Switching Transport Profile (MPLS-TP)		Multiprotocol Label Switching Transport Profile (MPLS-TP)
	MIB-based Management Overview		MIB-based Management Overview
	draft-ietf-mpls-tp-mib-management-overview-05.txt		draft-ietf-mpls-tp-mib-management-overview-06.txt
	Abstract		Abstract
	A range of Management Information Base (MIB) modules has been		A range of Management Information Base (MIB) modules has been
	developed to help model and manage the various aspects of		developed to help model and manage the various aspects of
	Multiprotocol Label Switching (MPLS) networks. These MIB modules are		Multiprotocol Label Switching (MPLS) networks. These MIB modules are
	defined in separate documents that focus on the specific areas of		defined in separate documents that focus on the specific areas of
	responsibility of the modules that they describe.		responsibility of the modules that they describe.
	The MPLS Transport Profile (MPLS-TP) is a profile of MPLS		The MPLS Transport Profile (MPLS-TP) is a profile of MPLS
	skipping to change at page 1, line 50		skipping to change at page 1, line 50
	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 February 5, 2012.		This Internet-Draft will expire on June 30, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2012 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 2, line 47		skipping to change at page 2, line 47
	4.2.9. Fault Management and Performance Management......10		4.2.9. Fault Management and Performance Management......10
	4.2.10. MIB Module Interdependencies....................11		4.2.10. MIB Module Interdependencies....................11
	4.2.11. Dependencies on External MIB Modules............13		4.2.11. Dependencies on External MIB Modules............13
	5. Applicability of MPLS MIB modules to MPLS-TP.................14		5. Applicability of MPLS MIB modules to MPLS-TP.................14
	5.1 MPLS-TP Tunnel...........................................14		5.1 MPLS-TP Tunnel...........................................14
	5.1.1 Gap Analysis.......................................14		5.1.1 Gap Analysis.......................................14
	5.1.2 Recommendations....................................15		5.1.2 Recommendations....................................15
	5.2 MPLS-TP Pseudowire.......................................15		5.2 MPLS-TP Pseudowire.......................................15
	5.2.1 Gap Analysis.......................................15		5.2.1 Gap Analysis.......................................15
	5.2.2 Recommendations....................................15		5.2.2 Recommendations....................................15
	5.3 MPLS-TP Sections.........................................16		5.3 MPLS-TP Sections.........................................15
	5.3.1 Gap Analysis.......................................16		5.3.1 Gap Analysis.......................................15
	5.3.2 Recommendations....................................16		5.3.2 Recommendations....................................15
	5.4 MPLS-TP OAM..............................................16		5.4 MPLS-TP OAM..............................................16
	5.4.1 Gap Analysis.......................................16		5.4.1 Gap Analysis.......................................16
	5.4.2 Recommendations....................................16		5.4.2 Recommendations....................................16
	5.5 MPLS-TP Protection Switching and Recovery................16		5.5 MPLS-TP Protection Switching and Recovery................16
	5.5.1 Gap Analysis.......................................16		5.5.1 Gap Analysis.......................................16
	5.5.2 Recommendations....................................17		5.5.2 Recommendations....................................17
	5.6 MPLS-TP Interfaces.......................................17		5.6 MPLS-TP Interfaces.......................................17
	5.6.1 Gap Analysis.......................................17		5.6.1 Gap Analysis.......................................17
	5.6.2 Recommendations....................................17		5.6.2 Recommendations....................................17
	6. An Introduction to the MPLS-TP MIB Modules...................17		6. An Introduction to the MPLS-TP MIB Modules...................17
	6.1 MPLS-TP MIB Modules......................................18		6.1 MPLS-TP MIB Modules......................................17
	6.1.1 Structure of the MPLS-TP MIB OID Tree.............18		6.1.1 Structure of the MPLS-TP MIB OID Tree.............17
	6.1.2 Textual Conventions for MPLS-TP...................18		6.1.2 Textual Conventions for MPLS-TP...................18
	6.1.3 Identifiers for MPLS-TP...........................18		6.1.3 Identifiers for MPLS-TP...........................18
	6.1.4 LSR MIB Extensions for MPLS-TP....................18		6.1.4 LSR MIB Extensions for MPLS-TP....................18
	6.1.5 Tunnel Extensions for MPLS-TP.....................19		6.1.5 Tunnel Extensions for MPLS-TP.....................18
	6.2 PWE3 MIB Modules for MPLS-TP.............................19		6.2 PWE3 MIB Modules for MPLS-TP.............................19
	6.2.1 Structure of the PWE3 MIB OID Tree for MPLS-TP....19		6.2.1 Structure of the PWE3 MIB OID Tree for MPLS-TP....19
	6.2.2 Pseudowire Textual Conventions for MPLS-TP........19		6.2.2 Pseudowire Textual Conventions for MPLS-TP........19
	6.2.3 Pseudowire Extensions for MPLS-TP.................19		6.2.3 Pseudowire Extensions for MPLS-TP.................19
	6.2.4 Pseudowire MPLS Extensions for MPLS-TP............19		6.2.4 Pseudowire MPLS Extensions for MPLS-TP............19
	6.3 OAM MIB Modules for MPLS-TP..............................20		6.3 OAM MIB Modules for MPLS-TP..............................20
	6.3.1 Structure of the OAM MIB OID Tree for MPLS-TP.....20		6.3.1 Structure of the OAM MIB OID Tree for MPLS-TP.....20
	6.3.2 BFD MIB module....................................20		6.3.2 BFD MIB module....................................20
	6.3.3 Common OAM MIB modules............................20		6.3.3 Common OAM MIB modules............................20
	6.4. Protection Switching and Recovery MIB Modules		6.4. Protection Switching and Recovery MIB Modules
	for MPLS-TP.............................................20		for MPLS-TP.............................................20
	6.4.1 Structure of the Protection Switching		6.4.1 Structure of the Protection Switching
	and Recovery MIB OID Tree for MPLS-TP.............21		and Recovery MIB OID Tree for MPLS-TP.............20
	6.4.2 Linear Protection Switching MIB module............21		6.4.2 Linear Protection Switching MIB module............21
	6.4.3 Ring Protection Switching MIB module..............21		6.4.3 Ring Protection Switching MIB module..............21
	6.4.4 Mesh Protection Switching MIB module..............21		6.4.4 Mesh Protection Switching MIB module..............21
	7. Management Options...........................................21		7. Management Options...........................................21
	8. Security Considerations......................................21		8. Security Considerations......................................21
	9. IANA Considerations..........................................22		9. IANA Considerations..........................................22
	10. Acknowledgements............................................22		10. Acknowledgements............................................22
	11. References..................................................22		11. References..................................................22
	11.1. Normative References...................................22		11.1. Normative References...................................22
	11.2. Informational References...............................24		11.2. Informational References...............................24
	skipping to change at page 5, line 9		skipping to change at page 5, line 9
	3. The SNMP Management Framework		3. The SNMP Management Framework
	Managed objects are accessed via a virtual information store, termed		Managed objects are accessed via a virtual information store, termed
	the Management Information Base or MIB. MIB objects are generally		the Management Information Base or MIB. MIB objects are generally
	accessed through the Simple Network Management Protocol (SNMP).		accessed through the Simple Network Management Protocol (SNMP).
	Objects in the MIB are defined using the mechanisms defined in the		Objects in the MIB are defined using the mechanisms defined in the
	Structure of Management Information (SMI).		Structure of Management Information (SMI).
	For a detailed overview of the documents that describe the current		For a detailed overview of the documents that describe the current
	Internet-Standard Management Framework, please refer to section 7 of		Internet-Standard Management Framework, please refer to Section 7. of
	RFC 3410 [RFC3410].		[RFC3410].
	This document discusses MIB modules that are compliant to the SMIv2,		This document discusses MIB modules that are compliant to the SMIv2,
	which is described in [RFC2578], [RFC2579] and [RFC2580].		which is described in [RFC2578], [RFC2579] and [RFC2580].
	4. Overview of Existing Work		4. Overview of Existing Work
	This section describes the existing tools and techniques for		This section describes the existing tools and techniques for
	managing and modeling MPLS networks, devices, and protocols. It is		managing and modeling MPLS networks, devices, and protocols. It is
	intended to provide a description of the tool kit that is already		intended to provide a description of the tool kit that is already
	available.		available.
	skipping to change at page 5, line 52		skipping to change at page 5, line 52
	[RFC5654] describes the requirements for the optional use of a		[RFC5654] describes the requirements for the optional use of a
	control plane to support dynamic provisioning of MPLS-TP transport		control plane to support dynamic provisioning of MPLS-TP transport
	paths. The MPLS-TP LSP control plane is based on GMPLS and is		paths. The MPLS-TP LSP control plane is based on GMPLS and is
	described in [RFC3945].		described in [RFC3945].
	4.2. An Introduction to the MPLS and Pseudowire MIB Modules		4.2. An Introduction to the MPLS and Pseudowire MIB Modules
	4.2.1. Structure of the MPLS MIB OID Tree		4.2.1. Structure of the MPLS MIB OID Tree
	The MPLS MIB OID tree has the following structure. It is based on the		The MPLS MIB Object Identifiers (OID) tree has the following
	tree originally set out in section 4.1 of [RFC4221] and has been		structure. It is based on the tree originally set out in section
	enhanced to include other relevant MIB modules.		4.1 of [RFC4221] and has been enhanced to include other relevant MIB
			modules.
	mib-2 -- RFC 2578 [RFC2578]		mib-2 -- RFC 2578 [RFC2578]
	|		|
	+-transmission		+-transmission
	| |		| |
	| +- mplsStdMIB		| +- mplsStdMIB
	| | |		| | |
	| | +- mplsTCStdMIB -- MPLS-TC-STD-MIB [RFC3811]		| | +- mplsTCStdMIB -- MPLS-TC-STD-MIB [RFC3811]
	| | |		| | |
	| | +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB [RFC3813]		| | +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB [RFC3813]
	skipping to change at page 7, line 14		skipping to change at page 7, line 14
	MPLS-TC-STD-MIB [RFC3811], GMPLS-TC-STD-MIB [RFC4801],		MPLS-TC-STD-MIB [RFC3811], GMPLS-TC-STD-MIB [RFC4801],
	IANA-GMPLS-TC-MIB [RFC4802] and PW-TC-STD-MIB [RFC5542] contains the		IANA-GMPLS-TC-MIB [RFC4802] and PW-TC-STD-MIB [RFC5542] contains the
	Textual Conventions for MPLS and GMPLS networks. These Textual		Textual Conventions for MPLS and GMPLS networks. These Textual
	Conventions should be imported by MIB modules which manage MPLS		Conventions should be imported by MIB modules which manage MPLS
	and GMPLS networks. Section 4.2.11. highlights dependencies on		and GMPLS networks. Section 4.2.11. highlights dependencies on
	additional external MIB modules		additional external MIB modules
	4.2.3. Label Switched Path (LSP) Modules		4.2.3. Label Switched Path (LSP) Modules
	An LSP is a path over which a labeled packet travels across the		An LSP is a path over which a labeled packet travels across the
	sequence of LSRs for a given FEC. When a packet, with or without		sequence of LSRs for a given Forward Equivalence Class (FEC). When a
	label, arrives at an ingress LER of an LSP, it is encapsulated with		packet, with or without label, arrives at an ingress LER of an LSP,
	the label corresponding to the FEC and sent across the LSP. The		it is encapsulated with the label corresponding to the FEC and sent
	labeled packet traverses across the LSRs and arrives at the egress		across the LSP. The labeled packet traverses across the LSRs and
	LER of the LSP, where, it gets forwarded depending on the packet type		arrives at the egress LER of the LSP, where, it gets forwarded
	it came with. LSPs could be nested using label stacking, such that,		depending on the packet type it came with. LSPs could be nested using
	an LSP could traverse over another LSP. A further description of		label stacking, such that, an LSP could traverse over another LSP. A
	an LSP can be found in [RFC3031].		further description of an LSP can be found in [RFC3031].
	MPLS-LSR-STD-MIB [RFC3813] describes the required objects to define		MPLS-LSR-STD-MIB [RFC3813] describes the required objects to define
	the LSP.		the LSP.
	4.2.4. Label Edge Router (LER) Modules		4.2.4. Label Edge Router (LER) Modules
	Ingress and Egress LSRs of an LSP are known as Label Edge Routers.		Ingress and Egress LSRs of an LSP are known as Label Edge Routers
	An ingress LER takes the incoming unlabeled or labeled packets and		(LER). An ingress LER takes the incoming unlabeled or labeled packets
	encapsulates it with the corresponding label of the LSP it		and encapsulates it with the corresponding label of the LSP it
	represents, and forwards it, over to the adjacent LSR of the LSP.		represents, and forwards it, over to the adjacent LSR of the LSP.
	Each FEC is mapped to a label forwarding entry, so that packet could		Each FEC is mapped to a label forwarding entry, so that packet could
	be encapsulated with one or more label entries, referred as label		be encapsulated with one or more label entries, referred as label
	stack.		stack.
	The packet traverses across the LSP, and upon reaching the Egress		The packet traverses across the LSP, and upon reaching the Egress
	LER, further action will be taken to handle the packet, depending on		LER, further action will be taken to handle the packet, depending on
	the packet it received. MPLS Architecture [RFC3031] details		the packet it received. MPLS Architecture [RFC3031] details
	the functionality of an Ingress and Egress LERs.		the functionality of an Ingress and Egress LERs.
	skipping to change at page 8, line 14		skipping to change at page 8, line 16
	MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for modeling		MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for modeling
	a Multiprotocol Label Switching (MPLS) [RFC3031] LSR.		a Multiprotocol Label Switching (MPLS) [RFC3031] LSR.
	MPLS-LSR-STD-MIB [RFC3813] contains the managed objects to maintain		MPLS-LSR-STD-MIB [RFC3813] contains the managed objects to maintain
	mapping of in-segments to out-segments.		mapping of in-segments to out-segments.
	4.2.6. Pseudowire Modules		4.2.6. Pseudowire Modules
	The PW (Pseudowire) MIB architecture provides a layered modular model		The PW (Pseudowire) MIB architecture provides a layered modular model
	into which any supported emulated service such as Frame Relay, ATM,		into which any supported emulated service such as Frame Relay, ATM,
	Ethernet, TDM and SONET/SDH can be connected to any supported packet		Ethernet, TDM and SONET/SDH can be connected to any supported Packet
	switched network (PSN) type. This MIB architecture is modeled based		Switched Network (PSN) type. This MIB architecture is modeled based
	on PW3 architecture [RFC3985].		on PW3 architecture [RFC3985].
	Emulated Service Layer, Generic PW Layer and PSN VC Layer constitute		Emulated Service Layer, Generic PW Layer and PSN VC Layer constitute
	the different layers of the model. A combination of the MIB modules		the different layers of the model. A combination of the MIB modules
	belonging to each layer provides the glue for mapping the emulated		belonging to each layer provides the glue for mapping the emulated
	service onto the native PSN service. At least three MIB modules each		service onto the native PSN service. At least three MIB modules each
	belonging to a different layer are required to define a PW emulated		belonging to a different layer are required to define a PW emulated
	service.		service.
	o Service-Specific module is dependent on the emulated signal type		- Service-Specific module is dependent on the emulated signal type
	and helps in modeling emulated service layer.		and helps in modeling emulated service layer.
	PW-ENET-STD-MIB [RFC5603] describes a model for managing Ethernet		PW-ENET-STD-MIB [RFC5603] describes a model for managing Ethernet
	pseudowire services for transmission over a PSN. This MIB module is		pseudowire services for transmission over a PSN. This MIB module is
	generic and common to all types of PSNs supported in the Pseudowire		generic and common to all types of PSNs supported in the Pseudowire
	Emulation Edge-to-Edge (PWE3) architecture [RFC3985], which describes		Emulation Edge-to-Edge (PWE3) Architecture [RFC3985], which describes
	the transport and encapsulation of L1 and L2 services over supported		the transport and encapsulation of L1 and L2 services over supported
	PSN types.		PSN types.
	In particular, the MIB module associates a port or specific VLANs on		In particular, the MIB module associates a port or specific VLANs on
	top of a physical Ethernet port or a virtual Ethernet interface (for		top of a physical Ethernet port or a virtual Ethernet interface (for
	Virtual Private LAN Service (VPLS)) to a point-to-point PW. It is		Virtual Private LAN Service (VPLS)) to a point-to-point PW. It is
	complementary to the PW-STD-MIB [RFC5601], which manages the generic		complementary to the PW-STD-MIB [RFC5601], which manages the generic
	PW parameters common to all services, including all supported PSN		PW parameters common to all services, including all supported PSN
	types.		types.
	PW-TDM-MIB [RFC5604] describes a model for managing TDM pseudowires,		PW-TDM-MIB [RFC5604] describes a model for managing TDM pseudowires,
	i.e., TDM data encapsulated for transmission over a Packet Switched		i.e., TDM data encapsulated for transmission over a Packet Switched
	Network (PSN). The term TDM in this document is limited to the		Network (PSN). The term TDM in this document is limited to the
	scope of Plesiochronous Digital Hierarchy (PDH). It is currently		scope of Plesiochronous Digital Hierarchy (PDH). It is currently
	specified to carry any TDM Signals in either Structure Agnostic		specified to carry any TDM Signals in either Structure Agnostic
	Transport mode (E1, T1, E3, and T3) or in Structure Aware		Transport mode (E1, T1, E3, and T3) or in Structure Aware
	Transport mode (E1, T1, and NxDS0) as defined in the Pseudowire		Transport mode (E1, T1, and NxDS0) as defined in the Pseudowire
	Emulation Edge-to-Edge (PWE3) TDM Requirements document [RFC4197].		Emulation Edge-to-Edge (PWE3) TDM Requirements document [RFC4197].
	o Generic PW Module configures general parameters of the PW that are		- Generic PW Module configures general parameters of the PW that are
	common to all types of emulated services and PSN types.		common to all types of emulated services and PSN types.
	PW-STD-MIB [RFC5601] defines a MIB module that can be		PW-STD-MIB [RFC5601] defines a MIB module that can be
	used to manage pseudowire (PW) services for transmission over a		used to manage pseudowire (PW) services for transmission over a
	Packet Switched Network (PSN) [RFC3931] [RFC4447]. This MIB module		Packet Switched Network (PSN) [RFC3931] [RFC4447]. This MIB module
	provides generic management of PWs that is common to all types of		provides generic management of PWs that is common to all types of
	PSN and PW services defined by the IETF PWE3 Working Group.		PSN and PW services defined by the IETF PWE3 Working Group.
	o PSN-specific module associate the PW with one or more "tunnels"		- PSN-specific module associate the PW with one or more "tunnels"
	that carry the service over the PSN. There is a different module		that carry the service over the PSN. There is a different module
	for each type of PSN.		for each type of PSN.
	PW-MPLS-STD-MIB [RFC5602] describes a model for managing pseudowire		PW-MPLS-STD-MIB [RFC5602] describes a model for managing pseudowire
	services for transmission over different flavors of MPLS tunnels.		services for transmission over different flavors of MPLS tunnels.
	The general PW MIB module [RFC5601] defines the parameters global to		The general PW MIB module [RFC5601] defines the parameters global to
	the PW regardless of the underlying Packet Switched Network (PSN)		the PW regardless of the underlying Packet Switched Network (PSN)
	and emulated service. This document is applicable for PWs that use		and emulated service. This document is applicable for PWs that use
	MPLS PSN type in the PW-STD-MIB. Additionally this document describes		MPLS PSN type in the PW-STD-MIB. Additionally this document describes
	the MIB objects that define pseudowire association to the MPLS PSN,		the MIB objects that define pseudowire association to the MPLS PSN,
	skipping to change at page 9, line 48		skipping to change at page 9, line 51
	Multiprotocol Label Switching (MPLS) [RFC3031] based traffic		Multiprotocol Label Switching (MPLS) [RFC3031] based traffic
	engineering. This MIB module should be used in conjunction with the		engineering. This MIB module should be used in conjunction with the
	companion document [RFC3813] for MPLS based traffic engineering		companion document [RFC3813] for MPLS based traffic engineering
	configuration and management.		configuration and management.
	4.2.8. Resiliency		4.2.8. Resiliency
	The purpose of MPLS resiliency is to ensure minimal interruption to		The purpose of MPLS resiliency is to ensure minimal interruption to
	traffic when the failure occurs within the system or network.		traffic when the failure occurs within the system or network.
	Various components of MPLS resiliency solutions are,		Various components of MPLS resiliency solutions are;
	1) Graceful restart in LDP and RSVP-TE modules
	2) Make Before Break		1) Graceful restart in LDP and RSVP-TE modules,
	3) Protection Switching for LSPs		2) Make Before Break,
	4) Fast ReRoute for LSPs		3) Protection Switching for LSPs,
	5) PW redundancy		4) Fast ReRoute for LSPs,
			5) PW redundancy.
	The below modules only support the SNMP based MIB management		The below modules only support the SNMP based MIB management
	for MPLS resiliency.		for MPLS resiliency.
	MPLS Fast Reroute is a restoration network resiliency mechanism used		MPLS Fast Reroute (FRR) is a restoration network resiliency mechanism
	in MPLS TE to redirect the traffic onto the backup LSP's in 10s of		used in MPLS TE to redirect the traffic onto the backup LSP's in 10s
	milliseconds in case of link or node failure across the LSP.		of milliseconds in case of link or node failure across the LSP.
	MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]		MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
	contains objects that apply to any MPLS LSR implementing MPLS TE fast		contains objects that apply to any MPLS LSR implementing MPLS TE fast
	reroute functionality.		reroute functionality.
	MPLS-FRR-ONE2ONE-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]		MPLS-FRR-ONE2ONE-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
	contains objects that apply to one-to-one backup method.		contains objects that apply to one-to-one backup method.
	MPLS-FRR-FACILITY-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]		MPLS-FRR-FACILITY-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
	contains objects that apply to facility backup method.		contains objects that apply to facility backup method.
	skipping to change at page 14, line 4		skipping to change at page 14, line 4
	an entry in ifTable.		an entry in ifTable.
	The interrelation of entries in ifTable is defined by the Interfaces		The interrelation of entries in ifTable is defined by the Interfaces
	Stack Group defined in [RFC2863].		Stack Group defined in [RFC2863].
	The MPLS MIB modules have dependencies with the TE-LINK-STD-MIB		The MPLS MIB modules have dependencies with the TE-LINK-STD-MIB
	for maintaining the traffic engineering information.		for maintaining the traffic engineering information.
	The MPLS MIB modules depend on the constrained shortest path first		The MPLS MIB modules depend on the constrained shortest path first
	(CSPF) module to obtain the path required for an MPLS tunnel to reach		(CSPF) module to obtain the path required for an MPLS tunnel to reach
	the end point of the tunnel and BFD module to verify the data-plane		the end point of the tunnel and Bidirectional Forwarding Detection
	failures of LSPs and PWs.		(BFD) module to verify the data-plane failures of LSPs and PWs.
	Finally, all of the MIB modules import standard textual conventions		Finally, all of the MIB modules import standard textual conventions
	such as integers, strings, timestamps, etc., from the MIB modules in		such as integers, strings, timestamps, etc., from the MIB modules in
	which they are defined.		which they are defined.
	5. Applicability of MPLS MIB modules to MPLS-TP		5. Applicability of MPLS MIB modules to MPLS-TP
	This section highlights gaps in existing MPLS MIB modules in		This section highlights gaps in existing MPLS MIB modules in
	order to determine extensions or additional MIB modules that are		order to determine extensions or additional MIB modules that are
	required to support MPLS-TP in MPLS networks		required to support MPLS-TP in MPLS networks
	skipping to change at page 14, line 41		skipping to change at page 14, line 41
	reused for MPLS based transport network management.		reused for MPLS based transport network management.
	Fault management and performance management form key parts of		Fault management and performance management form key parts of
	the Operations, Administration, and Maintenance (OAM) function.		the Operations, Administration, and Maintenance (OAM) function.
	MPLS-TP OAM is described in [MPLS-TP-OAM-FWK].		MPLS-TP OAM is described in [MPLS-TP-OAM-FWK].
	5.1 MPLS-TP Tunnel		5.1 MPLS-TP Tunnel
	5.1.1 Gap Analysis		5.1.1 Gap Analysis
	MPLS-TP tunnel can be operated over IP and/or ICC environments,		MPLS-TP tunnel can be operated over IP and/or ITU-T Carrier Code
	below points capture the gaps in existing MPLS MIB modules		(ICC) environments, below points capture the gaps in existing MPLS
	for managing the MPLS-TP networks.		MIB modules for managing the MPLS-TP networks.
	- IP based environment		- IP based environment
	i. MPLS-TE-STD-MIB [RFC3812] does not support tunnel		i. MPLS-TE-STD-MIB [RFC3812] does not support tunnel
	Ingress/Egress identifier based on Global_ID and Node_ID		Ingress/Egress identifier based on Global_ID and Node_ID
	[MPLS-TP-IDENTIFIERS].		[RFC6370].
	ii. MPLS-TE-STD-MIB [RFC3812] does not support		ii. MPLS-TE-STD-MIB [RFC3812] does not support
	co-routed/associated bidirectional tunnel configurations.		co-routed/associated bidirectional tunnel configurations.
	- ICC based environment		- ICC based environment
	i. MPLS-TE-STD-MIB [RFC3812] does not support tunnel LSR		i. MPLS-TE-STD-MIB [RFC3812] does not support tunnel LSR
	identifier based on ICC.		identifier based on ICC.
	ii. MPLS tunnel does not support forwarding other than the nexthop
	IP address.
	5.1.2 Recommendations		5.1.2 Recommendations
	- New MIB definitions may be created for Global_Node_ID and/or		- New MIB definitions may be created for Global_Node_ID and/or
	ICC configurations.		ICC configurations.
	- MPLS-LSR-STD-MIB [RFC3813] MIB modules may be enhanced to identify		- MPLS-LSR-STD-MIB [RFC3813] MIB modules may be enhanced to identify
	the nexthop based on MAC address for IP-less environments.		the nexthop based on MAC address for IP-less environments.
	OutSegment may be extended to hold the MAC-address also for		OutSegment may be extended to hold the MAC-address also for
	IP-less environments.		IP-less environments.
	skipping to change at page 15, line 33		skipping to change at page 15, line 27
	extensions for co-routed/associated bidirectional LSPs.		extensions for co-routed/associated bidirectional LSPs.
	5.2 MPLS-TP Pseudowire		5.2 MPLS-TP Pseudowire
	5.2.1 Gap Analysis		5.2.1 Gap Analysis
	MPLS-TP Pseudowire can be operated over IP and/or ICC environments,		MPLS-TP Pseudowire can be operated over IP and/or ICC environments,
	below points capture the gaps in existing PW MIB modules		below points capture the gaps in existing PW MIB modules
	for managing the MPLS-TP networks.		for managing the MPLS-TP networks.
	[MPLS-TP-IDENTIFIERS] specifies an initial set of identifiers to be		[RFC6370] specifies an initial set of identifiers to be
	used in MPLS-TP. These identifiers were chosen to be compatible with		used in MPLS-TP. These identifiers were chosen to be compatible with
	existing MPLS, GMPLS, and PW definitions.		existing MPLS, GMPLS, and PW definitions.
	- IP based environment		- IP based environment
	i. PW-STD-MIB [RFC5601] does not support		i. PW-STD-MIB [RFC5601] does not support
	PW end point identifier based on Global_ID and Node_ID.		PW end point identifier based on Global_ID and Node_ID.
	ii. PW-MPLS-STD-MIB [RFC5602] does not support		ii. PW-MPLS-STD-MIB [RFC5602] does not support
	its operation over co-routed/associated bidirectional tunnels.		its operation over co-routed/associated bidirectional tunnels.
	- ICC based environment		- ICC based environment
	i. PW-STD-MIB [RFC5601] does not support		i. PW-STD-MIB [RFC5601] does not support
	PW end point identifier based on ICC.		PW end point identifier based on ICC.
	ii. Pseudowire does not support forwarding other
	than the nexthop IP address.
	5.2.2 Recommendations		5.2.2 Recommendations
	- PW-MPLS-STD-MIB [RFC5602] can be enhanced to operate over		- PW-MPLS-STD-MIB [RFC5602] can be enhanced to operate over
	co-routed/associated bi-directional tunnel.		co-routed/associated bi-directional tunnel.
	- Pseudowire 129 FEC type-2 can be used in non-IP and IP
	environments with the required changes.
	5.3 MPLS-TP Sections		5.3 MPLS-TP Sections
	5.3.1 Gap Analysis		5.3.1 Gap Analysis
	The existing MPLS MIB modules does not support MPLS-TP sections.		The existing MPLS MIB modules does not support MPLS-TP sections.
	5.3.2 Recommendations		5.3.2 Recommendations
	Link specific and/or path/segment specific sections can be achieved		Link specific and/or path/segment specific sections can be achieved
	by enhancing the IF-MIB [RFC2863], MPLS-TE-STD-MIB [RFC3812] and		by enhancing the IF-MIB [RFC2863], MPLS-TE-STD-MIB [RFC3812] and
	PW-STD-MIB [RFC5601] MIB modules.		PW-STD-MIB [RFC5601] MIB modules.
	5.4 MPLS-TP OAM		5.4 MPLS-TP OAM
	5.4.1 Gap Analysis		5.4.1 Gap Analysis
	MPLS manages the LSP and pseudowire faults through LSP ping		MPLS manages the LSP and pseudowire faults through LSP ping
	[RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV		[RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV
	skipping to change at page 17, line 17		skipping to change at page 17, line 4
	available.		available.
	5.5.2 Recommendations		5.5.2 Recommendations
	New MIB modules can be created to address all the gaps mentioned		New MIB modules can be created to address all the gaps mentioned
	in the 5.5.1 Gap Analysis section.		in the 5.5.1 Gap Analysis section.
	5.6 MPLS-TP Interfaces		5.6 MPLS-TP Interfaces
	5.6.1 Gap Analysis		5.6.1 Gap Analysis
			As per [RFC6370], an LSR requires identification of the
	As per [MPLS-TP-IDENTIFIERS], an LSR requires identification of the
	node itself and of its interfaces. An interface is the attachment		node itself and of its interfaces. An interface is the attachment
	point to a server layer MPLS-TP section or MPLS-TP tunnel.		point to a server layer MPLS-TP section or MPLS-TP tunnel.
	The MPLS MIB modules do not provide support for configuring		The MPLS MIB modules do not provide support for configuring
	the interfaces within the context of an operator.		the interfaces within the context of an operator.
	5.6.2 Recommendations		5.6.2 Recommendations
	New MIB definitions can be created to address the gaps mentioned		New MIB definitions can be created to address the gaps mentioned
	in the 5.6.1 Gap Analysis section.		in the 5.6.1 Gap Analysis section.
	6. An Introduction to the MPLS-TP MIB Modules		6. An Introduction to the MPLS-TP MIB Modules
	This section highlights new MIB modules that have been identified		This section highlights MIB modules that have been identified
	as being required for MPLS-TP. This section also provides an overview		as being required for MPLS-TP. This section also provides an overview
	of the following:		of the following:
	- the MPLS Object Identifier (OID) tree structure and the position		- the MPLS Object Identifier (OID) tree structure and the position
	of different MPLS related MIB modules on this tree;		of different MPLS related MIB modules on this tree;
	- the purpose of each of the MIB modules within the MIB documents,		- the purpose of each of the MIB modules within the MIB documents,
	what it can be used for, and how it relates to the other MIB		what it can be used for, and how it relates to the other MIB
	modules.		modules.
	skipping to change at page 18, line 9		skipping to change at page 17, line 43
	define the MIB modules or in separate Applicability Statements, will		define the MIB modules or in separate Applicability Statements, will
	define which Compliance Statements need to be conformed to in order		define which Compliance Statements need to be conformed to in order
	to provide specific MPLS-TP function. This document does not set any		to provide specific MPLS-TP function. This document does not set any
	requirements in that respect although some recommendations are		requirements in that respect although some recommendations are
	included in the sections that follow.		included in the sections that follow.
	6.1 MPLS-TP MIB Modules		6.1 MPLS-TP MIB Modules
	6.1.1 Structure of the MPLS-TP MIB OID Tree		6.1.1 Structure of the MPLS-TP MIB OID Tree
	The MPLS-TP MIB OID tree has the following structure.		The MPLS-TP MIB OID tree as proposed in [MPLS-TP-TE-MIB] has the
			following structure:
	transmission -- RFC 2578 [RFC2578]		transmission -- RFC 2578 [RFC2578]
	|		|
	+- mplsStdMIB		+- mplsStdMIB
	|		|
	+- Textual Conventions for MPLS-TP		+- Textual Conventions for MPLS-TP
	|		|
	+- Identifiers for MPLS-TP		+- Identifiers for MPLS-TP
	|		|
	+- LSR MIB Extensions for MPLS-TP		+- LSR MIB Extensions for MPLS-TP
	|		|
	+- TE MIB Extensions for MPLS-TP		+- TE MIB Extensions for MPLS-TP
	Note that the MIB modules mentioned here are applicable		Note that the MIB modules described above are applicable
	for MPLS operations as well.		for MPLS operations as well.
	Note: The OIDs for MIB modules are yet to be assigned and managed by		Note: The OIDs for MIB modules are yet to be assigned and managed by
	IANA.		IANA.
	6.1.2 Textual Conventions for MPLS-TP		6.1.2 Textual Conventions for MPLS-TP
	A new textual convention MIB module will define textual		A new MIB module needs to be written that will define textual
	conventions [RFC2579] for MPLS-TP related MIB modules.		conventions [RFC2579] for MPLS-TP related MIB modules. These
	These conventions allow multiple MIB modules to use the		conventions allow multiple MIB modules to use the same syntax and
	same syntax and format for a concept that is shared between		format for a concept that is shared between the MIB modules.
	the MIB modules.
	For example, MEP identifier is used to identify maintenance entity		For example, MEP identifier is used to identify maintenance entity
	group end point within MPLS-TP networks. The textual convention		group end point within MPLS-TP networks. The textual convention
	representing the MEP identifier should be defined in a new textual		representing the MEP identifier should be defined in a new textual
	convention MIB module.		convention MIB module.
	All new extensions related to MPLS-TP are defined in the MIB module		All new extensions related to MPLS-TP are defined in the MIB module
	and will be referenced by other MIB modules to support MPLS-TP.		and will be referenced by other MIB modules to support MPLS-TP.
	6.1.3 Identifiers for MPLS-TP		6.1.3 Identifiers for MPLS-TP
	New Identifiers describe managed objects that are used to model		New Identifiers describe managed objects that are used to model
	common MPLS-TP identifiers [MPLS-TP-IDENTIFIERS].		common MPLS-TP identifiers [RFC6370].
	6.1.4 LSR MIB Extensions for MPLS-TP		6.1.4 LSR MIB Extensions for MPLS-TP
	MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS Label		MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS Label
	Switching Router (LSR). This puts it at the heart of the management		Switching Router (LSR). This puts it at the heart of the management
	architecture for MPLS.		architecture for MPLS.
	In the case of MPLS-TP, the MPLS-LSR-STD-MIB is extended to support		In the case of MPLS-TP, the MPLS-LSR-STD-MIB is extended to support
	the MPLS-TP LSP's, which are co-routed or associated bidirectional.		the MPLS-TP LSP's, which are co-routed or associated bidirectional.
	This extended MIB is also applicable for modeling MPLS-TP tunnels.		This extended MIB is also applicable for modeling MPLS-TP tunnels.
	skipping to change at page 19, line 44		skipping to change at page 19, line 37
	|		|
	+- Pseudowire Textual Conventions for MPLS-TP		+- Pseudowire Textual Conventions for MPLS-TP
	Note: The OIDs for MIB modules are yet to be assigned and managed by		Note: The OIDs for MIB modules are yet to be assigned and managed by
	IANA.		IANA.
	6.2.2 Pseudowire Textual Conventions for MPLS-TP		6.2.2 Pseudowire Textual Conventions for MPLS-TP
	PW-TC-STD-MIB MIB defines textual conventions used for pseudowire		PW-TC-STD-MIB MIB defines textual conventions used for pseudowire
	(PW) technology and for Pseudowire Edge-to-Edge Emulation (PWE3) MIB		(PW) technology and for Pseudowire Edge-to-Edge Emulation (PWE3) MIB
	Modules. A new textual convention MIB module will define textual		Modules. A new textual convention MIB module is required to define
	definitions for MPLS-TP specific Pseudowire attributes.		textual definitions for MPLS-TP specific Pseudowire attributes.
	6.2.3 Pseudowire Extensions for MPLS-TP		6.2.3 Pseudowire Extensions for MPLS-TP
	PW-STD-MIB describes managed objects for modeling of Pseudowire		PW-STD-MIB describes managed objects for modeling of Pseudowire
	Edge-to-Edge services carried over a general Packet Switched Network.		Edge-to-Edge services carried over a general Packet Switched Network.
	This MIB module is extended to support MPLS-TP specific attributes		This MIB module is extended to support MPLS-TP specific attributes
	related to Pseudowires.		related to Pseudowires.
	6.2.4 Pseudowire MPLS Extensions for MPLS-TP		6.2.4 Pseudowire MPLS Extensions for MPLS-TP
	PW-MPLS-STD-MIB defines the managed objects for Pseudowire		PW-MPLS-STD-MIB defines the managed objects for Pseudowire
	operations over MPLS LSR's. This MIB supports both,		operations over MPLS LSR's. This MIB supports both,
	manual and dynamically signaled PW's, point-to-point connections,		manual and dynamically signaled PW's, point-to-point connections,
	enables the use of any emulated service, MPLS-TE as outer tunnel		enables the use of any emulated service, MPLS-TE as outer tunnel
	and no outer tunnel as MPLS-TE.		and no outer tunnel as MPLS-TE.
	The newly extended MIB defines the managed objects, extending		The newly extended MIB defines the managed objects, extending
	PW-MPLS-STD-MIB, by supporting with or without MPLS-TP as outer		PW-MPLS-STD-MIB, by supporting with or without MPLS-TP as outer
	tunnel.		tunnel.
	skipping to change at page 20, line 36		skipping to change at page 20, line 31
	|		|
	+- OAM MIB module		+- OAM MIB module
	Note: The OIDs for MIB modules are yet to be assigned and managed by		Note: The OIDs for MIB modules are yet to be assigned and managed by
	IANA.		IANA.
	6.3.2 BFD MIB module		6.3.2 BFD MIB module
	BFD-STD-MIB defines managed objects for performing BFD operation in		BFD-STD-MIB defines managed objects for performing BFD operation in
	IP networks. This MIB is modeled to support BFD protocol [RFC5880].		IP networks. This MIB is modeled to support BFD protocol [RFC5880].
	A new MIB module will be an extension to BFD-STD-MIB managed objects		A new MIB module needs to be written that will be an extension to
	to support BFD operations on MPLS LSPs and PWs.		BFD-STD-MIB managed objects to support BFD operations on MPLS LSPs
			and PWs.
	6.3.3 Common OAM MIB modules		6.3.3 Common OAM MIB modules
	A new MIB module will define managed objects for OAM maintenance		A new MIB module needs to be written that will define managed objects
	identifiers i.e. Maintenance Entity Group Identifiers (MEG),		for OAM maintenance identifiers i.e. Maintenance Entity Group
	Maintenance Entity Group End-point (MEP), Maintenance Entity Group		Identifiers (MEG), Maintenance Entity Group End-point (MEP),
	Intermediate Point (MIP). Maintenance points are uniquely		Maintenance Entity Group Intermediate Point (MIP). Maintenance points
	associated with a MEG. Within the context of a MEG, MEPs and MIPs		are uniquely associated with a MEG. Within the context of a MEG, MEPs
	must be uniquely identified.		and MIPs must be uniquely identified.
	6.4. Protection Switching and Recovery MIB Modules for MPLS-TP		6.4. Protection Switching and Recovery MIB Modules for MPLS-TP
	This section provides an overview of protection switching and		This section provides an overview of protection switching and
	recovery MIB modules for MPLS LSPs and Pseudowires.		recovery MIB modules for MPLS LSPs and Pseudowires.
	6.4.1 Structure of the MPLS Protection Switching and Recovery MIB OID		6.4.1 Structure of the MPLS Protection Switching and Recovery MIB OID
	Tree for MPLS-TP		Tree for MPLS-TP
	mib-2 -- RFC 2578 [RFC2578]		mib-2 -- RFC 2578 [RFC2578]
	skipping to change at page 21, line 23		skipping to change at page 21, line 20
	|		|
	+- Ring Protection Switching MIB module		+- Ring Protection Switching MIB module
	|		|
	+- Mesh Protection Switching MIB module		+- Mesh Protection Switching MIB module
	Note: The OIDs for MIB modules are yet to be assigned and managed by		Note: The OIDs for MIB modules are yet to be assigned and managed by
	IANA.		IANA.
	6.4.2 Linear Protection Switching MIB module		6.4.2 Linear Protection Switching MIB module
	A new MIB module will define managed objects for linear protection		A new MIB module needs to be written that will define managed objects
	switching of MPLS LSPs and Pseudowires.		for linear protection switching of MPLS LSPs and Pseudowires.
	6.4.3 Ring Protection Switching MIB module		6.4.3 Ring Protection Switching MIB module
	A new MIB module will defined managed objects for ring protection		A new MIB module will define managed objects for ring protection
	switching of MPLS LSPs and Pseudowires.		switching of MPLS LSPs and Pseudowires.
	6.4.4 Mesh Protection Switching MIB module		6.4.4 Mesh Protection Switching MIB module
	A new MIB module will defined managed objects for Mesh protection		A new MIB module needs to be written that will define managed objects
	switching of MPLS LSPs and Pseudowires.		for Mesh protection switching of MPLS LSPs and Pseudowires.
	7. Management Options		7. Management Options
	This document applies only to scenarios where MIB modules are used to		This document applies only to scenarios where MIB modules are used to
	manage the MPLS-TP network. It is not the intention of this document		manage the MPLS-TP network. It is not the intention of this document
	to provide instructions or advice to implementers of management		to provide instructions or advice to implementers of management
	systems, management agents, or managed entities. It is, however,		systems, management agents, or managed entities. It is, however,
	useful to make some observations about how the MIB modules described		useful to make some observations about how the MIB modules described
	above might be used to manage MPLS systems, if SNMP is used in the		above might be used to manage MPLS systems, if SNMP is used in the
	management interface.		management interface.
	skipping to change at page 26, line 25		skipping to change at page 26, line 25
	RFC5885, June 2010.		RFC5885, June 2010.
	[RFC5950] Gray, E., Mansfield, S., Lam, K.,		[RFC5950] Gray, E., Mansfield, S., Lam, K.,
	"MPLS-TP Network Management Framework", RFC 5950,		"MPLS-TP Network Management Framework", RFC 5950,
	September 2010.		September 2010.
	[RFC5951] Gray, E., Mansfield, S., Lam, K., "MPLS TP		[RFC5951] Gray, E., Mansfield, S., Lam, K., "MPLS TP
	Network Management Requirements", RFC 5951, September		Network Management Requirements", RFC 5951, September
	2010.		2010.
	[MPLS-TP-IDENTIFIERS] Bocci, M., Swallow, G., Gray, E.,		[RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport
	"MPLS-TP Identifiers" draft-ietf-mpls-tp-identifiers-07,		Profile (MPLS-TP) Identifiers", RFC 6370, September 2011.
	July 2011 and Winter, R., Van Helvoort, H., Betts, M.,
	"MPLS-TP Identifiers Following ITU-T Conventions"
	draft-ietf-mpls-tp-itu-t-identifiers-00, July 2011.
	[MPLS-TP-OAM-FWK] Busi, I. and B. Niven-Jenkins, "MPLS-TP OAM		[MPLS-TP-OAM-FWK] Busi, I. and B. Niven-Jenkins, "MPLS-TP OAM
	Framework and Overview", 2009,		Framework and Overview", 2009,
	<draft-ietf-mpls-tp-oam-framework>.		<draft-ietf-mpls-tp-oam-framework>.
			[MPLS-TP-TE-MIB] Venkatesan, M., Sampath, Kannan KV., Nadeau, T.,
			Aldrin, S., "MPLS-TP Traffic Engineering (TE)
			Management Information Base (MIB)", 2011,
			<draft-ietf-mpls-tp-te-mib-01>.
	12. Authors' Addresses		12. Authors' Addresses
	Adrian Farrel		Adrian Farrel
	Old Dog Consulting		Old Dog Consulting
	UK		UK
	Email: adrian@olddog.co.uk		Email: adrian@olddog.co.uk
	Daniel King		Daniel King
	Old Dog Consulting		Old Dog Consulting
	UK		UK
	Email: daniel@olddog.co.uk		Email: daniel@olddog.co.uk
	Venkatesan Mahalingam		Venkatesan Mahalingam
	Aricent		Aricent
	India		India
	Email: venkatesan.mahalingam@aricent.com		Email: venkat.mahalingams@gmail.com
	Scott Mansfield		Scott Mansfield
	Ericsson		Ericsson
	300 Holger Way, San Jose, CA 95134, US		300 Holger Way, San Jose, CA 95134, US
	Phone: +1 724 931 9316		Phone: +1 724 931 9316
	Email: scott.mansfield@ericsson.com		Email: scott.mansfield@ericsson.com
	Jeong-dong Ryoo		Jeong-dong Ryoo
	ETRI		ETRI
	161 Gajeong, Yuseong, Daejeon, 305-700, South Korea		161 Gajeong, Yuseong, Daejeon, 305-700, South Korea
	Phone: +82 42 860 5384		Phone: +82 42 860 5384
End of changes. 44 change blocks.
	91 lines changed or deleted		88 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/