draft-ietf-opsawg-oam-overview-11.txt		draft-ietf-opsawg-oam-overview-12.txt
	Operations and Management Area Working Group T. Mizrahi		Operations and Management Area Working Group T. Mizrahi
	Internet Draft Marvell		Internet Draft Marvell
	Intended status: Informational N. Sprecher		Intended status: Informational N. Sprecher
	Expires: June 2014 NSN		Expires: July 2014 NSN
	E. Bellagamba		E. Bellagamba
	Ericsson		Ericsson
	Y. Weingarten		Y. Weingarten
	December 16, 2013		January 9, 2014
	An Overview of		An Overview of
	Operations, Administration, and Maintenance (OAM) Tools		Operations, Administration, and Maintenance (OAM) Tools
	draft-ietf-opsawg-oam-overview-11.txt		draft-ietf-opsawg-oam-overview-12.txt
	Abstract		Abstract
	Operations, Administration, and Maintenance (OAM) is a general term		Operations, Administration, and Maintenance (OAM) is a general term
	that refers to a toolset for fault detection and isolation, and for		that refers to a toolset for fault detection and isolation, and for
	performance measurement. Over the years various OAM tools have been		performance measurement. Over the years various OAM tools have been
	defined for various layers in the protocol stack.		defined for various layers in the protocol stack.
	This document summarizes some of the OAM tools defined in the IETF in		This document summarizes some of the OAM tools defined in the IETF in
	the context of IP unicast, MPLS, MPLS for the transport profile		the context of IP unicast, MPLS, MPLS for the transport profile
	skipping to change at page 2, line 16		skipping to change at page 2, line 16
	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 16, 2014.		This Internet-Draft will expire on July 9, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 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
	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 45		skipping to change at page 2, line 45
	1. Introduction ................................................. 4		1. Introduction ................................................. 4
	1.1. Background .............................................. 4		1.1. Background .............................................. 4
	1.2. Target Audience.......................................... 5		1.2. Target Audience.......................................... 5
	1.3. OAM-related Work in the IETF ............................ 5		1.3. OAM-related Work in the IETF ............................ 5
	1.4. Focusing on the Data Plane .............................. 6		1.4. Focusing on the Data Plane .............................. 6
	2. Terminology .................................................. 7		2. Terminology .................................................. 7
	2.1. Abbreviations ........................................... 7		2.1. Abbreviations ........................................... 7
	2.2. Terminology used in OAM Standards ....................... 9		2.2. Terminology used in OAM Standards ....................... 9
	2.2.1. General Terms ...................................... 9		2.2.1. General Terms ...................................... 9
	2.2.2. Operations, Administration and Maintenance ......... 9		2.2.2. Operations, Administration and Maintenance ......... 9
	2.2.3. Functions, Tools and Protocols ..................... 9		2.2.3. Functions, Tools and Protocols .................... 10
	2.2.4. Data Plane, Control Plane and Management Plane .... 10		2.2.4. Data Plane, Control Plane and Management Plane .... 10
	2.2.5. The Players ....................................... 11		2.2.5. The Players ....................................... 11
	2.2.6. Proactive and On-demand Activation ................ 12		2.2.6. Proactive and On-demand Activation ................ 12
	2.2.7. Connectivity Verification and Continuity Checks ... 12		2.2.7. Connectivity Verification and Continuity Checks ... 12
	2.2.8. Connection Oriented vs. Connectionless Communication13		2.2.8. Connection Oriented vs. Connectionless Communication13
	2.2.9. Point-to-point vs. Point-to-multipoint Services ... 14		2.2.9. Point-to-point vs. Point-to-multipoint Services ... 14
	2.2.10. Failures ......................................... 14		2.2.10. Failures ......................................... 15
	3. OAM Functions ............................................... 15		3. OAM Functions ............................................... 15
	4. OAM Tools in the IETF - a Detailed Description .............. 16		4. OAM Tools in the IETF - a Detailed Description .............. 16
	4.1. IP Ping ................................................ 16		4.1. IP Ping ................................................ 16
	4.2. IP Traceroute .......................................... 16		4.2. IP Traceroute .......................................... 17
	4.3. Bidirectional Forwarding Detection (BFD) ............... 17		4.3. Bidirectional Forwarding Detection (BFD) ............... 18
	4.3.1. Overview .......................................... 17		4.3.1. Overview .......................................... 18
	4.3.2. Terminology ....................................... 18		4.3.2. Terminology ....................................... 18
	4.3.3. BFD Control ....................................... 18		4.3.3. BFD Control ....................................... 18
	4.3.4. BFD Echo .......................................... 18		4.3.4. BFD Echo .......................................... 19
	4.4. MPLS OAM ............................................... 19		4.4. MPLS OAM ............................................... 19
	4.5. MPLS-TP OAM ............................................ 20		4.5. MPLS-TP OAM ............................................ 20
	4.5.1. Overview .......................................... 20		4.5.1. Overview .......................................... 20
	4.5.2. Terminology ....................................... 20		4.5.2. Terminology ....................................... 21
	4.5.3. Generic Associated Channel ........................ 22		4.5.3. Generic Associated Channel ........................ 22
	4.5.4. MPLS-TP OAM Toolset ............................... 22		4.5.4. MPLS-TP OAM Toolset ............................... 23
	4.5.4.1. Continuity Check and Connectivity Verification 23		4.5.4.1. Continuity Check and Connectivity Verification 23
	4.5.4.2. Route Tracing ................................ 23		4.5.4.2. Route Tracing ................................ 24
	4.5.4.3. Lock Instruct ................................ 23		4.5.4.3. Lock Instruct ................................ 24
	4.5.4.4. Lock Reporting ............................... 24		4.5.4.4. Lock Reporting ............................... 24
	4.5.4.5. Alarm Reporting .............................. 24		4.5.4.5. Alarm Reporting .............................. 24
	4.5.4.6. Remote Defect Indication ..................... 24		4.5.4.6. Remote Defect Indication ..................... 24
	4.5.4.7. Client Failure Indication .................... 24		4.5.4.7. Client Failure Indication .................... 25
	4.5.4.8. Performance Monitoring ....................... 24		4.5.4.8. Performance Monitoring ....................... 25
	4.5.4.8.1. Packet Loss Measurement (LM) ............ 25		4.5.4.8.1. Packet Loss Measurement (LM) ............ 25
	4.5.4.8.2. Packet Delay Measurement (DM) ........... 25		4.5.4.8.2. Packet Delay Measurement (DM) ........... 25
	4.6. Pseudowire OAM ......................................... 26		4.6. Pseudowire OAM ......................................... 26
	4.6.1. Pseudowire OAM using Virtual Circuit Connectivity		4.6.1. Pseudowire OAM using Virtual Circuit Connectivity
	Verification (VCCV) ...................................... 26		Verification (VCCV) ...................................... 26
	4.6.2. Pseudowire OAM using G-ACh ........................ 27		4.6.2. Pseudowire OAM using G-ACh ........................ 27
	4.6.3. Attachment Circuit - Pseudowire Mapping ........... 27		4.6.3. Attachment Circuit - Pseudowire Mapping ........... 27
	4.7. OWAMP and TWAMP......................................... 27		4.7. OWAMP and TWAMP......................................... 27
	4.7.1. Overview .......................................... 27		4.7.1. Overview .......................................... 27
	4.7.2. Control and Test Protocols ........................ 28		4.7.2. Control and Test Protocols ........................ 28
	4.7.3. OWAMP ............................................. 29		4.7.3. OWAMP ............................................. 29
	4.7.4. TWAMP ............................................. 29		4.7.4. TWAMP ............................................. 29
	4.8. TRILL .................................................. 29		4.8. TRILL .................................................. 30
	5. Summary ..................................................... 30		5. Summary ..................................................... 30
	5.1. Summary of OAM Tools ................................... 30		5.1. Summary of OAM Tools ................................... 31
	5.2. Summary of OAM Functions ............................... 32		5.2. Summary of OAM Functions ............................... 33
	5.3. Guidance to Network Equipment Vendors .................. 34		5.3. Guidance to Network Equipment Vendors .................. 34
	6. Security Considerations ..................................... 34		6. Security Considerations ..................................... 34
	7. IANA Considerations ......................................... 34		7. IANA Considerations ......................................... 34
	8. Acknowledgments ............................................. 34		8. Acknowledgments ............................................. 35
	9. References .................................................. 34		9. References .................................................. 35
	9.1. Informative References ................................. 34		9.1. Informative References ................................. 35
	Appendix A. List of OAM Documents .............................. 40		Appendix A. List of OAM Documents .............................. 40
	A.1. List of IETF OAM Documents ............................. 40		A.1. List of IETF OAM Documents ............................. 40
	A.2. List of Selected Non-IETF OAM Documents ................ 45		A.2. List of Selected Non-IETF OAM Documents ................ 45
	1. Introduction		1. Introduction
	OAM is a general term that refers to a toolset for detecting,		OAM is a general term that refers to a toolset for detecting,
	isolating and reporting failures and for monitoring the network		isolating and reporting failures and for monitoring the network
	performance.		performance.
	There are several different interpretations to the "OAM" acronym.		There are several different interpretations to the "OAM" acronym.
	This document refers to Operations, Administration and Maintenance,		This document refers to Operations, Administration and Maintenance,
	as recommended in Section 3 of [RFC6291].		as recommended in Section 3 of [OAM-Def].
	This document summarizes some of the OAM tools defined in the IETF in		This document summarizes some of the OAM tools defined in the IETF in
	the context of IP unicast, MPLS, MPLS for the transport profile		the context of IP unicast, MPLS, MPLS for the transport profile
	(MPLS-TP), pseudowires, and TRILL.		(MPLS-TP), pseudowires, and TRILL.
	This document focuses on tools for detecting and isolating failures		This document focuses on tools for detecting and isolating failures
	and for performance monitoring. Hence, this document focuses on the		and for performance monitoring. Hence, this document focuses on the
	tools used for monitoring and measuring the data plane; control and		tools used for monitoring and measuring the data plane; control and
	management aspects of OAM are outside the scope of this document.		management aspects of OAM are outside the scope of this document.
	Network repair functions such as Fast Reroute (FRR) and protection		Network repair functions such as Fast Reroute (FRR) and protection
	skipping to change at page 6, line 39		skipping to change at page 6, line 39
	+--------------+------------+		+--------------+------------+
	|Pseudowire OAM| Pseudowires|		|Pseudowire OAM| Pseudowires|
	+--------------+------------+		+--------------+------------+
	|OWAMP and | IPv4/IPv6 |		|OWAMP and | IPv4/IPv6 |
	|TWAMP | |		|TWAMP | |
	+--------------+------------+		+--------------+------------+
	|TRILL OAM | TRILL |		|TRILL OAM | TRILL |
	+--------------+------------+		+--------------+------------+
	Table 1 OAM Toolset Packages in the IETF Documents		Table 1 OAM Toolset Packages in the IETF Documents
			This document focuses on OAM tools that have been developed in the
			IETF. A short summary of some of the significant OAM standards that
			have been developed in other standard organizations is presented in
			Appendix A.2.
	1.4. Focusing on the Data Plane		1.4. Focusing on the Data Plane
	OAM tools may, and quite often do, work in conjunction with a control		OAM tools may, and quite often do, work in conjunction with a control
	plane and/or management plane. OAM provides instrumentation tools		plane and/or management plane. OAM provides instrumentation tools
	for measuring and monitoring the data plane. OAM tools often use		for measuring and monitoring the data plane. OAM tools often use
	control plane functions, e.g., to initialize OAM sessions and to		control plane functions, e.g., to initialize OAM sessions and to
	exchange various parameters. The OAM tools communicate with the		exchange various parameters. The OAM tools communicate with the
	management plane to raise alarms, and often OAM tools may be		management plane to raise alarms, and often OAM tools may be
	activated by the management (as well as by the control plane), e.g.		activated by the management (as well as by the control plane), e.g.
	to locate and localize problems.		to locate and localize problems.
	skipping to change at page 8, line 32		skipping to change at page 8, line 38
	MP Maintenance Point		MP Maintenance Point
	MPLS Multiprotocol Label Switching		MPLS Multiprotocol Label Switching
	MPLS-TP MPLS Transport Profile		MPLS-TP MPLS Transport Profile
	MTU Maximum Transmission Unit		MTU Maximum Transmission Unit
	OAM Operations, Administration, and Maintenance		OAM Operations, Administration, and Maintenance
			OWAMP One-way Active Measurement Protocol
	PDH Plesiochronous Digital Hierarchy		PDH Plesiochronous Digital Hierarchy
	PE Provider Edge		PE Provider Edge
	PW Pseudowire		PW Pseudowire
	PWE3 Pseudowire Emulation Edge-to-Edge		PWE3 Pseudowire Emulation Edge-to-Edge
	RBridge Routing Bridge		RBridge Routing Bridge
	skipping to change at page 8, line 43		skipping to change at page 9, line 4
	PE Provider Edge		PE Provider Edge
	PW Pseudowire		PW Pseudowire
	PWE3 Pseudowire Emulation Edge-to-Edge		PWE3 Pseudowire Emulation Edge-to-Edge
	RBridge Routing Bridge		RBridge Routing Bridge
	RDI Remote Defect Indication		RDI Remote Defect Indication
	SDH Synchronous Digital Hierarchy		SDH Synchronous Digital Hierarchy
	SONET Synchronous Optical Networking		SONET Synchronous Optical Networking
	TRILL Transparent Interconnection of Lots of Links		TRILL Transparent Interconnection of Lots of Links
	TTL Time To Live		TTL Time To Live
			TWAMP Two-way Active Measurement Protocol
	VCCV Virtual Circuit Connectivity Verification		VCCV Virtual Circuit Connectivity Verification
	2.2. Terminology used in OAM Standards		2.2. Terminology used in OAM Standards
	2.2.1. General Terms		2.2.1. General Terms
	A wide variety of terms is used in various OAM standards. This		A wide variety of terms is used in various OAM standards. This
	section presents a comparison of the terms used in various OAM		section presents a comparison of the terms used in various OAM
	standards, without fully quoting the definition of each term.		standards, without fully quoting the definition of each term.
	skipping to change at page 14, line 22		skipping to change at page 14, line 37
	Point-to-point (P2P)		Point-to-point (P2P)
	A P2P service delivers data from a single source to a single		A P2P service delivers data from a single source to a single
	destination.		destination.
	Point-to-multipoint (P2MP)		Point-to-multipoint (P2MP)
	A P2MP service delivers data from a single source to a one or more		A P2MP service delivers data from a single source to a one or more
	destinations (based on [Signal]).		destinations (based on [Signal]).
	An MP2MP service as a service that delivers data from more than one		An MP2MP service is a service that delivers data from more than one
	source to one or more receivers (based on [Signal]).		source to one or more receivers (based on [Signal]).
			Note: the two definitions for P2MP and MP2MP are quoted from
			[Signal]. Although [Signal] describes a specific case of P2MP and
			MP2MP which is MPLS-specific, these two definitions also apply to
			non-MPLS cases.
	Discussion		Discussion
	The OAM tools described in this document include tools for P2P		The OAM tools described in this document include tools for P2P
	services, as well as tools for P2MP services.		services, as well as tools for P2MP services.
	The distinction between P2P services and P2MP services affects the		The distinction between P2P services and P2MP services affects the
	corresponding OAM tools. A P2P service is typically simpler to		corresponding OAM tools. A P2P service is typically simpler to
	monitor, as it consists of a single pair of end points. P2MP services		monitor, as it consists of a single pair of end points. P2MP services
	present several challenges. For example, in a P2MP service, the OAM		present several challenges. For example, in a P2MP service, the OAM
	mechanism not only verifies that each of the destinations is		mechanism not only verifies that each of the destinations is
	skipping to change at page 17, line 15		skipping to change at page 17, line 35
	ever increasing values for the TTL field, until the packets actually		ever increasing values for the TTL field, until the packets actually
	reach the destination. Because no application listens to port 33434		reach the destination. Because no application listens to port 33434
	at the destination, the destination returns ICMP Destination		at the destination, the destination returns ICMP Destination
	Unreachable Messages indicating an unreachable port. This event		Unreachable Messages indicating an unreachable port. This event
	indicates to the Traceroute application that it is finished. The		indicates to the Traceroute application that it is finished. The
	Traceroute program displays the round-trip delay associated with each		Traceroute program displays the round-trip delay associated with each
	of the attempts.		of the attempts.
	While Traceroute is a tool that finds *a* path from A to B, it should		While Traceroute is a tool that finds *a* path from A to B, it should
	be noted that traffic from A to B is often forwarded through Equal		be noted that traffic from A to B is often forwarded through Equal
	Cost Multiple Paths (ECMP). Paris Traceroute [Paris] is an extension		Cost Multiple Paths (ECMP). Paris Traceroute [PARIS] is an extension
	to Traceroute that attempts to discovers all the available paths from		to Traceroute that attempts to discovers all the available paths from
	A to B by scanning different values of header fields (such as UDP		A to B by scanning different values of header fields (such as UDP
	ports) in the probe packets.		ports) in the probe packets.
	It is noted that Traceroute is an application, and not a protocol. As		It is noted that Traceroute is an application, and not a protocol. As
	such, it has various different implementations. One of the most		such, it has various different implementations. One of the most
	common ones uses UDP probe packets, as described above. Other		common ones uses UDP probe packets, as described above. Other
	implementations exist that use other types of probe messages, such as		implementations exist that use other types of probe messages, such as
	ICMP or TCP.		ICMP or TCP.
	skipping to change at page 26, line 25		skipping to change at page 26, line 39
	provides a control channel associated with each PW. [VCCV] defines		provides a control channel associated with each PW. [VCCV] defines
	three Control Channel (CC) types, i.e., three possible methods for		three Control Channel (CC) types, i.e., three possible methods for
	transmitting and identifying OAM messages:		transmitting and identifying OAM messages:
	o CC Type 1: In-band VCCV, as described in [VCCV], is also referred		o CC Type 1: In-band VCCV, as described in [VCCV], is also referred
	to as "PWE3 Control Word with 0001b as first nibble". It uses the		to as "PWE3 Control Word with 0001b as first nibble". It uses the
	PW Associated Channel Header [PW-ACH].		PW Associated Channel Header [PW-ACH].
	o CC Type 2: Out-of-band VCCV [VCCV], is also referred to as "MPLS		o CC Type 2: Out-of-band VCCV [VCCV], is also referred to as "MPLS
	Router Alert Label". In this case the control channel is created		Router Alert Label". In this case the control channel is created
	by using the MPLS router alert label [RFC3032] immediately above		by using the MPLS router alert label [MPLS-ENCAPS] immediately
	the PW label.		above the PW label.
	o CC Type 3: TTL expiry VCCV [VCCV], is also referred to as "MPLS PW		o CC Type 3: TTL expiry VCCV [VCCV], is also referred to as "MPLS PW
	Label with TTL == 1", i.e., the control channel is identified when		Label with TTL == 1", i.e., the control channel is identified when
	the value of the TTL field in the PW label is set to 1.		the value of the TTL field in the PW label is set to 1.
	VCCV currently supports the following OAM tools: ICMP Ping, LSP Ping,		VCCV currently supports the following OAM tools: ICMP Ping, LSP Ping,
	and BFD. ICMP and LSP Ping are IP encapsulated before being sent over		and BFD. ICMP and LSP Ping are IP encapsulated before being sent over
	the PW ACH. BFD for VCCV [BFD-VCCV] supports two modes of		the PW ACH. BFD for VCCV [BFD-VCCV] supports two modes of
	encapsulation - either IP/UDP encapsulated (with IP/UDP header) or		encapsulation - either IP/UDP encapsulated (with IP/UDP header) or
	PW-ACH encapsulated (with no IP/UDP header) and provides support to		PW-ACH encapsulated (with no IP/UDP header) and provides support to
	skipping to change at page 34, line 16		skipping to change at page 34, line 30
	| | | | | loss | |		| | | | | loss | |
	| | | | | measur| |		| | | | | measur| |
	| | | | | ement | |		| | | | | ement | |
	+-----------+-------+--------+--------+-------+----------+		+-----------+-------+--------+--------+-------+----------+
	Table 4 Summary of the OAM Functionality in IETF OAM Tools		Table 4 Summary of the OAM Functionality in IETF OAM Tools
	5.3. Guidance to Network Equipment Vendors		5.3. Guidance to Network Equipment Vendors
	As mentioned in Section 1.4. , it is imperative for OAM tools to be		As mentioned in Section 1.4. , it is imperative for OAM tools to be
	capable of testing the actual data plane in as much accuracy as		capable of testing the actual data plane in as much accuracy as
	possible. Thus, it is important to enforce fate-sharing between OAM		possible. While this guideline may appear obvious, it is worthwhile
			to emphasize the key importance of enforcing fate-sharing between OAM
	traffic that monitors the data plane and the data plane traffic it		traffic that monitors the data plane and the data plane traffic it
	monitors.		monitors.
	6. Security Considerations		6. Security Considerations
	This memo presents an overview of existing OAM tools, and proposes		This memo presents an overview of existing OAM tools, and proposes
	no new OAM tools. Therefore, this document introduces no security		no new OAM tools. Therefore, this document introduces no security
	considerations. However, the OAM tools reviewed in this document can		considerations. However, the OAM tools reviewed in this document can
	and do present security issues. The reader is encouraged to review		and do present security issues. The reader is encouraged to review
	the Security Considerations section of each document referenced by		the Security Considerations section of each document referenced by
	skipping to change at page 35, line 31		skipping to change at page 35, line 48
	(BFD) for Multihop Paths", RFC 5883, June 2010.		(BFD) for Multihop Paths", RFC 5883, June 2010.
	[BFD-VCCV] Nadeau, T., Pignataro, C., "Bidirectional Forwarding		[BFD-VCCV] Nadeau, T., Pignataro, C., "Bidirectional Forwarding
	Detection (BFD) for the Pseudowire Virtual Circuit		Detection (BFD) for the Pseudowire Virtual Circuit
	Connectivity Verification (VCCV)", RFC 5885, June		Connectivity Verification (VCCV)", RFC 5885, June
	2010.		2010.
	[Comp] Bonaventure, O., "Computer Networking: Principles,		[Comp] Bonaventure, O., "Computer Networking: Principles,
	Protocols and Practice", 2008.		Protocols and Practice", 2008.
	[Cont] Dugal, D., Pignataro, C., Dunn, R., "Protecting the
	Router Control Plane", RFC 6192, March 2011.
	[Dup] Uijterwaal, H., "A One-Way Packet Duplication Metric",		[Dup] Uijterwaal, H., "A One-Way Packet Duplication Metric",
	RFC 5560, May 2009.		RFC 5560, May 2009.
	[G-ACh] Bocci, M., Vigoureux, M., Bryant, S., "MPLS Generic		[G-ACh] Bocci, M., Vigoureux, M., Bryant, S., "MPLS Generic
	Associated Channel", RFC 5586, June 2009.		Associated Channel", RFC 5586, June 2009.
	[ICMP-Ext] Bonica, R., Gan, D., Tappan, D., Pignataro, C., "ICMP		[ICMP-Ext] Bonica, R., Gan, D., Tappan, D., Pignataro, C., "ICMP
	Extensions for Multiprotocol Label Switching", RFC		Extensions for Multiprotocol Label Switching", RFC
	4950, August 2007.		4950, August 2007.
	skipping to change at page 37, line 38		skipping to change at page 38, line 5
	Loopback Functions", RFC 6435, November 2011.		Loopback Functions", RFC 6435, November 2011.
	[LSP-Ping] Kompella, K., Swallow, G., "Detecting Multi-Protocol		[LSP-Ping] Kompella, K., Swallow, G., "Detecting Multi-Protocol
	Label Switched (MPLS) Data Plane Failures", RFC 4379,		Label Switched (MPLS) Data Plane Failures", RFC 4379,
	February 2006.		February 2006.
	[Mng] Farrel, A., "Inclusion of Manageability Sections in		[Mng] Farrel, A., "Inclusion of Manageability Sections in
	Path Computation Element (PCE) Working Group Drafts",		Path Computation Element (PCE) Working Group Drafts",
	RFC 6123, February 2011.		RFC 6123, February 2011.
			[MPLS-ENCAPS] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
			Farinacci, D., Li, T. and A. Conta, "MPLS Label Stack
			Encoding", RFC 3032, January 2001.
	[MPLS-LM-DM] Frost, D., Bryant, S., "Packet Loss and Delay		[MPLS-LM-DM] Frost, D., Bryant, S., "Packet Loss and Delay
	Measurement for MPLS Networks", RFC 6374, September		Measurement for MPLS Networks", RFC 6374, September
	2011.		2011.
	[MPLS-OAM] Nadeau, T., Morrow, M., Swallow, G., Allan, D.,		[MPLS-OAM] Nadeau, T., Morrow, M., Swallow, G., Allan, D.,
	Matsushima, S., "Operations and Management (OAM)		Matsushima, S., "Operations and Management (OAM)
	Requirements for Multi-Protocol Label Switched (MPLS)		Requirements for Multi-Protocol Label Switched (MPLS)
	Networks", RFC 4377, February 2006.		Networks", RFC 4377, February 2006.
	[MPLS-OAM-FW] Allan, D., Nadeau, T., "A Framework for Multi-Protocol		[MPLS-OAM-FW] Allan, D., Nadeau, T., "A Framework for Multi-Protocol
	skipping to change at page 39, line 19		skipping to change at page 39, line 35
	[PW-G-ACh] Li, H., Martini, L., He, J., Huang, F., "Using the		[PW-G-ACh] Li, H., Martini, L., He, J., Huang, F., "Using the
	Generic Associated Channel Label for Pseudowire in the		Generic Associated Channel Label for Pseudowire in the
	MPLS Transport Profile (MPLS-TP)", RFC 6423, November		MPLS Transport Profile (MPLS-TP)", RFC 6423, November
	2011.		2011.
	[PW-MAP] Aissaoui, M., Busschbach, P., Martini, L., Morrow, M.,		[PW-MAP] Aissaoui, M., Busschbach, P., Martini, L., Morrow, M.,
	Nadeau, T., and Y(J). Stein, "Pseudowire (PW)		Nadeau, T., and Y(J). Stein, "Pseudowire (PW)
	Operations, Administration, and Maintenance (OAM)		Operations, Administration, and Maintenance (OAM)
	Message Mapping", RFC 6310, July 2011.		Message Mapping", RFC 6310, July 2011.
	[PW-Map] M. Aissaoui, P. Busschbach, L. Martini, M. Morrow, T.
	Nadeau, "Pseudowire (PW) Operations, Administration,
	and Maintenance (OAM) Message Mapping", RFC 6310, July
	2011.
	[Reorder] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov,		[Reorder] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov,
	S., and J. Perser, "Packet Reordering Metrics", RFC		S., and J. Perser, "Packet Reordering Metrics", RFC
	4737, November 2006.		4737, November 2006.
	[Signal] Yasukawa, S., "Signaling Requirements for Point-to-		[Signal] Yasukawa, S., "Signaling Requirements for Point-to-
	Multipoint Traffic-Engineered MPLS Label Switched		Multipoint Traffic-Engineered MPLS Label Switched
	Paths (LSPs)", RFC 4461, April 2006.		Paths (LSPs)", RFC 4461, April 2006.
	[TCPIP-Tools] Kessler, G., Shepard, S., "A Primer On Internet and		[TCPIP-Tools] Kessler, G., Shepard, S., "A Primer On Internet and
	TCP/IP Tools and Utilities", RFC 2151, June 1997.		TCP/IP Tools and Utilities", RFC 2151, June 1997.
	skipping to change at page 40, line 6		skipping to change at page 40, line 18
	[TP-LM-DM] Frost, D., Bryant, S., "A Packet Loss and Delay		[TP-LM-DM] Frost, D., Bryant, S., "A Packet Loss and Delay
	Measurement Profile for MPLS-Based Transport		Measurement Profile for MPLS-Based Transport
	Networks", RFC 6375, September 2011.		Networks", RFC 6375, September 2011.
	[TP-OAM-FW] Busi, I., Allan, D., "Operations, Administration and		[TP-OAM-FW] Busi, I., Allan, D., "Operations, Administration and
	Maintenance Framework for MPLS-based Transport		Maintenance Framework for MPLS-based Transport
	Networks ", RFC 6371, September 2011.		Networks ", RFC 6371, September 2011.
	[TP-Term] Van Helvoort, H., Andersson, L., Sprecher, N., "A		[TP-Term] Van Helvoort, H., Andersson, L., Sprecher, N., "A
	Thesaurus for the Terminology used in Multiprotocol		Thesaurus for the Terminology used in MPLS Transport
	Label Switching Transport Profile (MPLS-TP)		Profile (MPLS-TP) Internet-Drafts and RFCs in the
	drafts/RFCs and ITU-T's Transport Network		Context of the ITU-T's Transport Network
	Recommendations", work-in-progress, draft-ietf-mpls-		Recommendations", RFC 7087, December 2013.
	tp-rosetta-stone, July 2012.
	[TRILL-OAM] Senevirathne, T., Bond, D., Aldrin, S., Li, Y., Watve,		[TRILL-OAM] Senevirathne, T., Bond, D., Aldrin, S., Li, Y., Watve,
	R., "Requirements for Operations, Administration, and		R., "Requirements for Operations, Administration, and
	Maintenance (OAM) in Transparent Interconnection of		Maintenance (OAM) in Transparent Interconnection of
	Lots of Links (TRILL)", RFC 6905, March 2013.		Lots of Links (TRILL)", RFC 6905, March 2013.
	[TWAMP] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and		[TWAMP] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and
	Babiarz, J., "A Two-Way Active Measurement Protocol		Babiarz, J., "A Two-Way Active Measurement Protocol
	(TWAMP)", RFC 5357, October 2008.		(TWAMP)", RFC 5357, October 2008.
	[VCCV] Nadeau, T., Pignataro, C., "Pseudowire Virtual Circuit		[VCCV] Nadeau, T., Pignataro, C., "Pseudowire Virtual Circuit
	Connectivity Verification (VCCV): A Control Channel		Connectivity Verification (VCCV): A Control Channel
	for Pseudowires", RFC 5085, December 2007.		for Pseudowires", RFC 5085, December 2007.
	[VCCV-SURVEY] Del Regno, N., Malis, A., "The Pseudowire (PW) &		[VCCV-SURVEY] Del Regno, N., Malis, A., "The Pseudowire (PW) and
	Virtual Circuit Connectivity Verification (VCCV)		Virtual Circuit Connectivity Verification (VCCV)
	Implementation Survey Results", work-in-progress,		Implementation Survey Results", RFC 7079, November
	draft-ietf-pwe3-vccv-impl-survey-results, August 2013.		2013.
	Appendix A. List of OAM Documents		Appendix A. List of OAM Documents
	A.1. List of IETF OAM Documents		A.1. List of IETF OAM Documents
	Table 5 summarizes the OAM related RFCs published by the IETF.		Table 5 summarizes the OAM related RFCs published by the IETF.
	It is important to note that the table lists various RFCs that are		It is important to note that the table lists various RFCs that are
	different by nature. For example, some of these documents define OAM		different by nature. For example, some of these documents define OAM
	tools or OAM protocols (or both), while others define protocols that		tools or OAM protocols (or both), while others define protocols that
	skipping to change at page 44, line 7		skipping to change at page 44, line 16
	| | Connectivity Verification (VCCV) | |		| | Connectivity Verification (VCCV) | |
	| | [BFD-VCCV] | |		| | [BFD-VCCV] | |
	| +--------------------------------------+----------+		| +--------------------------------------+----------+
	| | Using the Generic Associated Channel | RFC 6423 |		| | Using the Generic Associated Channel | RFC 6423 |
	| | Label for Pseudowire in the MPLS | |		| | Label for Pseudowire in the MPLS | |
	| | Transport Profile (MPLS-TP) | |		| | Transport Profile (MPLS-TP) | |
	| | [PW-G-ACh] | |		| | [PW-G-ACh] | |
	| +--------------------------------------+----------+		| +--------------------------------------+----------+
	| | Pseudowire (PW) Operations, | RFC 6310 |		| | Pseudowire (PW) Operations, | RFC 6310 |
	| | Administration, and Maintenance (OAM)| |		| | Administration, and Maintenance (OAM)| |
	| | Message Mapping [PW-Map] | |		| | Message Mapping [PW-MAP] | |
	+-----------+--------------------------------------+----------+		+-----------+--------------------------------------+----------+
	|OWAMP and | A One-way Active Measurement Protocol| RFC 4656 |		|OWAMP and | A One-way Active Measurement Protocol| RFC 4656 |
	|TWAMP | [OWAMP] | |		|TWAMP | [OWAMP] | |
	| +--------------------------------------+----------+		| +--------------------------------------+----------+
	| | A Two-Way Active Measurement Protocol| RFC 5357 |		| | A Two-Way Active Measurement Protocol| RFC 5357 |
	| | [TWAMP] | |		| | [TWAMP] | |
	| +--------------------------------------+----------+		| +--------------------------------------+----------+
	| | Framework for IP Performance Metrics | RFC 2330 |		| | Framework for IP Performance Metrics | RFC 2330 |
	| | [IPPM-FW] | |		| | [IPPM-FW] | |
	| +--------------------------------------+----------+		| +--------------------------------------+----------+
End of changes. 33 change blocks.
	47 lines changed or deleted		57 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/