Internet Engineering Task Force (IETF) L. Andersson
Request for Comments: 6291 Ericsson
BCP: 161 H. van Helvoort
Category: Best Current Practice Huawei Technologies
ISSN: 2070-1721 R. Bonica
Juniper Networks
D. Romascanu
Avaya
S. Mansfield
Ericsson
June 2011
Internet Engineering Task Force (IETF) L. Andersson
Request for Comments: 6291 Ericsson
BCP: 161 H. van Helvoort
Category: Best Current Practice Huawei Technologies
ISSN: 2070-1721 R. Bonica
Juniper Networks
D. Romascanu
Avaya
S. Mansfield
Ericsson
June 2011
Guidelines for the Use of the "OAM" Acronym in the IETF
IETF中“OAM”首字母缩略词的使用指南
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.
乍一看，首字母缩略词“OAM”似乎很有名，也很容易理解。更仔细地看一下首字母缩略词，就会发现一系列反复出现的问题，这些问题会被反复讨论。
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.
本文件提供了首字母缩略词“OAM”（操作、管理和维护）的定义，供将来所有涉及OAM的IETF文件使用。在探讨“OAM”术语组成部分的定义时，将讨论其他定义和首字母缩略词。
Status of This Memo
关于下段备忘
This memo documents an Internet Best Current Practice.
本备忘录记录了互联网最佳实践。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关BCP的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6291.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6291.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Pre-Existing Uses of OAM . . . . . . . . . . . . . . . . . . . 3
2.1. Uses of OAM in Other SDOs . . . . . . . . . . . . . . . . . 4
2.1.1. The "O" in OAM . . . . . . . . . . . . . . . . . . . . 4
2.1.2. The "A" in OAM . . . . . . . . . . . . . . . . . . . . 4
2.1.3. The "M" in OAM . . . . . . . . . . . . . . . . . . . . 5
2.2. Uses of OAM in the IETF . . . . . . . . . . . . . . . . . . 5
3. Recommendations on the Use of the "OAM" Acronym . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Informative References . . . . . . . . . . . . . . . . . . . . 7
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Pre-Existing Uses of OAM . . . . . . . . . . . . . . . . . . . 3
2.1. Uses of OAM in Other SDOs . . . . . . . . . . . . . . . . . 4
2.1.1. The "O" in OAM . . . . . . . . . . . . . . . . . . . . 4
2.1.2. The "A" in OAM . . . . . . . . . . . . . . . . . . . . 4
2.1.3. The "M" in OAM . . . . . . . . . . . . . . . . . . . . 5
2.2. Uses of OAM in the IETF . . . . . . . . . . . . . . . . . . 5
3. Recommendations on the Use of the "OAM" Acronym . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Informative References . . . . . . . . . . . . . . . . . . . . 7
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.
本文件的主要目的是提供首字母缩略词“OAM”（操作、管理和维护）的定义，以供将来所有涉及OAM的IETF文件使用。
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.
首字母缩略词“OAM”经常用于数据和电信行业。人们会认为，被如此广泛使用的东西是非常明确的定义。然而，仔细观察会发现一些需要澄清的问题。
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. Second, the acronym, as such, represents something that is more than just the sum of its parts.
试图理解与OAM一样“内容丰富”的首字母缩略词的使用揭示了两个层次的复杂性。首先，首字母缩写中的每个字母代表一个完整的功能。其次，首字母缩略词本身所代表的不仅仅是各部分的总和。
There is also the issue of how each piece of the acronym is defined. This document provides an analysis of what each initial of the initialism represents and provides possible interpretations of the acronym. Finally, a recommendation for the interpretation of the "OAM" acronym is provided.
还有一个问题是如何定义每个首字母缩写词。本文件分析了首字母缩写词的每个首字母所代表的内容，并提供了首字母缩写词的可能解释。最后，对“OAM”首字母缩略词的解释提出了建议。
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" [OAM-OVERVIEW].
另一个有助于使“OAM”一词在更广范围内易于理解的有用文档是“操作、管理和维护（OAM）机制概述”[OAM-Overview]。
o "Mgmt" - Management
o “管理”-管理
o O&M - OAM and Management
o 运营与维护-运营与管理
o OAM - Operations, Administration, and Maintenance
o OAM-运营、管理和维护
o SDO - Standards Development Organization
o SDO-标准开发组织
This section provides information on how OAM is used in other SDOs (Standards Development Organizations) and provides the background necessary to understand the how the term is used in the IETF.
本节提供了其他SDO（标准开发组织）如何使用OAM的信息，并提供了理解IETF中如何使用该术语所需的背景知识。
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.
操作和维护（OAM）：一组网络管理功能，提供网络故障指示、性能信息以及数据和诊断功能。ATM OAM ITU-T I.610[ITU-T-I.610]是使用“OAM”首字母缩略词扩展的示例规范。
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].
操作、管理和维护（OAM）：一组网络管理功能，提供网络故障指示、故障定位、性能信息以及数据和诊断功能。使用此首字母缩写的示例包括IEEE 802.3-2008[IEEE.802.3-2008]第57条和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).
ITU-T M.3010[ITU-T-M.3010]建议将操作系统功能定义为处理与电信管理相关信息的功能块，以监控/协调和/或控制电信功能，包括管理功能（即TMN（电信管理网络））本身）。
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].
Metro Ethernet Forum将OAM称为安装、监控和排除网络故障的工具和实用程序，帮助运营商更有效地运行其网络MEF 17[MEF-17]。
The "O" in OAM invariably stands for "Operations". However, there is some ambivalence in the definition and scope of the term "Operation".
OAM中的“O”总是代表“操作”。然而，“业务”一词的定义和范围存在一些矛盾。
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.
与“操作”相关的工具示例包括用于服务水平协议（SLA）测量的性能监视工具、用于监视网络中节点和链路健康状况的故障管理工具以及网络供应工具。
The "A" in OAM stands for "Administration".
OAM中的“A”代表“管理”。
Examples of "administration" tools are network discovery and planning tools.
“管理”工具的示例包括网络发现和规划工具。
The "M" in OAM stands for "Maintenance" or "Management".
OAM中的“M”代表“维护”或“管理”。
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.
建议ITU-T M.20[ITU-T-M.20]将维护定义为在规定范围内设置和维护连接设置所涉及的任何元件所需的全部操作（参见ITU-T M.60[ITU-T-M.60]建议）。目的是正确规划和规划建立和维护网络所需的维护操作。
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 examples below show a number of different ways that the "OAM" acronym has been expanded in IETF RFCs. The reference list is not exhaustive.
下面的例子展示了在IETF RFCs中扩展“OAM”首字母缩略词的多种不同方式。参考清单并非详尽无遗。
o OAM = Operations, Administration, and Maintenance in RFC 5586 [RFC5586]
o OAM=RFC 5586[RFC5586]中的操作、管理和维护
o OAM = Operations and Maintenance in RFC 3429 [RFC3429]
o OAM=RFC 3429[RFC3429]中的操作和维护
o OAM = Operations and Management in RFC 4377 [RFC4377]
o OAM=RFC 4377中的运营和管理[RFC4377]
o O&M = OAM and Maintenance in RFC 1812 [RFC1812]
o O&M=RFC 1812[RFC1812]中的OAM和维护
Sometimes there is a fourth letter added to the acronym:
有时首字母缩略词中会添加第四个字母：
o OAM&P = Operations, Administration, Maintenance and Provisioning in RFC 4594 [RFC4594]
o OAM&P=RFC 4594[RFC4594]中的运营、管理、维护和供应
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.
IETF建议对“OAM”首字母缩略词进行扩展，如下所示。除“OAM”首字母缩略词外，本节还提出了另外两项建议。
o OAM - Operations, Administration, and Maintenance
o OAM-运营、管理和维护
o O&M - OAM and Management
o 运营与维护-运营与管理
o "Mgmt" - Management
o “管理”-管理
The components of the "OAM" acronym (and provisioning) are defined as follows:
“OAM”首字母缩略词（和资源调配）的组成部分定义如下：
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 finding problems. Ideally these problems should be found before users are affected.
o 运营-运营活动旨在保持网络（以及网络提供的服务）正常运行。它包括监控网络和发现问题。理想情况下，应该在用户受到影响之前发现这些问题。
o 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.
o 管理-管理活动包括跟踪网络中的资源及其使用方式。它包括跟踪网络资源和受控网络所需的所有簿记。
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 effectively, e.g., adjusting device configuration and parameters.
o 维护-维护活动的重点是促进维修和升级——例如，当设备必须更换时，当路由器需要操作系统映像补丁时，或当新交换机添加到网络时。维护还包括纠正和预防措施，以使受管网络更有效地运行，例如调整设备配置和参数。
"Provisioning" is outside the scope of this document, but the following definition is provided for completeness.
“供应”不在本文件范围内，但为完整起见，提供了以下定义。
o 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 资源调配-资源调配活动涉及配置网络中的资源以支持提供的服务。这可能包括设置网络，以便新客户可以接收Internet访问服务。
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.
一般来说，资源调配用于配置网络以提供新服务，而OAM用于使网络保持在可以支持现有服务的状态。
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.
有时有必要讨论OAM和管理层提供的功能和工具的组合，最好将其表述为“OAM和管理”。如果需要首字母缩略词，则应使用O&M。
"Mgmt" will be used if an abbreviation for "Management" is needed. This document does not define Management.
如果需要“管理”的缩写，将使用“管理”。本文件未定义管理。
This document provides guidance for the use of the "OAM" acronym in other documents. This document does not have direct security implications.
本文件为在其他文件中使用“OAM”首字母缩略词提供了指导。本文件没有直接的安全影响。
The 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.
对首字母缩略词的误解可能导致不正确的规范或实现，进而可能引发协议或已部署网络的安全问题。因此，澄清OAM的含义有利于规范的未来稳定性。
The following individuals significantly contributed to this document.
以下个人对本文件作出了重大贡献。
o Malcolm Betts from M. C. Betts Consulting, Ltd.
o M.C.Betts咨询有限公司的Malcolm Betts。
o Kam Lam from Alcatel Lucent
o 来自阿尔卡特朗讯的金林
o Dieter Beller from Alcatel Lucent
o 来自阿尔卡特朗讯的迪特尔·贝勒
o David Harrington from Huawei Technologies
o 华为技术公司的David Harrington
Thanks to the experts of ITU-T SG 15 for their review and comments.
感谢ITU-T SG 15的专家们的审查和评论。
[IEEE.802.3-2008] 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.
[IEEE.802.3-2008]IEEE，“信息技术-系统间电信和信息交换-局域网和城域网-特定要求-第3部分：带冲突检测的载波侦听多址接入（CSMA/CD）接入方法和物理层规范”，IEEE标准802.3，2008年12月。
[ITU-T-I.610] International Telecommunication Union, "B-ISDN operation and maintenance principles and functions", ITU-T Recommendation I.610, February 1999.
[ITU-T-I.610]国际电信联盟，“B-ISDN运营和维护原则与功能”，ITU-T建议I.610，1999年2月。
[ITU-T-M.20] International Telecommunication Union, "Maintenance philosophy for telecommunication networks", ITU-T Recommendation M.20, October 1992.
[ITU-T-M.20]国际电信联盟，“电信网络的维护理念”，ITU-T建议M.20，1992年10月。
[ITU-T-M.3010] International Telecommunication Union, "Principles for a telecommunications management network", ITU-T Recommendation M.3010, February 2000.
[ITU-T-M.3010]国际电信联盟，“电信管理网络原则”，ITU-T建议M.3010，2000年2月。
[ITU-T-M.60] International Telecommunication Union, "Maintenance terminology and definitions", ITU-T Recommendation M.60, March 1993.
[ITU-T-M.60]国际电信联盟，“维护术语和定义”，ITU-T建议M.60，1993年3月。
[ITU-T-Y.1731] International Telecommunication Union, "OAM functions and mechanisms for Ethernet based networks", ITU-T Recommendation Y.1731, February 2008.
[ITU-T-Y.1731]国际电信联盟，“基于以太网的网络的OAM功能和机制”，ITU-T建议Y.17312008年2月。
[MEF-17] Metro Ethernet Forum, "Service OAM Requirements & Framework - Phase 1", MEF Technical Specification MEF 17, April 2007.
[MEF-17]城域以太网论坛，“业务OAM要求和框架-第1阶段”，MEF技术规范MEF 17，2007年4月。
[OAM-OVERVIEW] Mizrahi, T., Sprecher, N., Bellagamba, E., and Y. Weingarten, "An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms", Work in Progress, March 2011.
[OAM概述]Mizrahi，T.，Sprecher，N.，Bellagamba，E.，和Y.Weingarten，“运营、管理和维护（OAM）机制概述”，进展中的工作，2011年3月。
[RFC1812] Baker, F., "Requirements for IP Version 4 Routers", RFC 1812, June 1995.
[RFC1812]Baker，F.，“IP版本4路由器的要求”，RFC1812，1995年6月。
[RFC3429] Ohta, H., "Assignment of the 'OAM Alert Label' for Multiprotocol Label Switching Architecture (MPLS) Operation and Maintenance (OAM) Functions", RFC 3429, November 2002.
[RFC3429]Ohta，H.，“多协议标签交换体系结构（MPLS）操作和维护（OAM）功能的‘OAM警报标签’分配”，RFC 34292002年11月。
[RFC4377] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S. Matsushima, "Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks", RFC 4377, February 2006.
[RFC4377]Nadeau，T.，Morrow，M.，Swallow，G.，Allan，D.，和S.Matsushima，“多协议标签交换（MPLS）网络的运营和管理（OAM）要求”，RFC 4377，2006年2月。
[RFC4594] Babiarz, J., Chan, K., and F. Baker, "Configuration Guidelines for DiffServ Service Classes", RFC 4594, August 2006.
[RFC4594]Babiarz，J.，Chan，K.，和F.Baker，“区分服务服务类的配置指南”，RFC 45942006年8月。
[RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic Associated Channel", RFC 5586, June 2009.
[RFC5586]Bocci，M.，Vigoureux，M.，和S.Bryant，“MPLS通用关联信道”，RFC 55862009年6月。
Authors' Addresses
作者地址
Loa Andersson Ericsson
安达信爱立信银行
EMail: loa.andersson@ericsson.com
EMail: loa.andersson@ericsson.com
Huub van Helvoort Huawei Technologies
Huub van Helvoort华为技术有限公司
EMail: huub.van.helvoort@huawei.com
EMail: huub.van.helvoort@huawei.com
Ron Bonica Juniper Networks
Ron Bonica Juniper网络
EMail: rbonica@juniper.net
EMail: rbonica@juniper.net
Dan Romascanu Avaya
丹·罗马斯卡努·阿瓦亚
EMail: dromasca@avaya.com
EMail: dromasca@avaya.com
Scott Mansfield Ericsson
斯科特·曼斯菲尔德·爱立信
EMail: scott.mansfield@ericsson.com
EMail: scott.mansfield@ericsson.com