draft-ietf-opsawg-mpls-tp-oam-def-06.txt   draft-ietf-opsawg-mpls-tp-oam-def-07.txt 
Network Working Group L. Andersson Network Working Group L. Andersson
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Informational H. van Helvoort Intended status: BCP H. van Helvoort
Expires: December 26, 2010 Huawei Technologies Expires: March 31, 2011 Huawei Technologies
R. Bonica R. Bonica
Juniper Networks Juniper Networks
D. Romascanu D. Romascanu
Avaya Avaya
S. Mansfield S. Mansfield
Ericsson Ericsson
June 24, 2010 September 27, 2010
"The OAM Acronym Soup" "Guidelines for the use of the OAM acronym in the IETF"
draft-ietf-opsawg-mpls-tp-oam-def-06.txt draft-ietf-opsawg-mpls-tp-oam-def-07.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. In particular, it will be applied in all MPLS that refer to OAM. There are other definitions and acronyms that
Transport Profile (MPLS-TP) documents. will be discussed while exploring the definition of the constituent
parts of the OAM term.
This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network.
This Informational Internet-Draft is aimed at achieving IETF
Consensus before publication as an RFC and will be subject to an IETF
Last Call.
[RFC Editor, please remove this note before publication as an RFC and
insert the correct Streams Boilerplate to indicate that the published
RFC has IETF Consensus.]
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on December 26, 2010. This Internet-Draft will expire on March 31, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. OAM and O, A and M . . . . . . . . . . . . . . . . . . . . . . 6 2. OAM and O, A and M . . . . . . . . . . . . . . . . . . . . . . 5
2.1. OAM as a Functional Unit . . . . . . . . . . . . . . . . . 6 2.1. OAM as a Functional Unit . . . . . . . . . . . . . . . . . 5
2.2. The Acronym Broken Up . . . . . . . . . . . . . . . . . . 6 2.2. The Acronym Broken Up . . . . . . . . . . . . . . . . . . 5
2.2.1. O in OAM . . . . . . . . . . . . . . . . . . . . . . . 6 2.2.1. O in OAM . . . . . . . . . . . . . . . . . . . . . . . 5
2.2.2. A in OAM . . . . . . . . . . . . . . . . . . . . . . . 6 2.2.2. A in OAM . . . . . . . . . . . . . . . . . . . . . . . 5
2.2.3. M in OAM . . . . . . . . . . . . . . . . . . . . . . . 7 2.2.3. M in OAM . . . . . . . . . . . . . . . . . . . . . . . 6
3. Use of the OAM Acronym in the MPLS-TP effort . . . . . . . . . 8 3. Recommendations on the use of the OAM Acronym . . . . . . . . 7
4. Acronyms for the MPLS-TP effort . . . . . . . . . . . . . . . 10 4. Recommended Acronyms . . . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
8. Informative references . . . . . . . . . . . . . . . . . . . . 14 8. Informative references . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
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
OAM acronym such that it is useful for MPLS. However, the OAM acronym such that it is useful for the IETF.
information in this document is not specific to MPLS, so broader
applicability of the OAM definitions provided is appropriate.
The acronym OAM is frequently used in the data and telecommunication The acronym OAM is frequently used in the data and telecommunication
industry. One would assume that something that is so widely used is industry. One would assume that something that is so widely used is
very clearly defined. However a closer look reveals some points that very clearly defined. However a closer look reveals some points that
need to be clarified. need to be clarified.
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 previous documents. The examples come acronym has been expanded in previous documents.
from many sources including some of the early MPLS-TP I-Ds.
o OAM = Operation, Administration, Maintenance o OAM = Operation, Administration, Maintenance
o OAM = Operations, Administration, Maintenance o OAM = Operations, Administration, Maintenance
o OAM = Operations, Administration, and Maintenance o OAM = Operations, Administration, and Maintenance
o OAM = Operations, Administration, Management o OAM = Operations, Administration, Management
o OAM = Operations and Maintenance o OAM = Operations and Maintenance
skipping to change at page 5, line 8 skipping to change at page 4, line 5
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; secondly 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 how each piece of the acronym
is defined and provides possible interpretations of the acronym. is defined and provides possible interpretations of the acronym.
Finally the interpretation of the OAM acronym to use for the MPLS-TP Finally a recommendation for the interpretation of the OAM acronym is
effort based on the agreement reached in the JWT (Joint Working Team) provided.
report [1] 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 [2]. and Maintenance (OAM) Mechanisms [I-D.ietf-opsawg-oam-overview].
This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network.
2. OAM and O, A and M 2. OAM and O, A and M
2.1. OAM as a Functional Unit 2.1. OAM as a Functional Unit
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
[4] is an example specification that uses this expansion of the OAM [ITU-T I.610] is an example specification that uses this expansion of
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 [3] and ITU-T Y.1731 [8]. 802.3-2008 [IEEE.802.3-2008] and ITU-T Y.1731 [ITU-T Y.1731].
The ITU-T M.3010 [7] Recommendation defines operations systems The ITU-T M.3010 [ITU-T M.3010] Recommendation defines operations
function as a function block that processes information related to systems function as a function block that processes information
the telecommunications management for the purpose of monitoring/ related to the telecommunications management for the purpose of
coordinating and/or controlling telecommunication functions including monitoring/coordinating and/or controlling telecommunication
management functions (i.e. the TMN (Telecommunications Management functions including management functions (i.e., the TMN
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 [9]. their networks more effectively MEF 17 [MEF 17].
2.2. The Acronym Broken Up 2.2. The Acronym Broken Up
2.2.1. O in OAM 2.2.1. O in OAM
The O in the OAM acronym invariably stands for "Operations". The O in the OAM acronym invariably stands for "Operations".
However there is some ambivalence in the definition and scope of the However there is some ambivalence in the definition and scope of the
term "Operation". term "Operation".
skipping to change at page 7, line 23 skipping to change at page 6, line 23
described in Section 3. described in Section 3.
Since these terms have different interpretations, it is not a good Since these terms have different interpretations, it is not a good
idea to use them interchangeably. This document defines the "M" in idea to use them interchangeably. This document defines the "M" in
the OAM acronym to mean Maintenance. the OAM acronym to mean Maintenance.
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 [5] defines maintenance as the whole of The Recommendation ITU-T M.20 [ITU-T M.20] defines maintenance as the
operations required for setting up and maintaining, within prescribed whole of operations required for setting up and maintaining, within
limits, any element involved in the setting up of a connection (see prescribed limits, any element involved in the setting up of a
the ITU-T M.60 [6] Recommendation). The purpose is to properly plan connection (see the ITU-T M.60 [ITU-T M.60] Recommendation). The
and program the maintenance operations required to establish and purpose is to properly plan and program the maintenance operations
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. The ITU-T documents also failure the correct actions are taken.
clearly define a maintenance philosophy.
3. Use of the OAM Acronym in the MPLS-TP effort 3. Recommendations on the use of the OAM Acronym
In Section 4 the acronyms as they will be used in the MPLS-TP effort In Section 4 the recommended acronyms are listed. This section gives
are listed. This section gives some background on the definitions some background on the definitions provided.
provided.
"Mgt" will be used if an abbreviation for "Management" is needed. "Mgmt" will be used if an abbreviation for "Management" is needed.
This draft does not define Management. It is noted, however, that an This draft does not define Management. It is noted, however, that an
important part of management functionality relates to tools to report important part of management functionality relates to tools to report
the state of the network. the state of the network.
In MPLS-TP documents, the OAM acronym is to be used for "Operations, The OAM acronym is to be used for "Operations, Administration, and
Administration, and Maintenance", i.e. excluding provisioning. Maintenance", excluding provisioning.
OAM tools and protocols, and the "Management space" are complementary OAM tools and protocols, and the "Management space" are complementary
in nature. Management focuses on FCAPS (Fault, Configuration, in nature. Management focuses on FCAPS (Fault, Configuration,
Accounting, Provisioning, and Security) functionality and on manager Accounting, Performance, and Security) functionality and on manager
(or NOC (Network Operations Center)) to device (or network) (or NOC (Network Operations Center)) to device (or network)
interaction. interaction.
From an architecture point of view OAM protocols and tools deployed From an architecture point of view OAM protocols and tools deployed
in the data plane tend to be "horizontal", i.e., network element to in the data plane tend to be "horizontal", i.e., network element to
network element. The management protocols tend to be "vertical", network element. The management protocols tend to be "vertical",
i.e., between management stations and network elements. i.e., between management stations and network elements.
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 while the management protocols tend to be "vertical".
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
resources in the network to support the offered services. This resources in the network to support the offered services. This
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.
4. Acronyms for the MPLS-TP effort 4. Recommended Acronyms
OAM - Operations, Administration, and Maintenance OAM - Operations, Administration, and Maintenance
O&M - OAM and Management O&M - OAM and Management
"Mgt" - Management "Mgmt" - Management
5. IANA Considerations 5. IANA Considerations
This memo includes no request to IANA. This memo includes no request to IANA.
6. Security Considerations 6. 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.
skipping to change at page 13, line 15 skipping to change at page 12, line 15
7. Acknowledgments 7. 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
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.
8. Informative references 8. Informative references
[1] Bryant, S. and L. Andersson, "Joint Working Team (JWT) Report on [I-D.ietf-opsawg-oam-overview]
MPLS Architectural Considerations for a Transport Profile", Mizrahi, T., "An Overview of Operations, Administration,
RFC 5317, February 2009. and Maintenance (OAM) Mechanisms",
draft-ietf-opsawg-oam-overview-01 (work in progress),
[2] Mizrahi, T., "An Overview of Operations, Administration, and July 2010.
Maintenance (OAM) Mechanisms", draft-ietf-opsawg-oam-overview-00
(work in progress), January 2010.
[3] IEEE, "Information technology - Telecommunications and [IEEE.802.3-2008]
information exchange between systems - Local and metropolitan IEEE, "Information technology - Telecommunications and
area networks - Specific requirements - Part 3: Carrier sense information exchange between systems - Local and
multiple access with collision detection (CSMA/CD) access method metropolitan area networks - Specific requirements - Part
and physical layer specifications"", IEEE Standard 802.3, 3: Carrier sense multiple access with collision detection
December 2008. (CSMA/CD) access method and physical layer
specifications"", IEEE Standard 802.3, December 2008.
[4] International Telecommunication Union, "B-ISDN operation and [ITU-T I.610]
maintenance principles and functions", ITU-T Recommendation International Telecommunication Union, "B-ISDN operation
I.610, February 1999. and maintenance principles and functions", ITU-
T Recommendation I.610, February 1999.
[5] International Telecommunication Union, "Maintenance philosophy [ITU-T M.20]
for telecommunication networks", ITU-T Recommendation M.20, International Telecommunication Union, "Maintenance
October 1992. philosophy for telecommunication networks", ITU-
T Recommendation M.20, October 1992.
[6] International Telecommunication Union, "Maintenance terminology [ITU-T M.3010]
and definitions", ITU-T Recommendation M.60, March 1993. International Telecommunication Union, "Principles for a
telecommunications management network", ITU-
T Recommendation M.3010, February 2000.
[7] International Telecommunication Union, "Principles for a [ITU-T M.60]
telecommunications management network", ITU-T Recommendation International Telecommunication Union, "Maintenance
M.3010, February 2000. terminology and definitions", ITU-T Recommendation M.60,
March 1993.
[8] International Telecommunication Union, "OAM functions and [ITU-T Y.1731]
mechanisms for Ethernet based networks", ITU-T Recommendation International Telecommunication Union, "OAM functions and
Y.1731, February 2008. mechanisms for Ethernet based networks", ITU-
T Recommendation Y.1731, February 2008.
[9] Metro Ethernet Forum, "Service OAM Requirements & Framework - [MEF 17] Metro Ethernet Forum, "Service OAM Requirements &
Phase 1", MEF Technical Specification MEF 17, April 2007. Framework - Phase 1", MEF Technical Specification MEF 17,
April 2007.
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
 End of changes. 34 change blocks. 
113 lines changed or deleted 92 lines changed or added

This html diff was produced by rfcdiff 1.39. The latest version is available from http://tools.ietf.org/tools/rfcdiff/