draft-ietf-opsawg-mpls-tp-oam-def-02.txt   draft-ietf-opsawg-mpls-tp-oam-def-03.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: July 23, 2010 Huawei Technologies Expires: August 16, 2010 Huawei Technologies
R. Bonica R. Bonica
Juniper Networks Juniper Networks
D. Romascanu D. Romascanu
Avaya Avaya
January 19, 2010 S. Mansfield
Ericsson
February 12, 2010
"The OAM Acronym Soup" "The OAM Acronym Soup"
draft-ietf-opsawg-mpls-tp-oam-def-02.txt draft-ietf-opsawg-mpls-tp-oam-def-03.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 it a bit more closely reveals a set of
recurring problems that are revisited time and again. This document recurring problems that are revisited time and again. This document
has one primary and one secondary goal. The primary goal is to find has one primary and one secondary goal. The primary goal is to find
an understanding of OAM that is useful for the MPLS Transport Profile an understanding of OAM that is useful for the MPLS Transport Profile
(MPLS-TP) effort. The secondary goal is to make this understanding (MPLS-TP) effort. The secondary goal is to make this understanding
applicable in a wider scope. applicable in a wider scope.
skipping to change at page 2, line 16 skipping to change at page 2, line 17
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 23, 2010. 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
skipping to change at page 4, line 23 skipping to change at page 4, line 23
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 come mainly from the first set of MPLS-TP IDs. In The examples below come mainly from the first set of MPLS-TP IDs. In
the IDs there were a number of examples of how the OAM acronym could the IDs there were a number of examples of how the OAM acronym could
be used and there were a number of ways to expand and understand the be used and there were a number of ways to expand and understand the
acronym e.g.: acronym e.g.:
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
skipping to change at page 6, line 9 skipping to change at page 6, line 9
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, Administration, and Maintenance (OAM): A group of network Operations and Maintenance (OAM): A group of network management
management functions that provide network fault indication, functions that provide network fault indication, performance
performance information, and data and diagnosis functions. Examples information, and data and diagnosis functions. ATM OAM ITU-T I.610
are ATM OAM ITU-T I.610 [3] and Clause 57 of IEEE 802.3-2008 [2]. [3] is an example specification that uses this expansion of 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. functions. Examples where this acronym is used are Clause 57 of IEEE
802.3-2008 [2] and ITU-T Y.1731 [7].
The ITU-T M.3010 [6] recommendation defines operations systems The ITU-T M.3010 [6] 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 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.
Note: the paragraphs above are so far just placeholders.
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".
Note: Examples to be provided. 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.
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 mostly stands for "Administration", though
in a few cases it seems like "Accounting" is also used. For the in a few cases it seems like "Accounting" is also used. For the
purpose of this document it is assumed that "Administration" is the purpose of this document it is assumed that "Administration" is the
correct expansion of "A". correct expansion of "A".
Note: Examples to be provided. Examples of "administration" tools are network discovery and planning
tools.
Administration is used to support maintenance functions, e.g. by
collecting failure and performance information, continuous or on-
demand.
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 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. interchangeably. The concept behind OAM is management, so it makes
more sense to use maintenance as the expansion of the "M" in the
acronym.
Note: Examples to be provided. 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.
The recommendation ITU-T M.20 [4] defines maintenance as the whole of The recommendation ITU-T M.20 [4] 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 [5] 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 document also failure the correct actions are taken. The ITU-T documents also
clearly defines a maintenance philosophy. clearly defines a maintenance philosophy.
3. Use of the OAM acronym MPLS-TP effort 3. Use of the OAM acronym 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
skipping to change at page 11, line 7 skipping to change at page 11, line 7
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 - Operations, Administration, Maintenance and Management
"Mgt" - Management "Mgt" - Management
5. IANA considerations 5. IANA considerations
There are no requests for IANA allocation of code points in this This memo includes no request to IANA.
document.
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
skipping to change at page 15, line 5 skipping to change at page 14, line 37
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 [5] 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 [6] 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
mechanisms for Ethernet based networks", ITU-T Recommendation
Y.1731, February 2008.
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
skipping to change at line 368 skipping to change at page 15, line 26
Ron Bonica Ron Bonica
Juniper Networks Juniper Networks
Email: rbonica@juniper.net Email: rbonica@juniper.net
Dan Romascanu Dan Romascanu
Avaya Avaya
Email: dromasca@avaya.com Email: dromasca@avaya.com
Scott Mansfield
Ericsson
Email: scott.mansfield@ericsson.com
 End of changes. 16 change blocks. 
22 lines changed or deleted 33 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/