draft-ietf-opsawg-mpls-tp-oam-def-04.txt   draft-ietf-opsawg-mpls-tp-oam-def-05.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: November 1, 2010 Huawei Technologies Expires: November 7, 2010 Huawei Technologies
R. Bonica R. Bonica
Juniper Networks Juniper Networks
D. Romascanu D. Romascanu
Avaya Avaya
S. Mansfield S. Mansfield
Ericsson Ericsson
April 30, 2010 May 6, 2010
"The use of the OAM Acronym in MPLS-TP" "The OAM Acronym Soup"
draft-ietf-opsawg-mpls-tp-oam-def-04.txt draft-ietf-opsawg-mpls-tp-oam-def-05.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. The goal of of recurring problems that are revisited time and again.
this document is to find an understanding of the OAM acronym that is
useful for the MPLS Transport Profile (MPLS-TP) effort. The immediate goal of this document is to find an understanding of
the OAM acronym that is useful for MPLS. This document is
specifically applicable to the new OAM functionality developed for
the MPLS Transport Profile (MPLS-TP) project. However, broader
applicability of the definitions in this document may also come to
light, e.g. the intention is to use these definitions for all future
IETF documents.
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.
skipping to change at page 2, line 10 skipping to change at page 2, line 15
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 November 1, 2010. This Internet-Draft will expire on November 7, 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 7 skipping to change at page 4, line 7
3. Use of the OAM Acronym in the 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. Informative references . . . . . . . . . . . . . . . . . . . . 14 8. Informative references . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
The purpose of this document is to provide a definition of the OAM The main purpose of this document is to provide a definition of the
acronym such that it is useful for MPLS-TP. The acronym OAM is OAM acronym such that it is useful for MPLS. However, the
frequently used in the data and telecommunication industry. One information in this document is not specific to MPLS, so broader
would assume that something that is so widely used is very clearly applicability of the OAM definitions provided is appropriate. It is
defined. However a closer look reveals some points that need to be understood that all future IETF documents will use these definitions
clarified. when appropriate.
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 show a number of different ways that the OAM The examples below show a number of different ways that the OAM
acronym could be expanded and understood. The examples come from acronym could be expanded and understood. The examples come from
many sources including some of the early MPLS-TP I-Ds. many sources including some of the early MPLS-TP I-Ds.
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
 End of changes. 6 change blocks. 
14 lines changed or deleted 25 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/