draft-ietf-opsawg-mpls-tp-oam-def-03.txt   draft-ietf-opsawg-mpls-tp-oam-def-04.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: August 16, 2010 Huawei Technologies Expires: November 1, 2010 Huawei Technologies
R. Bonica R. Bonica
Juniper Networks Juniper Networks
D. Romascanu D. Romascanu
Avaya Avaya
S. Mansfield S. Mansfield
Ericsson Ericsson
February 12, 2010 April 30, 2010
"The OAM Acronym Soup" "The use of the OAM Acronym in MPLS-TP"
draft-ietf-opsawg-mpls-tp-oam-def-03.txt draft-ietf-opsawg-mpls-tp-oam-def-04.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 it a bit more closely reveals a set of understood. Looking at the acronym a bit more closely reveals a set
recurring problems that are revisited time and again. This document of recurring problems that are revisited time and again. The goal of
has one primary and one secondary goal. The primary goal is to find this document is to find an understanding of the OAM acronym that is
an understanding of OAM that is useful for the MPLS Transport Profile useful for the MPLS Transport Profile (MPLS-TP) effort.
(MPLS-TP) effort. The secondary goal is to make this understanding
applicable in a wider scope.
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.
[RFC Editor, please remove this note before publication as an RFC and [RFC Editor, please remove this note before publication as an RFC and
insert the correct Streams Boilerplate to indicate that the published insert the correct Streams Boilerplate to indicate that the published
RFC has IETF Consensus.] RFC has IETF Consensus.]
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on November 1, 2010.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 16, 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 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 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. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 8. Informative references . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative references . . . . . . . . . . . . . . . . . . . 14
8.2. Informative references . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
The state of this work is very much "work in progress" and the The purpose of this document is to provide a definition of the OAM
discussion is ongoing. The reason to publish the draft at this stage acronym such that it is useful for MPLS-TP. The acronym OAM is
is that some of the relevant MPLS-TP drafts are getting close to frequently used in the data and telecommunication industry. One
working group last call and some of the definitions in this document would assume that something that is so widely used is very clearly
are needed for consistency within that group of drafts. defined. However a closer look reveals some points that need to be
clarified.
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.
The examples below come mainly from the first set of MPLS-TP IDs. In The examples below show a number of different ways that the OAM
the IDs there were a number of examples of how the OAM acronym could acronym could be expanded and understood. The examples come from
be used and there were a number of ways to expand and understand the many sources including some of the early MPLS-TP I-Ds.
acronym e.g.:
o OAM = Operation, Administration, Maintenance o OAM = Operation, Administration, Maintenance
o OAM = Operations, Administration, Maintenance o OAM = Operations, Administration, 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
The examples above were taken from drafts that later were corrected o O&M = OAM and Management
and aligned with what is proposed in this document.
Sometimes there is a fourth letter added to the acronym: Sometimes there is a fourth letter added to the acronym:
o OAM and P = Operations, Administration, Maintenance and o OAM and P = Operations, Administration, Maintenance and
Provisioning Provisioning
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; 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 the interpretation of the OAM acronym to use for the MPLS-TP
effort based on the agreement reached in the JWT report [1] is effort based on the agreement reached in the JWT (Joint Working Team)
provided. report [1] is provided.
The immediate target is to document the use of the OAM acronym such Another useful document to make the OAM term understandable in a
that it is useful for MPLS-TP. However, broader applicability of the wider scope is found in An Overview of Operations, Administration,
definitions in this document may also come to light. 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
[3] 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
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 [2] and ITU-T Y.1731 [7]. 802.3-2008 [3] and ITU-T Y.1731 [8].
The ITU-T M.3010 [6] 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 itself). management functions (i.e. the TMN (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 efficiently. their networks more efficiently.
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".
skipping to change at page 7, line 21 skipping to change at page 7, line 23
Since Maintenance and Management are defined as two different Since Maintenance and Management are defined as two different
activities it does not seem to be a good idea to use them activities it does not seem to be a good idea to use them
interchangeably. The concept behind OAM is management, so it makes interchangeably. The concept behind OAM is management, so it makes
more sense to use maintenance as the expansion of the "M" in the more sense to use maintenance as the expansion of the "M" in the
acronym. acronym.
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 [4] 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 [5] 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
maintain a network. 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. The ITU-T documents also
clearly defines a maintenance philosophy. clearly define a maintenance philosophy.
3. Use of the OAM acronym MPLS-TP effort 3. Use of the OAM Acronym in the MPLS-TP effort
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 drafts, 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 functionality and on manager in nature. Management focuses on FCAPS (Fault, Configuration,
(or NOC) to device (or network) interaction. Accounting, Provisioning, and Security) functionality and on manager
(or NOC (Network Operations Center)) to device (or network)
interaction.
From an architecture point of view OAM protocols and tools tend to be From an architecture point of view OAM protocols and tools deployed
"horizontal" i.e. network element to network element while the in the data plane tend to be "horizontal" i.e. network element to
management protocols tend to be "vertical". network element while the management protocols tend to be "vertical".
Where each part of the acronym and provisioning is 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 efficiently, e.g. adjusting device managed network run more efficiently, e.g. adjusting device
configuration and parameters. configuration and parameters.
o Even though "Provisioning" is not included in this document, the Even though "Provisioning" is not included in this document, the
following definition is provided for completeness. following definition is provided for completeness.
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.
o Sometimes it is necessary to talk about the combination of In general, Provisioning is used to configure the network for
functions and tools supplied by OAM and Management, it is providing new services, whereas OAM is used to keep the network in a
preferred that this is spelled out as "OAM and Management". In state that it can support already existing services.
cases where an acronym is needed O&M should be used.
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.
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 - Operations, Administration, Maintenance 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 Security is a significant requirement of MPLS-TP. However, this
informational document is intended only to provide guidance on the informational document is intended only to provide guidance on the
use of the OAM acronym, and the security concerns are, therefore, out use of the OAM acronym, and the security concerns are, therefore, out
of scope. of scope.
7. Acknowledgments 7. Acknowledgments
Malcolm Betts from M. C. Betts Consulting Ltd. significantly Malcolm Betts from M. C. Betts Consulting Ltd. significantly
contributed to this document. contributed to this document.
8. References 8. Informative references
8.1. Normative references
8.2. 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] IEEE, "Information technology - Telecommunications and [2] Mizrahi, T., "An Overview of Operations, Administration, and
Maintenance (OAM) Mechanisms", draft-ietf-opsawg-oam-overview-00
(work in progress), January 2010.
[3] IEEE, "Information technology - Telecommunications and
information exchange between systems - Local and metropolitan information exchange between systems - Local and metropolitan
area networks - Specific requirements - Part 3: Carrier sense area networks - Specific requirements - Part 3: Carrier sense
multiple access with collision detection (CSMA/CD) access method multiple access with collision detection (CSMA/CD) access method
and physical layer specifications"", IEEE Standard 802.3, and physical layer specifications"", IEEE Standard 802.3,
December 2008. December 2008.
[3] International Telecommunication Union, "B-ISDN operation and [4] International Telecommunication Union, "B-ISDN operation and
maintenance principles and functions", ITU-T Recommendation maintenance principles and functions", ITU-T Recommendation
I.610, February 1999. I.610, February 1999.
[4] International Telecommunication Union, "Maintenance philosophy [5] International Telecommunication Union, "Maintenance philosophy
for telecommunication networks", ITU-T Recommendation M.20, for telecommunication networks", ITU-T Recommendation M.20,
October 1992. October 1992.
[5] International Telecommunication Union, "Maintenance terminology [6] International Telecommunication Union, "Maintenance terminology
and definitions", ITU-T Recommendation M.60, March 1993. and definitions", ITU-T Recommendation M.60, March 1993.
[6] 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.
[7] 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.
Authors' Addresses Authors' Addresses
Loa Andersson Loa Andersson
Ericsson Ericsson
Email: loa.andersson@ericsson.com Email: loa.andersson@ericsson.com
 End of changes. 40 change blocks. 
83 lines changed or deleted 74 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/