One document matched: draft-ietf-opsawg-mpls-tp-oam-def-08.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="no" ?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<rfc category="bcp" docName="draft-ietf-opsawg-mpls-tp-oam-def-08.txt" ipr="trust200902">
<!-- the 03-version -->

<front>
	<title abbrev="OAM terminology">"Guidelines for the use of the OAM acronym in the IETF"</title>

<author fullname="Loa Andersson"
	initials="L"
	surname="Andersson">
	<organization>Ericsson</organization>
		<address>
			<email>loa.andersson@ericsson.com</email>
		</address>

</author>
    
<author fullname="Huub van Helvoort"
	initials="H"
	surname="van Helvoort">
	<organization>Huawei Technologies</organization>
		<address>
			<email>hhelvoort@huawei.com</email>
		</address>
</author>    

<author fullname="Ron Bonica"
	initials="R"
	surname="Bonica">
	<organization>Juniper Networks</organization>
		<address>
			<email>rbonica@juniper.net</email>
		</address>
</author>

<author fullname="Dan Romascanu"
	initials="D"
	surname="Romascanu">
	<organization>Avaya</organization>
		<address>
			<email>dromasca@avaya.com</email>
		</address>
</author>
    
<author fullname="Scott Mansfield"
	initials="S"
	surname="Mansfield">
	<organization>Ericsson</organization>
		<address>
			<email>scott.mansfield@ericsson.com</email>
		</address>
</author>
    
<date year="2011" />

<keyword>Intended status: Best Current Practices</keyword>

<abstract>
	<t> 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 of recurring problems that are revisited time and again.
	</t>
	<t>This document provides a definition of the acronym OAM (Operations, Administration, and Maintenance) for use in all future IETF documents that refer to OAM.  There are other definitions and acronyms that will be discussed while exploring the definition of the constituent parts of the OAM term.
	</t>

</abstract>
</front>

<middle>
<!-- section 1 -->

<section anchor="intro" title="Introduction">
	<t> The main purpose of this document is to provide a definition of the OAM acronym such that it is useful for the IETF.
	</t>
	<t> The acronym OAM is frequently used in the data and telecommunication industry. One would assume that something that is so widely used is very clearly defined. However a closer look reveals some points that need to be clarified.
	</t>
      
	<t> The examples below show a number of different ways that the OAM acronym has been expanded in previous documents.
	<list style="symbols">
      
		<t> OAM = Operation, Administration, Maintenance
		</t>
	 
		<t> OAM = Operations, Administration, Maintenance
		</t>

		<t> OAM = Operations, Administration, and Maintenance
		</t>
	 
		<t> OAM = Operations, Administration, Management
		</t>
	 
		<t> OAM = Operations and Maintenance
		</t>
	 
		<t> OAM = Operations and Management
		</t>
	 
		<t> O&M = Operations and Maintenance
		</t>
	 
		<t> O&M = Operations and Management
		</t>
	 
		<t> O&M = OAM and Management
		</t>
	 	         
	</list>
	</t>

	<t> Sometimes there is a fourth letter added to the acronym:
	<list style="symbols">
		<t> OAM and P = Operations, Administration, Maintenance and Provisioning
		</t>
	</list>
	</t>

	<t> If such an important piece of our technology is so poorly defined, or if there are dialects of the technology with different understandings of such a key concept, this will eventually cause problems.
	</t>

	<t> 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 acronym represents an integrated piece of functionality; secondly the acronym as such represents something that is more than just the sum of its parts.
	</t>

	<t> 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 is defined and provides possible interpretations of the acronym.  Finally a recommendation for the interpretation of the OAM acronym is provided.
	</t>

	<t> Another useful document to make the OAM term understandable in a wider scope is found in <xref target="I-D.ietf-opsawg-oam-overview"> An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms </xref>.
	</t>

<!-- end section 1 -->
</section>

<!-- section 2 -->

<section anchor="acronym-oam" title="OAM and O, A and M">

<section anchor="acronym-unit" title="OAM as a Functional Unit">

	<t> Operations And Maintenance (OAM): A group of network management functions that provide network fault indication, performance information, and data and diagnosis functions.  ATM OAM <xref target="ITU-T-I.610">ITU-T I.610</xref> is an example specification that uses this expansion of the OAM acronym.
	</t>

	<t> Operations, Administration, and Maintenance (OAM): A group of network management functions that provide network fault indication, fault localization, performance information, and data and diagnosis functions.  Examples where this acronym is used are Clause 57 of <xref target="IEEE.802.3-2008">IEEE 802.3-2008</xref> and <xref target="ITU-T-Y.1731">ITU-T Y.1731</xref>.
	</t>

	<t> The <xref target="ITU-T-M.3010">ITU-T M.3010</xref> Recommendation defines operations systems function as a function block that processes information related to the telecommunications management for the purpose of monitoring/coordinating and/or controlling telecommunication functions including management functions (i.e., the TMN (Telecommunications Management Network) itself).
	</t>

	<t> The Metro Ethernet Forum refers to OAM as the tools and utilities to install, monitor and troubleshoot a network, helping carriers run their networks more effectively <xref target="MEF-17">MEF 17</xref>. 
	</t>

</section>

<section anchor="acronym-o" title="The Acronym Broken Up">

<section anchor="O" title="O in OAM">

	<t> The O in the OAM acronym invariably stands for "Operations".
	</t>

	<t> However there is some ambivalence in the definition and scope of the term "Operation".
	</t>
       
	<t> Examples of tools related to "operations" are performance monitoring tools used for service level agreement (SLA) measurement, fault management tools used to monitor the health of nodes and links in the network, and network provisioning tools.
	</t>

</section>

<section anchor="A" title="A in OAM">

	<t> The A in the OAM acronym stands for "Administration".
	</t>

	<t> Examples of "administration" tools are network discovery and planning tools.
	</t>

</section>

<section anchor="M" title="M in OAM">

	<t> In the list above the M in the OAM acronym stands for "Maintenance" or "Management".
	</t>

	<t> Maintenance and Management may have different interpretations. Maintenance is defined further in Section 3, while Management is a broader term applicable to many functions applied to the network as described in Section 3.
	</t>

	<t> Since these terms have different interpretations, it is not a good idea to use them interchangeably.  This document defines the "M" in the OAM acronym to mean Maintenance.
	</t>

	<t> Examples of "maintenance" tools are implementations of connectivity check, loopback, link trace, and other tools that can be used to monitor and diagnose failures in a network or network element.
	</t>

	<t> The Recommendation <xref target="ITU-T-M.20">ITU-T M.20</xref> defines maintenance as the whole of operations required for setting up and maintaining, within prescribed limits, any element involved in the setting up of a connection (see the <xref target="ITU-T-M.60">ITU-T M.60</xref> Recommendation). The purpose is to properly plan and program the maintenance operations required to establish and maintain a network.
	</t>

	<t> 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 failure the correct actions are taken.
	</t>

</section>

</section>

<!-- end of section 2 -->
</section>

<!-- section 3 -->

<section anchor="solution" title="Recommendations on the use of the OAM Acronym">
	<t> In  <xref target="acro"/> the recommended acronyms are listed.  This section gives some background on the definitions provided.
	</t>

	<t> "Mgmt" will be used if an abbreviation for "Management" is needed.  This draft does not define Management.  It is noted, however, that an important part of management functionality relates to tools to report the state of the network.
	</t>

	<t> The OAM acronym is to be used for "Operations, Administration, and Maintenance", excluding provisioning.
	</t>

	<t> OAM tools and protocols, and the "Management space" are complementary in nature. Management focuses on FCAPS (Fault, Configuration, Accounting, Performance, and Security) functionality and on manager (or NOC (Network Operations Center)) to device (or network) interaction. 
	</t>

	<t> From an architecture point of view OAM protocols and tools deployed in the data plane tend to be "horizontal", i.e., network element to network element. The management protocols tend to be "vertical", i.e., between management stations and network elements.
	</t>

	<t> The components of the OAM acronym (and provisioning) are defined as follows:
	<list style="symbols">

		<t> Operations - Operation activities are undertaken to keep the network (and the services that the network provides) up and running. It includes monitoring the network and finding problems. Ideally these problems should be found before users are affected.
		</t>

		<t> Administration - Administration activities involve keeping track of resources in the network and how they are used. It includes all the bookkeeping that is necessary to track networking resources and the network under control.
		</t>

		<t> Maintenance - Maintenance activities are focused on facilitating repairs and upgrades - for example, when equipment must be replaced, when a router needs a patch for an operating system image, or when a new switch is added to a network. Maintenance also involves corrective and preventive measures to make the managed network run more effectively, e.g., adjusting device configuration and parameters.
		</t>
	</list>

	</t>

	<t> "Provisioning" is outside the scope of this document, but the following definition is provided for completeness.
	</t>

	<t>
	<list style="symbols">

		<t> Provisioning -  Provisioning activities involve configuring resources in the network to support the offered services. This might include setting up the network so that a new customer can receive an Internet access service.
		</t>
	</list>
	</t>

	<t> 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 it can support already existing services.
	</t>

	<t> Sometimes it is necessary to talk about the combination of functions 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 needed O&M should be used.
	</t>

<!-- end of section 3 -->
</section>

<!-- section 4 -->
<section anchor="acro" title="Recommended Acronyms">

	<t> OAM - Operations, Administration, and Maintenance
	</t>

	<t> O&M - OAM and Management
	</t>

	<t> "Mgmt" - Management
	</t>

<!-- end of section 4 -->
</section>

<!-- section 5 -->
<section anchor="iana" title="IANA Considerations">

	<t> This memo includes no request to IANA.
	</t>

<!-- end of section 5 -->
</section>

<!-- section 6 -->
<section anchor="security" title="Security Considerations">

	<t> This document provides guidance for the use of the OAM acronym in other documents. This document does not have direct security implications.
	</t>

	<t> Misunderstanding of an acronym may lead to incorrect specification or implementation which may, in turn, open up security concerns with protocols or deployed networks. Clarifying the meaning of OAM is, therefore, a benefit for future stability of specifications.  
	</t>

<!-- end of section  6 -->
</section>

<!-- section 7 -->

<section anchor="acknowledgments" title="Acknowledgments">

	<t> The following individuals significantly contributed to this document.
	<list style="symbols">
      
		<t> Malcolm Betts from M. C. Betts Consulting Ltd.
		</t>
	 
		<t> Kam Lam from Alcatel Lucent
		</t>

		<t> Dieter Beller from Alcatel Lucent
		</t>
		
		<t> David Harrington from Huawei Technologies
		</t>
	</list>
	</t>
	<t> Thanks to the experts of ITU-T SG 15 for their review and comments.
	</t>

</section>
<!-- end of section  7 -->    

</middle>

<back>

<references title="Informative references">
	<?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-opsawg-oam-overview.xml" ?>
	<reference anchor="IEEE.802.3-2008">
		<front>
			<title>Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications"</title>
			<author>
				<organization>IEEE</organization>
			</author>
			<date month="December" year="2008" />
		</front>
		<seriesInfo name="IEEE" value="Standard 802.3" />
	</reference>
	
	<reference anchor="ITU-T-I.610">
		<front>
			<title>B-ISDN operation and maintenance principles and functions</title>
			<author>
				<organization>International Telecommunication Union</organization>
			</author>
			<date month="February" year="1999"/>
		</front>
		<seriesInfo name="ITU-T" value="Recommendation I.610"/>
	</reference>

	<reference anchor="ITU-T-M.20">
		<front>
			<title>Maintenance philosophy for telecommunication networks</title>
			<author>
				<organization>International Telecommunication Union</organization>
			</author>
			<date month="October" year="1992"/>
		</front>
		<seriesInfo name="ITU-T" value="Recommendation M.20"/>
	</reference>

	<reference anchor="ITU-T-M.60">
		<front>
			<title>Maintenance terminology and definitions</title>
			<author>
				<organization>International Telecommunication Union</organization>
			</author>
			<date month="March" year="1993"/>
		</front>
		<seriesInfo name="ITU-T" value="Recommendation M.60"/>
	</reference>

	<reference anchor="ITU-T-M.3010">
		<front>
			<title>Principles for a telecommunications management network</title>
			<author>
				<organization>International Telecommunication Union</organization>
			</author>
			<date month="February" year="2000"/>
		</front>
		<seriesInfo name="ITU-T" value="Recommendation M.3010"/>
	</reference>

	<reference anchor="ITU-T-Y.1731">
		<front>
			<title>OAM functions and mechanisms for Ethernet based networks</title>
			<author>
				<organization>International Telecommunication Union</organization>
			</author>
			<date month="February" year="2008"/>
		</front>
		<seriesInfo name="ITU-T" value="Recommendation Y.1731"/>
	</reference>

	<reference anchor="MEF-17">
		<front>
			<title>Service OAM Requirements & Framework - Phase 1 </title>
			<author>
				<organization>Metro Ethernet Forum</organization>
			</author>
			<date month="April" year="2007"/>
		</front>
		<seriesInfo name="MEF" value="Technical Specification MEF 17"/>
	</reference>
<!--    </references> -->
</references>
</back>
</rfc>