draft-ietf-opsawg-mpls-tp-oam-def-10.txt		rfc6291.txt
	Network Working Group L. Andersson		Internet Engineering Task Force (IETF) L. Andersson
	Internet-Draft Ericsson		Request for Comments: 6291 Ericsson
	Intended status: BCP H. van Helvoort		BCP: 161 H. van Helvoort
	Expires: November 13, 2011 Huawei Technologies		Category: Best Current Practice Huawei Technologies
	R. Bonica		ISSN: 2070-1721 R. Bonica
	Juniper Networks		Juniper Networks
	D. Romascanu		D. Romascanu
	Avaya		Avaya
	S. Mansfield		S. Mansfield
	Ericsson		Ericsson
	May 12, 2011		June 2011
	"Guidelines for the use of the OAM acronym in the IETF"		Guidelines for the Use of the "OAM" Acronym in the IETF
	draft-ietf-opsawg-mpls-tp-oam-def-10.txt
	Abstract		Abstract
	At first glance the acronym "OAM" seems to be well known and well		At first glance, the acronym "OAM" seems to be well-known and well-
	understood. Looking at the acronym a bit more closely reveals a set		understood. Looking at the acronym a bit more closely reveals a set
	of recurring problems that are revisited time and again.		of recurring problems that are revisited time and again.
	This document provides a definition of the acronym OAM (Operations,		This document provides a definition of the acronym "OAM" (Operations,
	Administration, and Maintenance) for use in all future IETF documents		Administration, and Maintenance) for use in all future IETF documents
	that refer to OAM. There are other definitions and acronyms that		that refer to OAM. There are other definitions and acronyms that
	will be discussed while exploring the definition of the constituent		will be discussed while exploring the definition of the constituent
	parts of the OAM term.		parts of the "OAM" term.
	Status of this Memo
	This Internet-Draft is submitted in full conformance with the		Status of This Memo
	provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		This memo documents an Internet Best Current Practice.
	Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		This document is a product of the Internet Engineering Task Force
	and may be updated, replaced, or obsoleted by other documents at any		(IETF). It represents the consensus of the IETF community. It has
	time. It is inappropriate to use Internet-Drafts as reference		received public review and has been approved for publication by the
	material or to cite them other than as "work in progress."		Internet Engineering Steering Group (IESG). Further information on
			BCPs is available in Section 2 of RFC 5741.
	This Internet-Draft will expire on November 13, 2011.		Information about the current status of this document, any errata,
			and how to provide feedback on it may be obtained at
			http://www.rfc-editor.org/info/rfc6291.
	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
	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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3		1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Pre-existing uses of OAM . . . . . . . . . . . . . . . . . . . 3		2. Pre-Existing Uses of OAM . . . . . . . . . . . . . . . . . . . 3
	2.1. Uses of OAM in other SDOs . . . . . . . . . . . . . . . . . 4		2.1. Uses of OAM in Other SDOs . . . . . . . . . . . . . . . . . 4
	2.1.1. O in OAM . . . . . . . . . . . . . . . . . . . . . . . 4		2.1.1. The "O" in OAM . . . . . . . . . . . . . . . . . . . . 4
	2.1.2. A in OAM . . . . . . . . . . . . . . . . . . . . . . . 4		2.1.2. The "A" in OAM . . . . . . . . . . . . . . . . . . . . 4
	2.1.3. M in OAM . . . . . . . . . . . . . . . . . . . . . . . 4		2.1.3. The "M" in OAM . . . . . . . . . . . . . . . . . . . . 5
	2.2. Uses of OAM in the IETF . . . . . . . . . . . . . . . . . . 5		2.2. Uses of OAM in the IETF . . . . . . . . . . . . . . . . . . 5
	3. Recommendations on the use of the OAM Acronym . . . . . . . . . 5		3. Recommendations on the Use of the "OAM" Acronym . . . . . . . . 5
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6		4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
	5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6		5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7		6. Informative References . . . . . . . . . . . . . . . . . . . . 7
	7. Informative references . . . . . . . . . . . . . . . . . . . . 7
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
	1. Introduction		1. Introduction
	The main purpose of this document is to provide a definition of the		The main purpose of this document is to provide a definition of the
	acronym OAM (Operations, Administration, and Maintenance) for use in		acronym "OAM" (Operations, Administration, and Maintenance) for use
	all future IETF documents that refer to OAM.		in all future IETF documents that refer to OAM.
	The acronym OAM is frequently used in the data and telecommunication		The acronym "OAM" is frequently used in the data and
	industry. One would assume that something that is so widely used is		telecommunication industry. One would assume that something that is
	very clearly defined. However a closer look reveals some points that		so widely used is very clearly defined. However, a closer look
	need to be clarified.		reveals some points that need to be clarified.
	If such an important piece of our technology is so poorly defined, or		If such an important piece of our technology is so poorly defined, or
	if there are dialects of the technology with different understandings		if there are dialects of the technology with different understandings
	of such a key concept, this will eventually cause problems.		of such a key concept, this will eventually cause problems.
	Trying to understand the use of an acronym that is as "content-rich"		Trying to understand the use of an acronym that is as "content-rich"
	as OAM reveals two levels of complexity. First, each letter in the		as OAM reveals two levels of complexity. First, each letter in the
	acronym represents an integrated piece of functionality; secondly the		acronym represents an integrated piece of functionality. Second, the
	acronym as such represents something that is more than just the sum		acronym, as such, represents something that is more than just the sum
	of its parts.		of its parts.
	There is also the issue of how each piece of the acronym is defined.		There is also the issue of how each piece of the acronym is defined.
	This document provides an analysis of how each piece of the acronym		This document provides an analysis of what each initial of the
	is defined and provides possible interpretations of the acronym.		initialism represents and provides possible interpretations of the
	Finally a recommendation for the interpretation of the OAM acronym is		acronym. Finally, a recommendation for the interpretation of the
	provided.		"OAM" acronym is provided.
	Another useful document to make the OAM term understandable in a		Another useful document to make the "OAM" term understandable in a
	wider scope is found in An Overview of Operations, Administration,		wider scope is found in "An Overview of Operations, Administration,
	and Maintenance (OAM) Mechanisms [I-D.ietf-opsawg-oam-overview].		and Maintenance (OAM) Mechanisms" [OAM-OVERVIEW].
	1.1. Terminology		1.1. Terminology
	o "Mgmt" - Management		o "Mgmt" - Management
	o O&M - OAM and Management		o O&M - OAM and Management
	o OAM - Operations, Administration, and Maintenance		o OAM - Operations, Administration, and Maintenance
	o SDO - Standards Development Organization		o SDO - Standards Development Organization
	2. Pre-existing uses of OAM		2. Pre-Existing Uses of OAM
	This section provides information on how OAM is used in other SDOs		This section provides information on how OAM is used in other SDOs
	(Standards Development Organization) and provides the background		(Standards Development Organizations) and provides the background
	necessary to understand the how the term is used in the IETF.		necessary to understand the how the term is used in the IETF.
	2.1. Uses of OAM in other SDOs		2.1. Uses of OAM in Other SDOs
	Operations And Maintenance (OAM): A group of network management		Operations And Maintenance (OAM): A group of network management
	functions that provide network fault indication, performance		functions that provide network fault indication, performance
	information, and data and diagnosis functions. ATM OAM ITU-T I.610		information, and data and diagnosis functions. ATM OAM ITU-T I.610
	[ITU-T-I.610] is an example specification that uses this expansion of		[ITU-T-I.610] is an example specification that uses this expansion of
	the OAM acronym.		the "OAM" acronym.
	Operations, Administration, and Maintenance (OAM): A group of network		Operations, Administration, and Maintenance (OAM): A group of network
	management functions that provide network fault indication, fault		management functions that provide network fault indication, fault
	localization, performance information, and data and diagnosis		localization, performance information, and data and diagnosis
	functions. Examples where this acronym is used are Clause 57 of IEEE		functions. Examples where this acronym is used are Clause 57 of IEEE
	802.3-2008 [IEEE.802.3-2008] and ITU-T Y.1731 [ITU-T-Y.1731].		802.3-2008 [IEEE.802.3-2008] and ITU-T Y.1731 [ITU-T-Y.1731].
	The ITU-T M.3010 [ITU-T-M.3010] Recommendation defines operations		The ITU-T M.3010 [ITU-T-M.3010] Recommendation defines operations
	systems function as a function block that processes information		systems function as a function block that processes information
	related to the telecommunications management for the purpose of		related to the telecommunications management for the purpose of
	monitoring/coordinating and/or controlling telecommunication		monitoring/coordinating and/or controlling telecommunication
	functions including management functions (i.e., the TMN		functions including management functions (i.e., the TMN
	(Telecommunications Management Network) itself).		(Telecommunications Management Network) itself).
	The Metro Ethernet Forum refers to OAM as the tools and utilities to		The Metro Ethernet Forum refers to OAM as the tools and utilities to
	install, monitor and troubleshoot a network, helping carriers run		install, monitor, and troubleshoot a network, helping carriers run
	their networks more effectively MEF 17 [MEF-17].		their networks more effectively MEF 17 [MEF-17].
	2.1.1. O in OAM		2.1.1. The "O" in OAM
	The O in the OAM acronym invariably stands for "Operations". However		The "O" in OAM invariably stands for "Operations". However, there is
	there is some ambivalence in the definition and scope of the term		some ambivalence in the definition and scope of the term "Operation".
	"Operation".
	Examples of tools related to "operations" are performance monitoring		Examples of tools related to "operations" are performance monitoring
	tools used for service level agreement (SLA) measurement, fault		tools used for service level agreement (SLA) measurement, fault
	management tools used to monitor the health of nodes and links in the		management tools used to monitor the health of nodes and links in the
	network, and network provisioning tools.		network, and network provisioning tools.
	2.1.2. A in OAM		2.1.2. The "A" in OAM
	The A in the OAM acronym stands for "Administration".		The "A" in OAM stands for "Administration".
	Examples of "administration" tools are network discovery and planning		Examples of "administration" tools are network discovery and planning
	tools.		tools.
	2.1.3. M in OAM		2.1.3. The "M" in OAM
	The M in the OAM acronym stands for "Maintenance" or "Management".		The "M" in OAM stands for "Maintenance" or "Management".
	Examples of "maintenance" tools are implementations of connectivity		Examples of "maintenance" tools are implementations of connectivity
	check, loopback, link trace, and other tools that can be used to		check, loopback, link trace, and other tools that can be used to
	monitor and diagnose failures in a network or network element.		monitor and diagnose failures in a network or network element.
	The Recommendation ITU-T M.20 [ITU-T-M.20] defines maintenance as the		The Recommendation ITU-T M.20 [ITU-T-M.20] defines maintenance as the
	whole of operations required for setting up and maintaining, within		whole of operations required for setting up and maintaining, within
	prescribed limits, any element involved in the setting up of a		prescribed limits, any element involved in the setting up of a
	connection (see the ITU-T M.60 [ITU-T-M.60] Recommendation). The		connection (see the ITU-T M.60 [ITU-T-M.60] Recommendation). The
	purpose is to properly plan and program the maintenance operations		purpose is to properly plan and program the maintenance operations
	required to establish and maintain a network.		required to establish and maintain a network.
	A major aim of the concept of maintenance is to minimize both the		A major aim of the concept of maintenance is to minimize both the
	occurrence and the impact of failures and to ensure that in case of a		occurrence and the impact of failures and to ensure that in case of a
	failure the correct actions are taken.		failure the correct actions are taken.
	2.2. Uses of OAM in the IETF		2.2. Uses of OAM in the IETF
	The examples below show a number of different ways that the OAM		The examples below show a number of different ways that the "OAM"
	acronym has been expanded in IETF RFCs. The reference list is not		acronym has been expanded in IETF RFCs. The reference list is not
	exhaustive.		exhaustive.
	o OAM = Operations, Administration, and Maintenance in RFC 5586		o OAM = Operations, Administration, and Maintenance in RFC 5586
	[RFC5586]		[RFC5586]
	o OAM = Operations and Maintenance in RFC 3429 [RFC3429]		o OAM = Operations and Maintenance in RFC 3429 [RFC3429]
	o OAM = Operations and Management in RFC 4377 [RFC4377]		o OAM = Operations and Management in RFC 4377 [RFC4377]
	o O&M = OAM and Maintenance in RFC 1812 [RFC1812]		o O&M = OAM and Maintenance in RFC 1812 [RFC1812]
	Sometimes there is a fourth letter added to the acronym:		Sometimes there is a fourth letter added to the acronym:
	o OAM&P = Operations, Administration, Maintenance and Provisioning		o OAM&P = Operations, Administration, Maintenance and Provisioning
	in RFC 4594 [RFC4594]		in RFC 4594 [RFC4594]
	3. Recommendations on the use of the OAM Acronym		3. Recommendations on the Use of the "OAM" Acronym
	The IETF recommended expansion of the OAM acronym is given below. In		The IETF-recommended expansion of the "OAM" acronym is given below.
	addition to the OAM acronym, two other recommendations are made in		In addition to the "OAM" acronym, two other recommendations are made
	this section.		in this section.
	o OAM - Operations, Administration, and Maintenance		o OAM - Operations, Administration, and Maintenance
	o O&M - OAM and Management		o O&M - OAM and Management
	o "Mgmt" - Management		o "Mgmt" - Management
	The components of the OAM acronym (and provisioning) are defined as		The components of the "OAM" acronym (and provisioning) are defined as
	follows:		follows:
	o Operations - Operation activities are undertaken to keep the		o Operations - Operation activities are undertaken to keep the
	network (and the services that the network provides) up and		network (and the services that the network provides) up and
	running. It includes monitoring the network and finding problems.		running. It includes monitoring the network and finding problems.
	Ideally these problems should be found before users are affected.		Ideally these problems should be found before users are affected.
	o Administration - Administration activities involve keeping track		o Administration - Administration activities involve keeping track
	of resources in the network and how they are used. It includes		of resources in the network and how they are used. It includes
	all the bookkeeping that is necessary to track networking		all the bookkeeping that is necessary to track networking
	resources and the network under control.		resources and the network under control.
	o Maintenance - Maintenance activities are focused on facilitating		o Maintenance - Maintenance activities are focused on facilitating
	repairs and upgrades - for example, when equipment must be		repairs and upgrades -- for example, when equipment must be
	replaced, when a router needs a patch for an operating system		replaced, when a router needs a patch for an operating system
	image, or when a new switch is added to a network. Maintenance		image, or when a new switch is added to a network. Maintenance
	also involves corrective and preventive measures to make the		also involves corrective and preventive measures to make the
	managed network run more effectively, e.g., adjusting device		managed network run more effectively, e.g., adjusting device
	configuration and parameters.		configuration and parameters.
	"Provisioning" is outside the scope of this document, but the		"Provisioning" is outside the scope of this document, but the
	following definition is provided for completeness.		following definition is provided for completeness.
	o Provisioning - Provisioning activities involve configuring		o Provisioning - Provisioning activities involve configuring
	skipping to change at page 6, line 32		skipping to change at page 6, line 42
	might include setting up the network so that a new customer can		might include setting up the network so that a new customer can
	receive an Internet access service.		receive an Internet access service.
	In general, Provisioning is used to configure the network to provide		In general, Provisioning is used to configure the network to provide
	new services, whereas OAM is used to keep the network in a state that		new services, whereas OAM is used to keep the network in a state that
	it can support already existing services.		it can support already existing services.
	Sometimes it is necessary to talk about the combination of functions		Sometimes it is necessary to talk about the combination of functions
	and tools supplied by OAM and Management, it is preferred that this		and tools supplied by OAM and Management, it is preferred that this
	is spelled out as "OAM and Management". In cases where an acronym is		is spelled out as "OAM and Management". In cases where an acronym is
	needed O&M should be used.		needed, O&M should be used.
	"Mgmt" will be used if an abbreviation for "Management" is needed.		"Mgmt" will be used if an abbreviation for "Management" is needed.
	This document does not define Management.		This document does not define Management.
	4. IANA Considerations		4. Security Considerations
	This memo includes no request to IANA.
	5. Security Considerations
	This document provides guidance for the use of the OAM acronym in		This document provides guidance for the use of the "OAM" acronym in
	other documents. This document does not have direct security		other documents. This document does not have direct security
	implications.		implications.
	Misunderstanding of an acronym may lead to incorrect specification or		The misunderstanding of an acronym may lead to incorrect
	implementation which may, in turn, open up security concerns with		specification or implementation which may, in turn, open up security
	protocols or deployed networks. Clarifying the meaning of OAM is,		concerns with protocols or deployed networks. Clarifying the meaning
	therefore, a benefit for future stability of specifications.		of OAM is, therefore, a benefit for future stability of
			specifications.
	6. Acknowledgments		5. Acknowledgments
	The following individuals significantly contributed to this document.		The following individuals significantly contributed to this document.
	o Malcolm Betts from M. C. Betts Consulting Ltd.
			o Malcolm Betts from M. C. Betts Consulting, Ltd.
	o Kam Lam from Alcatel Lucent		o Kam Lam from Alcatel Lucent
	o Dieter Beller from Alcatel Lucent		o Dieter Beller from Alcatel Lucent
	o David Harrington from Huawei Technologies		o David Harrington from Huawei Technologies
	Thanks to the experts of ITU-T SG 15 for their review and comments.		Thanks to the experts of ITU-T SG 15 for their review and comments.
	7. Informative references		6. Informative References
	[I-D.ietf-opsawg-oam-overview]		[IEEE.802.3-2008] IEEE, "Information technology - Telecommunications
	Mizrahi, T., Sprecher, N., Bellagamba, E., and Y.		and information exchange between systems - Local
	Weingarten, "An Overview of Operations, Administration,		and metropolitan area networks - Specific
	and Maintenance (OAM) Mechanisms",		requirements - Part 3: Carrier sense multiple
	draft-ietf-opsawg-oam-overview-04 (work in progress),		access with collision detection (CSMA/CD) access
	March 2011.		method and physical layer specifications",
			IEEE Standard 802.3, December 2008.
	[IEEE.802.3-2008]		[ITU-T-I.610] International Telecommunication Union, "B-ISDN
	IEEE, "Information technology - Telecommunications and		operation and maintenance principles and
	information exchange between systems - Local and		functions", ITU-T Recommendation I.610,
	metropolitan area networks - Specific requirements - Part		February 1999.
	3: Carrier sense multiple access with collision detection
	(CSMA/CD) access method and physical layer
	specifications"", IEEE Standard 802.3, December 2008.
	[ITU-T-I.610]		[ITU-T-M.20] International Telecommunication Union,
	International Telecommunication Union, "B-ISDN operation		"Maintenance philosophy for telecommunication
	and maintenance principles and functions", ITU-		networks", ITU-T Recommendation M.20,
	T Recommendation I.610, February 1999.		October 1992.
	[ITU-T-M.20]		[ITU-T-M.3010] International Telecommunication Union, "Principles
	International Telecommunication Union, "Maintenance		for a telecommunications management network", ITU-
	philosophy for telecommunication networks", ITU-		T Recommendation M.3010, February 2000.
	T Recommendation M.20, October 1992.
	[ITU-T-M.3010]		[ITU-T-M.60] International Telecommunication Union,
	International Telecommunication Union, "Principles for a		"Maintenance terminology and definitions", ITU-
	telecommunications management network", ITU-		T Recommendation M.60, March 1993.
	T Recommendation M.3010, February 2000.
	[ITU-T-M.60]		[ITU-T-Y.1731] International Telecommunication Union, "OAM
	International Telecommunication Union, "Maintenance		functions and mechanisms for Ethernet based
	terminology and definitions", ITU-T Recommendation M.60,		networks", ITU-T Recommendation Y.1731,
	March 1993.		February 2008.
	[ITU-T-Y.1731]		[MEF-17] Metro Ethernet Forum, "Service OAM Requirements &
	International Telecommunication Union, "OAM functions and		Framework - Phase 1", MEF Technical Specification
	mechanisms for Ethernet based networks", ITU-		MEF 17, April 2007.
	T Recommendation Y.1731, February 2008.
	[MEF-17] Metro Ethernet Forum, "Service OAM Requirements &		[OAM-OVERVIEW] Mizrahi, T., Sprecher, N., Bellagamba, E., and Y.
	Framework - Phase 1", MEF Technical Specification MEF 17,		Weingarten, "An Overview of Operations,
	April 2007.		Administration, and Maintenance (OAM) Mechanisms",
			Work in Progress, March 2011.
	[RFC1812] Baker, F., "Requirements for IP Version 4 Routers",		[RFC1812] Baker, F., "Requirements for IP Version 4
	RFC 1812, June 1995.		Routers", RFC 1812, June 1995.
	[RFC3429] Ohta, H., "Assignment of the 'OAM Alert Label' for		[RFC3429] Ohta, H., "Assignment of the 'OAM Alert Label' for
	Multiprotocol Label Switching Architecture (MPLS)		Multiprotocol Label Switching Architecture (MPLS)
	Operation and Maintenance (OAM) Functions", RFC 3429,		Operation and Maintenance (OAM) Functions",
	November 2002.		RFC 3429, November 2002.
	[RFC4377] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S.		[RFC4377] Nadeau, T., Morrow, M., Swallow, G., Allan, D.,
	Matsushima, "Operations and Management (OAM) Requirements		and S. Matsushima, "Operations and Management
	for Multi-Protocol Label Switched (MPLS) Networks",		(OAM) Requirements for Multi-Protocol Label
	RFC 4377, February 2006.		Switched (MPLS) Networks", RFC 4377,
			February 2006.
	[RFC4594] Babiarz, J., Chan, K., and F. Baker, "Configuration		[RFC4594] Babiarz, J., Chan, K., and F. Baker,
	Guidelines for DiffServ Service Classes", RFC 4594,		"Configuration Guidelines for DiffServ Service
	August 2006.		Classes", RFC 4594, August 2006.
	[RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic		[RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS
	Associated Channel", RFC 5586, June 2009.		Generic Associated Channel", RFC 5586, June 2009.
	Authors' Addresses		Authors' Addresses
	Loa Andersson		Loa Andersson
	Ericsson		Ericsson
	Email: loa.andersson@ericsson.com		EMail: loa.andersson@ericsson.com
	Huub van Helvoort		Huub van Helvoort
	Huawei Technologies		Huawei Technologies
	Email: hhelvoort@huawei.com		EMail: huub.van.helvoort@huawei.com
	Ron Bonica		Ron Bonica
	Juniper Networks		Juniper Networks
	Email: rbonica@juniper.net		EMail: rbonica@juniper.net
	Dan Romascanu		Dan Romascanu
	Avaya		Avaya
	Email: dromasca@avaya.com		EMail: dromasca@avaya.com
	Scott Mansfield		Scott Mansfield
	Ericsson		Ericsson
	Email: scott.mansfield@ericsson.com		EMail: scott.mansfield@ericsson.com
End of changes. 71 change blocks.
	139 lines changed or deleted		142 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/