draft-ietf-opsawg-mpls-tp-oam-def-07.txt   draft-ietf-opsawg-mpls-tp-oam-def-08.txt 
Network Working Group L. Andersson Network Working Group L. Andersson
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: BCP H. van Helvoort Intended status: BCP H. van Helvoort
Expires: March 31, 2011 Huawei Technologies Expires: September 30, 2011 Huawei Technologies
R. Bonica R. Bonica
Juniper Networks Juniper Networks
D. Romascanu D. Romascanu
Avaya Avaya
S. Mansfield S. Mansfield
Ericsson Ericsson
September 27, 2010 March 29, 2011
"Guidelines for the use of the OAM acronym in the IETF" "Guidelines for the use of the OAM acronym in the IETF"
draft-ietf-opsawg-mpls-tp-oam-def-07.txt draft-ietf-opsawg-mpls-tp-oam-def-08.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. There are other definitions and acronyms that that refer to OAM. There are other definitions and acronyms that
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 March 31, 2011. This Internet-Draft will expire on September 30, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 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
skipping to change at page 5, line 12 skipping to change at page 5, line 12
wider scope is found in An Overview of Operations, Administration, wider scope is found in An Overview of Operations, Administration,
and Maintenance (OAM) Mechanisms [I-D.ietf-opsawg-oam-overview]. and Maintenance (OAM) Mechanisms [I-D.ietf-opsawg-oam-overview].
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
[ITU-T I.610] is an example specification that uses this expansion of [ITU-T-I.610] is an example specification that uses this expansion of
the OAM 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 [IEEE.802.3-2008] and ITU-T Y.1731 [ITU-T Y.1731]. 802.3-2008 [IEEE.802.3-2008] and ITU-T Y.1731 [ITU-T-Y.1731].
The ITU-T M.3010 [ITU-T M.3010] Recommendation defines operations The ITU-T M.3010 [ITU-T-M.3010] Recommendation defines operations
systems function as a function block that processes information systems function as a function block that processes information
related to the telecommunications management for the purpose of related to the telecommunications management for the purpose of
monitoring/coordinating and/or controlling telecommunication monitoring/coordinating and/or controlling telecommunication
functions including management functions (i.e., the TMN functions including management functions (i.e., the TMN
(Telecommunications Management 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 [MEF 17]. 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 6, 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 [ITU-T M.20] defines maintenance as the The Recommendation ITU-T M.20 [ITU-T-M.20] defines maintenance as the
whole of operations required for setting up and maintaining, within whole of operations required for setting up and maintaining, within
prescribed limits, any element involved in the setting up of a prescribed limits, any element involved in the setting up of a
connection (see the ITU-T M.60 [ITU-T M.60] Recommendation). The connection (see the ITU-T M.60 [ITU-T-M.60] Recommendation). The
purpose is to properly plan and program the maintenance operations purpose is to properly plan and program the maintenance operations
required to establish and 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. failure the correct actions are taken.
3. Recommendations on the use of the OAM Acronym 3. Recommendations on the use of the OAM Acronym
In Section 4 the recommended acronyms are listed. This section gives In Section 4 the recommended acronyms are listed. This section gives
skipping to change at page 13, line 8 skipping to change at page 13, line 8
o Dieter Beller from Alcatel Lucent o Dieter Beller from Alcatel Lucent
o David Harrington from Huawei Technologies 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
[I-D.ietf-opsawg-oam-overview] [I-D.ietf-opsawg-oam-overview]
Mizrahi, T., "An Overview of Operations, Administration, Mizrahi, T., Sprecher, N., Bellagamba, E., and Y.
Weingarten, "An Overview of Operations, Administration,
and Maintenance (OAM) Mechanisms", and Maintenance (OAM) Mechanisms",
draft-ietf-opsawg-oam-overview-01 (work in progress), draft-ietf-opsawg-oam-overview-03 (work in progress),
July 2010. January 2011.
[IEEE.802.3-2008] [IEEE.802.3-2008]
IEEE, "Information technology - Telecommunications and IEEE, "Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific requirements - Part metropolitan area networks - Specific requirements - Part
3: Carrier sense multiple access with collision detection 3: Carrier sense multiple access with collision detection
(CSMA/CD) access method and physical layer (CSMA/CD) access method and physical layer
specifications"", IEEE Standard 802.3, December 2008. specifications"", IEEE Standard 802.3, December 2008.
[ITU-T I.610] [ITU-T-I.610]
International Telecommunication Union, "B-ISDN operation International Telecommunication Union, "B-ISDN operation
and maintenance principles and functions", ITU- and maintenance principles and functions", ITU-
T Recommendation I.610, February 1999. T Recommendation I.610, February 1999.
[ITU-T M.20] [ITU-T-M.20]
International Telecommunication Union, "Maintenance International Telecommunication Union, "Maintenance
philosophy for telecommunication networks", ITU- philosophy for telecommunication networks", ITU-
T Recommendation M.20, October 1992. T Recommendation M.20, October 1992.
[ITU-T M.3010] [ITU-T-M.3010]
International Telecommunication Union, "Principles for a International Telecommunication Union, "Principles for a
telecommunications management network", ITU- telecommunications management network", ITU-
T Recommendation M.3010, February 2000. T Recommendation M.3010, February 2000.
[ITU-T M.60] [ITU-T-M.60]
International Telecommunication Union, "Maintenance International Telecommunication Union, "Maintenance
terminology and definitions", ITU-T Recommendation M.60, terminology and definitions", ITU-T Recommendation M.60,
March 1993. March 1993.
[ITU-T Y.1731] [ITU-T-Y.1731]
International Telecommunication Union, "OAM functions and International Telecommunication Union, "OAM functions and
mechanisms for Ethernet based networks", ITU- mechanisms for Ethernet based networks", ITU-
T Recommendation Y.1731, February 2008. T Recommendation Y.1731, February 2008.
[MEF 17] Metro Ethernet Forum, "Service OAM Requirements & [MEF-17] Metro Ethernet Forum, "Service OAM Requirements &
Framework - Phase 1", MEF Technical Specification MEF 17, Framework - Phase 1", MEF Technical Specification MEF 17,
April 2007. April 2007.
Authors' Addresses Authors' Addresses
Loa Andersson Loa Andersson
Ericsson Ericsson
Email: loa.andersson@ericsson.com Email: loa.andersson@ericsson.com
 End of changes. 19 change blocks. 
20 lines changed or deleted 21 lines changed or added

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