draft-ietf-mpls-tp-mib-management-overview-01.txt		draft-ietf-mpls-tp-mib-management-overview-02.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: June 5, 2011 Aricent		Expires: June 26, 2011 Aricent
	January 5, 2011		January 26, 2011
	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-01.txt		draft-ietf-mpls-tp-mib-management-overview-02.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 2, line 26		skipping to change at page 2, line 26
	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 June 5, 2011.		This Internet-Draft will expire on June 26, 2011.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 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 8, line 19		skipping to change at page 8, line 19
	A label stack entry can be 'popped' or removed from the top of the		A label stack entry can be 'popped' or removed from the top of the
	label stack or a label stack entry is 'pushed' or inserted into the		label stack or a label stack entry is 'pushed' or inserted into the
	top of the stack based on the FEC information.		top of the stack based on the FEC information.
	When a 'swap' operation is executed, the topmost label stack entry is		When a 'swap' operation is executed, the topmost label stack entry is
	replaced with a different one and the depth of the label stack		replaced with a different one and the depth of the label stack
	remains the same. After the swap the packet is forwarded based on the		remains the same. After the swap the packet is forwarded based on the
	new entry.		new entry.
			MPLS-FTN-STD-MIB [RFC3814] describes the managed objects for mapping
			FEC's to label bindings.
	5.2.4. Label Switching Router Modules		5.2.4. Label Switching Router Modules
	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-TP is specific to the use of MPLS in transport networks.		MPLS-TP is specific to the use of MPLS in transport networks.
	According to [RFC5654] multipoint-to-point LSPs do not form part of		According to [RFC5654] multipoint-to-point LSPs do not form part of
	MPLS-TP, so multipoint-to-point cross-connects are out of scope for		MPLS-TP, so multipoint-to-point cross-connects are out of scope for
	this document.		this document.
	skipping to change at page 9, line 26		skipping to change at page 9, line 26
	The second is the PW-STD-MIB module, which configures general		The second is the PW-STD-MIB module, which configures general
	parameters of the PW that are common to all types of emulated		parameters of the PW that are common to all types of emulated
	services and PSN types.		services and PSN types.
	The third is a PSN-specific module. There is a different module for		The third is a PSN-specific module. There is a different module for
	each type of PSN. These modules associate the PW with one or more		each type of PSN. These modules associate the PW with one or more
	"tunnels" that carry the service over the PSN. These modules are		"tunnels" that carry the service over the PSN. These modules are
	defined in other documents.		defined in other documents.
			PW-TC-STD-MIB [RFC5542] contains the textual conventions required
			for PW MIB modules.
	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.
	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.		MPLS PSN type in the PW-STD-MIB.
	This document describes the MIB objects that define pseudowire		This document describes the MIB objects that define pseudowire
	association to the MPLS PSN, in a way that is not specific to the		association to the MPLS PSN, in a way that is not specific to the
	carried service.		carried service.
	Together, [RFC3811] and [RFC3812] describe the modeling of an MPLS		Together, [RFC3811], [RFC3812] and [RFC3813] describe the modeling of
	tunnel, and a tunnel's underlying cross-connects. This MIB module		an MPLS tunnel, and a tunnel's underlying cross-connects. This MIB
	supports MPLS-TE PSN, non-TE MPLS PSN (an outer tunnel created by the		module supports MPLS-TE PSN, non-TE MPLS PSN (an outer tunnel created
	Label Distribution Protocol (LDP) or manually), and MPLS PW label		by the Label Distribution Protocol (LDP) or manually), and MPLS PW
	only (no outer tunnel).		label only (no outer tunnel).
	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
	skipping to change at page 10, line 35		skipping to change at page 10, line 35
	some specific data can be routed around network hot spots.		some specific data can be routed around network hot spots.
	MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling a		MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling a
	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.
	5.2.8. Resiliency		5.2.8. Resiliency
	MPLS Fast Reroute is a local restoration network resiliency mechanism		MPLS Fast Reroute is a restoration network resiliency mechanism used
	in MPLS TE for link and node protection. Two different modes of local		in MPLS TE to redirect the traffic onto the backup LSP's in 10s of
	protection are described in the [RFC4090] to protect LSP.		milliseconds in case of link or node failure across the LSP. Two
			different modes of local protection are described in the [RFC4090] to
			protect LSP.
	o One-to-One Backup		o One-to-One Backup
	o Facility Backup		o Facility Backup
	Facility backup uses label stacking to reroute multiple protected TE		Facility backup uses label stacking to reroute multiple protected TE
	LSPs using a single backup TE LSP. One-to-one backup does not use		LSPs using a single backup TE LSP. One-to-one backup does not use
	label stacking, and every protected TE LSP requires a dedicated		label stacking, and every protected TE LSP requires a dedicated
	backup TE LSP.		backup TE LSP.
	MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]		MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
	skipping to change at page 13, line 16		skipping to change at page 13, line 16
	| ^ |		| ^ |
	| | |		| | |
	| MPLS-LSR-STD-MIB <--------------------------------+ |		| MPLS-LSR-STD-MIB <--------------------------------+ |
	| | |		| | |
	+<----------------------- MPLS-LDP-STD-MIB ---------------->+ |		+<----------------------- MPLS-LDP-STD-MIB ---------------->+ |
	| ^ | |		| ^ | |
	| | | |		| | | |
	+<-- MPLS-LDP-GENERIC-STD-MIB ------>+ | |		+<-- MPLS-LDP-GENERIC-STD-MIB ------>+ | |
	| | |		| | |
	+<------ MPLS-FTN-STD-MIB ---------+----------------------->+ |		+<------ MPLS-FTN-STD-MIB ---------+----------------------->+ |
	| ^ | |
	| | | |		| | | |
			| V | |
	+<------------- MPLS-TE-STD-MIB ->+ |		+<------------- MPLS-TE-STD-MIB ->+ |
	^ | GMPLS-TC-STD-MIB ------------>+		| GMPLS-TC-STD-MIB ------------>+
	| | ^ |		| ^ |
	| | | |		| | |
	| +---+ +<-- GMPLS-LABEL-STD-MIB -->+		+---+ +<-- GMPLS-LABEL-STD-MIB -->+
	| | ^ ^ ^ |		| ^ ^ ^ |
	| | | | | |		| | | | |
	+----> PW-TC-STD-MIB | | GMPLS-LSR-STD-MIB --------------->+		+----> PW-TC-STD-MIB | GMPLS-LSR-STD-MIB --------------->+
	| | | ^ ^ |		| | ^ ^ |
	| | | | | |		| | | | |
	| IANA-PWE3-MIB | | | | IANA-GMPLS-TC-MIB |		| IANA-PWE3-MIB | | | IANA-GMPLS-TC-MIB |
	| ^ | | | | ^ |		| ^ | | | ^ |
	| | | | | | | |		| | | | | | |
	| | | +<--- GMPLS-TE-STD-MIB ------------->+		| | +<--- GMPLS-TE-STD-MIB ------------->+
	| | | ^ |		| | ^ |
	+<--- PW-STD-MIB <------+ | | |		+<--- PW-STD-MIB <------+ | |
	| | | | |		| | | |
	+<--- PW-ENET-STD-MIB ->+ | | |		+<--- PW-ENET-STD-MIB ->+ | |
	| ^ | | |		| ^ | |
	| | | | |		| | | |
	+<---------------- PW-MPLS-STD-MIB -------------------------------->+		+<---------------- PW-MPLS-STD-MIB -------------------------------->+
	Thus:		Thus:
	- All the MPLS MIB modules depend on MPLS-TC-STD-MIB.		- All the MPLS MIB modules depend on MPLS-TC-STD-MIB.
	- All the GMPLS MIB modules depend on GMPLS-TC-STD-MIB.		- All the GMPLS MIB modules depend on GMPLS-TC-STD-MIB.
	- All the PW MIB modules depend on PW-TC-STD-MIB.		- All the PW MIB modules depend on PW-TC-STD-MIB.
	skipping to change at page 15, line 23		skipping to change at page 15, line 23
	[Editors note - A seperate draft will provide an MPLS-TP abstract		[Editors note - A seperate draft will provide an MPLS-TP abstract
	model and use a formal language to define the terminology, the		model and use a formal language to define the terminology, the
	information that must be retrieved and method for storing. The draft		information that must be retrieved and method for storing. The draft
	will also list the new MPLS-TP MIB modules identified in this		will also list the new MPLS-TP MIB modules identified in this
	document]		document]
	6.1 Gap Analysis		6.1 Gap Analysis
	6.1.1 MPLS-TP Tunnel		6.1.1 MPLS-TP Tunnel
	o An MPLS tunnel may not compatible for non-IP environments.		o An MPLS tunnel may not be compatible for non-IP environments.
	i.e., the tunnel ingress and egress identifiers are not always		i.e., the tunnel ingress and egress identifiers are not always
	identified via an IP address, rather identification is achieved		identified via an IP address, rather identification is achieved
	using local numbers to operate in a non-IP environment.		using local numbers to operate in a non-IP environment.
	o Next-hop IP address in MPLS XC table is not compatible for non-IP		o Next-hop IP address in MPLS XC table is not compatible for non-IP
	environment.		environment.
	o Bidirectional LSPs are not introduced until the GMPLS MIB modules,		o Bidirectional LSPs are not introduced until the GMPLS MIB modules,
	tunnel table should be enhanced to provide static and signalling		tunnel table should be enhanced to provide static and signalling
	corouted/associated bidirectional connectivity.		corouted/associated bidirectional connectivity.
	6.1.2 MPLS-TP Pseudowire		6.1.2 MPLS-TP Pseudowire
	skipping to change at page 18, line 39		skipping to change at page 18, line 39
	configured to give access to only those objects, and to those		configured to give access to only those objects, and to those
	principals (users) that have legitimate rights to access them.		principals (users) that have legitimate rights to access them.
	10. IANA Considerations		10. IANA Considerations
	This document makes no requests for IANA action.		This document makes no requests for IANA action.
	11. Acknowledgements		11. Acknowledgements
	The authors would like to thank Eric Gray, Thomas Nadeau, Benjamin		The authors would like to thank Eric Gray, Thomas Nadeau, Benjamin
	Niven-Jenkins, Sam Aldrin and Anirban Karmakar for their valuable		Niven-Jenkins, Sam Aldrin and Saravanan Narasimhan for their
	comments.		valuable comments.
	12. References		12. References
	12.1 Normative References		12.1 Normative References
	[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group		[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
	MIB using SMIv2", RFC 2863, June 2000.		MIB using SMIv2", RFC 2863, June 2000.
	[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual		[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
	Conventions and for Multiprotocol Label Switching (MPLS)		Conventions and for Multiprotocol Label Switching (MPLS)
End of changes. 13 change blocks.
	36 lines changed or deleted		43 lines changed or added
This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/