draft-ietf-opsawg-mpls-tp-oam-def-08.txt   draft-ietf-opsawg-mpls-tp-oam-def-09.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: September 30, 2011 Huawei Technologies Expires: October 8, 2011 Huawei Technologies
R. Bonica R. Bonica
Juniper Networks Juniper Networks
D. Romascanu D. Romascanu
Avaya Avaya
S. Mansfield S. Mansfield
Ericsson Ericsson
March 29, 2011 April 6, 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-08.txt draft-ietf-opsawg-mpls-tp-oam-def-09.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 September 30, 2011. This Internet-Draft will expire on October 8, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 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
skipping to change at page 3, line 8 skipping to change at page 3, line 8
4. Recommended Acronyms . . . . . . . . . . . . . . . . . . . . . 9 4. Recommended Acronyms . . . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
8. Informative references . . . . . . . . . . . . . . . . . . . . 13 8. Informative references . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
The main purpose of this document is to provide a definition of the The main purpose of this document is to provide a definition of the
OAM acronym such that it is useful for the IETF. 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 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 show a number of different ways that the OAM The examples below show a number of different ways that the OAM
acronym has been expanded in previous documents. acronym has been expanded in previous documents.
o OAM = Operation, Administration, Maintenance o OAM = Operation, Administration, Maintenance
skipping to change at page 7, line 7 skipping to change at page 7, line 7
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 IETF recommended expansion of the OAM acronym is
some background on the definitions provided. listed. This section gives some background on the definitions
provided.
"Mgmt" will be used if an abbreviation for "Management" is needed. "Mgmt" will be used if an abbreviation for "Management" is needed.
This draft does not define Management. It is noted, however, that an This document does not define Management. It is noted, however, that
important part of management functionality relates to tools to report an important part of management functionality relates to tools to
the state of the network. report the state of the network.
The OAM acronym is to be used for "Operations, Administration, and The OAM acronym is to be used for "Operations, Administration, and
Maintenance", excluding provisioning. Maintenance", excluding provisioning.
OAM tools and protocols, and the "Management space" are complementary OAM tools and protocols, and the "Management space" are complementary
in nature. Management focuses on FCAPS (Fault, Configuration, in nature. Management focuses on FCAPS (Fault, Configuration,
Accounting, Performance, and Security) functionality and on manager Accounting, Performance, and Security) functionality and on manager
(or NOC (Network Operations Center)) to device (or network) (or NOC (Network Operations Center)) to device (or network)
interaction. interaction.
skipping to change at page 9, line 7 skipping to change at page 9, line 7
new services, whereas OAM is used to keep the network in a state that new services, whereas OAM is used to keep the network in a state that
it can support already existing services. it can support already existing services.
Sometimes it is necessary to talk about the combination of functions Sometimes it is necessary to talk about the combination of functions
and tools supplied by OAM and Management, it is preferred that this 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 is spelled out as "OAM and Management". In cases where an acronym is
needed O&M should be used. needed O&M should be used.
4. Recommended Acronyms 4. Recommended Acronyms
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 OAM - Operations, Administration, and Maintenance
O&M - OAM and Management O&M - OAM and Management
"Mgmt" - Management "Mgmt" - Management
5. IANA Considerations 5. IANA Considerations
This memo includes no request to IANA. This memo includes no request to IANA.
skipping to change at page 13, line 11 skipping to change at page 13, line 11
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., Sprecher, N., Bellagamba, E., and Y. Mizrahi, T., Sprecher, N., Bellagamba, E., and Y.
Weingarten, "An Overview of Operations, Administration, Weingarten, "An Overview of Operations, Administration,
and Maintenance (OAM) Mechanisms", and Maintenance (OAM) Mechanisms",
draft-ietf-opsawg-oam-overview-03 (work in progress), draft-ietf-opsawg-oam-overview-04 (work in progress),
January 2011. March 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]
 End of changes. 9 change blocks. 
12 lines changed or deleted 18 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/