draft-ietf-opsawg-mpls-tp-oam-def-05.txt   draft-ietf-opsawg-mpls-tp-oam-def-06.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: Informational H. van Helvoort
Expires: November 7, 2010 Huawei Technologies Expires: December 26, 2010 Huawei Technologies
R. Bonica R. Bonica
Juniper Networks Juniper Networks
D. Romascanu D. Romascanu
Avaya Avaya
S. Mansfield S. Mansfield
Ericsson Ericsson
May 6, 2010 June 24, 2010
"The OAM Acronym Soup" "The OAM Acronym Soup"
draft-ietf-opsawg-mpls-tp-oam-def-05.txt draft-ietf-opsawg-mpls-tp-oam-def-06.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.
The immediate goal of this document is to find an understanding of This document provides a definition of the acronym OAM (Operations,
the OAM acronym that is useful for MPLS. This document is Administration, and Maintenance) for use in all future IETF documents
specifically applicable to the new OAM functionality developed for that refer to OAM. In particular, it will be applied in all MPLS
the MPLS Transport Profile (MPLS-TP) project. However, broader Transport Profile (MPLS-TP) documents.
applicability of the definitions in this document may also come to
light, e.g. the intention is to use these definitions for all future
IETF documents.
This document is a product of a joint Internet Engineering Task Force This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication (IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network. capabilities and functionalities of a packet transport network.
This Informational Internet-Draft is aimed at achieving IETF This Informational Internet-Draft is aimed at achieving IETF
Consensus before publication as an RFC and will be subject to an IETF Consensus before publication as an RFC and will be subject to an IETF
Last Call. Last Call.
skipping to change at page 2, line 15 skipping to change at page 2, line 12
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 November 7, 2010. This Internet-Draft will expire on December 26, 2010.
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. OAM and O, A and M . . . . . . . . . . . . . . . . . . . . . . 6 2. OAM and O, A and M . . . . . . . . . . . . . . . . . . . . . . 6
2.1. OAM as a functional unit . . . . . . . . . . . . . . . . . 6 2.1. OAM as a Functional Unit . . . . . . . . . . . . . . . . . 6
2.2. The acronym broken up . . . . . . . . . . . . . . . . . . 6 2.2. The Acronym Broken Up . . . . . . . . . . . . . . . . . . 6
2.2.1. O in OAM . . . . . . . . . . . . . . . . . . . . . . . 6 2.2.1. O in OAM . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.2. A in OAM . . . . . . . . . . . . . . . . . . . . . . . 6 2.2.2. A in OAM . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.3. M in OAM . . . . . . . . . . . . . . . . . . . . . . . 7 2.2.3. M in OAM . . . . . . . . . . . . . . . . . . . . . . . 7
3. Use of the OAM Acronym in the MPLS-TP effort . . . . . . . . . 8 3. Use of the OAM Acronym in the MPLS-TP effort . . . . . . . . . 8
4. Acronyms for the MPLS-TP effort . . . . . . . . . . . . . . . 10 4. Acronyms for the MPLS-TP effort . . . . . . . . . . . . . . . 10
5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 11 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6. Security considerations . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
8. Informative references . . . . . . . . . . . . . . . . . . . . 14 8. Informative references . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
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 MPLS. However, the
information in this document is not specific to MPLS, so broader information in this document is not specific to MPLS, so broader
applicability of the OAM definitions provided is appropriate. It is applicability of the OAM definitions provided is appropriate.
understood that all future IETF documents will use these definitions
when 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 could be expanded and understood. The examples come from acronym has been expanded in previous documents. The examples come
many sources including some of the early MPLS-TP I-Ds. 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, Management o OAM = Operations, Administration, Management
o OAM = Operations and Maintenance o OAM = Operations and Maintenance
o OAM = Operations and Management o OAM = Operations and Management
o O&M = Operations and Maintenance o O&M = Operations and Maintenance
o O&M = Operations and Management o O&M = Operations and Management
skipping to change at page 6, line 7 skipping to change at page 6, line 7
and Maintenance (OAM) Mechanisms [2]. and Maintenance (OAM) Mechanisms [2].
This document is a product of a joint Internet Engineering Task Force This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication (IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network. 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 [4] is an example specification that uses this expansion of the OAM
acronym. 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
skipping to change at page 6, line 30 skipping to change at page 6, line 30
The ITU-T M.3010 [7] Recommendation defines operations systems The ITU-T M.3010 [7] Recommendation defines operations systems
function as a function block that processes information related to function as a function block that processes information related to
the telecommunications management for the purpose of monitoring/ the telecommunications management for the purpose of monitoring/
coordinating and/or controlling telecommunication functions including coordinating and/or controlling telecommunication functions including
management functions (i.e. the TMN (Telecommunications Management management functions (i.e. the TMN (Telecommunications Management
Network) itself). 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 efficiently. their networks more effectively MEF 17 [9].
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".
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.2.2. A in OAM 2.2.2. A in OAM
The A in the OAM acronym mostly stands for "Administration", though The A in the OAM acronym stands for "Administration".
in a few cases it seems like "Accounting" is also used. For the
purpose of this document it is assumed that "Administration" is the
correct expansion of "A".
Examples of "administration" tools are network discovery and planning Examples of "administration" tools are network discovery and planning
tools. tools.
2.2.3. M in OAM 2.2.3. M in OAM
In the list above the M in the OAM acronym stands for "Maintenance" In the list above the M in the OAM acronym stands for "Maintenance"
or "Management". or "Management".
Since Maintenance and Management are defined as two different Maintenance and Management may have different interpretations.
activities it does not seem to be a good idea to use them Maintenance is defined further in Section 3, while Management is a
interchangeably. The concept behind OAM is management, so it makes broader term applicable to many functions applied to the network as
more sense to use maintenance as the expansion of the "M" in the described in Section 3.
acronym.
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.
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 [5] defines maintenance as the whole of
operations required for setting up and maintaining, within prescribed operations required for setting up and maintaining, within prescribed
limits, any element involved in the setting up of a connection (see limits, any element involved in the setting up of a connection (see
the ITU-T M.60 [6] Recommendation). The purpose is to properly plan the ITU-T M.60 [6] Recommendation). The purpose is to properly plan
and program the maintenance operations required to establish and and program the maintenance operations required to establish and
skipping to change at page 8, line 17 skipping to change at page 8, line 17
In Section 4 the acronyms as they will be used in the MPLS-TP effort In Section 4 the acronyms as they will be used in the MPLS-TP effort
are listed. This section gives some background on the definitions are listed. This section gives some background on the definitions
provided. provided.
"Mgt" will be used if an abbreviation for "Management" is needed. "Mgt" 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, In MPLS-TP documents, the OAM acronym is to be used for "Operations,
Administration and Maintenance", i.e. excluding provisioning. Administration, and Maintenance", i.e. 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, Provisioning, 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
network element. The management protocols tend to be "vertical",
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 in the data plane tend to be "horizontal" i.e. network element to
network element while the management protocols tend to be "vertical". 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.
skipping to change at page 8, line 47 skipping to change at page 8, line 52
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 efficiently, e.g. adjusting device managed network run more effectively, e.g. adjusting device
configuration and parameters. configuration and parameters.
Even though "Provisioning" is not included in this document, 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 for In general, Provisioning is used to configure the network to provide
providing new services, whereas OAM is used to keep the network in a new services, whereas OAM is used to keep the network in a state that
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. Acronyms for the MPLS-TP effort
OAM - Operations, Administration and Maintenance OAM - Operations, Administration, and Maintenance
O&M - OAM and Management O&M - OAM and Management
"Mgt" - Management "Mgt" - 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
Security is a significant requirement of MPLS-TP. However, this This document provides guidance for the use of the OAM acronym in
informational document is intended only to provide guidance on the other documents. This document does not have direct security
use of the OAM acronym, and the security concerns are, therefore, out implications.
of scope.
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.
7. Acknowledgments 7. Acknowledgments
Malcolm Betts from M. C. Betts Consulting Ltd. significantly The following individuals significantly contributed to this document.
contributed to this document.
o Malcolm Betts from M. C. Betts Consulting Ltd.
o Kam Lam from Alcatel Lucent
o Dieter Beller from Alcatel Lucent
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 [1] Bryant, S. and L. Andersson, "Joint Working Team (JWT) Report on
MPLS Architectural Considerations for a Transport Profile", MPLS Architectural Considerations for a Transport Profile",
RFC 5317, February 2009. RFC 5317, February 2009.
[2] Mizrahi, T., "An Overview of Operations, Administration, and [2] Mizrahi, T., "An Overview of Operations, Administration, and
Maintenance (OAM) Mechanisms", draft-ietf-opsawg-oam-overview-00 Maintenance (OAM) Mechanisms", draft-ietf-opsawg-oam-overview-00
(work in progress), January 2010. (work in progress), January 2010.
skipping to change at page 15, line 5 skipping to change at page 14, line 41
and definitions", ITU-T Recommendation M.60, March 1993. and definitions", ITU-T Recommendation M.60, March 1993.
[7] International Telecommunication Union, "Principles for a [7] International Telecommunication Union, "Principles for a
telecommunications management network", ITU-T Recommendation telecommunications management network", ITU-T Recommendation
M.3010, February 2000. M.3010, February 2000.
[8] International Telecommunication Union, "OAM functions and [8] International Telecommunication Union, "OAM functions and
mechanisms for Ethernet based networks", ITU-T Recommendation mechanisms for Ethernet based networks", ITU-T Recommendation
Y.1731, February 2008. Y.1731, February 2008.
[9] Metro Ethernet Forum, "Service OAM Requirements & 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. 27 change blocks. 
48 lines changed or deleted 64 lines changed or added

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