"Guidelines for the use of the OAM acronym in the IETF"
draft-ietf-opsawg-mpls-tp-oam-def-10.txt

Abstract

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 of recurring problems that are revisited time and again.

This document provides a definition of the acronym OAM (Operations, Administration, and Maintenance) for use in all future IETF documents that refer to OAM. There are other definitions and acronyms that will be discussed while exploring the definition of the constituent parts of the OAM term.

Status of this Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on November 13, 2011.

Copyright Notice

Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 1.1. Terminology
• 2. Pre-existing uses of OAM
• 2.1. Uses of OAM in other SDOs
• 2.1.1. O in OAM
• 2.1.2. A in OAM
• 2.1.3. M in OAM
• 2.2. Uses of OAM in the IETF
• 3. Recommendations on the use of the OAM Acronym
• 4. IANA Considerations
• 5. Security Considerations
• 6. Acknowledgments
• 7. References
• Authors' Addresses

1. Introduction

The main purpose of this document is to provide a definition of the acronym OAM (Operations, Administration, and Maintenance) for use in all future IETF documents that refer to OAM.

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.

If such an important piece of our technology is so poorly defined, or if there are dialects of the technology with different understandings of such a key concept, this will eventually cause problems.

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 acronym represents an integrated piece of functionality; secondly the acronym as such represents something that is more than just the sum of its parts.

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 is defined and provides possible interpretations of the acronym. Finally a recommendation for the interpretation of the OAM acronym is provided.

Another useful document to make the OAM term understandable in a wider scope is found in An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms [I-D.ietf-opsawg-oam-overview].

1.1. Terminology

• "Mgmt" - Management
• O&M - OAM and Management
• OAM - Operations, Administration, and Maintenance
• SDO - Standards Development Organization

2. Pre-existing uses of OAM

This section provides information on how OAM is used in other SDOs (Standards Development Organization) and provides the background necessary to understand the how the term is used in the IETF.

2.1. Uses of OAM in other SDOs

Operations And Maintenance (OAM): A group of network management functions that provide network fault indication, performance 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 the OAM acronym.

Operations, Administration, and Maintenance (OAM): A group of network management functions that provide network fault indication, fault localization, performance information, and data and diagnosis 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].

The ITU-T M.3010 [ITU-T-M.3010] Recommendation defines operations systems function as a function block that processes information related to the telecommunications management for the purpose of monitoring/coordinating and/or controlling telecommunication functions including management functions (i.e., the TMN (Telecommunications Management Network) itself).

The Metro Ethernet Forum refers to OAM as the tools and utilities to install, monitor and troubleshoot a network, helping carriers run their networks more effectively MEF 17 [MEF-17].

2.1.1. O in OAM

The O in the OAM acronym invariably stands for "Operations". However there is some ambivalence in the definition and scope of the term "Operation".

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.1.2. A in OAM

The A in the OAM acronym stands for "Administration".

Examples of "administration" tools are network discovery and planning tools.

2.1.3. M in OAM

The M in the OAM acronym stands for "Maintenance" or "Management".

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 [ITU-T-M.20] defines maintenance as the whole of operations required for setting up and maintaining, within prescribed limits, any element involved in the setting up of a connection (see the ITU-T M.60 [ITU-T-M.60] Recommendation). The purpose is to properly plan and program the maintenance operations required to establish and maintain a network.

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 failure the correct actions are taken.

2.2. Uses of OAM in the IETF

The examples below show a number of different ways that the OAM acronym has been expanded in IETF RFCs. The reference list is not exhaustive.

• OAM = Operations, Administration, and Maintenance in RFC 5586 [RFC5586]
• OAM = Operations and Maintenance in RFC 3429 [RFC3429]
• OAM = Operations and Management in RFC 4377 [RFC4377]
• O&M = OAM and Maintenance in RFC 1812 [RFC1812]

Sometimes there is a fourth letter added to the acronym:

• OAM&P = Operations, Administration, Maintenance and Provisioning in RFC 4594 [RFC4594]

3. Recommendations on the use of the OAM Acronym

The IETF recommended expansion of the OAM acronym is given below. In addition to the OAM acronym, two other recommendations are made in this section.

• OAM - Operations, Administration, and Maintenance
• O&M - OAM and Management
• "Mgmt" - Management

The components of the OAM acronym (and provisioning) are defined as follows:

• Operations - Operation activities are undertaken to keep the network (and the services that the network provides) up and running. It includes monitoring the network and finding problems. Ideally these problems should be found before users are affected.
• Administration - Administration activities involve keeping track of resources in the network and how they are used. It includes all the bookkeeping that is necessary to track networking resources and the network under control.
• Maintenance - Maintenance activities are focused on facilitating repairs and upgrades - for example, when equipment must be replaced, when a router needs a patch for an operating system image, or when a new switch is added to a network. Maintenance also involves corrective and preventive measures to make the managed network run more effectively, e.g., adjusting device configuration and parameters.

"Provisioning" is outside the scope of this document, but the following definition is provided for completeness.

• Provisioning - Provisioning activities involve configuring resources in the network to support the offered services. This might include setting up the network so that a new customer can receive an Internet access service.

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 it can support already existing services.

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.

"Mgmt" will be used if an abbreviation for "Management" is needed. This document does not define Management.

4. IANA Considerations

This memo includes no request to IANA.

5. Security Considerations

This document provides guidance for the use of the OAM acronym in other documents. This document does not have direct security implications.

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.

6. Acknowledgments

The following individuals significantly contributed to this document.

• Malcolm Betts from M. C. Betts Consulting Ltd.
• Kam Lam from Alcatel Lucent
• Dieter Beller from Alcatel Lucent
• David Harrington from Huawei Technologies

Thanks to the experts of ITU-T SG 15 for their review and comments.

7. References

Authors' Addresses