Internet Engineering Task Force (IETF) D. King, Ed.
Request for Comments: 6639 Old Dog Consulting
Category: Informational M. Venkatesan, Ed.
ISSN: 2070-1721 Aricent
June 2012
Internet Engineering Task Force (IETF) D. King, Ed.
Request for Comments: 6639 Old Dog Consulting
Category: Informational M. Venkatesan, Ed.
ISSN: 2070-1721 Aricent
June 2012
Multiprotocol Label Switching Transport Profile (MPLS-TP) MIB-Based Management Overview
多协议标签交换传输配置文件（MPLS-TP）基于MIB的管理概述
Abstract
摘要
A range of Management Information Base (MIB) modules has been developed to help model and manage the various aspects of Multiprotocol Label Switching (MPLS) networks. These MIB modules are defined in separate documents that focus on the specific areas of responsibility of the modules that they describe.
已经开发了一系列管理信息库（MIB）模块来帮助建模和管理多协议标签交换（MPLS）网络的各个方面。这些MIB模块在单独的文档中定义，这些文档侧重于它们描述的模块的特定职责领域。
The MPLS Transport Profile (MPLS-TP) is a profile of MPLS functionality specific to the construction of packet-switched transport networks.
MPLS传输配置文件（MPLS-TP）是特定于分组交换传输网络构造的MPLS功能的配置文件。
This document describes the MIB-based architecture for MPLS-TP, indicates the interrelationships between different existing MIB modules that can be leveraged for MPLS-TP network management, and identifies areas where additional MIB modules are required.
本文档描述了MPLS-TP基于MIB的体系结构，指出了可用于MPLS-TP网络管理的不同现有MIB模块之间的相互关系，并确定了需要额外MIB模块的领域。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
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). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见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/rfc6639.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6639.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 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 ....................................................4
1.1. MPLS-TP Management Function ................................5
2. Terminology .....................................................5
3. The SNMP Management Framework ...................................5
4. Overview of Existing Work .......................................6
4.1. MPLS Management Overview and Requirements ..................6
4.2. An Introduction to the MPLS and Pseudowire MIB Modules .....6
4.2.1. Structure of the MPLS MIB OID Tree ..................6
4.2.2. Textual Convention Modules ..........................8
4.2.3. Label Switched Path (LSP) Modules ...................8
4.2.4. Label Edge Router (LER) Modules .....................8
4.2.5. Label Switching Router (LSR) Modules ................9
4.2.6. Pseudowire Modules ..................................9
4.2.7. Routing and Traffic Engineering ....................10
4.2.8. Resiliency .........................................11
4.2.9. Fault Management and Performance Management ........11
4.2.10. MIB Module Interdependencies ......................13
4.2.11. Dependencies on External MIB Modules ..............15
5. Applicability of MPLS MIB Modules to MPLS-TP ...................16
5.1. MPLS-TP Tunnel ............................................17
5.1.1. Gap Analysis .......................................17
5.1.2. Recommendations ....................................17
5.2. MPLS-TP Pseudowire ........................................17
5.2.1. Gap Analysis .......................................17
5.2.2. Recommendations ....................................18
5.3. MPLS-TP Sections ..........................................18
5.3.1. Gap Analysis .......................................18
5.3.2. Recommendations ....................................18
5.4. MPLS-TP OAM ...............................................18
5.4.1. Gap Analysis .......................................18
5.4.2. Recommendations ....................................19
5.5. MPLS-TP Protection Switching and Recovery .................19
5.5.1. Gap Analysis .......................................19
5.5.2. Recommendations ....................................19
5.6. MPLS-TP Interfaces ........................................19
5.6.1. Gap Analysis .......................................19
5.6.2. Recommendations ....................................19
1. Introduction ....................................................4
1.1. MPLS-TP Management Function ................................5
2. Terminology .....................................................5
3. The SNMP Management Framework ...................................5
4. Overview of Existing Work .......................................6
4.1. MPLS Management Overview and Requirements ..................6
4.2. An Introduction to the MPLS and Pseudowire MIB Modules .....6
4.2.1. Structure of the MPLS MIB OID Tree ..................6
4.2.2. Textual Convention Modules ..........................8
4.2.3. Label Switched Path (LSP) Modules ...................8
4.2.4. Label Edge Router (LER) Modules .....................8
4.2.5. Label Switching Router (LSR) Modules ................9
4.2.6. Pseudowire Modules ..................................9
4.2.7. Routing and Traffic Engineering ....................10
4.2.8. Resiliency .........................................11
4.2.9. Fault Management and Performance Management ........11
4.2.10. MIB Module Interdependencies ......................13
4.2.11. Dependencies on External MIB Modules ..............15
5. Applicability of MPLS MIB Modules to MPLS-TP ...................16
5.1. MPLS-TP Tunnel ............................................17
5.1.1. Gap Analysis .......................................17
5.1.2. Recommendations ....................................17
5.2. MPLS-TP Pseudowire ........................................17
5.2.1. Gap Analysis .......................................17
5.2.2. Recommendations ....................................18
5.3. MPLS-TP Sections ..........................................18
5.3.1. Gap Analysis .......................................18
5.3.2. Recommendations ....................................18
5.4. MPLS-TP OAM ...............................................18
5.4.1. Gap Analysis .......................................18
5.4.2. Recommendations ....................................19
5.5. MPLS-TP Protection Switching and Recovery .................19
5.5.1. Gap Analysis .......................................19
5.5.2. Recommendations ....................................19
5.6. MPLS-TP Interfaces ........................................19
5.6.1. Gap Analysis .......................................19
5.6.2. Recommendations ....................................19
6. An Introduction to the MPLS-TP MIB Modules .....................20
6.1. MPLS-TP MIB Modules .......................................20
6.1.1. New MIB Modules for MPLS-TP ........................20
6.1.2. Textual Conventions for MPLS-TP ....................20
6.1.3. Identifiers for MPLS-TP ............................21
6.1.4. LSR MIB Extensions for MPLS-TP .....................21
6.1.5. Tunnel Extensions for MPLS-TP ......................21
6.2. PWE3 MIB Modules for MPLS-TP ..............................21
6.2.1. New MIB Modules for MPLS-TP Pseudowires ............21
6.2.2. Pseudowire Textual Conventions for MPLS-TP .........21
6.2.3. Pseudowire Extensions for MPLS-TP ..................22
6.2.4. Pseudowire MPLS Extensions for MPLS-TP .............22
6.3. OAM MIB Modules for MPLS-TP ...............................22
6.3.1. New MIB Modules for OAM for MPLS-TP ................22
6.3.2. BFD MIB Module .....................................22
6.3.3. OAM MIB Module .....................................23
6.4. Protection Switching and Recovery MIB Modules for MPLS-TP .23
6.4.1. New MIB Modules for MPLS Protection
Switching and Recovery .............................23
6.4.2. Linear Protection Switching MIB Module .............23
6.4.3. Ring Protection Switching MIB Module ...............23
6.4.4. Mesh Protection Switching MIB Module ...............23
7. Management Options .............................................23
8. Security Considerations ........................................24
9. IANA Considerations ............................................24
10. Acknowledgements ..............................................24
11. Contributors' Addresses .......................................25
12. References ....................................................26
12.1. Normative References .....................................26
12.2. Informative References ...................................27
6. An Introduction to the MPLS-TP MIB Modules .....................20
6.1. MPLS-TP MIB Modules .......................................20
6.1.1. New MIB Modules for MPLS-TP ........................20
6.1.2. Textual Conventions for MPLS-TP ....................20
6.1.3. Identifiers for MPLS-TP ............................21
6.1.4. LSR MIB Extensions for MPLS-TP .....................21
6.1.5. Tunnel Extensions for MPLS-TP ......................21
6.2. PWE3 MIB Modules for MPLS-TP ..............................21
6.2.1. New MIB Modules for MPLS-TP Pseudowires ............21
6.2.2. Pseudowire Textual Conventions for MPLS-TP .........21
6.2.3. Pseudowire Extensions for MPLS-TP ..................22
6.2.4. Pseudowire MPLS Extensions for MPLS-TP .............22
6.3. OAM MIB Modules for MPLS-TP ...............................22
6.3.1. New MIB Modules for OAM for MPLS-TP ................22
6.3.2. BFD MIB Module .....................................22
6.3.3. OAM MIB Module .....................................23
6.4. Protection Switching and Recovery MIB Modules for MPLS-TP .23
6.4.1. New MIB Modules for MPLS Protection
Switching and Recovery .............................23
6.4.2. Linear Protection Switching MIB Module .............23
6.4.3. Ring Protection Switching MIB Module ...............23
6.4.4. Mesh Protection Switching MIB Module ...............23
7. Management Options .............................................23
8. Security Considerations ........................................24
9. IANA Considerations ............................................24
10. Acknowledgements ..............................................24
11. Contributors' Addresses .......................................25
12. References ....................................................26
12.1. Normative References .....................................26
12.2. Informative References ...................................27
The MPLS Transport Profile (MPLS-TP) is a packet transport technology based on a profile of the MPLS functionality specific to the construction of packet-switched transport networks. MPLS is described in [RFC3031], and requirements for MPLS-TP are specified in [RFC5654].
MPLS传输配置文件（MPLS-TP）是基于特定于分组交换传输网络构造的MPLS功能配置文件的分组传输技术。MPLS在[RFC3031]中有描述，MPLS-TP的要求在[RFC5654]中有规定。
A range of Management Information Base (MIB) modules has been developed to help model and manage the various aspects of Multiprotocol Label Switching (MPLS) networks. These MIB modules are defined in separate documents that focus on the specific areas of responsibility for the modules that they describe.
已经开发了一系列管理信息库（MIB）模块来帮助建模和管理多协议标签交换（MPLS）网络的各个方面。这些MIB模块在单独的文档中定义，这些文档侧重于它们所描述的模块的特定责任领域。
An MPLS-TP network can be operated via static provisioning of transport paths, Label Switched Paths (LSPs) and pseudowires (PWs), or the elective use of a Generalized MPLS (GMPLS) control plane to support dynamic provisioning of transport paths, LSPs, and PWs.
MPLS-TP网络可以通过传输路径、标签交换路径（LSP）和伪线（PW）的静态供应来运行，或者选择性地使用通用MPLS（GMPLS）控制平面来支持传输路径、LSP和PW的动态供应。
This document describes the MIB-based management architecture for MPLS, as extended for MPLS-TP. The document also indicates the interrelationships between existing MIB modules that should be leveraged for MPLS-TP network management and identifies areas where additional MIB modules are required.
本文档描述了MPLS的基于MIB的管理体系结构，以及对MPLS-TP的扩展。该文件还指出了应用于MPLS-TP网络管理的现有MIB模块之间的相互关系，并确定了需要额外MIB模块的领域。
Note that [RFC5951] does not specify a preferred management interface protocol to be used as the standard protocol for managing MPLS-TP networks.
请注意，[RFC5951]未指定用作管理MPLS-TP网络的标准协议的首选管理接口协议。
The management of the MPLS-TP networks is separable from that of its client networks so that the same means of management can be used regardless of the client. The management function of MPLS-TP includes fault management, configuration management, performance monitoring, and security management.
MPLS-TP网络的管理与其客户机网络的管理是分开的，因此无论客户机是什么，都可以使用相同的管理手段。MPLS-TP的管理功能包括故障管理、配置管理、性能监控和安全管理。
The purpose of the management function is to provide control and monitoring of the MPLS transport profile protocol mechanisms and procedures. The requirements for the network management functionality are found in [RFC5951]. A description of the network and element management architectures that can be applied to the management of MPLS-based transport networks is found in [RFC5950].
管理功能的目的是提供对MPLS传输配置文件协议机制和过程的控制和监视。网络管理功能的要求见[RFC5951]。[RFC5950]中介绍了可应用于基于MPLS的传输网络管理的网络和元件管理体系结构。
This document also uses terminology from the MPLS architecture document [RFC3031], Pseudowire Emulation Edge-to-Edge (PWE3) architecture [RFC3985], and the following MPLS-related MIB modules: the MPLS-TC-STD-MIB [RFC3811], MPLS-LSR-STD-MIB [RFC3813], MPLS-TE-STD-MIB [RFC3812], MPLS-LDP-STD-MIB [RFC3815], MPLS-FTN-STD-MIB [RFC3814], and TE-LINK-STD-MIB [RFC4220].
本文件还使用了MPLS体系结构文件[RFC3031]、伪线仿真边对边（PWE3）体系结构[RFC3985]和以下MPLS相关MIB模块中的术语：MPLS-TC-STD-MIB[RFC3811]、MPLS-LSR-STD-MIB[RFC3813]、MPLS-TE-STD-MIB[RFC3812]、MPLS-LDP-STD-MIB[RFC3815]、MPLS-FTN-STD-MIB[RFC3814]、MPLS-FTN-MIB，和TE-LINK-STD-MIB[RFC4220]。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP).
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。
Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI).
MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to Section 7 of [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅[RFC3410]第7节。
This document discusses MIB modules that are compliant to the SMIv2, which is described in [RFC2578], [RFC2579], and [RFC2580].
本文档讨论了符合SMIv2的MIB模块，如[RFC2578]、[RFC2579]和[RFC2580]所述。
This section describes the existing tools and techniques for managing and modeling MPLS networks, devices, and protocols. It is intended to provide a description of the tool kit that is already available.
本节介绍用于管理和建模MPLS网络、设备和协议的现有工具和技术。其目的是提供已提供的工具包的说明。
Section 5 of this document outlines the applicability of existing MPLS MIB modules to MPLS-TP, describes the optional use of GMPLS MIB modules in MPLS-TP networks, and examines the additional MIB modules and objects that would be required for managing an MPLS-TP network.
本文件第5节概述了现有MPLS MIB模块对MPLS-TP的适用性，描述了在MPLS-TP网络中可选使用GMPLS MIB模块，并检查了管理MPLS-TP网络所需的其他MIB模块和对象。
[RFC4378] outlines how data-plane protocols can assist in providing the Operations, Administration, and Maintenance (OAM) requirements outlined in [RFC4377] and how it is applied to the management functions of fault, configuration, accounting, performance, and security (commonly known as FCAPS) for MPLS networks.
[RFC4378]概述了数据平面协议如何帮助提供[RFC4377]中概述的操作、管理和维护（OAM）要求，以及如何将其应用于MPLS网络的故障、配置、计费、性能和安全（通常称为FCAP）管理功能。
[RFC4221] describes the management architecture for MPLS. In particular, it describes how the managed objects defined in various MPLS-related MIB modules model different aspects of MPLS, as well as the interactions and dependencies between each of these MIB modules.
[RFC4221]描述了MPLS的管理架构。特别是，它描述了在各种与MPLS相关的MIB模块中定义的托管对象如何对MPLS的不同方面进行建模，以及每个MIB模块之间的交互和依赖关系。
[RFC4377] describes the requirements for user- and data-plane OAM and applications for MPLS.
[RFC4377]描述了用户和数据平面OAM以及MPLS应用程序的要求。
[RFC5654] describes the requirements for the optional use of a control plane to support dynamic provisioning of MPLS-TP transport paths. The MPLS-TP LSP control plane is based on GMPLS and is described in [RFC3945].
[RFC5654]描述了可选使用控制平面以支持MPLS-TP传输路径的动态资源调配的要求。MPLS-TP LSP控制平面基于GMPLS，如[RFC3945]所述。
The MPLS MIB Object Identifier (OID) tree has the following structure. It is based on the tree originally set out in Section 4.1 of [RFC4221] and has been enhanced to include other relevant MIB modules.
MPLS MIB对象标识符（OID）树具有以下结构。它基于[RFC4221]第4.1节中最初规定的树，并经过增强，包括其他相关MIB模块。
mib-2 -- RFC 2578 [RFC2578]
|
+-transmission
| |
| +- mplsStdMIB
| | |
| | +- mplsTCStdMIB -- MPLS-TC-STD-MIB [RFC3811]
| | |
| | +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB [RFC3813]
| | |
| | +- mplsTeStdMIB -- MPLS-TE-STD-MIB [RFC3812]
| | |
| | +- mplsLdpStdMIB -- MPLS-LDP-STD-MIB [RFC3815]
| | |
| | +- mplsLdpGenericStdMIB
| | | -- MPLS-LDP-GENERIC-STD-MIB [RFC3815]
| | |
| | +- mplsFTNStdMIB -- MPLS-FTN-STD-MIB [RFC3814]
| | |
| | +- gmplsTCStdMIB -- GMPLS-TC-STD-MIB [RFC4801]
| | |
| | +- gmplsTeStdMIB -- GMPLS-TE-STD-MIB [RFC4802]
| | |
| | +- gmplsLsrStdMIB -- GMPLS-LSR-STD-MIB [RFC4803]
| | |
| | +- gmplsLabelStdMIB -- GMPLS-LABEL-STD-MIB [RFC4803]
| |
| +- teLinkStdMIB -- TE-LINK-STD-MIB [RFC4220]
| |
| +- pwStdMIB -- PW-STD-MIB [RFC5601]
|
+- ianaGmpls -- IANA-GMPLS-TC-MIB [RFC4802]
|
+- ianaPwe3MIB -- IANA-PWE3-MIB [RFC5601]
|
+- pwEnetStdMIB -- PW-ENET-STD-MIB [RFC5603]
|
+- pwMplsStdMIB -- PW-MPLS-STD-MIB [RFC5602]
|
+- pwTDMMIB -- PW-TDM-MIB [RFC5604]
|
+- pwTcStdMIB -- PW-TC-STD-MIB [RFC5542]
mib-2 -- RFC 2578 [RFC2578]
|
+-transmission
| |
| +- mplsStdMIB
| | |
| | +- mplsTCStdMIB -- MPLS-TC-STD-MIB [RFC3811]
| | |
| | +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB [RFC3813]
| | |
| | +- mplsTeStdMIB -- MPLS-TE-STD-MIB [RFC3812]
| | |
| | +- mplsLdpStdMIB -- MPLS-LDP-STD-MIB [RFC3815]
| | |
| | +- mplsLdpGenericStdMIB
| | | -- MPLS-LDP-GENERIC-STD-MIB [RFC3815]
| | |
| | +- mplsFTNStdMIB -- MPLS-FTN-STD-MIB [RFC3814]
| | |
| | +- gmplsTCStdMIB -- GMPLS-TC-STD-MIB [RFC4801]
| | |
| | +- gmplsTeStdMIB -- GMPLS-TE-STD-MIB [RFC4802]
| | |
| | +- gmplsLsrStdMIB -- GMPLS-LSR-STD-MIB [RFC4803]
| | |
| | +- gmplsLabelStdMIB -- GMPLS-LABEL-STD-MIB [RFC4803]
| |
| +- teLinkStdMIB -- TE-LINK-STD-MIB [RFC4220]
| |
| +- pwStdMIB -- PW-STD-MIB [RFC5601]
|
+- ianaGmpls -- IANA-GMPLS-TC-MIB [RFC4802]
|
+- ianaPwe3MIB -- IANA-PWE3-MIB [RFC5601]
|
+- pwEnetStdMIB -- PW-ENET-STD-MIB [RFC5603]
|
+- pwMplsStdMIB -- PW-MPLS-STD-MIB [RFC5602]
|
+- pwTDMMIB -- PW-TDM-MIB [RFC5604]
|
+- pwTcStdMIB -- PW-TC-STD-MIB [RFC5542]
Note: The OIDs for MIB modules are assigned and managed by IANA. They can be found in the referenced MIB documents.
注：MIB模块的OID由IANA分配和管理。它们可以在参考的MIB文档中找到。
The MPLS-TC-STD-MIB [RFC3811], GMPLS-TC-STD-MIB [RFC4801], IANA-GMPLS-TC-MIB [RFC4802], and PW-TC-STD-MIB [RFC5542] contain the Textual Conventions for MPLS and GMPLS networks. These Textual Conventions should be imported by MIB modules that manage MPLS and GMPLS networks. Section 4.2.11 highlights dependencies on additional external MIB modules.
MPLS-TC-STD-MIB[RFC3811]、GMPLS-TC-STD-MIB[RFC4801]、IANA-GMPLS-TC-MIB[RFC4802]和PW-TC-STD-MIB[RFC5542]包含MPLS和GMPLS网络的文本约定。这些文本约定应由管理MPLS和GMPLS网络的MIB模块导入。第4.2.11节强调了对附加外部MIB模块的依赖性。
An LSP is a path over which a labeled packet travels across the sequence of Label Switching Routers (LSRs) for a given Forward Equivalence Class (FEC). When a packet, with or without a label, arrives at an ingress Label Edge Router (LER) of an LSP, it is encapsulated with the label corresponding to the FEC and sent across the LSP. The labeled packet traverses the LSRs and arrives at the egress LER of the LSP, where it gets forwarded, depending on the packet type it came with. LSPs could be nested using label stacking, such that an LSP could traverse another LSP. A more detailed description of an LSP can be found in [RFC3031].
LSP是一条路径，对于给定的前向等价类（FEC），标签分组在标签交换路由器（LSR）序列上移动。当带有或不带有标签的数据包到达LSP的入口标签边缘路由器（LER）时，它用对应于FEC的标签封装并通过LSP发送。带标签的数据包通过LSR到达LSP的出口LER，在那里根据其附带的数据包类型进行转发。LSP可以使用标签堆叠进行嵌套，这样一个LSP可以遍历另一个LSP。有关LSP的更详细说明，请参见[RFC3031]。
The MPLS-LSR-STD-MIB [RFC3813] describes the objects required to define the LSP.
MPLS-LSR-STD-MIB[RFC3813]描述了定义LSP所需的对象。
Ingress and egress LSRs of an LSP are known as Label Edge Routers (LERs). An ingress LER takes each incoming unlabeled or labeled packet and encapsulates it with the corresponding label of the LSP it represents, and then forwards it to the adjacent LSR of the LSP. Each FEC is mapped to a label-forwarding entry, so that a packet could be encapsulated with one or more label entries; this is referred to as a label stack.
LSP的入口和出口LSR称为标签边缘路由器（LER）。入口LER接收每个传入的未标记或标记的数据包，并用其表示的LSP的相应标签将其封装，然后将其转发给LSP的相邻LSR。每个FEC映射到标签转发条目，以便可以用一个或多个标签条目封装分组；这称为标签堆栈。
The packet traverses the LSP. Upon reaching the egress LER, further action will be taken to handle the packet, depending on the type of packet received. MPLS Architecture [RFC3031] details the functionality of ingress and egress LERs.
数据包通过LSP。在到达出口LER时，将根据接收到的数据包的类型采取进一步的操作来处理数据包。MPLS体系结构[RFC3031]详细说明了入口和出口LER的功能。
The MPLS-FTN-STD-MIB [RFC3814] describes the managed objects for mapping FEC to label bindings.
MPLS-FTN-STD-MIB[RFC3814]描述了用于将FEC映射到标签绑定的托管对象。
A router that performs MPLS forwarding is known as an LSR. An LSR receives a labeled packet and performs forwarding action based on the label received.
执行MPLS转发的路由器称为LSR。LSR接收带标签的分组并基于接收到的标签执行转发动作。
The LSR maintains a mapping of an incoming label and incoming interface to one or more outgoing labels and outgoing interfaces in its forwarding database. When a labeled packet is received, the LSR examines the topmost label in the label stack and then does a 'swap', 'push', or 'pop' operation based on the contents.
LSR维护传入标签和传入接口到其转发数据库中的一个或多个传出标签和传出接口的映射。当接收到带标签的数据包时，LSR检查标签堆栈中最上面的标签，然后根据内容执行“交换”、“推送”或“弹出”操作。
The MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for modeling an MPLS [RFC3031] LSR. The MPLS-LSR-STD-MIB [RFC3813] contains the managed objects to maintain mapping of in-segments to out-segments.
MPLS-LSR-STD-MIB[RFC3813]描述了用于建模MPLS[RFC3031]LSR的托管对象。MPLS-LSR-STD-MIB[RFC3813]包含用于维护in段到out段映射的托管对象。
The pseudowire (PW) MIB architecture provides a layered modular model into which any supported emulated service such as Frame Relay, ATM, Ethernet, Time-Division Multiplexing (TDM), and Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) can be connected to any supported Packet Switched Network (PSN) type. This MIB architecture is modeled based on PW3 architecture [RFC3985].
伪线（PW）MIB体系结构提供了一个分层模块化模型，其中任何受支持的模拟服务（如帧中继、ATM、以太网、时分复用（TDM）和同步光网络/同步数字体系（SONET/SDH））都可以连接到任何受支持的分组交换网络（PSN）类型。该MIB体系结构基于PW3体系结构[RFC3985]建模。
The emulated service layer, generic PW layer, and PSN Virtual Circuit (VC) layer constitute the different layers of the model. A combination of the MIB modules belonging to each layer provides the glue for mapping the emulated service onto the native PSN service. At least three MIB modules, each belonging to a different layer, are required to define a PW emulated service.
仿真服务层、通用PW层和PSN虚拟电路（VC）层构成了模型的不同层。属于每一层的MIB模块的组合提供了将模拟服务映射到本机PSN服务的粘合剂。定义PW模拟服务至少需要三个MIB模块，每个模块属于不同的层。
- The service-specific module is dependent on the emulated signal type and helps in modeling the emulated service layer.
- 特定于服务的模块取决于仿真信号类型，并有助于对仿真服务层进行建模。
The PW-ENET-STD-MIB [RFC5603] describes a model for managing Ethernet pseudowire services for transmission over a PSN. This MIB module is generic and common to all types of PSNs supported in the PWE3 Architecture [RFC3985], which describes the transport and encapsulation of L1 and L2 services over supported PSN types.
PW-ENET-STD-MIB[RFC5603]描述了一种用于管理以太网伪线服务的模型，以便通过PSN进行传输。该MIB模块是PWE3体系结构[RFC3985]中支持的所有类型PSN的通用模块，描述了支持的PSN类型上L1和L2服务的传输和封装。
In particular, the MIB module associates a port or specific VLANs on top of a physical Ethernet port or a virtual Ethernet interface (for the Virtual Private LAN Service (VPLS)) to a point-to-point PW. It is complementary to the PW-STD-MIB [RFC5601], which manages the generic PW parameters common to all services, including all supported PSN types.
具体而言，MIB模块将物理以太网端口或虚拟以太网接口（用于虚拟专用LAN服务（VPLS））上的端口或特定vlan与点到点PW相关联。它是对PW-STD-MIB[RFC5601]的补充，PW-STD-MIB[RFC5601]管理所有服务通用的PW参数，包括所有支持的PSN类型。
The PW-TDM-MIB [RFC5604] describes a model for managing TDM pseudowires, i.e., TDM data encapsulated for transmission over a PSN. The term "TDM" in this document is limited to the scope of Plesiochronous Digital Hierarchy (PDH). It is currently specified to carry any TDM signals in either Structure Agnostic Transport mode (E1, T1, E3, and T3) or Structure Aware Transport mode (E1, T1, and NxDS0) as defined in the PWE3 TDM Requirements document [RFC4197].
PW-TDM-MIB[RFC5604]描述了一种用于管理TDM伪线的模型，即封装用于通过PSN传输的TDM数据。本文件中的术语“TDM”仅限于准同步数字体系（PDH）的范围。按照PWE3 TDM需求文件[RFC4197]中的定义，目前规定以结构无关传输模式（E1、T1、E3和T3）或结构感知传输模式（E1、T1和NxDS0）传输任何TDM信号。
- The generic PW module configures general parameters of the PW that are common to all types of emulated services and PSN types.
- 通用PW模块配置PW的通用参数，这些参数对于所有类型的仿真服务和PSN类型都是通用的。
The PW-STD-MIB [RFC5601] defines a MIB module that can be used to manage PW services for transmission over a PSN [RFC3931] [RFC4447]. This MIB module provides generic management of PWs that is common to all types of PSN and PW services defined by the IETF PWE3 Working Group.
PW-STD-MIB[RFC5601]定义了一个MIB模块，可用于管理PW服务，以便通过PSN[RFC3931][RFC4447]进行传输。该MIB模块提供了对PWs的通用管理，这是IETF PWE3工作组定义的所有类型的PSN和PW服务所共有的。
- The PSN-specific module associates the PW with one or more "tunnels" that carry the service over the PSN. There is a different module for each type of PSN.
- PSN特定模块将PW与一个或多个通过PSN承载服务的“隧道”相关联。每种类型的PSN都有一个不同的模块。
The PW-MPLS-STD-MIB [RFC5602] describes a model for managing pseudowire services for transmission over different flavors of MPLS tunnels. The generic PW MIB module [RFC5601] defines the parameters global to the PW, regardless of the underlying PSN and emulated service. This document is applicable for PWs that use the MPLS PSN type in the PW-STD-MIB. Additionally, this document describes the MIB objects that define pseudowire association to the MPLS PSN that is not specific to the carried service.
PW-MPLS-STD-MIB[RFC5602]描述了一种管理伪线服务的模型，用于在不同类型的MPLS隧道上传输。通用PW MIB模块[RFC5601]定义PW的全局参数，而不考虑底层PSN和模拟服务。本文件适用于PW-STD-MIB中使用MPLS PSN类型的PW。此外，本文档还描述了MIB对象，这些对象定义了与MPLS PSN的伪线关联，该关联不是特定于所承载服务的。
Together, [RFC3811], [RFC3812], and [RFC3813] describe the modeling of an MPLS tunnel and a tunnel's underlying cross-connects. This MIB module supports MPLS Traffic Engineering (MPLS-TE) PSNs, non-TE MPLS PSNs (an outer tunnel created by the Label Distribution Protocol (LDP) or manually), and MPLS PW labels only (no outer tunnel).
[RFC3811]、[RFC3812]和[RFC3813]共同描述了MPLS隧道和隧道底层交叉连接的建模。此MIB模块仅支持MPLS流量工程（MPLS-TE）PSN、非TE MPLS PSN（由标签分发协议（LDP）或手动创建的外部隧道）和MPLS PW标签（无外部隧道）。
In MPLS traffic engineering, it's possible to specify explicit routes or choose routes based on QoS metrics in setting up a path such that some specific data can be routed around network hot spots. TE LSPs can be set up through a management plane or a control plane.
在MPLS流量工程中，在设置路径时，可以指定显式路由或基于QoS度量选择路由，以便在网络热点周围路由某些特定数据。TE LSP可以通过管理平面或控制平面进行设置。
The MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling MPLS [RFC3031]-based traffic engineering. This MIB module should be used in conjunction with the companion document [RFC3813] for MPLS-based traffic engineering configuration and management.
MPLS-TE-STD-MIB[RFC3812]描述了用于建模基于MPLS[RFC3031]的流量工程的托管对象。该MIB模块应与配套文件[RFC3813]一起用于基于MPLS的流量工程配置和管理。
The purpose of MPLS resiliency is to ensure minimal interruption to traffic when a failure occurs within the system or network.
MPLS弹性的目的是确保在系统或网络内发生故障时，流量中断最小。
Various components of MPLS resiliency solutions are as follows:
MPLS弹性解决方案的各个组成部分如下：
1) Graceful restart in LDP and RSVP-TE modules
1) LDP和RSVP-TE模块中的优雅重启
2) Make before break
2) 先做后休息
3) Protection switching for LSPs
3) lsp的保护切换
4) Fast reroute for LSPs
4) LSP的快速重路由
5) PW redundancy
5) PW冗余
The MIB modules below only support MIB-based management for MPLS resiliency.
下面的MIB模块仅支持基于MIB的MPLS弹性管理。
MPLS Fast Reroute (FRR) is a restoration network resiliency mechanism used in MPLS TE to redirect traffic onto the backup LSPs in tens of milliseconds in case of link or node failure across the LSP.
MPLS快速重路由（FRR）是MPLS TE中使用的一种恢复网络弹性机制，用于在LSP上发生链路或节点故障时，在数十毫秒内将流量重定向到备份LSP上。
The MPLS-FRR-GENERAL-STD-MIB [RFC6445] contains objects that apply to any MPLS LSR implementing MPLS TE fast-reroute functionality.
MPLS-FRR-GENERAL-STD-MIB[RFC6445]包含适用于任何实现MPLS TE快速重路由功能的MPLS LSR的对象。
The MPLS-FRR-ONE2ONE-STD-MIB [RFC6445] contains objects that apply to the one-to-one backup method.
MPLS-FRR-ONE2ONE-STD-MIB[RFC6445]包含适用于一对一备份方法的对象。
The MPLS-FRR-FACILITY-STD-MIB [RFC6445] contains objects that apply to the facility backup method.
MPLS-FRR-FACILITY-STD-MIB[RFC6445]包含应用于设施备份方法的对象。
Protection switching mechanisms have been designed to provide network resiliency for MPLS networks. Different types of protection switching mechanisms, such as 1:1, 1:N, and 1+1, have been designed.
保护交换机制旨在为MPLS网络提供网络弹性。设计了不同类型的保护切换机制，如1:1、1:N和1+1。
MPLS manages LSP and pseudowire faults through the use of LSP ping
[RFC4379], Virtual Circuit Connectivity Verification (VCCV)
[RFC5085], Bidirectional Forwarding Detection (BFD) for LSPs
[RFC5884], and BFD for VCCV [RFC5885] tools.
MPLS manages LSP and pseudowire faults through the use of LSP ping
[RFC4379], Virtual Circuit Connectivity Verification (VCCV)
[RFC5085], Bidirectional Forwarding Detection (BFD) for LSPs
[RFC5884], and BFD for VCCV [RFC5885] tools.
MPLS currently focuses on in and/or out packet counters, errored packets, and discontinuity time.
MPLS目前主要关注入和/或出数据包计数器、错误数据包和中断时间。
Some of the MPLS and pseudowire performance tables used for performance management are given below.
下面给出了用于性能管理的一些MPLS和伪线性能表。
The mplsTunnelPerfTable [RFC3812] provides several counters (e.g., packets forwarded, packets dropped because of errors) to measure the performance of the MPLS tunnels.
mplsTunnelPerfTable[RFC3812]提供几个计数器（例如，转发的数据包、由于错误而丢弃的数据包）来测量MPLS隧道的性能。
The mplsInterfacePerfTable [RFC3813] provides performance information (incoming and outgoing labels in use, and lookup failures) on a per-interface basis.
mplsInterfacePerfTable[RFC3813]提供每个接口的性能信息（使用中的传入和传出标签，以及查找失败）。
The mplsInSegmentPerfTable [RFC3813] contains statistical information (total packets received by the in-segment, total errored packets received, total packets discarded, discontinuity time) for incoming MPLS segments to an LSR.
mplsInSegmentPerfTable[RFC3813]包含LSR的传入MPLS段的统计信息（段内接收的总数据包、接收的总错误数据包、丢弃的总数据包、中断时间）。
The mplsOutSegmentPerfTable [RFC3813] contains statistical information (total packets received, total errored packets received, total packets discarded, discontinuity time) for outgoing MPLS segments from an LSR.
mplsOutSegmentPerfTable[RFC3813]包含来自LSR的传出MPLS段的统计信息（接收的数据包总数、接收的错误数据包总数、丢弃的数据包总数、中断时间）。
The mplsFTNPerfTable [RFC3814] contains performance information for the specified interface and an FTN entry mapped to this interface.
mplsFTNPerfTable[RFC3814]包含指定接口的性能信息和映射到此接口的FTN条目。
The mplsLdpEntityStatsTable [RFC3815] and mplsLdpSessionStatsTable [RFC3815] contain statistical information (session attempts, errored packets, notifications) about an LDP entity.
MPLSLDEntityStatsTable[RFC3815]和mplsLdpSessionStatsTable[RFC3815]包含关于LDP实体的统计信息（会话尝试、错误数据包、通知）。
The pwPerfCurrentTable [RFC5601], pwPerfIntervalTable [RFC5601], and pwPerf1DayIntervalTable [RFC5601] provide pseudowire performance information (in and/or out packets) based on time (current interval, preconfigured specific interval, 1-day interval).
pwPerfCurrentTable[RFC5601]、pwPerfIntervalTable[RFC5601]和pwPerf1DayIntervalTable[RFC5601]基于时间（当前间隔、预配置的特定间隔、1天间隔）提供伪线性能信息（输入和/或输出数据包）。
The pwEnetStatsTable [RFC5603] contains statistical counters specific for Ethernet PW.
pwEnetStatsTable[RFC5603]包含以太网PW专用的统计计数器。
The pwTDMPerfCurrentTable [RFC5604], pwTDMPerfIntervalTable [RFC5604], and pwTDMPerf1DayIntervalTable [RFC5604] contain statistical information accumulated per 15-minute, 24-hour, and 1-day periods, respectively.
pwTDMPerfCurrentTable[RFC5604]、pwTDMPerfIntervalTable[RFC5604]和pwTDMPerf1DayIntervalTable[RFC5604]分别包含每15分钟、24小时和1天期间累积的统计信息。
The gmplsTunnelErrorTable [RFC4802] and gmplsTunnelReversePerfTable [RFC4802] provide information about performance, errored packets, and in/out packet counters.
gmplsTunnelErrorTable[RFC4802]和GMPLSTunnelReverSeperTable[RFC4802]提供有关性能、错误数据包和输入/输出数据包计数器的信息。
This section provides an overview of the relationship between the MPLS MIB modules for managing MPLS networks. More details of these relationships are given below.
本节概述了用于管理MPLS网络的MPLS MIB模块之间的关系。下面给出了这些关系的更多细节。
[RFC4221] mainly focuses on MPLS MIB module interdependencies. This section also highlights GMPLS and PW MIB module interdependencies.
[RFC4221]主要关注MPLS MIB模块的相互依赖性。本节还强调了GMPLS和PW MIB模块的相互依赖性。
The relationship "A --> B" means that A depends on B and that MIB module A uses an object, object identifier, or Textual Convention defined in MIB module B, or that MIB module A contains a pointer (index or RowPointer) to an object in MIB module B.
关系“A-->B”表示A依赖于B，MIB模块A使用MIB模块B中定义的对象、对象标识符或文本约定，或者MIB模块A包含指向MIB模块B中对象的指针（索引或行指针）。
+-------> MPLS-TC-STD-MIB <-----------------------------------------+
^ ^ ^
| | |
| MPLS-LSR-STD-MIB <--------------------------------+ |
| ^ |
| | |
+<----------------------- MPLS-LDP-STD-MIB ---------------->+ |
^ ^ ^ |
| | | |
+<-- MPLS-LDP-GENERIC-STD-MIB ------>+ | |
^ | |
| | |
+<------ MPLS-FTN-STD-MIB --------------------------------->+ |
^ | ^ |
| V | |
+<------------- MPLS-TE-STD-MIB -->+----------------------->+ |
^ GMPLS-TC-STD-MIB ------------>+
| ^ ^
| | |
+---+ +<-- GMPLS-LABEL-STD-MIB -->+
^ ^ ^ ^ ^
| | | | |
+----> PW-TC-STD-MIB | GMPLS-LSR-STD-MIB --------------->+
^ | ^ ^ ^
| | | | |
| IANA-PWE3-MIB | | | IANA-GMPLS-TC-MIB |
| ^ | | | ^ |
| | | | | | |
| | +<--- GMPLS-TE-STD-MIB ------------->+
| | ^ ^
+<--- PW-STD-MIB <------+ | |
^ ^ | |
| | | |
+<--- PW-ENET-STD-MIB ->+ | |
^ ^ | |
| | | |
| | | |
+<---------------- PW-MPLS-STD-MIB--------------------------------->+
+-------> MPLS-TC-STD-MIB <-----------------------------------------+
^ ^ ^
| | |
| MPLS-LSR-STD-MIB <--------------------------------+ |
| ^ |
| | |
+<----------------------- MPLS-LDP-STD-MIB ---------------->+ |
^ ^ ^ |
| | | |
+<-- MPLS-LDP-GENERIC-STD-MIB ------>+ | |
^ | |
| | |
+<------ MPLS-FTN-STD-MIB --------------------------------->+ |
^ | ^ |
| V | |
+<------------- MPLS-TE-STD-MIB -->+----------------------->+ |
^ GMPLS-TC-STD-MIB ------------>+
| ^ ^
| | |
+---+ +<-- GMPLS-LABEL-STD-MIB -->+
^ ^ ^ ^ ^
| | | | |
+----> PW-TC-STD-MIB | GMPLS-LSR-STD-MIB --------------->+
^ | ^ ^ ^
| | | | |
| IANA-PWE3-MIB | | | IANA-GMPLS-TC-MIB |
| ^ | | | ^ |
| | | | | | |
| | +<--- GMPLS-TE-STD-MIB ------------->+
| | ^ ^
+<--- PW-STD-MIB <------+ | |
^ ^ | |
| | | |
+<--- PW-ENET-STD-MIB ->+ | |
^ ^ | |
| | | |
| | | |
+<---------------- PW-MPLS-STD-MIB--------------------------------->+
Thus,
因此
- All the MPLS MIB modules depend on the MPLS-TC-STD-MIB.
- 所有MPLS MIB模块都依赖于MPLS-TC-STD-MIB。
- All the GMPLS MIB modules depend on the GMPLS-TC-STD-MIB.
- 所有GMPLS MIB模块都依赖于GMPLS-TC-STD-MIB。
- All the PW MIB modules depend on the PW-TC-STD-MIB.
- 所有PW MIB模块均依赖于PW-TC-STD-MIB。
- The MPLS-LDP-STD-MIB, MPLS-TE-STD-MIB, MPLS-FTN-STD-MIB, GMPLS-LSR-STD-MIB, and PW-MPLS-STD-MIB contain references to objects in the MPLS-LSR-STD-MIB.
- MPLS-LDP-STD-MIB、MPLS-TE-STD-MIB、MPLS-FTN-STD-MIB、GMPLS-LSR-STD-MIB和PW-MPLS-STD-MIB包含对MPLS-LSR-STD-MIB中对象的引用。
- The MPLS-LDP-GENERIC-STD-MIB contains references to objects in the MPLS-LDP-STD-MIB.
- MPLS-LDP-GENERIC-STD-MIB包含对MPLS-LDP-STD-MIB中对象的引用。
- The MPLS-FTN-STD-MIB, PW-MPLS-STD-MIB, and GMPLS-TE-STD-MIB contain references to objects in the MPLS-TE-STD-MIB.
- MPLS-FTN-STD-MIB、PW-MPLS-STD-MIB和GMPLS-TE-STD-MIB包含对MPLS-TE-STD-MIB中对象的引用。
- The PW-MPLS-STD-MIB and PW-ENET-STD-MIB contain references to objects in the PW-STD-MIB.
- PW-MPLS-STD-MIB和PW-ENET-STD-MIB包含对PW-STD-MIB中对象的引用。
- The PW-STD-MIB contains references to objects in the IANA-PWE3-MIB.
- PW-STD-MIB包含对IANA-PWE3-MIB中对象的引用。
- The GMPLS-TE-STD-MIB contains references to objects in the IANA-GMPLS-TC-MIB.
- GMPLS-TE-STD-MIB包含对IANA-GMPLS-TC-MIB中对象的引用。
- The GMPLS-LSR-STD-MIB contains references to objects in the GMPLS-LABEL-STD-MIB.
- GMPLS-LSR-STD-MIB包含对GMPLS-LABEL-STD-MIB中对象的引用。
Note that there is a Textual Convention (MplsIndexType) defined in the MPLS-LSR-STD-MIB that is imported by the MPLS-LDP-STD-MIB.
请注意，MPLS-LDP-STD-MIB导入的MPLS-LSR-STD-MIB中定义了一个文本约定（MplsIndexType）。
With the exception of the MPLS-TC-STD-MIB, all the MPLS MIB modules have dependencies on the Interfaces MIB (also called the Interfaces Group MIB or the IF-MIB) [RFC2863]. The MPLS-FTN-STD-MIB references IP-capable interfaces on which received traffic is to be classified using indexes in the Interfaces Table (ifTable) of the IF-MIB [RFC2863]. The other MPLS MIB modules reference MPLS-capable interfaces in the ifTable.
除MPLS-TC-STD-MIB外，所有MPLS MIB模块都依赖于接口MIB（也称为接口组MIB或IF-MIB）[RFC2863]。MPLS-FTN-STD-MIB引用支持IP的接口，使用IF-MIB[RFC2863]的接口表（ifTable）中的索引对接收到的流量进行分类。其他MPLS MIB模块引用ifTable中支持MPLS的接口。
The IF-MIB [RFC2863] defines generic managed objects for managing interfaces. The MPLS MIB modules contain media-specific extensions to the Interfaces Group for managing MPLS interfaces.
IF-MIB[RFC2863]定义了用于管理接口的通用托管对象。MPLS MIB模块包含接口组的媒体特定扩展，用于管理MPLS接口。
The MPLS MIB modules assume the interpretation of the Interfaces Group to be in accordance with [RFC2863], which states that the ifTable contains information on the managed resource's interfaces and that each sub-layer below the internetwork layer of a network interface is considered an interface. Thus, the MPLS interface is represented as an entry in the ifTable.
MPLS MIB模块假定接口组的解释符合[RFC2863]，该解释说明ifTable包含关于受管资源接口的信息，并且网络接口的网络层下的每个子层都被视为接口。因此，MPLS接口被表示为ifTable中的条目。
The interrelation of entries in the ifTable is defined by the Interface Stack Group defined in [RFC2863].
ifTable中条目的相互关系由[RFC2863]中定义的接口堆栈组定义。
The MPLS MIB modules have dependencies on the TE-LINK-STD-MIB for maintaining traffic engineering information.
MPLS MIB模块依赖于TE-LINK-STD-MIB来维护流量工程信息。
The MPLS MIB modules depend on the Constrained Shortest Path First (CSPF) component to obtain the path required for an MPLS tunnel to reach the end point of the tunnel, and on the BFD component to verify data-plane failures of LSPs and PWs.
MPLS MIB模块依赖约束最短路径优先（CSPF）组件获得MPLS隧道到达隧道终点所需的路径，并依赖BFD组件验证LSP和PWs的数据平面故障。
Finally, all of the MIB modules import standard Textual Conventions such as integers, strings, timestamps, etc., from the MIB modules in which they are defined.
最后，所有MIB模块都从定义它们的MIB模块导入标准文本约定，如整数、字符串、时间戳等。
This section highlights gaps in existing MPLS MIB modules in order to determine extensions or additional MIB modules that are required to support MPLS-TP in MPLS networks.
本节重点介绍现有MPLS MIB模块中的差距，以确定在MPLS网络中支持MPLS-TP所需的扩展或附加MIB模块。
[RFC5951] specifies the requirements for the management of equipment used in networks supporting MPLS-TP. It also details the essential network management capabilities for operating networks consisting of MPLS-TP equipment.
[RFC5951]规定了支持MPLS-TP的网络中所用设备的管理要求。它还详细说明了由MPLS-TP设备组成的操作网络的基本网络管理功能。
[RFC5950] provides the network management framework for MPLS-TP. The document explains how network elements and networks that support MPLS-TP can be managed using solutions that satisfy the requirements defined in [RFC5951]. The relationship between MPLS-TP management and OAM is described in the MPLS-TP framework document [RFC5950].
[RFC5950]提供MPLS-TP的网络管理框架。本文档解释了如何使用满足[RFC5951]中定义的要求的解决方案来管理支持MPLS-TP的网元和网络。MPLS-TP管理和OAM之间的关系在MPLS-TP框架文档[RFC5950]中进行了描述。
The MPLS MIB documents MPLS-TE-STD-MIB [RFC3812], PW-STD-MIB [RFC5601], and MPLS-LSR-STD-MIB [RFC3813], and their associated MIB modules, are reused for MPLS-based transport network management.
MPLS MIB文档MPLS-TE-STD-MIB[RFC3812]、PW-STD-MIB[RFC5601]和MPLS-LSR-STD-MIB[RFC3813]及其相关MIB模块可用于基于MPLS的传输网络管理。
Fault management and performance management form key parts of the OAM function. MPLS-TP OAM is described in [RFC6371].
故障管理和性能管理构成了OAM功能的关键部分。[RFC6371]中描述了MPLS-TP OAM。
An MPLS-TP tunnel can be operated over IP and/or ITU-T Carrier Code (ICC) environments. The points below capture the gaps in existing MPLS MIB modules for managing MPLS-TP networks.
MPLS-TP隧道可以在IP和/或ITU-T载波代码（ICC）环境中运行。下面几点说明了用于管理MPLS-TP网络的现有MPLS MIB模块中存在的差距。
- IP-based environment
- 基于IP的环境
i. The MPLS-TE-STD-MIB [RFC3812] does not support the tunnel Ingress/Egress identifier based on Global_ID and Node_ID [RFC6370].
i. MPLS-TE-STD-MIB[RFC3812]不支持基于全局_ID和节点_ID[RFC6370]的隧道入口/出口标识符。
ii. The MPLS-TE-STD-MIB [RFC3812] does not support co-routed/associated bidirectional tunnel configurations.
二,。MPLS-TE-STD-MIB[RFC3812]不支持共路由/相关双向隧道配置。
- ICC-based environment
- 基于ICC的环境
i. The MPLS-TE-STD-MIB [RFC3812] does not support the tunnel LSR identifier based on ICC.
i. MPLS-TE-STD-MIB[RFC3812]不支持基于ICC的隧道LSR标识符。
- New MIB definitions may be created for Global_Node_ID and/or ICC configurations.
- 可以为全局节点ID和/或ICC配置创建新的MIB定义。
- The MPLS-LSR-STD-MIB [RFC3813] module may be enhanced to identify the next hop based on a Media Access Control (MAC) address for environments that do not use IP. The mplsOutSegmentTable may be extended to hold the MAC address.
- MPLS-LSR-STD-MIB[RFC3813]模块可以增强，以基于不使用IP的环境的媒体访问控制（MAC）地址来识别下一跳。mplsOutSegmentTable可以扩展以保存MAC地址。
- The MPLS-TE-STD-MIB [RFC3812] and MPLS-LSR-STD-MIB may be enhanced to provide static and signaling MIB module extensions for co-routed/associated bidirectional LSPs.
- MPLS-TE-STD-MIB[RFC3812]和MPLS-LSR-STD-MIB可以增强，以便为共路由/相关联的双向LSP提供静态和信令MIB模块扩展。
MPLS-TP pseudowire can be operated over IP and/or ICC environments. The points below capture the gaps in existing PW MIB modules for managing MPLS-TP networks.
MPLS-TP伪线可以在IP和/或ICC环境上运行。下面几点说明了用于管理MPLS-TP网络的现有PW MIB模块中存在的差距。
[RFC6370] specifies an initial set of identifiers to be used in MPLS-TP. These identifiers were chosen to be compatible with existing MPLS, GMPLS, and PW definitions.
[RFC6370]指定要在MPLS-TP中使用的初始标识符集。选择这些标识符是为了与现有的MPLS、GMPLS和PW定义兼容。
- IP-based environment
- 基于IP的环境
i. The PW-STD-MIB [RFC5601] does not support the PW end point identifier based on Global_ID and Node_ID.
i. PW-STD-MIB[RFC5601]不支持基于全局_ID和节点_ID的PW端点标识符。
ii. The PW-MPLS-STD-MIB [RFC5602] does not support operation over co-routed/associated bidirectional tunnels.
二,。PW-MPLS-STD-MIB[RFC5602]不支持通过共同路由/相关双向隧道进行操作。
- ICC-based environment
- 基于ICC的环境
i. The PW-STD-MIB [RFC5601] does not support the PW end point identifier based on ICC.
i. PW-STD-MIB[RFC5601]不支持基于ICC的PW端点标识符。
- The PW-MPLS-STD-MIB [RFC5602] can be enhanced to operate over co-routed/associated bidirectional tunnels.
- PW-MPLS-STD-MIB[RFC5602]可以增强，以便在共同路由/相关双向隧道上运行。
The existing MPLS MIB modules do not support MPLS-TP sections.
现有MPLS MIB模块不支持MPLS-TP部分。
Link-specific and/or path/segment-specific sections can be supported by enhancing the IF-MIB [RFC2863], MPLS-TE-STD-MIB [RFC3812], and PW-STD-MIB [RFC5601] MIB modules.
通过增强IF-MIB[RFC2863]、MPLS-TE-STD-MIB[RFC3812]和PW-STD-MIB[RFC5601]MIB模块，可以支持特定于链路和/或特定于路径/段的部分。
MPLS manages LSP and pseudowire faults through LSP ping [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884], and BFD for VCCV [RFC5885] tools.
MPLS通过LSP ping[RFC4379]、VCCV[RFC5085]、LSP的BFD[RFC5884]和VCCV的BFD[RFC5885]工具管理LSP和伪线故障。
The MPLS MIB modules do not support the following MPLS-TP OAM functions:
MPLS MIB模块不支持以下MPLS-TP OAM功能：
o Continuity Check and Connectivity Verification
o 连续性检查和连通性验证
o Remote Defect Indication
o 远程缺陷指示
o Alarm Reporting
o 报警报告
o Lock Reporting
o 锁定报告
o Lock Instruct
o 锁定指令
o Client Failure Indication
o 客户端故障指示
o Packet Loss Measurement
o 丢包测量
o Packet Delay Measurement
o 包延迟测量
New MIB module for BFD can be created to address all the gaps mentioned in Section 5.4.1.
可以为BFD创建新的MIB模块，以解决第5.4.1节中提到的所有差距。
An important aspect that MPLS-TP technology provides is protection switching. In general, the mechanism of protection switching can be described as the substitution of a protection or standby facility for a working or primary facility.
MPLS-TP技术提供的一个重要方面是保护交换。一般来说，保护切换机制可描述为用保护或备用设施替代工作或主设施。
The MPLS MIB modules do not provide support for protection switching and recovery in the following three topologies: linear, ring, and mesh.
MPLS MIB模块不支持以下三种拓扑中的保护切换和恢复：线性、环形和网状。
New MIB modules can be created to address all the gaps mentioned in Section 5.5.1.
可以创建新的MIB模块，以解决第5.5.1节中提到的所有差距。
As per [RFC6370], an LSR requires identification of the node itself and of its interfaces. An interface is the attachment point to a server layer MPLS-TP section or MPLS-TP tunnel.
根据[RFC6370]，LSR需要识别节点本身及其接口。接口是服务器层MPLS-TP节或MPLS-TP隧道的连接点。
The MPLS MIB modules do not provide support for configuring the interfaces within the context of an operator.
MPLS MIB模块不支持在操作员上下文中配置接口。
New MIB definitions can be created to address the gaps mentioned in Section 5.6.1.
可以创建新的MIB定义，以解决第5.6.1节中提到的差距。
This section highlights new MIB modules that have been identified as being required for MPLS-TP. This section also provides an overview of the purpose of each MIB module within the MIB documents, what it can be used for, and how it relates to the other MIB modules.
本节重点介绍MPLS-TP所需的新MIB模块。本节还概述了MIB文档中每个MIB模块的用途、它的用途以及它与其他MIB模块的关系。
Note that each new MIB module (apart from Textual Conventions modules) will contain one or more Compliance Statements to indicate which objects must be supported in what manner to claim a specific level of compliance. Additional text, either in the documents that define the MIB modules or in separate Applicability Statements, will define which Compliance Statements need to be conformed to in order to provide specific MPLS-TP functionality. This document does not set any requirements in that respect, although some recommendations are included in the sections that follow.
请注意，每个新的MIB模块（文本约定模块除外）将包含一个或多个符合性声明，以指示必须以何种方式支持哪些对象以声明特定的符合性级别。在定义MIB模块的文件中或在单独的适用性声明中的其他文本将定义需要遵守哪些合规性声明，以提供特定的MPLS-TP功能。本文件未在这方面规定任何要求，尽管以下章节中包含了一些建议。
Four new MIB modules are identified as follows:
四个新的MIB模块标识如下：
- Textual Conventions for MPLS-TP
- MPLS-TP的文本约定
- Identifiers for MPLS-TP
- MPLS-TP的标识符
- LSR MIB Extensions for MPLS-TP
- 用于MPLS-TP的LSR MIB扩展
- Tunnel Extensions for MPLS-TP
- MPLS-TP的隧道扩展
Note that the MIB modules mentioned here are applicable for MPLS operations as well.
注意，这里提到的MIB模块也适用于MPLS操作。
A new MIB module needs to be written that will define Textual Conventions [RFC2579] for MPLS-TP-related MIB modules. These conventions allow multiple MIB modules to use the same syntax and format to provide a concept that is shared between the MIB modules.
需要编写一个新的MIB模块，为MPLS TP相关的MIB模块定义文本约定[RFC2579]。这些约定允许多个MIB模块使用相同的语法和格式来提供在MIB模块之间共享的概念。
For example, a Maintenance Entity Group End Point (MEP) identifier is used to identify a maintenance entity group end point within MPLS-TP networks. The Textual Convention representing the MEP identifier should be defined in a new Textual Convention MIB module.
例如，维护实体组端点（MEP）标识符用于标识MPLS-TP网络内的维护实体组端点。表示MEP标识符的文本约定应该在新的文本约定MIB模块中定义。
All new extensions related to MPLS-TP are defined in the MIB module and will be referenced by other MIB modules to support MPLS-TP.
所有与MPLS-TP相关的新扩展都在MIB模块中定义，并将被其他MIB模块引用以支持MPLS-TP。
New identifiers describe managed objects that are used to model common MPLS-TP identifiers [RFC6370].
新标识符描述用于对公共MPLS-TP标识符建模的托管对象[RFC6370]。
The MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS LSR. This puts it at the heart of the management architecture for MPLS.
MPLS-LSR-STD-MIB描述了用于建模MPLS LSR的托管对象。这使它成为MPLS管理体系结构的核心。
In the case of MPLS-TP, the MPLS-LSR-STD-MIB is extended to support MPLS-TP LSPs, which are co-routed or associated bidirectionally. This extended MIB is also applicable for modeling MPLS-TP tunnels.
在MPLS-TP的情况下，MPLS-LSR-STD-MIB被扩展以支持MPLS-TP lsp，其被共同路由或双向关联。该扩展MIB也适用于MPLS-TP隧道的建模。
The MPLS-TE-STD-MIB describes managed objects that are used to model and manage MPLS-TE tunnels.
MPLS-TE-STD-MIB描述了用于建模和管理MPLS-TE隧道的托管对象。
MPLS-TP tunnels are very similar to MPLS-TE tunnels but are co-routed or associated bidirectionally.
MPLS-TP隧道与MPLS-TE隧道非常相似，但它们是共同路由或双向关联的。
The MPLS-TE-STD-MIB must be extended to support the MPLS-TP-specific attributes for the tunnel.
必须扩展MPLS-TE-STD-MIB以支持隧道的MPLS TP特定属性。
This section provides an overview of pseudowire-extension MIB modules used to meet MPLS-based transport network requirements.
本节概述了用于满足基于MPLS的传输网络要求的伪线扩展MIB模块。
Three new MIB modules are identified as follows:
三个新的MIB模块标识如下：
- Pseudowire Textual Conventions for MPLS-TP
- MPLS-TP的伪连线文本约定
- Pseudowire Extensions for MPLS-TP
- MPLS-TP的伪线扩展
- Pseudowire MPLS Extensions for MPLS-TP
- MPLS-TP的伪线MPLS扩展
The PW-TC-STD-MIB defines Textual Conventions used for PW technology and for PWE3 MIB modules. A new Textual Convention MIB module is required to define textual definitions for MPLS-TP-specific pseudowire attributes.
PW-TC-STD-MIB定义了用于PW技术和PWE3 MIB模块的文本约定。需要一个新的文本约定MIB模块来定义MPLS TP特定伪线属性的文本定义。
The PW-STD-MIB describes managed objects for the modeling of pseudowire edge-to-edge services carried over a general PSN. This MIB module is extended to support MPLS-TP-specific attributes related to pseudowires.
PW-STD-MIB描述了用于建模通过通用PSN承载的伪线边缘到边缘服务的托管对象。此MIB模块扩展为支持与伪线相关的MPLS TP特定属性。
The PW-MPLS-STD-MIB defines the managed objects for pseudowire operations over MPLS LSRs. This MIB module supports
PW-MPLS-STD-MIB定义了MPLS LSR上伪线操作的托管对象。此MIB模块支持
- manually and dynamically signaled PWs
- 手动和动态信号PWs
- point-to-point connections
- 点对点连接
- the use of any emulated service
- 任何模拟服务的使用
- outer tunnels provisioned using MPLS-TE
- 使用MPLS-TE配置的外部隧道
- PWs with no outer tunnel
- 无外部隧道的PWs
An extended MIB module would define additional objects, extending the PW-MPLS-STD-MIB by continuing to support configurations that operate with or without an outer tunnel.
扩展MIB模块将定义其他对象，通过继续支持使用或不使用外部隧道的配置来扩展PW-MPLS-STD-MIB。
This section provides an overview of Operations, Administration, and Maintenance (OAM) MIB modules for MPLS LSPs and pseudowires.
本节概述了MPLS LSP和伪线的操作、管理和维护（OAM）MIB模块。
Two new MIB modules are identified as follows:
两个新的MIB模块标识如下：
- BFD MIB module
- BFD MIB模块
- OAM MIB module
- OAM MIB模块
The BFD-STD-MIB defines managed objects for performing BFD operations in IP networks. This MIB module is modeled to support the BFD protocol [RFC5880].
BFD-STD-MIB定义用于在IP网络中执行BFD操作的托管对象。该MIB模块建模为支持BFD协议[RFC5880]。
A new MIB module needs to be written that will be an extension to BFD-STD-MIB managed objects to support BFD operations on MPLS LSPs and PWs.
需要编写一个新的MIB模块，作为BFD-STD-MIB管理对象的扩展，以支持MPLS LSP和PWs上的BFD操作。
A new MIB module needs to be written that will define managed objects for OAM maintenance identifiers, i.e., Maintenance Entity Group (MEG) identifiers, the MEP, and the Maintenance Entity Group Intermediate Point (MIP). Maintenance points are uniquely associated with a MEG. Within the context of a MEG, MEPs and MIPs must be uniquely identified.
需要编写一个新的MIB模块，该模块将定义OAM维护标识符的托管对象，即维护实体组（MEG）标识符、MEP和维护实体组中间点（MIP）。维护点与MEG唯一关联。在MEG的上下文中，MEP和MIP必须唯一标识。
This section provides an overview of protection switching and recovery MIB modules for MPLS LSPs and pseudowires.
本节概述了MPLS LSP和伪线的保护交换和恢复MIB模块。
Three new MIB modules are identified as follows:
三个新的MIB模块标识如下：
- Linear Protection Switching MIB module
- 线性保护开关MIB模块
- Ring Protection Switching MIB module
- 环保护交换MIB模块
- Mesh Protection Switching MIB module
- 网状保护交换MIB模块
A new MIB module needs to be written that will define managed objects for linear protection switching of MPLS LSPs and pseudowires.
需要编写一个新的MIB模块，该模块将为MPLS LSP和伪线的线性保护切换定义托管对象。
A new MIB module needs to be written that will define managed objects for ring protection switching of MPLS LSPs and pseudowires.
需要编写一个新的MIB模块，该模块将为MPLS LSP和伪线的环保护切换定义托管对象。
A new MIB module needs to be written that will define managed objects for mesh protection switching of MPLS LSPs and pseudowires.
需要编写一个新的MIB模块，该模块将为MPLS LSP和伪线的网状保护切换定义托管对象。
This document applies only to scenarios where MIB modules are used to manage the MPLS-TP network. It is not the intention of this document to provide instructions or advice to implementers of management systems, management agents, or managed entities. It is, however, useful to make some observations about how the MIB modules described above might be used to manage MPLS systems, if SNMP is used in the management interface.
本文档仅适用于使用MIB模块管理MPLS-TP网络的场景。本文件的目的不是向管理系统的实施者、管理代理或被管理实体提供指示或建议。但是，如果在管理接口中使用SNMP，则对上述MIB模块如何用于管理MPLS系统进行一些观察是有用的。
For MPLS-specific management options, refer to [RFC4221] Section 12 ("Management Options").
有关MPLS特定的管理选项，请参阅[RFC4221]第12节（“管理选项”）。
This document describes the interrelationships amongst the different MIB modules relevant to MPLS-TP management and as such does not have any security implications in and of itself.
本文档描述了与MPLS-TP管理相关的不同MIB模块之间的相互关系，因此其本身不具有任何安全含义。
Each IETF MIB document that specifies MIB objects for MPLS-TP must provide a proper Security Considerations section that explains the security aspects of those objects.
为MPLS-TP指定MIB对象的每个IETF MIB文档必须提供一个适当的安全注意事项部分，解释这些对象的安全方面。
The attention of readers is particularly drawn to the security implications of making MIB objects available for create or write access through an access protocol such as SNMP. SNMPv1 by itself is an insecure environment. Even if the network itself is made secure (for example, by using IPsec), there is no control over who on the secure network is allowed to access the objects in the MIB module. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model STD 62, RFC 3414 [RFC3414], and the View-based Access Control Model STD 62, RFC 3415 [RFC3415], is recommended.
读者特别注意通过访问协议（如SNMP）使MIB对象可用于创建或写入访问的安全含义。SNMPv1本身就是一个不安全的环境。即使网络本身是安全的（例如，通过使用IPsec），也无法控制安全网络上的谁可以访问MIB模块中的对象。建议实施者考虑SNMPv3框架提供的安全特性。具体而言，建议使用基于用户的安全模型STD 62、RFC 3414[RFC3414]和基于视图的访问控制模型STD 62、RFC 3415[RFC3415]。
It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of each MIB module is properly configured to give access to only those objects, and to those principals (users) that have legitimate rights to access them.
然后，客户/用户有责任确保对每个MIB模块的实例进行访问的SNMP实体正确配置为仅对这些对象以及具有合法访问权限的主体（用户）进行访问。
This document has identified areas where additional MIB modules are necessary for MPLS-TP. The new MIB modules recommended by this document will require OID assignments from IANA. However, this document makes no specific request for IANA action.
本文件确定了MPLS-TP需要额外MIB模块的领域。本文档推荐的新MIB模块需要IANA分配OID。然而，本文件并未对IANA行动提出具体要求。
The authors would like to thank Eric Gray, Thomas Nadeau, Benjamin Niven-Jenkins, Saravanan Narasimhan, Joel Halpern, David Harrington, and Stephen Farrell for their valuable comments.
作者要感谢Eric Gray、Thomas Nadeau、Benjamin Niven Jenkins、Saravanan Narasimhan、Joel Halpern、David Harrington和Stephen Farrell的宝贵评论。
This document also benefited from review by participants in ITU-T Study Group 15.
本文件还得益于ITU-T第15研究组与会者的审查。
Adrian Farrel Old Dog Consulting UK
阿德里安·法雷尔英国老狗咨询公司
EMail: adrian@olddog.co.uk
EMail: adrian@olddog.co.uk
Scott Mansfield Ericsson 300 Holger Way San Jose, CA 95134 US
斯科特·曼斯菲尔德·爱立信加利福尼亚州圣何塞霍尔格大道300号，美国95134
Phone: +1 724 931 9316
EMail: scott.mansfield@ericsson.com
Phone: +1 724 931 9316
EMail: scott.mansfield@ericsson.com
Jeong-dong Ryoo ETRI 161 Gajeong, Yuseong Daejeon, 305-700 South Korea
Jeong dong Ryoo ETRI 161 Gajeong，玉成大田，305-700韩国
Phone: +82 42 860 5384
EMail: ryoo@etri.re.kr
Phone: +82 42 860 5384
EMail: ryoo@etri.re.kr
A S Kiran Koushik Cisco Systems Inc.
A S Kiran Koushik思科系统公司。
EMail: kkoushik@cisco.com
EMail: kkoushik@cisco.com
A. Karmakar Cisco Systems Inc.
A.卡玛卡尔思科系统公司。
EMail: akarmaka@cisco.com
EMail: akarmaka@cisco.com
Sam Aldrin Huawei Technologies Co. 2330 Central Expressway Santa Clara, CA 95051 USA
山姆·奥尔德林华为技术有限公司，美国加利福尼亚州圣克拉拉中央高速公路2330号，邮编95051
EMail: aldrin.ietf@gmail.com
EMail: aldrin.ietf@gmail.com
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management", RFC 3811, June 2004.
[RFC3811]Nadeau，T.，Ed.，和J.Cucchiara，Ed.，“多协议标签交换（MPLS）管理的文本约定（TC）定义”，RFC 3811，2004年6月。
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)", RFC 3812, June 2004.
[RFC3812]Srinivasan，C.，Viswanathan，A.，和T.Nadeau，“多协议标签交换（MPLS）流量工程（TE）管理信息库（MIB）”，RFC 3812，2004年6月。
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)", RFC 3813, June 2004.
[RFC3813]Srinivasan，C.，Viswanathan，A.，和T.Nadeau，“多协议标签交换（MPLS）标签交换路由器（LSR）管理信息库（MIB）”，RFC 38132004年6月。
[RFC3814] Nadeau, T., Srinivasan, C., and A. Viswanathan, "Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)", RFC 3814, June 2004.
[RFC3814]Nadeau，T.，Srinivasan，C.，和A.Viswanathan，“多协议标签交换（MPLS）转发等价类到下一跳标签转发条目（FEC到NHLFE）管理信息库（MIB）”，RFC 3814，2004年6月。
[RFC3815] Cucchiara, J., Sjostrand, H., and J. Luciani, "Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)", RFC 3815, June 2004.
[RFC3815]Cucchiara，J.，Sjostrand，H.，和J.Luciani，“多协议标签交换（MPLS）管理对象的定义，标签分发协议（LDP）”，RFC 3815，2004年6月。
[RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic Engineering Link Management Information Base", RFC 4220, November 2005.
[RFC4220]Dubuc，M.，Nadeau，T.，和J.Lang，“交通工程链路管理信息库”，RFC 4220，2005年11月。
[RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol Label Switching (MPLS) Management Overview", RFC 4221, November 2005.
[RFC4221]Nadeau，T.，Srinivasan，C.，和A.Farrel，“多协议标签交换（MPLS）管理概述”，RFC 42212005年11月。
[RFC4801] Nadeau, T., Ed., and A. Farrel, Ed., "Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management", RFC 4801, February 2007.
[RFC4801]Nadeau，T.，Ed.，和A.Farrel，Ed.“通用多协议标签交换（GMPLS）管理的文本约定定义”，RFC 4801，2007年2月。
[RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base", RFC 4802, February 2007.
[RFC4802]Nadeau，T.，Ed.，和A.Farrel，Ed.，“通用多协议标签交换（GMPLS）流量工程管理信息库”，RFC 4802，2007年2月。
[RFC4803] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base", RFC 4803, February 2007.
[RFC4803]Nadeau，T.，Ed.，和A.Farrel，Ed.，“通用多协议标签交换（GMPLS）标签交换路由器（LSR）管理信息库”，RFC 4803，2007年2月。
[RFC5542] Nadeau, T., Ed., Zelig, D., Ed., and O. Nicklass, Ed., "Definitions of Textual Conventions for Pseudowire (PW) Management", RFC 5542, May 2009.
[RFC5542]Nadeau，T.，Ed.，Zelig，D.，Ed.，和O.Nicklass，Ed.，“伪线（PW）管理文本约定的定义”，RFC 5542，2009年5月。
[RFC5601] Nadeau, T., Ed., and D. Zelig, Ed., "Pseudowire (PW) Management Information Base (MIB)", RFC 5601, July 2009.
[RFC5601]Nadeau，T.，Ed.，和D.Zelig，Ed.，“伪线（PW）管理信息库（MIB）”，RFC 56012009年7月。
[RFC5602] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over MPLS PSN Management Information Base (MIB)", RFC 5602, July 2009.
[RFC5602]Zelig，D.，Ed.，和T.Nadeau，Ed.，“MPLS PSN管理信息库（MIB）上的伪线（PW）”，RFC 5602，2009年7月。
[RFC5603] Zelig, D., Ed., and T. Nadeau, Ed., "Ethernet Pseudowire (PW) Management Information Base (MIB)", RFC 5603, July 2009.
[RFC5603]Zelig，D.，Ed.，和T.Nadeau，Ed.，“以太网伪线（PW）管理信息库（MIB）”，RFC 5603，2009年7月。
[RFC5604] Nicklass, O., "Managed Objects for Time Division Multiplexing (TDM) over Packet Switched Networks (PSNs)", RFC 5604, July 2009.
[RFC5604]Nicklass，O.“分组交换网络（PSN）上时分复用（TDM）的受管对象”，RFC 5604，2009年7月。
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, January 2001.
[RFC3031]Rosen，E.，Viswanathan，A.，和R.Callon，“多协议标签交换体系结构”，RFC 30312001年1月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3414]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）版本3的基于用户的安全模型（USM）”，STD 62，RFC 3414，2002年12月。
[RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3415, December 2002.
[RFC3415]Wijnen，B.，Presuhn，R.，和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，STD 62，RFC 3415，2002年12月。
[RFC3931] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed., "Layer Two Tunneling Protocol - Version 3 (L2TPv3)", RFC 3931, March 2005.
[RFC3931]Lau，J.，Ed.，Townsley，M.，Ed.，和I.Goyret，Ed.，“第二层隧道协议-版本3（L2TPv3）”，RFC 39312005年3月。
[RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label Switching (GMPLS) Architecture", RFC 3945, October 2004.
[RFC3945]Mannie，E.，Ed.“通用多协议标签交换（GMPLS）体系结构”，RFC 39452004年10月。
[RFC3985] Bryant, S., Ed., and P. Pate, Ed., "Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture", RFC 3985, March 2005.
[RFC3985]Bryant，S.，Ed.，和P.Pate，Ed.，“伪线仿真边到边（PWE3）架构”，RFC 39852005年3月。
[RFC4197] Riegel, M., Ed., "Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching Networks", RFC 4197, October 2005.
[RFC4197]Riegel，M.，Ed.“分组交换网络上时分多路复用（TDM）电路的边到边仿真要求”，RFC 4197，2005年10月。
[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月。
[RFC4378] Allan, D., Ed., and T. Nadeau, Ed., "A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM)", RFC 4378, February 2006.
[RFC4378]Allan，D.，Ed.，和T.Nadeau，Ed.，“多协议标签交换（MPLS）操作和管理（OAM）框架”，RFC 4378，2006年2月。
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures", RFC 4379, February 2006.
[RFC4379]Kompella，K.和G.Swallow，“检测多协议标签交换（MPLS）数据平面故障”，RFC 4379，2006年2月。
[RFC4447] Martini, L., Ed., Rosen, E., El-Aawar, N., Smith, T., and G. Heron, "Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)", RFC 4447, April 2006.
[RFC4447]Martini，L.，Ed.，Rosen，E.，El Aawar，N.，Smith，T.，和G.Heron，“使用标签分发协议（LDP）的伪线设置和维护”，RFC 4447，2006年4月。
[RFC5085] Nadeau, T., Ed., and C. Pignataro, Ed., "Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires", RFC 5085, December 2007.
[RFC5085]Nadeau，T.，Ed.，和C.Pignataro，Ed.，“伪线虚拟电路连接验证（VCCV）：伪线的控制通道”，RFC 5085，2007年12月。
[RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS Transport Profile", RFC 5654, September 2009.
[RFC5654]Niven Jenkins，B.，Ed.，Brungard，D.，Ed.，Betts，M.，Ed.，Sprecher，N.，和S.Ueno，“MPLS传输配置文件的要求”，RFC 56542009年9月。
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD)", RFC 5880, June 2010.
[RFC5880]Katz，D.和D.Ward，“双向转发检测（BFD）”，RFC 58802010年6月。
[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, "Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)", RFC 5884, June 2010.
[RFC5884]Aggarwal，R.，Kompella，K.，Nadeau，T.，和G.Swallow，“MPLS标签交换路径（LSP）的双向转发检测（BFD）”，RFC 58842010年6月。
[RFC5885] Nadeau, T., Ed., and C. Pignataro, Ed., "Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)", RFC 5885, June 2010.
[RFC5885]Nadeau，T.，Ed.，和C.Pignataro，Ed.，“用于伪线虚拟电路连接验证（VCCV）的双向转发检测（BFD）”，RFC 58852010年6月。
[RFC5950] Mansfield, S., Ed., Gray, E., Ed., and K. Lam, Ed., "Network Management Framework for MPLS-based Transport Networks", RFC 5950, September 2010.
[RFC5950]Mansfield，S.，Ed.，Gray，E.，Ed.，和K.Lam，Ed.，“基于MPLS的传输网络的网络管理框架”，RFC 59502010年9月。
[RFC5951] Lam, K., Mansfield, S., and E. Gray, "Network Management Requirements for MPLS-based Transport Networks", RFC 5951, September 2010.
[RFC5951]Lam，K.，Mansfield，S.，和E.Gray，“基于MPLS的传输网络的网络管理要求”，RFC 59512010年9月。
[RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport Profile (MPLS-TP) Identifiers", RFC 6370, September 2011.
[RFC6370]Bocci，M.，Swallow，G.和E.Gray，“MPLS传输配置文件（MPLS-TP）标识符”，RFC 63702011年9月。
[RFC6371] Busi, I., Ed., and D. Allan, Ed., "Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks", RFC 6371, September 2011.
[RFC6371]Busi，I.，Ed.和D.Allan，Ed.“基于MPLS的传输网络的操作、管理和维护框架”，RFC 63712011年9月。
[RFC6445] Nadeau, T., Ed., Koushik, A., Ed., and R. Cetin, Ed., "Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base for Fast Reroute", RFC 6445, November 2011.
[RFC6445]Nadeau，T.，Ed.，Koushik，A.，Ed.，和R.Cetin，Ed.，“用于快速重路由的多协议标签交换（MPLS）流量工程管理信息库”，RFC 64452011年11月。
Authors' Addresses
作者地址
Daniel King (editor) Old Dog Consulting UK
丹尼尔·金（编辑）英国老狗咨询公司
EMail: daniel@olddog.co.uk
EMail: daniel@olddog.co.uk
Venkatesan Mahalingam (editor) Aricent India
文卡泰桑·马哈林根（编辑）印度
EMail: venkat.mahalingams@gmail.com
EMail: venkat.mahalingams@gmail.com