Network Working Group T. Nadeau
Request for Comments: 4221 Cisco Systems, Inc.
Category: Informational C. Srinivasan
Bloomberg L.P.
A. Farrel
Old Dog Consulting
November 2005
Network Working Group T. Nadeau
Request for Comments: 4221 Cisco Systems, Inc.
Category: Informational C. Srinivasan
Bloomberg L.P.
A. Farrel
Old Dog Consulting
November 2005
Multiprotocol Label Switching (MPLS) Management Overview
多协议标签交换（MPLS）管理概述
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
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模块在单独的文档中定义，这些文档侧重于它们描述的模块的特定职责领域。
This document describes the management architecture for MPLS and indicates the interrelationships between the different MIB modules used for MPLS network management.
本文档描述了MPLS的管理体系结构，并指出了用于MPLS网络管理的不同MIB模块之间的相互关系。
Table of Contents
目录
1. Introduction ....................................................3
2. Terminology .....................................................3
3. The SNMP Management Framework ...................................3
4. An Introduction to the MPLS Working Group MIB Modules ...........4
4.1. Structure of the MPLS MIB OID Tree .........................5
4.2. MPLS-TC-STD-MIB ............................................5
4.3. MPLS-LSR-STD-MIB ...........................................5
4.4. MPLS-LDP-STD-MIB ...........................................6
4.5. MPLS-LDP-GENERIC-STD-MIB ...................................6
4.6. MPLS-LDP-ATM-STD-MIB .......................................6
4.7. MPLS-LDP-FRAME-RELAY-STD-MIB ...............................7
4.8. MPLS-TE-STD-MIB ............................................7
4.9. MPLS-FTN-STD-MIB ...........................................7
1. Introduction ....................................................3
2. Terminology .....................................................3
3. The SNMP Management Framework ...................................3
4. An Introduction to the MPLS Working Group MIB Modules ...........4
4.1. Structure of the MPLS MIB OID Tree .........................5
4.2. MPLS-TC-STD-MIB ............................................5
4.3. MPLS-LSR-STD-MIB ...........................................5
4.4. MPLS-LDP-STD-MIB ...........................................6
4.5. MPLS-LDP-GENERIC-STD-MIB ...................................6
4.6. MPLS-LDP-ATM-STD-MIB .......................................6
4.7. MPLS-LDP-FRAME-RELAY-STD-MIB ...............................7
4.8. MPLS-TE-STD-MIB ............................................7
4.9. MPLS-FTN-STD-MIB ...........................................7
4.10. TE-LINK-STD-MIB ...........................................7
4.11. MIB Module Interdependencies ..............................8
4.12. Dependencies on External MIB Modules ......................9
5. Tables, Scalars, and Notifications in MPLS-LSR-STD-MIB .........10
5.1. Tables ....................................................10
5.2. Scalars ...................................................10
5.3. Indexing ..................................................11
5.4. Notifications .............................................12
5.5. Dependencies between MIB Module Tables ....................12
6. Tables, Scalars, and Notifications in the LDP MIB ..............13
6.1. MIB Modules ...............................................13
6.2. Tables ....................................................14
6.3. Scalars ...................................................15
6.4. Notifications .............................................15
6.5. Dependencies between MIB Module Tables ....................15
7. Tables, Scalars, and Notifications in MPLS-TE-STD-MIB ..........16
7.1. Tables ....................................................16
7.2. Scalars ...................................................17
7.3. Notifications .............................................18
7.4. Dependencies between MIB Module Tables ....................18
8. Tables, Scalars, and Notifications in MPLS-FTN-STD-MIB .........18
8.1. Tables ....................................................18
8.2. Scalars ...................................................19
8.3. Notifications .............................................19
8.4. Dependencies between MIB Module Tables ....................19
9. Tables and Objects in TE-LINK-STD-MIB ..........................19
9.1. Tables ....................................................19
9.2. Scalars ...................................................20
9.3. Notifications .............................................20
9.4. Dependencies between MIB Module Tables ....................20
10. Table Dependencies between MPLS MIB Modules ...................21
11. A Note on Interfaces ..........................................21
11.1. MPLS Tunnels as Interfaces ...............................21
11.2. Application of the Interfaces Group to TE Links ..........22
11.3. References to Interface MIB Objects from MPLS MIB
Modules ..................................................23
12. Management Options ............................................24
13. Related IETF MIB Modules ......................................25
13.1. PWE3 Working Group MIB Modules ...........................26
13.2. PPVPN Working Group MIB Modules ..........................26
13.2.1. PPVPN-MPLS-VPN-STD-MIB ............................26
13.3. CCAMP Working Group MIB Modules ..........................26
14. Traffic Engineering Working Group TE MIB ......................27
14.1. Choosing between TE MIB Modules ..........................27
15. Security Considerations .......................................28
16. Acknowledgements ..............................................28
17. Normative References ..........................................29
18. Informative References ........................................30
4.10. TE-LINK-STD-MIB ...........................................7
4.11. MIB Module Interdependencies ..............................8
4.12. Dependencies on External MIB Modules ......................9
5. Tables, Scalars, and Notifications in MPLS-LSR-STD-MIB .........10
5.1. Tables ....................................................10
5.2. Scalars ...................................................10
5.3. Indexing ..................................................11
5.4. Notifications .............................................12
5.5. Dependencies between MIB Module Tables ....................12
6. Tables, Scalars, and Notifications in the LDP MIB ..............13
6.1. MIB Modules ...............................................13
6.2. Tables ....................................................14
6.3. Scalars ...................................................15
6.4. Notifications .............................................15
6.5. Dependencies between MIB Module Tables ....................15
7. Tables, Scalars, and Notifications in MPLS-TE-STD-MIB ..........16
7.1. Tables ....................................................16
7.2. Scalars ...................................................17
7.3. Notifications .............................................18
7.4. Dependencies between MIB Module Tables ....................18
8. Tables, Scalars, and Notifications in MPLS-FTN-STD-MIB .........18
8.1. Tables ....................................................18
8.2. Scalars ...................................................19
8.3. Notifications .............................................19
8.4. Dependencies between MIB Module Tables ....................19
9. Tables and Objects in TE-LINK-STD-MIB ..........................19
9.1. Tables ....................................................19
9.2. Scalars ...................................................20
9.3. Notifications .............................................20
9.4. Dependencies between MIB Module Tables ....................20
10. Table Dependencies between MPLS MIB Modules ...................21
11. A Note on Interfaces ..........................................21
11.1. MPLS Tunnels as Interfaces ...............................21
11.2. Application of the Interfaces Group to TE Links ..........22
11.3. References to Interface MIB Objects from MPLS MIB
Modules ..................................................23
12. Management Options ............................................24
13. Related IETF MIB Modules ......................................25
13.1. PWE3 Working Group MIB Modules ...........................26
13.2. PPVPN Working Group MIB Modules ..........................26
13.2.1. PPVPN-MPLS-VPN-STD-MIB ............................26
13.3. CCAMP Working Group MIB Modules ..........................26
14. Traffic Engineering Working Group TE MIB ......................27
14.1. Choosing between TE MIB Modules ..........................27
15. Security Considerations .......................................28
16. Acknowledgements ..............................................28
17. Normative References ..........................................29
18. Informative References ........................................30
This document describes the Management Architecture for Multi-Protocol Label Switching (MPLS) [RFC3031]. In particular, it describes how the managed objects defined in various MPLS-related Management Information Base (MIB) documents model different aspects of MPLS. Furthermore, this document explains the interactions and dependencies between each of these MIB modules.
本文档描述了多协议标签交换（MPLS）[RFC3031]的管理体系结构。特别是，它描述了在各种与MPLS相关的管理信息库（MIB）文档中定义的托管对象如何对MPLS的不同方面进行建模。此外，本文档还解释了每个MIB模块之间的交互和依赖关系。
For additional information, this document also includes a brief note on MIB modules produced by the Pseudo Wire Emulation Edge to Edge (PWE3), Provider Provisioned Virtual Private Network (PPVPN), Common Control and Measurement Plane (CCAMP), and Internet Traffic Engineering (TEWG) working groups.
关于其他信息，本文件还包括关于伪线仿真边到边（PWE3）、提供商提供的虚拟专用网络（PPVPN）、公共控制和测量平面（CCAMP）和互联网流量工程（TEWG）工作组生产的MIB模块的简要说明。
The document begins with a brief outline of the SNMP framework. This is not intended to be a complete reference on SNMP, but is provided to give context to the rest of the document and to indicate reference material for readers that need to know more about SNMP.
本文档首先简要介绍SNMP框架。这并不是关于SNMP的完整参考，而是为了给文档的其余部分提供上下文，并为需要更多了解SNMP的读者提供参考资料。
This document does not propose any additions to the MPLS MIB framework, nor define any standards for the Internet community. It is an informational document. In all cases, the reader is advised to turn to the document that defines the MIB module in question for further information.
本文档不建议对MPLS MIB框架进行任何添加，也不为互联网社区定义任何标准。这是一份信息性文件。在所有情况下，建议读者查阅定义相关MIB模块的文档以获取更多信息。
Comments should be made directly to the MPLS mailing list at mpls@uu.net.
应直接向MPLS邮件列表提出意见，地址为mpls@uu.net.
This document uses terminology from the MPLS architecture document
[RFC3031] and the following MPLS related MIB modules: MPLS TC MIB
[TCMIB], MPLS LSR MIB [LSRMIB], MPLS TE MIB [TEMIB], MPLS LDP MIB
[LDPMIB], MPLS FTN MIB [FTNMIB], TE LINK MIB [TELMIB], and PPVPN MPLS
VPN MIB [VPNMIB].
This document uses terminology from the MPLS architecture document
[RFC3031] and the following MPLS related MIB modules: MPLS TC MIB
[TCMIB], MPLS LSR MIB [LSRMIB], MPLS TE MIB [TEMIB], MPLS LDP MIB
[LDPMIB], MPLS FTN MIB [FTNMIB], TE LINK MIB [TELMIB], and PPVPN MPLS
VPN MIB [VPNMIB].
Throughout this document hyphenated MIB names (such as MPLS-TE-STD-MIB) should be taken to refer to specific MIB modules. Non-hyphenated MIB names (such as MPLS LDP MIB) indicate MIB documents.
在本文档中，应使用连字符的MIB名称（如MPLS-TE-STD-MIB）来表示特定的MIB模块。非连字符MIB名称（如MPLS LDP MIB）表示MIB文档。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
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). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This document specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本文件规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
This section addresses the MIB documents produced by the MPLS working group, namely MPLS TC MIB, MPLS LSR MIB, MPLS TE MIB, MPLS LDP MIB, MPLS FTN MIB, and TE LINK MIB. The rest of this section briefly describes the following:
本节介绍MPLS工作组生成的MIB文档，即MPLS TC MIB、MPLS LSR MIB、MPLS TE MIB、MPLS LDP MIB、MPLS FTN MIB和TE LINK MIB。本节其余部分简要介绍以下内容：
- the MPLS Object Identifier (OID) tree structure and the position of different MPLS related MIB modules on this tree;
- MPLS对象标识符（OID）树结构以及与MPLS相关的不同MIB模块在此树上的位置；
- the purpose of each of the MIB modules within the MIB documents, what it can be used for, and how it relates to the other MIB modules.
- MIB文档中每个MIB模块的用途、可用于什么以及它与其他MIB模块的关系。
Note that each MIB document contains one or more compliance statements for the modules and objects that it defines. Therefore, the support for the different MIB modules and objects is beyond the scope of this document, although some recommendations are included in the sections that follow.
请注意，每个MIB文档都包含一个或多个其定义的模块和对象的符合性声明。因此，对不同MIB模块和对象的支持超出了本文档的范围，尽管以下章节中包含了一些建议。
The MPLS MIB OID tree has the following structure.
MPLS MIB OID树具有以下结构。
transmission -- RFC 2578 [RFC2578]
|
+- mplsStdMIB -- MPLS-TC-STD-MIB
| |
| +- mplsTCStdMIB -- MPLS-TC-STD-MIB
| |
| +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB
| |
| +- mplsTeStdMIB -- MPLS-TE-STD-MIB
| |
| +- mplsLdpStdMIB -- MPLS-LDP-STD-MIB
| |
| +- mplsLdpAtmStdMIB -- MPLS-LDP-ATM-STD-MIB
| |
| +- mplsLdpFrameRelayStdMIB -- MPLS-LDP-FRAME-RELAY-STD-MIB
| |
| +- mplsLdpGenericStdMIB -- MPLS-LDP-GENERIC-STD-MIB
| |
| +- mplsFTNStdMIB -- MPLS-FTN-STD-MIB
|
+- teLinkStdMIB -- TE-LINK-STD-MIB
transmission -- RFC 2578 [RFC2578]
|
+- mplsStdMIB -- MPLS-TC-STD-MIB
| |
| +- mplsTCStdMIB -- MPLS-TC-STD-MIB
| |
| +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB
| |
| +- mplsTeStdMIB -- MPLS-TE-STD-MIB
| |
| +- mplsLdpStdMIB -- MPLS-LDP-STD-MIB
| |
| +- mplsLdpAtmStdMIB -- MPLS-LDP-ATM-STD-MIB
| |
| +- mplsLdpFrameRelayStdMIB -- MPLS-LDP-FRAME-RELAY-STD-MIB
| |
| +- mplsLdpGenericStdMIB -- MPLS-LDP-GENERIC-STD-MIB
| |
| +- mplsFTNStdMIB -- MPLS-FTN-STD-MIB
|
+- teLinkStdMIB -- TE-LINK-STD-MIB
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文档中找到。
MPLS-TC-STD-MIB defines textual conventions [RFC2579] that may be common to MPLS-related MIB modules. These conventions allow multiple MIB modules to use the same syntax and format for a concept that is shared between the MIB modules.
MPLS-TC-STD-MIB定义了与MPLS相关的MIB模块通用的文本约定[RFC2579]。这些约定允许多个MIB模块对MIB模块之间共享的概念使用相同的语法和格式。
For example, labels are a central part of MPLS and need to be presented in many of the MIB modules. The textual convention for representing an MPLS label is defined in MPLS-TC-STD-MIB.
例如，标签是MPLS的核心部分，需要在许多MIB模块中显示。表示MPLS标签的文本约定在MPLS-TC-STD-MIB中定义。
All of the other MPLS MIB modules import textual conventions from this MIB module.
所有其他MPLS MIB模块都从该MIB模块导入文本约定。
MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS Label Switching Router (LSR). This puts it at the heart of the management architecture for MPLS.
MPLS-LSR-STD-MIB描述了用于建模MPLS标签交换路由器（LSR）的托管对象。这使它成为MPLS管理体系结构的核心。
This MIB module is used to model and manage the basic label switching behavior of an MPLS LSR. It represents the label forwarding information base (LFIB) of the LSR and provides a view of the LSPs that are being switched by the LSR in question.
该MIB模块用于建模和管理MPLS LSR的基本标签交换行为。它表示LSR的标签转发信息库（LFIB），并提供由相关LSR切换的LSP的视图。
Since basic MPLS label switching is common to all MPLS applications, this MIB module is referenced by many of the other MPLS MIB modules.
由于基本的MPLS标签交换对于所有MPLS应用程序都是通用的，所以许多其他MPLS MIB模块都引用了此MIB模块。
In general, MPLS-LSR-STD-MIB provides a model of incoming labels on MPLS-enabled interfaces being mapped to outgoing labels on MPLS-enabled interfaces via a conceptual object called an MPLS cross-connect. MPLS cross-connect entries and their properties are represented in MPLS-LSR-STD-MIB and are typically referenced by other MIB modules in order to refer to the underlying MPLS LSP.
一般来说，MPLS-LSR-STD-MIB提供了一个MPLS启用接口上的传入标签模型，该模型通过一个称为MPLS交叉连接的概念对象映射到MPLS启用接口上的传出标签。MPLS交叉连接条目及其属性在MPLS-LSR-STD-MIB中表示，通常由其他MIB模块引用，以引用底层MPLS LSP。
For example, MPLS-TE-STD-MIB models traffic-engineered tunnels. These tunnels map to one or more underlying MPLS LSPs. MPLS-TE-STD-MIB refers to the underlying LSPs by pointing to cross-connect entries in MPLS-LSR-STD-MIB.
例如，MPLS-TE-STD-MIB为流量工程隧道建模。这些隧道映射到一个或多个底层MPLS LSP。MPLS-TE-STD-MIB通过指向MPLS-LSR-STD-MIB中的交叉连接条目来引用底层LSP。
MPLS-LDP-STD-MIB describes managed objects used to model and manage the MPLS Label Distribution Protocol (LDP) [RFC3036]. LDP is one of the MPLS protocols used to distribute labels and establish LSPs.
MPLS-LDP-STD-MIB描述了用于建模和管理MPLS标签分发协议（LDP）[RFC3036]的托管对象。LDP是用于分发标签和建立LSP的MPLS协议之一。
This MIB module contains objects common to all LDP implementations. For an LDP implementation that provides standard MIB support, this MIB module provides the core set of objects that are needed, along with one or more of the other LDP MIB modules from the following sections.
此MIB模块包含所有LDP实现所共有的对象。对于提供标准MIB支持的LDP实现，此MIB模块提供所需的核心对象集，以及以下部分中的一个或多个其他LDP MIB模块。
This MIB module provides objects for managing the LDP Per Platform Label Space and is typically implemented along with the MPLS-LDP-STD-MIB module. This MIB Module contains tables for configuring MPLS Generic Label Ranges. Although the LDP Specification does not provide a way to configure Label Ranges for Generic Labels, the MIB module does provide a way to reserve a range of generic labels because the working group thought this was useful.
此MIB模块提供用于管理每个平台标签空间的LDP的对象，通常与MPLS-LDP-STD-MIB模块一起实现。此MIB模块包含用于配置MPLS通用标签范围的表。尽管LDP规范没有提供为通用标签配置标签范围的方法，但MIB模块确实提供了保留一系列通用标签的方法，因为工作组认为这很有用。
This MIB module is typically supported along with MPLS-LDP-STD-MIB by LDP implementations if LDP uses ATM as the Layer 2 medium. Tables in this MIB module allow for configuring LDP to use ATM.
如果LDP使用ATM作为第2层介质，则LDP实现通常支持此MIB模块和MPLS-LDP-STD-MIB。此MIB模块中的表允许配置LDP以使用ATM。
This MIB module is typically supported along with MPLS-LDP-STD-MIB by LDP implementations if LDP uses Frame Relay as the Layer 2 medium. Tables in this MIB module allow for configuration of LDP to use Frame Relay.
如果LDP使用帧中继作为第2层介质，则LDP实现通常支持此MIB模块以及MPLS-LDP-STD-MIB。此MIB模块中的表允许配置LDP以使用帧中继。
MPLS-TE-STD-MIB describes managed objects that are used to model and manage MPLS Traffic Engineered (TE) Tunnels.
MPLS-TE-STD-MIB描述了用于建模和管理MPLS流量工程（TE）隧道的托管对象。
This MIB module is based on a table that represents TE tunnels that either originate from, traverse via, or terminate on the LSR in question. The MIB module provides configuration and statistics objects needed for TE tunnels.
此MIB模块基于一个表，该表表示源自、穿过或终止于相关LSR的TE隧道。MIB模块提供TE隧道所需的配置和统计对象。
MPLS-FTN-STD-MIB describes managed objects that are used to model and manage the MPLS FEC-to-NHLFE (FTN) mappings that take place at an ingress Label Edge Router (LER).
MPLS-FTN-STD-MIB描述了用于建模和管理在入口标签边缘路由器（LER）上发生的MPLS FEC到NHLFE（FTN）映射的托管对象。
An LER is an LSR placed at the edge of an MPLS domain, and it passes traffic into and out of the MPLS domain. An ingress LER is responsible for classifying data and assigning it to a suitable LSP or tunnel.
LER是放置在MPLS域边缘的LSR，它将流量传入和传出MPLS域。入口LER负责对数据进行分类，并将其分配给合适的LSP或隧道。
This classification is done using Forwarding Equivalence Classes (FECs) that define the common attributes of data (usually packets) that will be treated in the same way. Once data has been classified, it can be handed off to an LSP or tunnel through the Next Hop Label Forwarding Entry (NHLFE).
这种分类是使用转发等价类（FEC）来完成的，FEC定义了将以相同方式处理的数据（通常是数据包）的公共属性。一旦数据被分类，它就可以通过下一跳标签转发条目（NHLFE）传递到LSP或隧道。
In the case of an IP-to-MPLS mapping, the FEC objects describe IP 6-tuples that represent source and destination address ranges, source and destination port ranges, the IPv4 Protocol field or IPv6 next-header field, and the DiffServ Code Point (DSCP).
在IP到MPLS映射的情况下，FEC对象描述表示源和目标地址范围、源和目标端口范围、IPv4协议字段或IPv6下一报头字段以及区分服务代码点（DSCP）的IP 6元组。
TE-LINK-STD-MIB describes managed objects that are used to model and manage TE links, including bundled links, in an MPLS network.
TE-LINK-STD-MIB描述用于在MPLS网络中建模和管理TE链路（包括捆绑链路）的托管对象。
The TE link feature is designed to aggregate one or more similar data channels or TE links between a pair of LSRs. A TE link is a sub-interface capable of carrying traffic-engineered MPLS traffic.
TE链路功能旨在聚合一对LSR之间的一个或多个类似数据信道或TE链路。TE链路是能够承载流量工程MPLS流量的子接口。
A bundled link is a sub-interface that bonds the traffic of a group of one or more TE links.
捆绑链路是将一组或多个TE链路的流量绑定在一起的子接口。
This section provides an overview of the relationship between the MPLS MIB modules described above. More details of these relationships are given below after the MIB modules have been discussed in more detail.
本节概述了上述MPLS MIB模块之间的关系。在对MIB模块进行了更详细的讨论之后，下面给出了这些关系的更多细节。
The arrows in the following diagram show a 'depends on' relationship. A relationship "MIB module A depends on MIB module B" means 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.
下图中的箭头显示了“依赖”关系。关系“MIB模块A依赖于MIB模块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-LDP-ATM-STD-MIB ---------->+ |
| | |
+<-- MPLS-LDP-FRAME-RELAY-STD-MIB -->+ |
| |
+<------- MPLS-TE-STD-MIB ------------------->+
| ^ |
| | |
+<------- MPLS-FTN-STD-MIB ------------------>+
+-------> MPLS-TC-STD-MIB
| ^
| |
| MPLS-LSR-STD-MIB <------------------+
| |
+<----------------------- MPLS-LDP-STD-MIB -->+
| ^ |
| | |
+<-- MPLS-LDP-GENERIC-STD-MIB ------>+ |
| | |
+<-- MPLS-LDP-ATM-STD-MIB ---------->+ |
| | |
+<-- MPLS-LDP-FRAME-RELAY-STD-MIB -->+ |
| |
+<------- MPLS-TE-STD-MIB ------------------->+
| ^ |
| | |
+<------- MPLS-FTN-STD-MIB ------------------>+
Thus:
因此：
- All the MPLS MIB modules depend on MPLS-TC-STD-MIB.
- 所有MPLS MIB模块都依赖于MPLS-TC-STD-MIB。
- MPLS-LDP-STD-MIB, MPLS-TE-STD-MIB, and MPLS-FTN-STD-MIB contain references to objects in MPLS-LSR-STD-MIB.
- MPLS-LDP-STD-MIB、MPLS-TE-STD-MIB和MPLS-FTN-STD-MIB包含对MPLS-LSR-STD-MIB中对象的引用。
- MPLS-LDP-GENERIC-STD-MIB, MPLS-LDP-ATM-STD-MIB, and MPLS-LDP-FRAME-RELAY-STD-MIB contain references to objects in MPLS-LDP-STD-MIB.
- MPLS-LDP-GENERIC-STD-MIB、MPLS-LDP-ATM-STD-MIB和MPLS-LDP-FRAME-RELAY-STD-MIB包含对MPLS-LDP-STD-MIB中对象的引用。
- MPLS-FTN-STD-MIB contains references to objects in MPLS-TE-STD-MIB.
- MPLS-FTN-STD-MIB包含对MPLS-TE-STD-MIB中对象的引用。
Note that there is a textual convention (MplsIndexType) defined in MPLS-LSR-STD-MIB that is imported by MPLS-LDP-STD-MIB.
请注意，MPLS-LSR-STD-MIB中定义了一个文本约定（MplsIndexType），该约定由MPLS-LDP-STD-MIB导入。
With the exception of MPLS-TC-STD-MIB, all the MPLS MIB modules have dependencies on the Interfaces MIB [RFC2863]. MPLS-FTN-STD-MIB references IP-capable interfaces on which received traffic is to be classified using indexes in the Interface Table (ifTable) of IF-MIB [RFC2863]. The other MPLS MIB modules reference MPLS-capable interfaces in ifTable.
除MPLS-TC-STD-MIB外，所有MPLS MIB模块都依赖于接口MIB[RFC2863]。MPLS-FTN-STD-MIB引用支持IP的接口，使用IF-MIB[RFC2863]接口表（ifTable）中的索引对接收到的通信量进行分类。其他MPLS MIB模块在ifTable中引用支持MPLS的接口。
The Interfaces Group of 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 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 ifTable.
MPLS MIB模块假定接口组的解释符合[RFC2863]，该解释说明ifTable包含受管资源接口的信息，并且网络接口的网络层下的每个子层都被视为接口。因此，MPLS接口在ifTable中表示为一个条目。
The interrelation of entries in ifTable is defined by the Interfaces Stack Group defined in [RFC2863].
ifTable中条目的相互关系由[RFC2863]中定义的接口堆栈组定义。
Additionally, MPLS-LDP-ATM-STD-MIB imports the textual convention AtmVpIdentifier from ATM-TC-MIB to represent an ATM virtual path identifier, whereas MPLS-LDP-FRAME-RELAY-STD-MIB imports the textual convention DLCI from FRAME-RELAY-DTE-MIB to represent a Data Link Channel identifier.
此外，MPLS-LDP-ATM-STD-MIB从ATM-TC-MIB导入文本约定AtmVpIdentifier以表示ATM虚拟路径标识符，而MPLS-LDP-FRAME-RELAY-STD-MIB从FRAME-RELAY-DTE-MIB导入文本约定DLCI以表示数据链路信道标识符。
MPLS-LDP-STD-MIB imports the textual conventions IndexInteger and IndexIntegerNextFree from [RFC3289], and MPLS-TE-STD-MIB imports IndexIntegerNextFree. IndexInteger provides a standard arbitrary index, whereas IndexIntegerNextFree is used by a management agent that needs to select an appropriate value for an arbitrary index.
MPLS-LDP-STD-MIB从[RFC3289]导入文本约定IndexInteger和IndexIntegerNextFree，MPLS-TE-STD-MIB导入IndexIntegerNextFree。IndexIntegrater提供标准的任意索引，而IndexIntegraterExtFree由需要为任意索引选择适当值的管理代理使用。
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. This is business as usual for a MIB module and is not discussed further in this document.
最后，所有MIB模块都从定义它们的MIB模块导入标准文本约定，如整数、字符串、时间戳等。这对于MIB模块来说是正常的，在本文档中不再进一步讨论。
MPLS-LSR-STD-MIB contains the following tables.
MPLS-LSR-STD-MIB包含以下表格。
- The interface configuration table (mplsInterfaceTable) is used for enabling MPLS on MPLS-capable interfaces.
- 接口配置表（mplsInterfaceTable）用于在支持MPLS的接口上启用MPLS。
- The in-segment (mplsInSegmentTable) and out-segment (mplsOutSegmentTable) tables are used to configure and monitor LSP segments carrying data into and out of the LSR, respectively.
- 段内（mplsInSegmentTable）和段外（MPLSOUTSEGENTTABLE）表分别用于配置和监视将数据携带到LSR和从LSR中运出的LSP段。
- The in-segment mapping table (mplsInSegmentMapTable) provides a look-up table that enables the discovery of an in-segment in mplsInSegmentTable from the known incoming interface and incoming label.
- 段内映射表（mplsInSegmentMapTable）提供了一个查找表，可以从已知的传入接口和传入标签中发现mplsInSegmentTable中的段内映射。
- The cross-connect table (mplsXCTable) is used to associate in and out segments in order to form a cross-connect (i.e., to represent an LSP transiting the LSR).
- 交叉连接表（mplsXCTable）用于关联输入和输出段，以形成交叉连接（即，表示通过LSR的LSP）。
- The label stack table (mplsLabelStackTable) allows the specification of multi-label stacks to be imposed on a given LSP at this LSR.
- 标签堆栈表（mplsLabelStackTable）允许在此LSR中对给定LSP施加多标签堆栈规范。
- The MPLS in-segment (mplsInSegmentPerfTable) and out-segment (mplsOutSegmentPerfTable) performance tables contain objects to measure the performance of LSPs.
- MPLS段内（mplsInSegmentPerfTable）和段外（mplsOutSegmentPerfTable）性能表包含用于测量LSP性能的对象。
- The MPLS interface performance table (mplsInterfacePerfTable) has objects to measure MPLS performance on a per-interface basis.
- MPLS接口性能表（mplsInterfacePerfTable）中有用于测量每个接口的MPLS性能的对象。
Where tables in the MIB module have arbitrary indexes, scalars are provided to supply the next available index. This applies to mplsInSegmentTable, mplsOutSegmentTable, mplsXCTable, and mplsLabelStackTable, but see the section on indexing, below.
当MIB模块中的表具有任意索引时，将提供标量以提供下一个可用索引。这适用于mplsInSegmentTable、mplsOutSegmentTable、mplsXCTable和mplsLabelStackTable，但请参见下面的索引部分。
mplsMaxLabelStackDepth defines the maximum size of a imposed label stack supported at this LSR (and not, as the description in MPLS-LSR-STD-MIB states, the maximum label stack depth supported by the LSR).
mplsMaxLabelStackDepth定义此LSR支持的强制标签堆栈的最大大小（而不是如MPLS-LSR-STD-MIB中所述，LSR支持的最大标签堆栈深度）。
mplsXCNotificationsEnable is used to enable and disable notifications from MPLS-LSR-STD-MIB.
mplsXCNotificationsEnable用于启用和禁用来自MPLS-LSR-STD-MIB的通知。
Note that the indexing used by the tables in MPLS-LSR-STD-MIB is unusual. A specific textual convention, MplsIndexType, is defined in the MIB module and is used as the type for indexes to mplsInSegmentTable, mplsOutSegmentTable, mplsXCTable, and mplsLabelStackTable. The textual convention is defined as an octet string of between one and twenty-four octets, inclusive.
请注意，MPLS-LSR-STD-MIB中的表所使用的索引是不寻常的。在MIB模块中定义了一个特定的文本约定MplsIndexType，它用作mplsInSegmentTable、mplsOutSegmentTable、mplsXCTable和mplsLabelStackTable的索引类型。文本约定定义为一个八位字节字符串，包含一到二十四个八位字节。
Although this convention can be used to map simple integers and so preserve the normal indexing techniques, it may also be used to encode more complex indexing rules that may be useful to implementations that subdivide their label spaces according to physical or implementation constraints (such as placing the responsibility for a subset of labels with a line card).
尽管此约定可用于映射简单整数，从而保留常规索引技术，但也可用于编码更复杂的索引规则，这些规则对于根据物理或实现约束细分标签空间的实现可能有用（例如，将标签子集的责任放在线路卡上）。
Note that it would be unusual, but not impossible, to make sophisticated use of these indexes in a write-access MIB since the 'next' index value would be hard to determine. Thus, non-simple values are likely only to be used in read-only MIBs in which the indexes are generated as a result of signaling protocol implementations or other configuration means. The formatting and interpretation of non-simple indexes is out of the scope of the MIB module definition and is expected to be part of the manageability statement for a particular device. When the formatting is not known by an agent, it should treat the index as a plain octet string containing an integer of between one and twenty-four octets.
请注意，在写访问MIB中复杂地使用这些索引是不寻常的，但并非不可能的，因为很难确定“下一个”索引值。因此，非简单值可能仅用于只读mib中，其中索引是作为信令协议实现或其他配置手段的结果而生成的。非简单索引的格式化和解释不在MIB模块定义的范围内，预计将成为特定设备的可管理性语句的一部分。如果代理不知道格式，则应将索引视为包含1到24个八位字节的整数的普通八位字节字符串。
As described in the previous section, scalars are provided to allow agents to discover a suitable value to use as an index when creating a new row in one of these tables. These scalars all use a second textual convention, MplsIndexNextType, also defined within MPLS-LSR-STD-MIB. This textual convention allows the 'null string', (that is, a string of length one octet with value 0x00). The null string is used to indicate that either write access is not supported or no more indexes are currently available.
如前一节所述，提供标量是为了允许代理在其中一个表中创建新行时发现一个合适的值用作索引。这些标量都使用第二个文本约定MplsIndexNextType，也在MPLS-LSR-STD-MIB中定义。此文本约定允许使用“空字符串”（即长度为一个八位字节、值为0x00的字符串）。空字符串用于指示不支持写访问或当前没有更多索引可用。
Note that the usage of the nextIndex scalars is such that at any time a scalar supplies a value that is currently unused as an index to the specific table. In order to avoid lacunae in the indexing of a table under normal usage, implementations are recommended to change the value in an nextIndex scalar only when the index is used (that is, when a row is created) and not when the nextIndex scalar is read. In a 'busy' table, this may result in row creation attempts failing and agents having to re-read the scalar before making a second row creation attempt. The desire to avoid this issue is in opposition to the desire to avoid lacunae.
请注意，nextIndex标量的使用使得标量随时提供当前未使用的值作为特定表的索引。为了避免在正常使用情况下索引表时出现漏洞，建议实现仅在使用索引时（即，创建行时）而不是在读取nextIndex标量时更改nextIndex标量中的值。在“繁忙”表中，这可能导致行创建尝试失败，并且代理必须在进行第二次行创建尝试之前重新读取标量。避免这一问题的愿望与避免空白的愿望相反。
MPLS-LSR-STD-MIB can issue two notifications (if notifications are enabled).
MPLS-LSR-STD-MIB可以发出两个通知（如果启用了通知）。
- mplsXCUp reports when a cross-connect becomes active.
- mplsXCUp报告交叉连接何时变为活动状态。
- mplsXCDown reports when a cross-connect becomes inactive.
- 当交叉连接变为非活动状态时，mplsXCDown会报告。
The tables in MPLS-LSR-STD-MIB are related as shown on the diagram below. The arrows indicate a reference from one table to another.
MPLS-LSR-STD-MIB中的表格如下图所示。箭头表示从一个表到另一个表的引用。
Note that the various MIB tables contain two instances of pointers to external tables that are not currently defined. Entries in an external Traffic Parameters Table (external_Traffic_Table) are pointed to using RowPointers from the mplsInSegmentTable (mplsInSegmentTrafficParamPtr) and from the mplsOutSegmentTable (mplsOutSegmentTrafficParamPtr) to allow representation of the traffic parameters for the MPLS segment. Alternatively, the pointers may indicate an entry in the Tunnel Resource Table (mplsTunnelResourceTable) in MPLS-TE-STD-MIB. Similarly, an external label table may be used to store label values if, for some reason, they are not stored in place within the LSR MIB tables. This might occur if extra per-label space information needs to be stored, and it paves the way for GMPLS where labels cannot always be stored in a 32-bit value. RowPointers are used from the mplsInSegmentTable (mplsInSegmentLabelPtr), the mplsOutSegmentTable (mplsOutSegmentTopLabelPtr), and from the mplsLabelStackTable (mplsLabelStackLabelPtr).
请注意，各种MIB表包含两个指向当前未定义的外部表的指针实例。外部流量参数表（external_Traffic_表）中的条目通过使用mplsInSegmentTable（mplsInSegmentTrafficParamPtr）和MPLSOUTTSEgmentTable（MPLSOUTTSEgmentTrafficParamptr）中的行指针指向，以允许表示MPLS段的流量参数。或者，指针可以指示MPLS-TE-STD-MIB中隧道资源表（mplsTunnelResourceTable）中的条目。类似地，如果出于某种原因，标签值没有存储在LSR MIB表中，则可以使用外部标签表来存储标签值。如果需要存储额外的每个标签空间信息，则可能会出现这种情况，这为GMPLS铺平了道路，因为在GMPLS中，标签不能始终以32位值存储。行指针从mplsInSegmentTable（mplsInSegmentLabelPtr）、MPLSOUTSEGENTTABLE（MPLSOUTSEGENTTOPLabelPtr）和mplsLabelStackTable（MPLSLABELSTACKELPTR）中使用。
mplsInterfacePerfTable
^
|
V
mplsInterfaceTable
^ ^
mplsInSegmentMapTable | | mplsLabelStackTable
| | | ^ |
| +----+ +----+ | |
| | | | |
| | external_Traffic_Table | | |
| | ^ ^ | | |
V | | | | | |
mplsInSegmentTable mplsOutSegmentTable |
| ^ ^ ^ ^ | |
| | | | | | V
+------+ | +----> mplsXCTable <----+ | +--+
| V V |
| mplsInSegmentPerfTable mplsOutSegmentPerfTable |
| |
+--------------> external_Label_Table <-------------+
mplsInterfacePerfTable
^
|
V
mplsInterfaceTable
^ ^
mplsInSegmentMapTable | | mplsLabelStackTable
| | | ^ |
| +----+ +----+ | |
| | | | |
| | external_Traffic_Table | | |
| | ^ ^ | | |
V | | | | | |
mplsInSegmentTable mplsOutSegmentTable |
| ^ ^ ^ ^ | |
| | | | | | V
+------+ | +----> mplsXCTable <----+ | +--+
| V V |
| mplsInSegmentPerfTable mplsOutSegmentPerfTable |
| |
+--------------> external_Label_Table <-------------+
The MIB document for LDP contains four MIB modules. This structure makes it easier for an implementation to select only those modules that are relevant to it. The MIB Modules are MPLS-LDP-STD-MIB, MPLS-LDP-GENERIC-STD-MIB, MPLS-LDP-ATM-STD-MIB, and MPLS-LDP-FRAME-RELAY-STD-MIB.
LDP的MIB文档包含四个MIB模块。这种结构使实现更容易只选择与之相关的模块。MIB模块为MPLS-LDP-STD-MIB、MPLS-LDP-GENERIC-STD-MIB、MPLS-LDP-ATM-STD-MIB和MPLS-LDP-FRAME-RELAY-STD-MIB。
MPLS-LDP-STD-MIB defines objects that are specific to LDP without any Layer 2 objects. MPLS-LDP-GENERIC-STD-MIB defines Layer 2 Per Platform Label Space objects for use with MPLS-LDP-STD-MIB and for use on Ethernet. MPLS-LDP-ATM-STD-MIB defines Layer 2 Asynchronous Transfer Mode (ATM) objects for use with MPLS-LDP-STD-MIB. MPLS-LDP-FRAME-RELAY-STD-MIB defines Layer 2 FRAME-RELAY objects for use with MPLS-LDP-STD-MIB.
MPLS-LDP-STD-MIB定义特定于LDP的对象，而不包含任何第2层对象。MPLS-LDP-GENERIC-STD-MIB定义每个平台的第2层标签空间对象，用于MPLS-LDP-STD-MIB和以太网。MPLS-LDP-ATM-STD-MIB定义了用于MPLS-LDP-STD-MIB的第2层异步传输模式（ATM）对象。MPLS-LDP-FRAME-RELAY-STD-MIB定义第2层帧中继对象，用于MPLS-LDP-STD-MIB。
The MPLS-LDP-STD-MIB module provides the core support and is typically supported along with at least one of the Layer 2 MIB modules.
MPLS-LDP-STD-MIB模块提供核心支持，通常与至少一个第2层MIB模块一起支持。
The tables in the LDP MIB for configuring the LDP behavior of an LSR are as follows.
LDP MIB中用于配置LSR的LDP行为的表如下所示。
- The LDP Entity Table (mplsLdpEntityTable) provides a way to configure the LSR for using LDP. There must be at least one LDP Entity for the LSR to support LDP. Each entry/row in this table represents a single LDP Entity.
- LDP实体表（MPLSLDEntityTable）提供了一种配置LSR以使用LDP的方法。LSR必须至少有一个LDP实体才能支持LDP。此表中的每个条目/行表示一个LDP实体。
- Several tables exist to help configure LDP's use of labels. These are spread through the MIB modules described in the previous section. They are: mplsLdpEntityGenLRTable, mplsLdpEntityAtmParmsTable and mplsLdpEntityAtmLRTable, mplsLdpEntityFrameRelayParmsTable and mplsLdpEntityFrLRTable. They are used to configure generic, ATM, and Frame Relay labels as their names suggest.
- 有几个表可以帮助配置LDP对标签的使用。这些信息通过上一节中描述的MIB模块传播。它们是：mplsldEntityGenlTable、mplsldEntityAtMparmStable和mplsldEntityAtmLrtable、mplsldEntityFrameRelayArmStable和mplsldEntityFrlTable。它们用于按照名称配置通用、ATM和帧中继标签。
- The LDP Peer Table (mplsLdpPeerTable) is a read-only table that contains information about LDP Peers known to LDP Entities.
- LDP对等表（mplsLdpPeerTable）是一个只读表，其中包含LDP实体已知的LDP对等信息。
- The LDP Hello Adjacencies Table (mplsLdpHelloAdjacencyTable) is a table of all adjacencies between all LDP Entities and all LDP Peers.
- LDP Hello邻接表（MPLSLDHelloadJacycytable）是一个包含所有LDP实体和所有LDP对等方之间所有邻接的表。
- Several tables exist to monitor and control LDP sessions. The LDP Session Table (mplsLdpSessionTable) represents sessions between an LDP Entity and a Peer. mplsLdpAtmSesTable and mplsLdpFrameRelaySesTable contain session information specific to ATM.
- 存在多个表来监视和控制LDP会话。LDP会话表（mplsLdpSessionTable）表示LDP实体和对等方之间的会话。mplsldpatmsetable和mplsldpframerelaysetable包含特定于ATM的会话信息。
- The MPLS LDP Session Peer Address Table (mplsLdpSesPeerAddrTable) stores addresses learned after session initialization via Address Message advertisement.
- MPLS LDP会话对等地址表（MPLSLPSESPEERADRDTABLE）存储会话初始化后通过地址消息播发获得的地址。
- The LDP FEC Table (mplsFecTable) represents FEC (Forwarding Equivalence Class) information that may be in use on one or more LSPs. The LDP LSP FEC Table (mplsLdpLspFecTable) shows the FECs associated with each LSP.
- LDP FEC表（mplsFecTable）表示可能在一个或多个lsp上使用的FEC（转发等价类）信息。LDP LSP FEC表（MPLSDPLSPFECTABLE）显示与每个LSP关联的FEC。
- MPLS-LDP-STD-MIB has a mapping table (mplsLdpLspTable) that maps the LDP MIB's representation of LDP sessions to the underlying LSR MIB's representation of the LSPs created by these sessions, by pointing to mplsInSegmentTable, mplsOutSegmentTable, and mplsXCTable, respectively.
- MPLS-LDP-STD-MIB有一个映射表（MPLSLPLSPTABLE），通过分别指向mplsInSegmentTable、MPLSSoutSegmentTable和mplsXCTable，将LDP MIB对LDP会话的表示映射到这些会话创建的LSP的底层LSR MIB表示。
- Statistics may be gathered through the LDP Entity Statistics Table (mplsLdpEntityStatsTable) and the LDP Session Statistics Table (mplsLdpSesStatsTable).
- 可以通过LDP实体统计表（MPLSLDEntityStatsTable）和LDP会话统计表（MPLSLDPSStatsTable）收集统计信息。
Where tables in the MIB modules have arbitrary indexes, scalars are provided to supply the next available index. This applies to mplsLdpEntityTable and mplsFecTable.
当MIB模块中的表具有任意索引时，将提供标量以提供下一个可用索引。这适用于MPLSLDEntityTable和mplsFecTable。
Two scalars exist to configure the LSR. The LSR ID is set in mplsLdpLsrId, and the loop detection capabilities are reported in mplsLdpLsrLoopDetectionCapable.
存在两个标量来配置LSR。LSR ID在MPLSDPLSRID中设置，循环检测能力在MPLSDPLSRLOOPDetectionCapable中报告。
MPLS-LDP-STD-MIB defines four notifications that a device can issue.
MPLS-LDP-STD-MIB定义了设备可以发出的四个通知。
- mplsLdpInitSesThresholdExceeded is reported when the number of Session Initialization messages exceeds a configured threshold.
- 当会话初始化消息数超过配置的阈值时，将报告MPLSLDPInitsesThresholdExcepended。
- mplsLdpPVLMismatch is issued if the Path Vector Limit for a configured Entity and Peer do not match.
- 如果已配置实体和对等方的路径向量限制不匹配，则会发出mplsLdpPVLMismatch。
- mplsLdpSessionUp and mplsLdpSessionDown report the transition of Session state.
- mplsLdpSessionUp和mplsLdpSessionDown报告会话状态的转换。
No scalar object is provided to enable and disable notifications from MPLS-LDP-STD-MIB. Instead, the implementer is referred to [RFC3413].
没有提供标量对象来启用和禁用来自MPLS-LDP-STD-MIB的通知。相反，实现者参考[RFC3413]。
The many tables in the four LDP MIB modules are related as shown on the diagram below. The arrows indicate a reference from one table to another. Note that in many cases the reference is through an augmentation of the referenced table.
如下图所示，四个LDP MIB模块中的许多表相互关联。箭头表示从一个表到另一个表的引用。注意，在许多情况下，引用是通过对引用表的扩充来实现的。
mplsLdpEntityGenLRTable ------------->+
mplsLdpEntityAtmParmsTable ---------->+
mplsLdpEntityAtmLRTable ------------->+
mplsLdpEntityFrameRelayParmsTable --->+
mplsLdpEntityFrLRTable -------------->+
mplsLdpEntityStatsTable ------------->+
|
mplsLdpHelloAdjacencyTable |
| |
| mplsLdpEntityTable <--+
| ^ ^
V | |
mplsLdpPeerTable <-+- mplsLdpSesPeerAddrTable
^ |
| V
mplsLdpSessionTable
^ ^
| |
mplsLdpSesStatsTable ------+ +-- mplsLdpLspFecTable
mplsLdpAtmSesTable --------+ | | |
mplsLdpFrameRelaySesTable--+ | | V
| | mplsFecTable
| V
+-- mplsLdpLspTable
mplsLdpEntityGenLRTable ------------->+
mplsLdpEntityAtmParmsTable ---------->+
mplsLdpEntityAtmLRTable ------------->+
mplsLdpEntityFrameRelayParmsTable --->+
mplsLdpEntityFrLRTable -------------->+
mplsLdpEntityStatsTable ------------->+
|
mplsLdpHelloAdjacencyTable |
| |
| mplsLdpEntityTable <--+
| ^ ^
V | |
mplsLdpPeerTable <-+- mplsLdpSesPeerAddrTable
^ |
| V
mplsLdpSessionTable
^ ^
| |
mplsLdpSesStatsTable ------+ +-- mplsLdpLspFecTable
mplsLdpAtmSesTable --------+ | | |
mplsLdpFrameRelaySesTable--+ | | V
| | mplsFecTable
| V
+-- mplsLdpLspTable
MPLS-TE-STD-MIB contains the following tables.
MPLS-TE-STD-MIB包含以下表格。
- The Tunnel Table (mplsTunnelTable) is used to configure and report MPLS tunnels. Note that reporting of tunnels in this table at transit LSRs is optional.
- 隧道表（mplsTunnelTable）用于配置和报告MPLS隧道。请注意，在运输LSR时，此表中的隧道报告是可选的。
Entries in mplsTunnelTable are indexed by four objects. The source and destination LSR IDs give context to the entry, and an index (mplsTunnelIndex) identifies the tunnel itself. However, the fourth index (mplsTunnelInstance) may give rise to some confusion since its usage is not clearly explained.
mplsTunnelTable中的条目由四个对象索引。源和目标LSR ID为条目提供上下文，索引（mplsTunnelIndex）标识隧道本身。然而，第四个索引（mplsTunnelInstance）可能会引起一些混淆，因为它的用法没有明确解释。
The description says: "Uniquely identifies an instance of a tunnel. It is useful to identify multiple instances of tunnels for the purposes of backup and parallel tunnels." In the case of backup tunnels, multiple instances of the same tunnel may be defined, but only one is active at any time. Different instances may have different properties (such as explicit routes), and one instance may be set up to protect against failure of another.
描述中说：“唯一标识一个隧道实例。为了备份和并行隧道的目的，标识多个隧道实例非常有用。”在备份隧道的情况下，可以定义同一隧道的多个实例，但在任何时候只有一个实例处于活动状态。不同的实例可能具有不同的属性（例如显式路由），可以设置一个实例以防止另一个实例出现故障。
Parallel tunnels may be used to provide load sharing or protection.
平行隧道可用于提供荷载分担或保护。
The mplsTunnelInstancePriority object is used to indicate the precedence of tunnels with the same LSR IDs and mplsTunnelIndex value. The mplsTunnelPrimaryInstance object gives a quick reference back to the preferred instance of the tunnel.
mplsTunnelInstancePriority对象用于指示具有相同LSR ID和mplsTunnelIndex值的隧道的优先级。mplsTunnelPrimaryInstance对象快速引用回隧道的首选实例。
The mplsTunnelIndex value is typically signaled as the Tunnel ID, and the mplsTunnelInstance as the LSP ID, in protocols where both fields exist. In protocols where there is only one identifying index (usually known as the LSP ID), only the mplsTunnelIndex is signaled.
在两个字段都存在的协议中，mplsTunnelIndex值通常作为隧道ID发出信号，而MPLStunnelinInstance作为LSP ID发出信号。在只有一个标识索引（通常称为LSP ID）的协议中，只有mplsTunnelIndex被发信号。
- The Resource Table (mplsTunnelResourceTable) is used to configure resources to be requested on this tunnel. The CRLDP resource table (mplsTunnelCRLDPResTable) is used to request additional resource details that are specific to tunnels signaled using CR-LDP.
- 资源表（mplsTunnelResourceTable）用于配置要在此隧道上请求的资源。CRLDP资源表（mplsTunnelCRLDPResTable）用于请求特定于使用CR-LDP发送信号的隧道的额外资源详细信息。
- The routes requested, computed, and actually used for a tunnel are found in the Tunnel Hop Table (mplsTunnelHopTable), Tunnel Computed Hop Table (mplsTunnelCHopTable), and Tunnel Actual Hop Table (mplsTunnelARHopTable).
- 隧道请求、计算和实际使用的路由可在隧道跃点表（mplsTunnelHopTable）、隧道计算跃点表（mplsTunnelHopTable）和隧道实际跃点表（mplsTunnelHopTable）中找到。
- Statistics about the performance of tunnels may be gathered through the Tunnel Performance Table (mplsTunnelPerfTable).
- 有关隧道性能的统计信息可通过隧道性能表（mplsTunnelPerfTable）收集。
Where tables in the MIB module have arbitrary indexes, scalars are provided to supply the next available index. This applies to mplsTunnelTable, mplsTunnelResourceTable, and mplsTunnelHopTable.
当MIB模块中的表具有任意索引时，将提供标量以提供下一个可用索引。这适用于mplsTunnelTable、mplsTunnelResourceTable和mplsTunnelHopTable。
Two scalars exist to configure the support for MPLS tunnels on the LSR. mplsTunnelTEDistProto lists the signaling methods and protocols supported. mplsTunnelMaxHops defines the size of route that may be configured on the LSR.
存在两个标量来配置对LSR上MPLS隧道的支持。mplsTunnelTEDistProto列出了支持的信令方法和协议。mplsTunnelMaxHops定义可在LSR上配置的路由大小。
Two further scalars enhance the statistics on the LSR by counting the number of configured (mplsTunnelConfigured) and active (mplsTunnelActive) tunnels.
另外两个标量通过计算已配置（mplsTunnelConfigured）和活动（mplsTunnelActive）隧道的数量来增强LSR的统计信息。
The scalar mplsTunnelNotificationMaxRate is used to control the rate at which notifications are issued from MPLS-TE-STD-MIB. A rate of zero means that notifications must not be issued. If notifications
标量mplsTunnelNotificationMaxRate用于控制从MPLS-TE-STD-MIB发出通知的速率。比率为零意味着不得发布通知。如果通知
would be generated faster than the configured rate, an implementation may choose to discard notifications or to queue them for distribution at a quieter time.
将以比配置的速率更快的速度生成，则实现可以选择放弃通知或将其排队以便在更安静的时间分发。
MPLS-TE-STD-MIB defines four notifications that a device can issue. The rate of dispatch of notifications is controlled as described in the previous section.
MPLS-TE-STD-MIB定义了设备可以发出的四个通知。通知的发送速率如前一节所述进行控制。
- mplsTunnelUp and mplsTunnelDown report the transition of Tunnel state.
- mplsTunnelUp和mplsTunnelDown报告隧道状态的转换。
- Rerouting and re-optimization of Tunnels paths are reported by mplsTunnelRerouted and mplsTunnelReoptimized.
- 隧道路径的重新路由和重新优化由mplsTunnelRerouted和mplsTunnelReoptimized报告。
The tables in MPLS-TE-STD-MIB are related as shown on the diagram below. The arrows indicate a reference from one table to another.
MPLS-TE-STD-MIB中的表格如下图所示。箭头表示从一个表到另一个表的引用。
mplsTunnelPerfTable
^
|
V
mplsTunnelTable
| |
V |
mplsTunnelResourceTable +--> mplsTunnelHopTable
^ |
| +--> mplsTunnelCHopTable
V |
mplsTunnelCRLDPResTable +--> mplsTunnelARHopTable
mplsTunnelPerfTable
^
|
V
mplsTunnelTable
| |
V |
mplsTunnelResourceTable +--> mplsTunnelHopTable
^ |
| +--> mplsTunnelCHopTable
V |
mplsTunnelCRLDPResTable +--> mplsTunnelARHopTable
MPLS-FTN-STD-MIB contains the following tables.
MPLS-FTN-STD-MIB包含以下表格。
- The FEC-to-NHLFE Table (mplsFTNTable) defines the FEC to NHLFE rules to be applied to incoming packets, and the actions to be taken on matching packets.
- FEC到NHLFE表（MPLSTNTABLE）定义了要应用于传入数据包的FEC到NHLFE规则，以及要对匹配数据包采取的操作。
- The FEC-to-NHLFE Mapping Table (mplsFTNMapTable) provides the capability to activate FTN rules defined in the mplsFTNTable on specific interfaces in the system.
- FEC到NHLFE映射表（MPLSTNMATABLE）提供了在系统特定接口上激活MPLSTNTABLE中定义的FTN规则的功能。
- Performance statistics for FTN rules are found in the mplsFTNPerfTable.
- FTN规则的性能统计信息可在MPLSFTNPERFER表中找到。
This MIB module contains the scalars mplsFTNTableLastChanged and mplsFTNMapTableLastChanged to indicate the last time an object changed in mplsFTNTable and mplsFTNMapTable, respectively. Another scalar, mplsFTNIndexNext, is used to supply the next valid index for creating new conceptual rows in mplsFTNTable.
此MIB模块包含标量mplsFTNTableLastChanged和mplsFTNMapTableLastChanged，分别指示对象上次在mplsFTNTable和mplsFTNMapTable中更改的时间。另一个标量MPLSTNINDEXNEXT用于提供下一个有效索引，以便在MPLSTNTABLE中创建新的概念行。
There are no notifications in this MIB module.
此MIB模块中没有通知。
The tables in MPLS-FTN-STD-MIB are related as shown on the diagram below. The arrows indicate a reference from one table to another.
MPLS-FTN-STD-MIB中的表格如下图所示。箭头表示从一个表到另一个表的引用。
mplsFTNTable ^ | mplsFTNMapTable ^ | mplsFTNPerfTable
MPLSTNTABLE^ | MPLSTNTABLE^ | MPLSTNPURFTABLE
TE-LINK-STD-MIB contains the following tables.
TE-LINK-STD-MIB包含以下表格。
- The TE link table (teLinkTable) is used to specify TE links, including bundled links, and their generic traffic-engineering parameters.
- TE链路表（teLinkTable）用于指定TE链路（包括捆绑链路）及其通用流量工程参数。
- The TE link descriptor table (teLinkDescriptorTable) is used to list the TE link descriptors.
- TE链接描述符表（teLinkDescriptorTable）用于列出TE链接描述符。
- The shared risk link group (SRLG) table (teLinkSrlgTable) is used to specify the SRLGs associated with TE links.
- 共享风险链接组（SRLG）表（teLinkSrlgTable）用于指定与TE链接关联的SRLG。
- The TE link bandwidth table (teLinkBandwidthTable) is used to report priority-based bandwidth values associated with TE links.
- TE链路带宽表（teLinkBandwidthTable）用于报告与TE链路相关的基于优先级的带宽值。
- The component link table (componentLinkTable) is used to identify the data-bearing component links that are associated with the TE links and specify the data-bearing link generic traffic engineering parameters.
- 组件链接表（componentLinkTable）用于识别与TE链接关联的数据承载组件链接，并指定数据承载链接通用流量工程参数。
- The component link descriptor table (componentLinkDescriptorTable) is used to list the data-bearing component link descriptors.
- 组件链接描述符表（ComponentLinkDescriptor表）用于列出数据承载组件链接描述符。
- The component link bandwidth table (componentLinkBandwidthTable) is used to report priority-based bandwidth values associated with data-bearing component links.
- 组件链路带宽表（componentLinkBandwidthTable）用于报告与数据承载组件链路相关的基于优先级的带宽值。
There are no scalars in this MIB module.
此MIB模块中没有标量。
There are no notifications in this MIB module.
此MIB模块中没有通知。
The tables in TE-LINK-STD-MIB are related as shown on the diagram below. The arrows indicate a reference from one table to another.
TE-LINK-STD-MIB中的表格如下图所示。箭头表示从一个表到另一个表的引用。
Note that many of the associations between tables are through a common index that is the ifIndex of the related interface.
请注意，表之间的许多关联都是通过一个公共索引进行的，该索引是相关接口的ifIndex。
teLinkTable
^
|
teLinkDescriptorTable ---+
|
teLinkSrlgTable ---------+
|
teLinkBandwidthTable ----+
teLinkTable
^
|
teLinkDescriptorTable ---+
|
teLinkSrlgTable ---------+
|
teLinkBandwidthTable ----+
componentLinkTable
^
|
componentLinkDescriptorTable ---+
|
componentLinkBandwidthTable ----+
componentLinkTable
^
|
componentLinkDescriptorTable ---+
|
componentLinkBandwidthTable ----+
Section 4.11 gave an overview of how the MPLS MIB modules are related. Now that the tables in the MIB modules have been introduced, it is possible to give a more detailed diagram of these relationships.
第4.11节概述了MPLS MIB模块之间的关系。现在已经介绍了MIB模块中的表，可以给出这些关系的更详细的图表。
MPLS-TC-STD-MIB is left off the diagram because many of the MIB module tables use textual conventions from that MIB module.
MPLS-TC-STD-MIB不在图中，因为许多MIB模块表使用该MIB模块的文本约定。
mplsLsrXCTable mplsLsrInSegmentTable
^ ^
| |
+---- mplsLdpLspTable
| |
mplsTunnelTable ------+ V
^ | mplsLsrOutSegmentTable
| |
mplsFTNTable ---------+
mplsLsrXCTable mplsLsrInSegmentTable
^ ^
| |
+---- mplsLdpLspTable
| |
mplsTunnelTable ------+ V
^ | mplsLsrOutSegmentTable
| |
mplsFTNTable ---------+
The Interfaces Group of IF-MIB [RFC2863] defines generic managed objects for managing interfaces. The MPLS MIB modules make references to interfaces so that it can be clearly determined where the procedures managed by the MIB modules should be performed. Additionally, the MPLS MIB modules (notably MPLS-TE-STD-MIB and TE-LINK-STD-MIB) utilize interface stacking within the Interface Group.
IF-MIB[RFC2863]的接口组定义了用于管理接口的通用托管对象。MPLS MIB模块引用接口，以便可以清楚地确定MIB模块管理的过程应在何处执行。此外，MPLS MIB模块（尤其是MPLS-TE-STD-MIB和TE-LINK-STD-MIB）利用接口组内的接口堆叠。
MPLS-TE-STD-MIB builds on the concept of managing MPLS Tunnels as logical interfaces. [RFC2863] states that the interfaces table (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, an MPLS Tunnel managed as an interface is represented as an entry in the ifTable. The interrelation of entries in the ifTable is defined by the Interfaces Stack Group defined in [RFC2863].
MPLS-TE-STD-MIB建立在将MPLS隧道作为逻辑接口进行管理的概念之上。[RFC2863]声明接口表（ifTable）包含有关受管资源接口的信息，并且网络接口的网络层下的每个子层都被视为接口。因此，作为接口管理的MPLS隧道表示为ifTable中的条目。ifTable中条目的相互关系由[RFC2863]中定义的接口堆栈组定义。
When using MPLS Tunnels as interfaces, the interface stack table might appear as follows:
当使用MPLS隧道作为接口时，接口堆栈表可能如下所示：
+------------------------------------------------+
| MPLS tunnel interface ifType = mplsTunnel(150) |
+------------------------------------------------+
| MPLS interface ifType = mpls(166) |
+------------------------------------------------+
| Underlying layer |
+------------------------------------------------+
+------------------------------------------------+
| MPLS tunnel interface ifType = mplsTunnel(150) |
+------------------------------------------------+
| MPLS interface ifType = mpls(166) |
+------------------------------------------------+
| Underlying layer |
+------------------------------------------------+
In the diagram above, "Underlying layer" refers to the ifIndex of any interface type for which MPLS internetworking has been defined. Examples include ATM, Frame Relay, and Ethernet.
在上图中，“底层”是指定义了MPLS互连的任何接口类型的ifIndex。示例包括ATM、帧中继和以太网。
A detailed listing of the mapping between ifTable objects and their use for MPLS Tunnels is given in [TEMIB]. A few key objects are listed here to provide an overview of the concepts.
[TEMIB]中给出了ifTable对象之间的映射及其在MPLS隧道中的使用的详细列表。这里列出了几个关键对象，以概述这些概念。
Each MPLS tunnel is represented by an entry in the ifTable. Each tunnel is therefore assigned a unique ifIndex.
每个MPLS隧道由ifTable中的一个条目表示。因此，将为每个隧道指定一个唯一的ifIndex。
The type of an interface represented by an entry in the ifTable is indicated by the ifType object. The value that is allocated to identify an MPLS tunnel is 150.
ifTable中的条目表示的接口类型由ifType对象指示。分配用于标识MPLS隧道的值为150。
The ifOperStatus object reflects the actual operational status of the MPLS tunnel and may be mapped from the mplsTunnelOperStatus object.
IfOperaStatus对象反映MPLS隧道的实际运行状态，可以从mplsTunnelOperStatus对象映射。
It may be considered convenient and good management to set the ifName object to reflect the name of the MPLS tunnel as contained in the mplsTunnelName object.
将ifName对象设置为反映包含在mplsTunnelName对象中的MPLS隧道的名称可能被认为是方便和良好的管理。
TE-LINK-STD-MIB also uses interface stacking to manage TE Link interfaces as logical interfaces. The TE Link interface is represented as an entry in the ifTable. The interrelation of entries in the ifTable is defined by Interfaces Stack Group defined in [RFC2863]. When using TE Link interfaces, the interface stack table might appear as follows:
TE-LINK-STD-MIB还使用接口堆叠将TE-LINK接口作为逻辑接口进行管理。TE Link接口表示为ifTable中的一个条目。ifTable中条目的相互关系由[RFC2863]中定义的接口堆栈组定义。使用TE Link接口时，接口堆栈表可能显示如下：
+-------------------------------------------------------------------+
| MPLS interface ifType = mpls(166) |
| ifIndex = 1 |
+-------------------------------------------------------------------+
| TE link (bundled link) ifType = teLink(200) |
| ifIndex = 2 |
+--------------------------------+-+--------------------------------+
| TE link ifType = teLink(200) | | TE link ifType = teLink(200) |
| ifIndex = 3 | | ifIndex = 4 |
+--------------------------------+ +--------------------------------+
| Component link | | Component link |
| ifType = opticalTransport(196) | | ifType = opticalTransport(196) |
| ifIndex = 5 | | ifIndex = 6 |
+--------------------------------+ +--------------------------------+
+-------------------------------------------------------------------+
| MPLS interface ifType = mpls(166) |
| ifIndex = 1 |
+-------------------------------------------------------------------+
| TE link (bundled link) ifType = teLink(200) |
| ifIndex = 2 |
+--------------------------------+-+--------------------------------+
| TE link ifType = teLink(200) | | TE link ifType = teLink(200) |
| ifIndex = 3 | | ifIndex = 4 |
+--------------------------------+ +--------------------------------+
| Component link | | Component link |
| ifType = opticalTransport(196) | | ifType = opticalTransport(196) |
| ifIndex = 5 | | ifIndex = 6 |
+--------------------------------+ +--------------------------------+
In the above diagram, "opticalTransport" is an example of an underlying physical interface: in this case an optical transport interface. TE link management and bundling can be seen in the levels of interface stacking. Two TE links are defined, each managing an optical transport link. These two TE links are combined into a bundle, which is managed as a single TE link interface. This TE Link interface supports MPLS and is presented as an MPLS interface.
在上图中，“opticalTransport”是底层物理接口的一个示例：在本例中为光传输接口。TE链路管理和捆绑可以在接口堆叠的层次上看到。定义了两个TE链路，每个链路管理一个光传输链路。这两个TE链接组合成一个捆绑包，作为单个TE链接接口进行管理。此TE链路接口支持MPLS，并作为MPLS接口提供。
A detailed listing of the mapping between ifTable objects and their use for TE Links is given in [TELMIB]. A few key objects are listed here to provide an overview of the concepts.
[TELMIB]中给出了ifTable对象之间的映射及其对TE链接的使用的详细列表。这里列出了几个关键对象，以概述这些概念。
Each TE Link interface is represented by a separate entry in the ifTable, with a unique ifIndex.
每个TE链接接口由ifTable中的一个单独条目表示，该条目具有唯一的ifIndex。
The type of an interface represented by an entry in the ifTable is indicated by the ifType object. The value that is allocated to identify a TE Link is 200.
ifTable中的条目表示的接口类型由ifType对象指示。分配用于标识TE链路的值为200。
MPLS-TE-STD-MIB contains two objects that reference the management of an MPLS tunnel as an interface. mplsTunnelIsIf is a TruthValue that indicates whether the tunnel is present in the ifTable. If the tunnel is managed as an interface, the mplsTunnelIfIndex object contains the ifIndex that identifies the corresponding entry in the ifTable.
MPLS-TE-STD-MIB包含两个对象，它们将MPLS隧道的管理作为接口引用。mplsTunnelIsIf是一个TruthValue，指示ifTable中是否存在隧道。如果隧道作为接口管理，则mplsTunnelIfIndex对象包含标识ifTable中相应项的ifIndex。
MPLS-LSR-STD-MIB includes a table (mplsInterfaceTable) for configuring the support for MPLS on specific interfaces. A conceptual row in this table is created automatically by an LSR for every interface that is capable of and configured for support of MPLS. A conceptual row in this table will exist if and only if a
MPLS-LSR-STD-MIB包括一个表（mplsInterfaceTable），用于在特定接口上配置对MPLS的支持。此表中的一个概念行由LSR为每个能够支持MPLS并配置为支持MPLS的接口自动创建。当且仅当
corresponding entry in ifTable exists with ifType = mpls(166). The fate of the entries in the two tables are closely linked so that if the entry in the ifTable is operationally disabled, the entry in mplsInterfaceTable is deleted. During the life of an entry in mplsInterfaceTable, a corresponding entry is managed in mplsInterfacePerfTable to show performance counters for the MPLS-capable interface.
ifTable中存在ifType=mpls（166）的对应条目。两个表中条目的命运紧密相连，因此如果ifTable中的条目在操作上被禁用，则mplsInterfaceTable中的条目将被删除。在mplsInterfaceTable中的条目的生命周期内，在mplsInterfacePerfTable中管理相应的条目，以显示支持MPLS的接口的性能计数器。
The ifIndex that identifies MPLS-capable interfaces also plays an important indexing role in MPLS-LSR-STD-MIB. In-segments (that is, incoming LSP labels) are represented in mplsInSegmentTable, which is indexed by the mplsInSegmentIfIndex and mplsInSegmentLabel objects. mplsInSegmentIfIndex is set to the ifIndex of the incoming MPLS-capable interface. mplsInSegmentLabel identifies the incoming MPLS label. Note that the corresponding mplsOutSegmentTable contains an mplsOutSegmentIfIndex object to identify the outgoing MPLS-capable interface, but that this does not form part of the index of the table.
标识支持MPLS的接口的ifIndex在MPLS-LSR-STD-MIB中也起着重要的索引作用。In段（即传入的LSP标签）在mplsInSegmentTable中表示，该表由MPLSINSegmentiIndex和mplsInSegmentLabel对象索引。MPLSINSegmentiIndex设置为传入支持MPLS的接口的iIndex。mplsInSegmentLabel标识传入的MPLS标签。请注意，对应的MPLSOUTSEGENTTABLE包含一个MPLSOUTSEGENTIFINDEX对象，用于标识支持MPLS的传出接口，但这并不构成表索引的一部分。
MPLS-LDP-STD-MIB uses ifIndex extensively to identify the interface over which MPLS is active.
MPLS-LDP-STD-MIB广泛使用ifIndex来标识MPLS活动的接口。
Within MPLS-FTN-STD-MIB, mplsFTNMapTable maps entries in mplsFTNTable to interfaces on which mplsFTNTable entries should be activated. Interfaces are identified using their ifIndex values.
在MPLS-FTN-STD-MIB中，MPLSTNMATABLE将MPLSTNTABLE中的条目映射到应激活MPLSTNTABLE条目的接口。接口使用其ifIndex值进行标识。
It is not the intention of this document to provide instructions or advice to implementers of Management Stations, 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.
本文件的目的不是向管理站、管理代理或被管理实体的实施者提供指示或建议。然而，对上面描述的MIB模块如何用于管理MPLS系统进行一些观察是有用的。
All MPLS LSPs may appear in MPLS-LSR-STD-MIB. At transit nodes, they are seen as full cross-connects between incoming labels on incoming interfaces and outgoing labels on outgoing interfaces. At ingress or egress points, the cross-connections are unbalanced having spoof upstream or downstream legs, respectively.
所有MPLS LSP都可能出现在MPLS-LSR-STD-MIB中。在传输节点上，它们被视为传入接口上的传入标签和传出接口上的传出标签之间的完全交叉连接。在入口或出口点，交叉连接不平衡，分别具有欺骗上游或下游分支。
Split and merge points of LSPs may be represented as more complex cross-connects in MPLS-LSR-STD-MIB. Similarly, bidirectional LSPs can be represented by using the same cross-connect index for each of the forward and reverse cross-connections.
在MPLS-LSR-STD-MIB中，LSP的拆分和合并点可以表示为更复杂的交叉连接。类似地，双向lsp可以通过为每个正向和反向交叉连接使用相同的交叉连接索引来表示。
The modules in the LDP MIB are intended solely for use with LDP and CR-LDP. LSPs that are signaled through other means may conveniently be stored in mplsLdpLspTable for consistency with LSPs set up using
LDP MIB中的模块仅用于LDP和CR-LDP。通过其他方式发信号的LSP可以方便地存储在MPLSDPLSPTABLE中，以便与使用
LDP, but there is little further value to this because the table gives only pointers into MPLS-LSR-STD-MIB. If, however, the LSPs are established with associated FECs using some signaling method other than LDP (for example, BGP), it may be advantageous to use mplsLdpLspTable, mplsFecTable, and mplsLdpLspFecTable to correlate the LSPs.
LDP，但由于该表只提供指向MPLS-LSR-STD-MIB的指针，因此没有什么进一步的价值。然而，如果使用LDP（例如，BGP）以外的一些信令方法与相关联的fec建立lsp，则使用mplsLdpLspTable、mplsFecTable和mplsLdpLspFecTable来关联lsp可能是有利的。
Note that if CR-LDP is the signaling protocol, there is no requirement to use the LSP-related tables in the LDP MIB since the LSP will be adequately represented in MPLS-TE-MIB and MPLS-LSR-STD-MIB.
注意，如果CR-LDP是信令协议，则不需要在LDP MIB中使用LSP相关表，因为LSP将在MPLS-TE-MIB和MPLS-LSR-STD-MIB中充分表示。
MPLS tunnels may be represented in MPLS-TE-STD-MIB with their cross-connects indicated in MPLS-LSR-STD-MIB. Tunnels are often (although not always) set up with a series of constraints that may be represented in MPLS-TE-STD-MIB. Note that a distinguishing feature of a tunnel is that it has an ingress and an egress, where LSPs established through LDP may be end-to-end or may be hop-by-hop.
MPLS隧道可以用MPLS-TE-STD-MIB表示，其交叉连接用MPLS-LSR-STD-MIB表示。隧道通常（尽管并非总是）设置有一系列约束，这些约束可以在MPLS-TE-STD-MIB中表示。注意，隧道的区别特征是其具有入口和出口，其中通过LDP建立的lsp可以是端到端的，或者可以是逐跳的。
All LSPs (tunnels and non-tunnels) may be established as a result of signaling protocols already defined or for future study. In addition, LSPs may be set up manually by issuing configuration commands to each of the LSRs on the LSP. These commands may utilize SNMP by performing SET operations to the MIB module tables and objects described here. Alternatively, configuration may be through some non-standard interface such as a Command Line or a Graphical User Interface. Such configured LSPs may also be represented in the MIB module tables.
所有LSP（隧道和非隧道）可根据已定义的信令协议建立，或用于未来研究。此外，可以通过向LSP上的每个LSR发出配置命令来手动设置LSP。这些命令可以通过对此处描述的MIB模块表和对象执行SET操作来利用SNMP。或者，可以通过一些非标准界面（例如命令行或图形用户界面）进行配置。这种配置的lsp也可以在MIB模块表中表示。
Do not be misled by considerations of the "permanence" of LSPs when deciding which tables of which MIB modules to use. An MPLS tunnel may have a very long life expectancy if it is set up by an amnesiac user. Otherwise, it may have a very short lifetime if it is automatically provisioned to satisfy on-demand traffic requirements. Similarly, an LSP established in response to a routing protocol (sometimes known as a hop-by-hop LSP) may be equally stable or unstable.
在决定使用哪个MIB模块的哪些表时，不要被LSP的“持久性”考虑所误导。如果MPLS隧道是由健忘症患者建立的，那么它的预期寿命可能会很长。否则，如果自动配置它以满足按需流量需求，它的生命周期可能很短。类似地，响应于路由协议而建立的LSP（有时称为逐跳LSP）可以同样稳定或不稳定。
This section describes the broad interactions between MIB modules produced by the PWE3, PPVPN, and CCAMP working groups and the MPLS MIB modules. This information is provided as background and is not central to this document.
本节描述了PWE3、PPVPN和CCAMP工作组产生的MIB模块与MPLS MIB模块之间的广泛交互。此信息作为背景信息提供，并非本文件的核心内容。
The PWE3 working group has produced a document [PWE3FW] that includes a description of the framework for MIB modules within PWE3 operation. Since the PWE3 architecture includes the use of MPLS as an emulated service and as a PSN service, the MPLS MIB modules described above may be leveraged. The PWE3 framework document describes the interactions between the MPLS MIB modules and the PWE3 MIB modules.
PWE3工作组编制了一份文件[PWE3FW]，其中包括对PWE3操作中MIB模块框架的描述。由于PWE3体系结构包括将MPLS用作模拟服务和PSN服务，因此可以利用上述MPLS MIB模块。PWE3框架文档描述了MPLS MIB模块和PWE3 MIB模块之间的交互。
At present, the PPVPN working group has not included a discussion of how the MPLS MIB modules interact with the MIB modules being produced by that working group. The authors of this document hope to make a forthcoming addition to the PPVPN framework document [PPVPNFW] detailing these interactions. At the moment, there are two MIB modules, [VPNMIB] and [VPNTCMIB], which are discussed next.
目前，PPVPN工作组尚未讨论MPLS MIB模块如何与该工作组生产的MIB模块交互。本文档的作者希望在PPVPN框架文档[PPVPNFW]中添加一个详细说明这些交互的内容。目前，有两个MIB模块，[VPNMIB]和[VPNTCMIB]，下面将讨论这两个模块。
PPVPN-MPLS-VPN-STD-MIB describes managed objects that are used to model and manage RFC2547bis MPLS VPNs [RFC2547Bis]. This MIB module contains tables that model virtual routing forwarding entries (VRFs), as well as the interfaces associated with those VRFs.
PPVPN-MPLS-VPN-STD-MIB描述了用于建模和管理RFC2547bis MPLS VPN[RFC2547bis]的托管对象。此MIB模块包含为虚拟路由转发条目（VRF）建模的表，以及与这些VRF关联的接口。
transmission -- RFC 2578 [RFC2578] | +- vpnMIB -- PPVPN-MPLS-VPN-STD-MIB
传输--RFC22578[RFC2578]|+-vpnMIB--PPVPN-MPLS-VPN-STD-MIB
This MIB module currently has no direct dependencies on any of the MPLS MIB modules. This MIB module models MPLS VPN interfaces as entries in the Interfaces MIB's Interfaces Table (ifTable). This MIB module may be modified in the future to import textual conventions from MPLS-TC-STD-MIB.
此MIB模块当前与任何MPLS MIB模块都没有直接依赖关系。此MIB模块将MPLS VPN接口建模为接口MIB的接口表（ifTable）中的条目。将来可能会修改此MIB模块，以便从MPLS-TC-STD-MIB导入文本约定。
A specific textual conventions MIB module [VPNTCMIB] defines textual conventions that are imported into PPVPN-MPLS-VPN-STD-MIB.
特定的文本约定MIB模块[VPNTCMIB]定义导入PPVPN-MPLS-VPN-STD-MIB的文本约定。
The CCAMP working group is developing MIB modules in support of GMPLS that interact directly with the MPLS MIB modules. Along with any MIB modules produced by the CCAMP working group, a separate CCAMP-
CCAMP工作组正在开发MIB模块，以支持直接与MPLS MIB模块交互的GMPLS。与CCAMP工作组生产的任何MIB模块一起，单独的CCAMP-
specific Management Framework document is expected to be issued describing the relationship between these MIB modules and the existing MPLS (and other) MIB modules.
预计将发布具体的管理框架文件，描述这些MIB模块与现有MPLS（和其他）MIB模块之间的关系。
The TEWG has produced a traffic engineering MIB (TE-MIB) [TEWGMIB] containing objects for monitoring traffic-engineered tunnels at their ingress points.
TEWG已经制作了一个交通工程MIB（TE-MIB）[TEWGMIB]，其中包含用于在入口点监控交通工程隧道的对象。
In many senses TE-MIB contains the same information as MPLS-TE-STD-MIB. Both MIB modules can be used to monitor MPLS tunnels; however, TE-MIB is minimalistic and caters best to TE tunnels as tunnels, at the expense of not having many advanced features of MPLS-TE-STD-MIB, whereas MPLS-TE-STD-MIB can deconstruct tunnels into hop-by-hop cross-connects, at the expense of more complexity.
在许多意义上，TE-MIB包含与MPLS-TE-STD-MIB相同的信息。这两个MIB模块都可用于监控MPLS隧道；然而，TE-MIB是最低限度的，最适合作为隧道的TE隧道，代价是没有MPLS-TE-STD-MIB的许多高级功能，而MPLS-TE-STD-MIB可以将隧道解构为逐跳交叉连接，代价是更复杂。
The TE-MIB module imports textual conventions from the MPLS-TC-STD-MIB module and therefore is dependent on that document.
TE-MIB模块从MPLS-TC-STD-MIB模块导入文本约定，因此依赖于该文档。
TE-MIB is a flexible MIB module designed to manage traffic engineering tunnels regardless of the implementation technology. This flexibility and a focus on simplicity lead to some compromises.
TE-MIB是一个灵活的MIB模块，设计用于管理交通工程隧道，而不考虑实施技术。这种灵活性和对简单性的关注导致了一些折衷。
- Some MPLS configuration parameters are left out. For example, the resource management in TE-MIB is confined to bandwidth, so missing the full IntServ control.
- 遗漏了一些MPLS配置参数。例如，TE-MIB中的资源管理仅限于带宽，因此缺少完整的IntServ控制。
- Other TE-MIB parameters are present but with only limited options; for example, the ability to configure different label distribution methods per LSP.
- 存在其他TE-MIB参数，但选项有限；例如，能够为每个LSP配置不同的标签分发方法。
Extensibility of TE-MIB to related concepts (such as DiffServ and Fast Reroute) and integrations with other MIB modules (such as that in MPLS-LSR-STD-MIB) are not work items at the time of writing. The MPLS MIB modules are more closely integrated as described in this document.
TE-MIB对相关概念（如区分服务和快速重路由）的可扩展性以及与其他MIB模块（如MPLS-LSR-STD-MIB中的模块）的集成在编写本文时不是工作项。如本文档所述，MPLS MIB模块的集成更加紧密。
Write/create access to TE-MIB is only available at the ingress, where it can be used to configure an ingress to signal a tunnel with constraints. It cannot be used to configure hop-by-hop cross-connects to build a tunnel.
TE-MIB的写入/创建访问权限仅在入口可用，可用于配置入口，以向具有约束的隧道发送信号。它不能用于配置逐跳交叉连接以构建隧道。
The purpose of TE-MIB module is to allow a Management Agent to configure tunnels, and to inspect and monitor all tunnels (however created) at their ingress points. It does not provide information
TE-MIB模块的目的是允许管理代理配置隧道，并在其入口点检查和监控所有隧道（无论创建何种隧道）。它没有提供信息
about tunnels at any other point in the network (that is, at transit or egress nodes). This module can be used, for example, to configure the constraints of a tunnel, whereupon the ingress would compute the tunnel path and signal it. The MIB module can then be used at the ingress to monitor the tunnel's path(s), their status, and the tunnel's uptime and counters. This MIB module is not designed to configure hop-by-hop cross-connects to build a tunnel.
关于网络中任何其他点（即，在传输或出口节点）的隧道。例如，该模块可用于配置隧道的约束，因此入口将计算隧道路径并向其发送信号。然后，可以在入口使用MIB模块来监控隧道的路径、状态以及隧道的正常运行时间和计数器。此MIB模块的设计目的不是配置逐跳交叉连接以构建隧道。
This document describes the interrelationships amongst the different MIB modules relevant to MPLS management and as such does not have any security implications in and of itself.
本文档描述了与MPLS管理相关的不同MIB模块之间的相互关系，因此其本身不具有任何安全含义。
Each specific MIB document specifies specific MIB objects, and such a document must provide a proper security considerations section that explains the security aspects of those objects.
每个特定的MIB文档都指定特定的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 and GET (read) the objects in this MIB. 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 this MIB is properly configured to give access to only those objects, and to those principals (users) that have legitimate rights to access them.
然后，客户/用户有责任确保授予访问此MIB实例权限的SNMP实体正确配置为仅授予访问这些对象以及具有访问这些对象的合法权限的主体（用户）的权限。
Many small pieces of text in this document have been borrowed from the documents that define the MIB modules described here. The authors would like to express appreciation to all who worked on those MIB documents.
本文档中的许多小部分文本都是从定义此处描述的MIB模块的文档中借来的。作者谨向所有从事这些MIB文档工作的人员表示感谢。
Thanks also to all those who attended the November 2002 MPLS MIB open meeting and gave constructive feedback, and in particular to Sharon Chisholm for her thoughts on Management Options.
还感谢所有参加2002年11月MPLS MIB公开会议并提供建设性反馈的人，特别是Sharon Chisholm对管理选项的想法。
Thanks to Kireeti Kompella for revising the text on TE-MIB.
感谢Kireeti Kompella修改了TE-MIB上的文本。
Without the consistent pressure and encouragement from Bert Wijnen, this document would not have been written.
如果没有伯特·维恩（Bert Wijnen）始终如一的压力和鼓励，这份文件就不会写成。
[FTNMIB] 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.
[FTNMIB]Nadeau，T.，Srinivasan，C.，和A.Viswanathan，“多协议标签交换（MPLS）转发等价类到下一跳标签转发条目（FEC到NHLFE）管理信息库（MIB）”，RFC 3814，2004年6月。
[LDPMIB] 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.
[LDPMIB]Cucchiara，J.，Sjostrand，H.，和J.Luciani，“多协议标签交换（MPLS）管理对象的定义，标签分发协议（LDP）”，RFC 3815，2004年6月。
[LSRMIB] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)", RFC 3813, June 2004.
[LSRMIB]Srinivasan，C.，Viswanathan，A.，和T.Nadeau，“多协议标签交换（MPLS）标签交换路由器（LSR）管理信息库（MIB）”，RFC 38132004年6月。
[RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group MIB ", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholtz，“接口组MIB”，RFC 28632000年6月。
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information Base for the Differentiated Services Architecture", RFC 3289, May 2002.
[RFC3289]Baker，F.，Chan，K.和A.Smith，“差异化服务体系结构的管理信息库”，RFC 3289，2002年5月。
[TCMIB] Nadeau, T. and J. Cucchiara, "Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management", RFC 3811, June 2004.
[TCMIB]Nadeau，T.和J.Cucchiara，“多协议标签交换（MPLS）管理的文本约定（TC）定义”，RFC 3811，2004年6月。
[TELMIB] Dubuc, M., Dharanikota, S., Nadeau, T., J. Lang, "Traffic Engineering Link Management Information Base", RFC 4220, November 2005.
[TELMIB]Dubuc，M.，Dharanikota，S.，Nadeau，T.，J.Lang，“交通工程链路管理信息库”，RFC 4220，2005年11月。
[TEMIB] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)", RFC 3812, June 2004.
[TEMIB]Srinivasan，C.，Viswanathan，A.，和T.Nadeau，“多协议标签交换（MPLS）流量工程（TE）管理信息库（MIB）”，RFC 3812，2004年6月。
[PPVPNFW] Callon, R. and M. Suzuki, "A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)", RFC 4110, July 2005.
[PPVPNFW]Callon，R.和M.Suzuki，“第三层提供商提供的虚拟专用网络（PPVPN）框架”，RFC 4110，2005年7月。
[PWE3FW] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture", RFC 3985, March 2005.
[PWE3FW]Bryant，S.和P.Pate，“伪线仿真边到边（PWE3）架构”，RFC 39852005年3月。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[RFC2547Bis] Rosen, E., et al., "MPLS/BGP VPNs", Work in Progress, October 2002.
[RFC2547Bis]Rosen，E.等人，“MPLS/BGP VPN”，正在进行的工作，2002年10月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“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月。
[RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. Thomas, "LDP Specification", RFC 3036, January 2001.
[RFC3036]Andersson，L.，Doolan，P.，Feldman，N.，Fredette，A.，和B.Thomas，“LDP规范”，RFC 3036，2001年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月。
[RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network Management Protocol (SNMP) Applications", STD 62, RFC 3413, December 2002.
[RFC3413]Levi，D.，Meyer，P.，和B.Stewart，“简单网络管理协议（SNMP）应用”，STD 62，RFC 3413，2002年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月。
[TEWGMIB] Kompella, K., "A Traffic Engineering (TE) MIB", RFC 3970, January 2005.
[TEWGMIB]Kompella，K.，“交通工程（TE）MIB”，RFC 39702005年1月。
[VPNMIB] Nadeau, T., et al., "MPLS/BGP Virtual Private Network Management Information Base Using SMIv2", Work in Progress, November 2002.
[VPNMIB]Nadeau，T.等人，“使用SMIv2的MPLS/BGP虚拟专用网络管理信息库”，正在进行的工作，2002年11月。
[VPNTCMIB] Schliesser, B. and T. Nadeau, "Definition of Textual Conventions for Provider Provisioned Virtual Private Network (PPVPN) Management", Work in Progress, November 2002.
[VPNTCMIB]Schliesser，B.和T.Nadeau，“供应商提供的虚拟专用网络（PPVPN）管理文本约定的定义”，正在进行的工作，2002年11月。
Authors' Addresses
作者地址
Thomas D. Nadeau Cisco Systems, Inc. 1414 Massachusetts Ave. Boxborough, MA 01719
Thomas D.Nadeau Cisco Systems，Inc.马萨诸塞州Boxborough大道1414号，邮编01719
EMail: tnadeau@cisco.com
EMail: tnadeau@cisco.com
Cheenu Srinivasan Bloomberg L.P. 731 Lexington Avenue New York, NY 10022
Cheenu Srinivasan Bloomberg L.P.纽约州莱克星顿大道731号，邮编10022
Phone: (212) 617-3682 EMail: cheenu@bloomberg.net
电话：（212）617-3682电子邮件：cheenu@bloomberg.net
Adrian Farrel Old Dog Consulting
阿德里安·法雷尔老狗咨询公司
Phone: +44 (0) 1978 860944
EMail: adrian@olddog.co.uk
Phone: +44 (0) 1978 860944
EMail: adrian@olddog.co.uk
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。