wdiff draft-ietf-opsawg-mpls-tp-oam-def-00.txt draft-ietf-opsawg-mpls-tp-oam-def-01.txt

Network Working Group L. Andersson
Internet-Draft Ericsson
Intended status: Informational M. Betts
Expires: March 13, July 19, 2010 ZTE Corporation
H. van Helvoort
Huawei Tecnologies Technologies
R. Bonica
Juniper Networks
D. Romascanu
Avaya
September 9, 2009
January 15, 2010

"The OAM Acronym Soup"
draft-ietf-opsawg-mpls-tp-oam-def-00.txt
draft-ietf-opsawg-mpls-tp-oam-def-01.txt

Abstract

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
recurring problems that are revisited time and again. This document
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
(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
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network.

This Informational Internet-Draft is aimed at achieving IETF
Consensus before publication as an RFC and will be subject to an IETF
Last Call.

[RFC Editor, please remove this note before publication as an RFC and
insert the correct Streams Boilerplate to indicate that the published
RFC has IETF Consensus.]

Status of this Memo

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

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.

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."

The list of current Internet-Drafts can be accessed at
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 March 13, July 19, 2010.

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 (http://trustee.ietf.org/license-info). document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.

Abstract

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
recurring problems that are revisited time and again. This Code Components extracted from this document
has one primary and a secondary goal. The primary goal is to find an
understanding must
include Simplified BSD License text as described in Section 4.e of OAM that is feasible for
the MPLS Transport Profile
(MPLS-TP)effort. The secondary goal is to make this understanding
applicable Trust Legal Provisions and are provided without warranty as
described in a wider scope the BSD License.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 4
2. OAM and O, A and M . . . . . . . . . . . . . . . . . . . . . . 5 6
2.1. OAM as a functional unit . . . . . . . . . . . . . . . . . 5 6
2.2. The acronym broken up . . . . . . . . . . . . . . . . . . 5 6
2.2.1. O in OAM . . . . . . . . . . . . . . . . . . . . . . . 5 6
2.2.2. A in OAM . . . . . . . . . . . . . . . . . . . . . . . 5 6
2.2.3. M in OAM . . . . . . . . . . . . . . . . . . . . . . . 6 7
3. Use of the OAM acronym MPLS-TP effort . . . . . . . . . . . . 7 8
4. Acronyms for the MPLS-TP effort . . . . . . . . . . . . . . . 9 10
5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 10 11
6. Security considerations . . . . . . . . . . . . . . . . . . . 11 12
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 13
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 14
8.1. Normative References references . . . . . . . . . . . . . . . . . . . 13 14
8.2. Informative references . . . . . . . . . . . . . . . . . . 13 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 15

1. Introduction

The state of this work is very much "work in progress" and the
discussion is ongoing. The reason to publish the draft at this stage
is that some of the relevant MPLS-TP drafts are getting close to
working group last call and some of the directives definitions in this document
is
are needed for consistency within that group af draft. of drafts.

The acronym OAM is frequently used in the data- 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
needs
need to be clarified.

The examples used below comes 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
be used and there were a number of ways to expand and understand the
acronym e.g.:

o OAM = Operations, Administration, Maintenance

o OAM = Operations, Administration, Management

o OAM = Operations and Maintenance

o OAM = Operations and Management

o O&M = Operations and Maintenance

o O&M = Operations and Management

The examples above were taken from drafts that later has been were corrected
and aligned with what is proposed in this document.

Sometimes there is a fourth letter added to the acronym:

o OAM and P = Operations, Administration, Maintenance and
Provisioning

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

There is also the issue of how each piece of the acronym is defined.

In this
This document we will analyse provides an analysis of how each piece of the acronym
is defined and provide provides possible interpretations of the acronym.
Finally
we will suggest the use interpretation of the OAM acronym to use for the MPLS-TP
effort based on the greement agreement reached based on in the JWT report
[I-D.bryant-mpls-tp-jwt-report].

Our [1] is
provided.

The immediate target is to document the use of the OAM acronym such
that it is useful for MPLS-TP. However, we hope to shed some light
on the issue in a broader scope.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" applicability of the
definitions in this document are may also come to be interpreted as described in RFC 2119 [RFC2119]. light.

2. OAM and O, A and M

2.1. OAM as a functional unit

Operations, Administration, and Maintenance (OAM): A group of network
management functions that provide network fault indication,
performance information, and data and diagnosis functions. Examples
are ATM OAM [ITU-T I-610] ITU-T I.610 [3] and IEEE Std. 802.3 Clause 57 OAM

Alternatively (Huub :) ) of IEEE 802.3-2008 [2].

Operations, Administration, and Maintenance (OAM): A group of network
management functions that provide network fault indication, fault
localisation
localization, performance information, and data and diagnosis
functions.

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

The Metro Ethernet Forum refers to OAM as to: OAM refers to the tools and utilities to
install, monitor and troubleshoot a network, helping carriers run
their networks more efficiently.

Note: the paragraphs above are so far just placeholders.

2.2. The acronym broken up

2.2.1. O in OAM

The O in the OAM acronym invariably stands for "Operations".

However there is some ambivalences ambivalence in the definition and scope of
"Operation" the
term "Operation".

Note: Examples to be provided.

2.2.2. A in OAM

The A in the OAM acronym mostly stands for "Adminstration", "Administration", though
in a few cases it seems like "Accounting" have crept in. is also used. For the
purpose of this document we will assume it is assumed that "Adminstration" "Administration" is the
correct expansion of "A".

Note: Examples to be provided.

Admistration

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

In the list above the M in the OAM acronym stands for "Maintenance"
or "Management".

Since Maintenance and Management are defined as two different
actvities
activities it does not seem to be a good idea to use them
interchangeably.

Note: Examples to be provided.

The recommendation M.20 from ITU-T M.20 [4] defines mainteance:

Maintenance involves maintenance as the whole of
operations required for setting up and maintaining, within prescribed
limits, any element entering into involved in the setting-up setting up of a connection (see Recommendation M.60). In order
the ITU-T M.60 [5] recommendation). The purpose is to properly plan
and program the maintenance operations required to establish and
maintain a network.

It should have as a

A major aim of the concept of maintenance is to minimize both the
occurrence and the impact of failures and to ensure that in cause case of a
failure the correct actions are taken. The ITU-T document also
clearly defines a
maintenace philosphy. maintenance philosophy.

3. Use of the OAM acronym MPLS-TP effort

In Section 4 we list the acronyms as they will be used in the MPLS-TP
effort, this effort
are listed. This section gives somwe background.

If we need as some background on the definitions
provided.

"Mgt" will be used if an abbreviation for "Management" we will use "Mgt". We
do is needed.
This draft does not define Management in this draft, but note Management. It is noted, however, that an
important part of the Management funtionality management functionality relates to tools to report
the state of the network.

We propose that

In MPLS-TP drafts, the OAM acronym is reserved to be used for "Operations,
Administration and Maintenance", i.e. excluding provisioning.

OAM tools and protocols and the "Management space" are complementary
in natur. nature. Management focuses on FCAPS functionality and on manager
(or NOC) to device (or network) interaction.

From an architecture point of view OAM protocols and tools tend to be
"horizontal" i.e. network element to network element while the
management protocols tend to be "vertical" "vertical".

Where each part of the acronym and provisioning is defined as
follows:

o Operations - Operation activities is are undertaken to keep the
network (and the services that the network provides) up and
running. It includes monitoring the network and find finding problems.
Ideally these problems should be found before users are affected."

o Administration - Administration activities involves involve keeping track
of resources in the network and how they are used. It includes
all the book keeping bookkeeping that is necessary to keep track of networking
resources and the network under control.

o 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 efficient, efficiently, e.g. adjusting device
configuration and parameters.

o Even though we don't include "Provisioning" is not included in this document, the OAM acronym we
note that:
following definition is provided for completeness.

Provisioning - Provisioning activities involves 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.

o We also note that sometimes Sometimes it is necessary to talk about the combination of
functions and tools suplied supplied by OAM and Management,
we prefer 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

OAM - Operations, Administration and Maintenance

O&M - Operations, Administration, Maintenance and Management

"Mgt" - Management

5. IANA considerations

There are no requests for IANA allocation of code points in this
document.

6. Security considerations

This

Security is a significant requirement of MPLS-TP. However, this
informational document is intended only changes to provide guidance on the name
use of one field in the MPLS Shim
Header OAM acronym, and thus does not introduce any new the security considerations. concerns are, therefore, out
of scope.

7. Acknowledgments

8. References

8.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. references

8.2. Informative references

[I-D.bryant-mpls-tp-jwt-report]

[1] Bryant, S. and L. Andersson, "JWT "Joint Working Team (JWT) Report on
MPLS Architectural Considerations for a Transport Profile",
draft-bryant-mpls-tp-jwt-report-00 (work in progress),
July
RFC 5317, February 2009.

[2] IEEE, "Information technology - Telecommunications and
information exchange between systems - Local and metropolitan
area networks - Specific requirements - Part 3: Carrier sense
multiple access with collision detection (CSMA/CD) access method
and physical layer specifications"", IEEE Standard 802.3,
December 2008.

[3] International Telecommunication Union, "B-ISDN operation and
maintenance principles and functions", ITU-T Recommendation
I.610, February 1999.

[4] International Telecommunication Union, "Maintenance philosophy
for telecommunication networks", ITU-T Recommendation M.20,
October 1992.

[5] International Telecommunication Union, "Maintenance terminology
and definitions", ITU-T Recommendation M.60, March 1993.

[6] International Telecommunication Union, "Principles for a
telecommunications management network", ITU-T Recommendation
M.3010, February 2000.

Authors' Addresses

Loa Andersson
Ericsson

Email: loa.andersson@ericsson.com

Malcolm Betts
Huawei Tecnologies
ZTE Corporation

Email: malcolm.betts@huawei.com malcolm.betts@zte.com.cn

Huub van Helvoort
Huawei Tecnologies Technologies

Email: hhelvoort@huawei.com

Ron Bonica
Juniper Networks

Email: rbonica@juniper.net

Dan Romascanu
Avaya

Email: dromasca@avaya.com