--- 1/draft-ietf-opsawg-mpls-tp-oam-def-00.txt 2010-01-19 02:10:54.000000000 +0100 +++ 2/draft-ietf-opsawg-mpls-tp-oam-def-01.txt 2010-01-19 02:10:54.000000000 +0100 @@ -1,24 +1,49 @@ Network Working Group L. Andersson Internet-Draft Ericsson Intended status: Informational M. Betts -Expires: March 13, 2010 H. van Helvoort - Huawei Tecnologies +Expires: July 19, 2010 ZTE Corporation + H. van Helvoort + Huawei 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. @@ -27,310 +52,320 @@ 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, 2010. + This Internet-Draft will expire on July 19, 2010. Copyright Notice - Copyright (c) 2009 IETF Trust and the persons identified as the + Copyright (c) 2010 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 in effect on the date of - publication of this document (http://trustee.ietf.org/license-info). - 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 document - has one primary and a secondary goal. The primary goal is to find an - understanding of OAM that is feasible for the MPLS Transport Profile - (MPLS-TP)effort. The secondary goal is to make this understanding - applicable in a wider scope + 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 BSD License. Table of Contents - 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2. OAM and O, A and M . . . . . . . . . . . . . . . . . . . . . . 5 - 2.1. OAM as a functional unit . . . . . . . . . . . . . . . . . 5 - 2.2. The acronym broken up . . . . . . . . . . . . . . . . . . 5 - 2.2.1. O in OAM . . . . . . . . . . . . . . . . . . . . . . . 5 - 2.2.2. A in OAM . . . . . . . . . . . . . . . . . . . . . . . 5 - 2.2.3. M in OAM . . . . . . . . . . . . . . . . . . . . . . . 6 - 3. Use of the OAM acronym MPLS-TP effort . . . . . . . . . . . . 7 - 4. Acronyms for the MPLS-TP effort . . . . . . . . . . . . . . . 9 - 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 10 - 6. Security considerations . . . . . . . . . . . . . . . . . . . 11 - 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 - 8.1. Normative References . . . . . . . . . . . . . . . . . . . 13 - 8.2. Informative references . . . . . . . . . . . . . . . . . . 13 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 + 2. OAM and O, A and M . . . . . . . . . . . . . . . . . . . . . . 6 + 2.1. OAM as a functional unit . . . . . . . . . . . . . . . . . 6 + 2.2. The acronym broken up . . . . . . . . . . . . . . . . . . 6 + 2.2.1. O in OAM . . . . . . . . . . . . . . . . . . . . . . . 6 + 2.2.2. A in OAM . . . . . . . . . . . . . . . . . . . . . . . 6 + 2.2.3. M in OAM . . . . . . . . . . . . . . . . . . . . . . . 7 + 3. Use of the OAM acronym MPLS-TP effort . . . . . . . . . . . . 8 + 4. Acronyms for the MPLS-TP effort . . . . . . . . . . . . . . . 10 + 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 11 + 6. Security considerations . . . . . . . . . . . . . . . . . . . 12 + 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 + 8.1. Normative references . . . . . . . . . . . . . . . . . . . 14 + 8.2. Informative references . . . . . . . . . . . . . . . . . . 14 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 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 in this document - is needed for consistency within that group af draft. + working group last call and some of the definitions in this document + are needed for consistency within that group of drafts. - 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 very clearly defined. However a closer look reveals some points that - needs to be clarified. + need to be clarified. - The examples used below comes mainly from the first set of MPLS-TP - IDs. In the IDs there were a number of examples of how the acronym - could be a number of ways to expand and understand the acronym e.g.: + The examples below 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 - corrected and aligned with what is proposed in this document. + The examples above were taken from drafts that later 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 integrated piece of functionality; secondly the - acronym as such represent something that is more than just the sum of - the pieces + 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 the interpretation of the OAM acronym to use for the MPLS-TP + effort based on the agreement reached in the JWT report [1] is + provided. - In this document we will analyse how each piece of the acronym is - defined and provide possible interpretations of the acronym. Finally - we will suggest the use of the OAM acronym for the MPLS-TP effort - based on the greement reached based on the JWT report - [I-D.bryant-mpls-tp-jwt-report]. - - Our 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 immediate target is to document the use of the OAM acronym such + that it is useful for MPLS-TP. However, broader applicability of the + definitions in this document may also come to light. - The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", - "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this - document are to be interpreted as described in RFC 2119 [RFC2119]. + 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. 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] and IEEE Std. 802.3 Clause 57 OAM - - Alternatively (Huub :) ) + are ATM OAM ITU-T I.610 [3] and Clause 57 of IEEE 802.3-2008 [2]. Operations, Administration, and Maintenance (OAM): A group of network management functions that provide network fault indication, fault - localisation performance information, and data and diagnosis + localization, performance information, and data and diagnosis functions. - ITU-T M.3010 recommendation defines: - - operations systems function: 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 itself). + The ITU-T M.3010 [6] 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 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. + 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 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 in the definition and scope of - "Operation" + However there is some ambivalence in the definition and scope of the + term "Operation". Note: Examples to be provided. 2.2.2. A in OAM - The A in the OAM acronym mostly stands for "Adminstration", though in - a few cases it seems like "Accounting" have crept in. For the - purpose of this document we will assume that "Adminstration" is the + The A in the OAM acronym mostly stands for "Administration", though + in a few cases it seems like "Accounting" is also used. For the + purpose of this document it is assumed that "Administration" is the correct expansion of "A". Note: Examples to be provided. - Admistration is used to support maintenance functions, e.g. by + 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 it does not seem to be a good idea to use them + 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 defines mainteance: - - Maintenance involves the whole of operations required for setting up - and maintaining, within prescribed limits, any element entering into - the setting-up of a connection (see Recommendation M.60). In order - to properly plan and program the maintenance operations required to - establish and maintain a network. + The recommendation ITU-T M.20 [4] 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 [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 major aim to minimize both the occurrence and the - impact of failures and to ensure that in cause of a failure the - correct actions are taken. The ITU-T document also clearly defines a - maintenace philosphy. + 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. The ITU-T document also + clearly defines a 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 section gives somwe background. + In Section 4 the acronyms as they will be used in the MPLS-TP effort + are listed. This section gives some background on the definitions + provided. - If we need as an abbreviation for "Management" we will use "Mgt". We - do not define Management in this draft, but note that an important - part of the Management funtionality relates to tools to report the - state of the network. + "Mgt" will be used if an abbreviation for "Management" is needed. + This draft does not define Management. It is noted, however, that an + important part of management functionality relates to tools to report + the state of the network. - We propose that the OAM acronym is reserved to be used for - "Operations, Administration and Maintenance", i.e. excluding - provisioning. + In MPLS-TP drafts, the OAM acronym is to be used for "Operations, + Administration and Maintenance", i.e. excluding provisioning. OAM tools and protocols and the "Management space" are complementary - in natur. Management focuses on FCAPS functionality and on manager + in 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" + management protocols tend to be "vertical". Where each part of the acronym and provisioning is defined as follows: - o Operations - Operation activities is undertaken to keep the + o 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 find problems. + running. It includes monitoring the network and finding problems. Ideally these problems should be found before users are affected." - o Administration - Administration activities involves keeping track + o Administration - Administration activities involve keeping track of resources in the network and how they are used. It includes - all the book keeping that is necessary to keep track of networking + all the bookkeeping that is necessary to track 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, when a new switch is added to a network. Maintenance also - involves corrective and preventive measures to make the managed - network run more efficient, e.g. adjusting device configuration - and parameters. + 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 efficiently, e.g. adjusting device + configuration and parameters. - o Even though we don't include "Provisioning" in the OAM acronym we - note that: + o Even though "Provisioning" is not included in this document, the + following definition is provided for completeness. - Provisioning - Provisioning activities involves configuring + 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. - o We also note that sometimes it is necessary to talk about the - combination of functions and tools suplied by OAM and Management, - we prefer that this is spelled out as "OAM and Management". In + o 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. 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 document only changes the name of one field in the MPLS Shim - Header and thus does not introduce any new security considerations. + Security is a significant requirement of MPLS-TP. However, this + informational document is intended only to provide guidance on the + use of the OAM acronym, and the security 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. +8.1. Normative references 8.2. Informative references - [I-D.bryant-mpls-tp-jwt-report] - Bryant, S. and L. Andersson, "JWT Report on MPLS - Architectural Considerations for a Transport Profile", - draft-bryant-mpls-tp-jwt-report-00 (work in progress), - July 2008. + [1] Bryant, S. and L. Andersson, "Joint Working Team (JWT) Report on + MPLS Architectural Considerations for a Transport Profile", + 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 + Email: malcolm.betts@zte.com.cn Huub van Helvoort - Huawei Tecnologies + Huawei Technologies Email: hhelvoort@huawei.com Ron Bonica Juniper Networks Email: rbonica@juniper.net Dan Romascanu Avaya