Network Working Group T. Nadeau, Ed.
Request for Comment: 4803 Cisco Systems, Inc.
Category: Standards Track A. Farrel, Ed.
Old Dog Consulting
February 2007
Network Working Group T. Nadeau, Ed.
Request for Comment: 4803 Cisco Systems, Inc.
Category: Standards Track A. Farrel, Ed.
Old Dog Consulting
February 2007
Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base
通用多协议标签交换（GMPLS）标签交换路由器（LSR）管理信息库
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects to configure and/or monitor a Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR).
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于配置和/或监视通用多协议标签交换（GMPLS）标签交换路由器（LSR）的托管对象。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Migration Strategy .........................................2
2. Terminology .....................................................3
3. The Internet-Standard Management Framework ......................4
4. Outline .........................................................5
4.1. MIB Modules ................................................5
4.1.1. Summary of the GMPLS-LSR-STD-MIB Module .............5
4.1.2. Summary of the GMPLS-LABEL-STD-MIB Module ...........5
4.2. Configuring Statically Provisioned LSPs ....................5
5. Bidirectional LSPs ..............................................6
6. Example of LSP Setup ............................................7
7. GMPLS Label Switching Router MIB Definitions ...................11
8. GMPLS Label MIB Definitions ....................................22
9. Security Considerations ........................................36
10. Acknowledgments ...............................................37
11. IANA Considerations ...........................................38
12. References ....................................................38
12.1. Normative References .....................................38
12.2. Informative References ...................................40
1. Introduction ....................................................2
1.1. Migration Strategy .........................................2
2. Terminology .....................................................3
3. The Internet-Standard Management Framework ......................4
4. Outline .........................................................5
4.1. MIB Modules ................................................5
4.1.1. Summary of the GMPLS-LSR-STD-MIB Module .............5
4.1.2. Summary of the GMPLS-LABEL-STD-MIB Module ...........5
4.2. Configuring Statically Provisioned LSPs ....................5
5. Bidirectional LSPs ..............................................6
6. Example of LSP Setup ............................................7
7. GMPLS Label Switching Router MIB Definitions ...................11
8. GMPLS Label MIB Definitions ....................................22
9. Security Considerations ........................................36
10. Acknowledgments ...............................................37
11. IANA Considerations ...........................................38
12. References ....................................................38
12.1. Normative References .....................................38
12.2. Informative References ...................................40
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling a Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] Label Switching Router (LSR).
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于建模通用多协议标签交换（GMPLS）[RFC3945]标签交换路由器（LSR）的托管对象。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[RFC2119]中的说明进行解释。
MPLS LSRs may be modeled and managed using the MPLS-LSR-STD-MIB module [RFC3813].
可以使用MPLS-LSR-STD-MIB模块[RFC3813]对MPLS LSR进行建模和管理。
LSRs may be migrated to be modeled and managed using the MIB modules in this document in order to migrate the LSRs to GMPLS support, or to take advantage of additional MIB objects defined in these MIB modules that are applicable to MPLS-TE.
为了将LSR迁移到GMPLS支持，或利用这些MIB模块中定义的适用于MPLS-TE的附加MIB对象，可以使用本文档中的MIB模块对LSR进行建模和管理。
The GMPLS LSR MIB module (GMPLS-LSR-STD-MIB), defined in this document, extends the MPLS-LSR-STD-MIB module [RFC3813] through a series of sparse augmentations of the MIB tables. The only additions are for support of GMPLS or to support the increased complexity of MPLS and GMPLS systems.
本文件中定义的GMPLS LSR MIB模块（GMPLS-LSR-STD-MIB）通过MIB表的一系列稀疏扩充扩展了MPLS-LSR-STD-MIB模块[RFC3813]。唯一的补充是支持GMPLS或支持MPLS和GMPLS系统的复杂性增加。
In order to migrate from MPLS-LSR-STD-MIB support to GMPLS-LSR-STD-MIB support, an implementation needs only to add support for the additional tables and objects defined in GMPLS-LSR-STD-MIB. The gmplsInterfaceSignalingCaps object allows an implementation to use the objects and tables of GMPLS-LSR-STD-MIB without supporting the GMPLS protocols.
为了从MPLS-LSR-STD-MIB支持迁移到GMPLS-LSR-STD-MIB支持，实现只需添加对GMPLS-LSR-STD-MIB中定义的附加表和对象的支持。gmplsInterfaceSignalingCaps对象允许实现在不支持GMPLS协议的情况下使用GMPLS-LSR-STD-MIB的对象和表。
The GMPLS Label MIB module (GMPLS-LABEL-STD-MIB), also defined in this document, allows labels to be configured and examined, and it supports more varieties of labels as appropriate for GMPLS. Labels may be referenced using a row pointer from objects within the GMPLS-LSR-STD-MIB module. MPLS implementations (MPLS-LSR-STD-MIB) may also reference labels held in the GMPLS-LABEL-STD-MIB module through the various label pointer objects in the MPLS-LSR-STD-MIB module (such as mplsInSegmentLabelPtr), and may do so without implementing the GMPLS-LSR-STD-MIB module.
本文件中还定义了GMPLS标签MIB模块（GMPLS-Label-STD-MIB），该模块允许配置和检查标签，并支持更多种类的标签（适用于GMPLS）。可以使用GMPLS-LSR-STD-MIB模块内对象的行指针引用标签。MPLS实现（MPLS-LSR-STD-MIB）还可以通过MPLS-LSR-STD-MIB模块（例如mplsInSegmentLabelPtr）中的各种标签指针对象引用GMPLS-LABEL-STD-MIB模块中保存的标签，并且可以在不实现GMPLS-LSR-STD-MIB模块的情况下这样做。
The companion document modeling and managing GMPLS-based traffic engineering [RFC4802] extends the MPLS-TE-STD-MIB module [RFC3812] with the same intentions.
配套文件《基于GMPLS的流量工程建模和管理》[RFC4802]以同样的意图扩展了MPLS-TE-STD-MIB模块[RFC3812]。
Textual conventions are defined in [RFC4801], which extends the set of textual conventions originally defined in [RFC3811].
文本约定在[RFC4801]中定义，它扩展了[RFC3811]中最初定义的文本约定集。
This document uses terminology from the document describing the MPLS architecture [RFC3031] and the GMPLS architecture [RFC3945].
本文件使用描述MPLS体系结构[RFC3031]和GMPLS体系结构[RFC3945]的文件中的术语。
A Label Switched Path (LSP) is modeled as a connection consisting of one or more incoming segments (in-segments) and/or one or more outgoing segments (out-segments) at an LSR. The association or interconnection of the in-segments and out-segments is accomplished by using a cross-connect. We use the terminology "connection" and "LSP" interchangeably where the meaning is clear from the context.
标签交换路径（LSP）被建模为在LSR处由一个或多个输入段（in段）和/或一个或多个输出段（out段）组成的连接。通过使用交叉连接来实现输入段和输出段的关联或互连。我们可以互换使用术语“连接”和“LSP”，从上下文中可以清楚地理解其含义。
in-segment This is analogous to a GMPLS Label on an interface.
在段中，这类似于接口上的GMPLS标签。
out-segment This is analogous to a GMPLS Label on an interface.
out段这类似于接口上的GMPLS标签。
cross-connect This describes the conceptual connection between a set of in-segments and out-segments. Note that either set may be empty; for example, a cross-connect may connect only out-segments together with no in-segments in the case where an LSP originates on an LSR.
交叉连接这描述了一组输入段和输出段之间的概念连接。请注意，任何一个集合都可能为空；例如，在LSP源于LSR的情况下，交叉连接可以仅连接out段而不连接in段。
The terms 'ingress' and 'head-end' (or 'head') are used in this document to indicate the signaling source of an LSP. This is sometimes also referred to as the 'sender'.
本文件中使用术语“入口”和“前端”（或“前端”）来表示LSP的信令源。这有时也称为“发送者”。
The terms 'egress' and 'tail-end' (or 'tail') are used in this document to indicate the signaling destination of an LSP.
本文件中使用术语“出口”和“尾端”（或“尾端”）来指示LSP的信令目的地。
The term 'upstream' is used in this document to refer to the part of an LSP that is closer to the ingress than the current point of reference.
本文件中的术语“上游”是指LSP中比当前参考点更靠近入口的部分。
The term 'downstream' is used in this document to refer to the part of an LSP that is closer to the egress than the current point of reference.
本文件中的术语“下游”是指LSP中比当前参考点更靠近出口的部分。
The term 'forward' is used in this document to indicate the direction of data flow from the ingress toward the egress.
本文件中使用术语“向前”表示数据流从入口流向出口的方向。
The term 'reverse' is used in this document to indicate the direction of data flow from the egress toward the ingress.
本文件中使用术语“反向”表示数据流从出口流向入口的方向。
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 memo 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]所述。
There are two MIB modules defined in this document.
本文档中定义了两个MIB模块。
The GMPLS-LSR-STD-MIB module contains tables that sparse augment tables defined in the MPLS-LSR-STD-MIB module [RFC3813]. This MIB module is used in conjunction with the MPLS-LSR-STD-MIB module [RFC3813] in systems that support GMPLS.
GMPLS-LSR-STD-MIB模块包含在MPLS-LSR-STD-MIB模块[RFC3813]中定义的稀疏扩充表。在支持GMPLS的系统中，此MIB模块与MPLS-LSR-STD-MIB模块[RFC3813]一起使用。
The GMPLS-LABEL-STD-MIB module contains objects for managing GMPLS Labels when they cannot be represented using the textual conventions of the MPLS-TC-STD-MIB module [RFC3811], or when more detailed access to the sub-fields of the labels is required.
当无法使用MPLS-TC-STD-MIB模块[RFC3811]的文本约定表示GMPLS标签时，或者当需要更详细地访问标签的子字段时，GMPLS-LABEL-STD-MIB模块包含用于管理GMPLS标签的对象。
The MIB tables in the GMPLS-LSR-STD-MIB module are as follows:
GMPLS-LSR-STD-MIB模块中的MIB表如下所示：
- The interface configuration table (gmplsInterfaceTable) sparse augments the mplsInterfaceTable [RFC3813] to enable the GMPLS protocol on MPLS-capable interfaces.
- 接口配置表（gmplsInterfaceTable）稀疏地扩充了mplsInterfaceTable[RFC3813]，以便在支持MPLS的接口上启用GMPLS协议。
- The in-segment (gmplsInSegmentTable) and out-segment (gmplsOutSegmentTable) tables sparse augment mplsInSegmentTable and mplsOutSegmentTable [RFC3813] to enable configuration of GMPLS-specific parameters for LSP segments at an LSR.
- 段内（gmplsInSegmentTable）和段外（gmplsOutSegmentTable）表格稀疏地扩充mplsInSegmentTable和MPLSSoutSegmentTable[RFC3813]，以便在LSR上为LSP段配置GMPLS特定参数。
These tables are described in the subsequent sections.
这些表格将在后续章节中介绍。
There is one MIB table in the GMPLS-LABEL-STD-MIB module as follows:
GMPLS-LABEL-STD-MIB模块中有一个MIB表，如下所示：
- The gmplsLabelTable allows Generalized Labels to be defined and managed in a central location. Generalized Labels can be of variable length and have distinct bit-by-bit interpretations depending upon how they are defined for the specific technology in which they are used. For example, labels used for MPLS packet switching are different in length and content from labels used in Time Division Multiplexer (TDM) timeslot switching.
- gmplsLabelTable允许在中心位置定义和管理通用标签。通用标签的长度可以是可变的，并且具有不同的逐位解释，这取决于它们是如何为使用它们的特定技术定义的。例如，用于MPLS分组交换的标签在长度和内容上与用于时分多路复用器（TDM）时隙交换的标签不同。
Configuring statically provisioned GMPLS LSPs through an LSR involves the following steps:
通过LSR配置静态配置的GMPLS LSP包括以下步骤：
- Configuring an interface using the MPLS-LSR-STD-MIB module [RFC3813].
- 使用MPLS-LSR-STD-MIB模块配置接口[RFC3813]。
- Enabling GMPLS on GMPLS-capable interfaces using the GMPLS-LSR-STD-MIB module in this document.
- 使用本文件中的GMPLS-LSR-STD-MIB模块在支持GMPLS的接口上启用GMPLS。
- Configuring in-segments and out-segments using the MPLS-LSR-STD-MIB module [RFC3813].
- 使用MPLS-LSR-STD-MIB模块配置入段和出段[RFC3813]。
- Configuring GMPLS extensions to the in-segments and out-segments using the GMPLS-LSR-STD-MIB module in this document.
- 使用本文档中的GMPLS-LSR-STD-MIB模块，为输入段和输出段配置GMPLS扩展。
- Setting up the cross-connect table in the MPLS-LSR-STD-MIB module [RFC3813] to associate segments and/or to indicate connection origination and termination.
- 在MPLS-LSR-STD-MIB模块[RFC3813]中设置交叉连接表，以关联段和/或指示连接起始和终止。
- Optionally setting up labels in the label table in the GMPLS-LABEL-STD-MIB module in this document if the textual convention MplsLabel [RFC3811] is not capable of holding the required label (for example, if the label requires more than 32 bits to encode it), or if the operator wishes to disambiguate GMPLS Label types.
- 如果文本约定MplsLabel[RFC3811]无法保存所需标签（例如，如果标签需要超过32位来编码），或者如果操作员希望消除GMPLS标签类型的歧义，则可以选择在本文档中GMPLS-label-STD-MIB模块的标签表中设置标签。
- Optionally specifying label stack actions in the MPLS-LSR-STD-MIB module [RFC3813].
- 可选地指定MPLS-LSR-STD-MIB模块[RFC3813]中的标签堆栈操作。
- Optionally specifying segment traffic parameters in the MPLS-LSR-STD-MIB module [RFC3813].
- 可选地指定MPLS-LSR-STD-MIB模块[RFC3813]中的段流量参数。
The GMPLS-LSR-STD-MIB module supports bidirectional LSPs as required for GMPLS. A single value of mplsXCIndex is shared by all of the segments for the entire bidirectional LSP. This facilitates a simple reference from [RFC3812] and [RFC4802] and makes fate-sharing more obvious.
GMPLS-LSR-STD-MIB模块支持GMPLS所需的双向LSP。整个双向LSP的所有段共享单个mplsXCIndex值。这有助于对[RFC3812]和[RFC4802]进行简单的引用，并使命运共享更加明显。
It is, however, important that the direction of segments is understood to avoid connecting all in-segments to all out-segments. This is achieved by an object in each segment that indicates the direction of the segment with respect to data flow.
但是，重要的是要理解段的方向，以避免将所有入段连接到所有出段。这是通过每个段中的一个对象来实现的，该对象指示段相对于数据流的方向。
A segment that is marked as 'forward' carries data from the 'head' of the LSP to the 'tail'. A segment marked as 'reverse' carries data in the reverse direction.
标记为“前进”的段将数据从LSP的“头部”传送到“尾部”。标记为“反向”的段以反向传输数据。
Where an LSP is signaled using a conventional signaling protocol, the 'head' of the LSP is the source of the signaling (also known as the ingress) and the 'tail' is the destination (also known as the egress). For manually configured LSPs, an arbitrary decision must be made about which segments are 'forward' and which 'reverse'. For consistency, this decision should be made across all LSRs that participate in the LSP by assigning 'head' and 'tail' ends to the LSP.
在使用常规信令协议向LSP发送信令的情况下，LSP的“头”是信令的源（也称为入口），而“尾”是目的地（也称为出口）。对于手动配置的LSP，必须对哪些段是“正向”和哪些段是“反向”做出任意决定。为保持一致性，应通过将“头”和“尾”端分配给LSP，在参与LSP的所有LSR中做出此决定。
In this section, we provide a brief example of using the MIB objects described in sections 7 and 8 to set up an LSP. While this example is not meant to illustrate every nuance of the MIB modules, it is intended as an aid to understanding some of the key concepts. It is meant to be read after going through the MIB modules themselves. A prerequisite is an understanding of the MPLS-LSR-STD-MIB module [RFC3813].
在本节中，我们提供了一个使用第7节和第8节中描述的MIB对象来设置LSP的简单示例。虽然这个例子并不是要说明MIB模块的每一个细微差别，但它旨在帮助理解一些关键概念。这意味着要在通过MIB模块本身后读取。先决条件是了解MPLS-LSR-STD-MIB模块[RFC3813]。
Suppose that one would like to manually create a best-effort, bidirectional LSP. Assume that, in the forward direction, the LSP enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR via MPLS interface B with ifIndex 13. For the reverse direction, we assume that the LSP enters via interface B and leaves via interface A (i.e., the forward and reverse directions use the same bidirectional interfaces). Let us also assume that we do not wish to have a label stack beneath the top label on the outgoing labeled packets. The following example illustrates which rows and corresponding objects might be created to accomplish this.
假设您想手动创建一个尽力而为的双向LSP。假设在前进方向上，LSP通过MPLS接口A和ifIndex 12进入LSR，并通过MPLS接口B和ifIndex 13退出LSR。对于反向，我们假设LSP通过接口B进入，通过接口A离开（即，正向和反向使用相同的双向接口）。让我们也假设我们不希望在带标签的传出数据包的顶部标签下有标签堆栈。下面的示例说明了可以创建哪些行和相应的对象来实现这一点。
We must first create rows in the gmplsLabelTable corresponding to the labels required for each of the forward- and reverse-direction in-and out-segments. For the purpose of this example, the forward and reverse labels on each interface will be the same, hence we need to create just two rows in the gmplsLabelTable - one for each interface.
我们必须首先在gmplsLabelTable中创建与每个正向和反向输入和输出段所需的标签对应的行。在本例中，每个接口上的正向和反向标签是相同的，因此我们只需要在gmplsLabelTable中创建两行，每个接口一行。
In gmplsLabelTable:
{
gmplsLabelInterface = 12,
gmplsLabelIndex = 1,
gmplsLabelSubindex = 0,
gmplsLabelType = gmplsFreeformLabel(3),
gmplsLabelFreeform = 0x123456789ABCDEF0
gmplsLabelRowStatus = createAndGo(4)
}
In gmplsLabelTable:
{
gmplsLabelInterface = 12,
gmplsLabelIndex = 1,
gmplsLabelSubindex = 0,
gmplsLabelType = gmplsFreeformLabel(3),
gmplsLabelFreeform = 0x123456789ABCDEF0
gmplsLabelRowStatus = createAndGo(4)
}
In gmplsLabelTable:
{
gmplsLabelInterface = 13,
gmplsLabelIndex = 1,
gmplsLabelSubindex = 0,
gmplsLabelType = gmplsFreeformLabel(3),
gmplsLabelFreeform = 0xFEDCBA9876543210
gmplsLabelRowStatus = createAndGo(4)
}
In gmplsLabelTable:
{
gmplsLabelInterface = 13,
gmplsLabelIndex = 1,
gmplsLabelSubindex = 0,
gmplsLabelType = gmplsFreeformLabel(3),
gmplsLabelFreeform = 0xFEDCBA9876543210
gmplsLabelRowStatus = createAndGo(4)
}
We must next create the appropriate in-segment and out-segment entries. These are done in [RFC3813] using the mplsInSegmentTable and mplsOutSegmentTable. Note that we use a row pointer to the two rows in the gmplsLabelTable rather than specify the labels explicitly in the in- and out-segment tables. Also note that the row status for each row is set to createAndWait(5) to allow corresponding entries in the gmplsInSegmentTable and gmplsOutSegmentTable to be created.
接下来，我们必须创建适当的段内和段外条目。这些都是在[RFC3813]中使用mplsInSegmentTable和mplsOutSegmentTable完成的。注意，我们使用一个指向gmplsLabelTable中两行的行指针，而不是在in-segment表和out-segment表中显式指定标签。还要注意，每行的行状态设置为createAndWait（5），以允许创建GMPLSINSEMENTTABLE和gmplsOutSegmentTable中的相应条目。
For the forward direction.
为了前进的方向。
In mplsInSegmentTable:
{
mplsInSegmentIndex = 0x00000015
mplsInSegmentLabel = 0, -- incoming label in label table
mplsInSegmentNPop = 1,
mplsInSegmentInterface = 12, -- incoming interface
In mplsInSegmentTable:
{
mplsInSegmentIndex = 0x00000015
mplsInSegmentLabel = 0, -- incoming label in label table
mplsInSegmentNPop = 1,
mplsInSegmentInterface = 12, -- incoming interface
-- RowPointer MUST point to the first accessible column.
mplsInSegmentTrafficParamPtr = 0.0,
mplsInSegmentLabelPtr = gmplsLabelTable(12,1,0)
mplsInSegmentRowStatus = createAndWait(5)
}
-- RowPointer MUST point to the first accessible column.
mplsInSegmentTrafficParamPtr = 0.0,
mplsInSegmentLabelPtr = gmplsLabelTable(12,1,0)
mplsInSegmentRowStatus = createAndWait(5)
}
In mplsOutSegmentTable:
{
mplsOutSegmentIndex = 0x00000012,
mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 0, -- outgoing label in label table
In mplsOutSegmentTable:
{
mplsOutSegmentIndex = 0x00000012,
mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 0, -- outgoing label in label table
-- RowPointer MUST point to the first accessible column.
mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentLabelPtr = gmplsLabelTable(13,1,0)
mplsOutSegmentRowStatus = createAndWait(5)
}
-- RowPointer MUST point to the first accessible column.
mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentLabelPtr = gmplsLabelTable(13,1,0)
mplsOutSegmentRowStatus = createAndWait(5)
}
For the reverse direction.
相反的方向。
In mplsInSegmentTable:
{
mplsInSegmentIndex = 0x00000016
mplsInSegmentLabel = 0, -- incoming label in label table
mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface
In mplsInSegmentTable:
{
mplsInSegmentIndex = 0x00000016
mplsInSegmentLabel = 0, -- incoming label in label table
mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface
-- RowPointer MUST point to the first accessible column. mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentLabelPtr = gmplsLabelTable(13,1,0)
--行指针必须指向第一个可访问的列。mplsInSegmentTrafficParamPtr=0.0，mplsInSegmentLabelPtr=gmplsLabelTable（13,1,0）
mplsInSegmentRowStatus = createAndWait(5) }
mplsInSegmentRowStatus=createAndWait（5）}
In mplsOutSegmentTable:
{
mplsOutSegmentIndex = 0x00000013,
mplsOutSegmentInterface = 12, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 0, -- outgoing label in label table
In mplsOutSegmentTable:
{
mplsOutSegmentIndex = 0x00000013,
mplsOutSegmentInterface = 12, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 0, -- outgoing label in label table
-- RowPointer MUST point to the first accessible column.
mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentLabelPtr = gmplsLabelTable(12,1,0)
mplsOutSegmentRowStatus = createAndWait(5)
}
-- RowPointer MUST point to the first accessible column.
mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentLabelPtr = gmplsLabelTable(12,1,0)
mplsOutSegmentRowStatus = createAndWait(5)
}
These table entries are extended by entries in the gmplsInSegmentTable and gmplsOutSegmentTable. Note that the nature of the 'extends' relationship is a sparse augmentation so that the entry in the gmplsInSegmentTable has the same index values as the entry in the mplsInSegmentTable. Similarly, the entry in the gmplsOutSegmentTable has the same index values as the entry in the mplsOutSegmentTable.
这些表项由GMPLSINSEMENTTABLE和gmplsOutSegmentTable中的项扩展。请注意，“extends”关系的本质是稀疏扩充，因此gmplsinsegmentable中的条目与mplsinsegmentable中的条目具有相同的索引值。类似地，gmplsOutSegmentTable中的条目与mplsOutSegmentTable中的条目具有相同的索引值。
First for the forward direction:
首先是前进方向：
In gmplsInSegmentTable(0x00000015)
{
gmplsInSegmentDirection = forward(1)
}
In gmplsInSegmentTable(0x00000015)
{
gmplsInSegmentDirection = forward(1)
}
In gmplsOutSegmentTable(0x00000012)
{
gmplsOutSegmentDirection = forward(1)
}
In gmplsOutSegmentTable(0x00000012)
{
gmplsOutSegmentDirection = forward(1)
}
Next for the reverse direction:
下一步为反向：
In gmplsInSegmentTable(0x00000016)
{
gmplsInSegmentDirection = reverse(2)
}
In gmplsInSegmentTable(0x00000016)
{
gmplsInSegmentDirection = reverse(2)
}
In gmplsOutSegmentTable(0x00000013)
{
gmplsOutSegmentDirection = reverse(2)
}
In gmplsOutSegmentTable(0x00000013)
{
gmplsOutSegmentDirection = reverse(2)
}
Next, two cross-connect entries are created in the mplsXCTable of the MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created segments together.
接下来，在MPLS-LSR-STD-MIB[RFC3813]的mplsXCTable中创建两个交叉连接条目，从而将新创建的段关联在一起。
In mplsXCTable:
{
mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000015,
mplsXCOutSegmentIndex = 0x00000012,
mplsXCLspId = 0x0102 -- unique ID
mplsXCLabelStackIndex = 0x00, -- only a single outgoing label
mplsXCRowStatus = createAndGo(4)
}
In mplsXCTable:
{
mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000015,
mplsXCOutSegmentIndex = 0x00000012,
mplsXCLspId = 0x0102 -- unique ID
mplsXCLabelStackIndex = 0x00, -- only a single outgoing label
mplsXCRowStatus = createAndGo(4)
}
In mplsXCTable:
{
mplsXCIndex = 0x02,
mplsXCInSegmentIndex = 0x00000016,
mplsXCOutSegmentIndex = 0x00000013,
mplsXCLspId = 0x0102 -- unique ID
mplsXCLabelStackIndex = 0x00, -- only a single outgoing label
mplsXCRowStatus = createAndGo(4)
}
In mplsXCTable:
{
mplsXCIndex = 0x02,
mplsXCInSegmentIndex = 0x00000016,
mplsXCOutSegmentIndex = 0x00000013,
mplsXCLspId = 0x0102 -- unique ID
mplsXCLabelStackIndex = 0x00, -- only a single outgoing label
mplsXCRowStatus = createAndGo(4)
}
Finally, the in-segments and out-segments are activated.
最后，将激活输入段和输出段。
In mplsInSegmentTable(0x00000015):
{
mplsInSegmentRowStatus = active(1)
}
In mplsInSegmentTable(0x00000016):
{
mplsInSegmentRowStatus = active(1)
}
In mplsInSegmentTable(0x00000015):
{
mplsInSegmentRowStatus = active(1)
}
In mplsInSegmentTable(0x00000016):
{
mplsInSegmentRowStatus = active(1)
}
In mplsOutSegmentTable(0x00000012):
{
mplsOutSegmentRowStatus = active(1)
}
In mplsOutSegmentTable(0x00000012):
{
mplsOutSegmentRowStatus = active(1)
}
In mplsOutSegmentTable(0x00000013):
{
mplsOutSegmentRowStatus = active(1)
}
In mplsOutSegmentTable(0x00000013):
{
mplsOutSegmentRowStatus = active(1)
}
This MIB module makes reference to the following documents: [RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC3209], [RFC3443], [RFC3468], [RFC3472], [RFC3473], [RFC3811], [RFC3813], and [RFC4801].
此MIB模块参考以下文档：[RFC2578]、[RFC2579]、[RFC2580]、[RFC2863]、[RFC3209]、[RFC3443]、[RFC3468]、[RFC3472]、[RFC3473]、[RFC3811]、[RFC3813]和[RFC4801]。
GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN
GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, zeroDotZero FROM SNMPv2-SMI -- RFC 2578 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 RowPointer FROM SNMPv2-TC -- RFC 2579 GmplsSegmentDirectionTC FROM GMPLS-TC-STD-MIB -- RFC 4801 mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex, mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup FROM MPLS-LSR-STD-MIB -- RFC 3813 ifGeneralInformationGroup, ifCounterDiscontinuityGroup FROM IF-MIB -- RFC 2863 mplsStdMIB FROM MPLS-TC-STD-MIB -- RFC 3811 ;
从SNMPv2 SMI导入MODULE-IDENTITY、OBJECT-TYPE、Unsigned32、zeroDotZero——从SNMPv2 CONF导入RFC 2578 MODULE-COMPLIANCE、OBJECT-GROUP——从SNMPv2 TC导入RFC 2580行指针——从GMPLS-TC-STD-MIB导入RFC 2579 GmplsSegmentDirectionTC——RFC 4801 mplsInterfaceIndex、mplsInSegmentIndex、mplsOutSegmentIndex、mplsInterfaceGroup、mplsInSegmentGroup、，MPLS-LSR-STD-MIB中的MPLSutSegmentGroup、MPLSXCGGroup、mplsPerfGroup、MPLSLRNotificationGroup--RFC 3813 IFGeneralInformation Group、IF-MIB中的IFCounterInterructionGroup--MPLS-TC-STD-MIB中的RFC 2863 MPLSTDMIB--RFC 3811；
gmplsLsrStdMIB MODULE-IDENTITY LAST-UPDATED "200702270000Z" -- 27 February 2007 00:00:00 GMT ORGANIZATION "IETF Common Control And Measurement Plane (CCAMP) Working Group" CONTACT-INFO " Thomas D. Nadeau Cisco Systems, Inc. Email: tnadeau@cisco.com Adrian Farrel Old Dog Consulting
gmplsLsrStdMIB MODULE-IDENTITY上次更新“20070227000Z”-2007年2月27日00:00:00 GMT组织“IETF通用控制和测量平面（CCAMP）工作组”联系方式“Thomas D.Nadeau Cisco Systems，Inc.电子邮件：tnadeau@cisco.com阿德里安·法雷尔老狗咨询公司
Email: adrian@olddog.co.uk
Comments about this document should be emailed directly to the
CCAMP working group mailing list at ccamp@ops.ietf.org."
Email: adrian@olddog.co.uk
Comments about this document should be emailed directly to the
CCAMP working group mailing list at ccamp@ops.ietf.org."
DESCRIPTION "Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4803; see the RFC itself for full legal notices.
描述“IETF信托（2007）版权所有。此MIB模块的此版本是RFC 4803的一部分；有关完整的法律通知，请参阅RFC本身。
This MIB module contains managed object definitions for the
Generalized Multiprotocol (GMPLS) Label Switching Router as
defined in Generalized Multi-Protocol Label Switching (GMPLS)
Architecture, Mannie et al., RFC 3945, October 2004."
REVISION
"200702270000Z" -- 27 February 2007 00:00:00 GMT
DESCRIPTION
"Initial version issued as part of RFC 4803."
::= { mplsStdMIB 15 }
This MIB module contains managed object definitions for the
Generalized Multiprotocol (GMPLS) Label Switching Router as
defined in Generalized Multi-Protocol Label Switching (GMPLS)
Architecture, Mannie et al., RFC 3945, October 2004."
REVISION
"200702270000Z" -- 27 February 2007 00:00:00 GMT
DESCRIPTION
"Initial version issued as part of RFC 4803."
::= { mplsStdMIB 15 }
-- no notifications are currently defined.
gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 }
gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 }
-- no notifications are currently defined.
gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 }
gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 }
gmplsInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies per-interface GMPLS capability and
associated information. It extends the information in the
mplsInterfaceTable of MPLS-LSR-STD-MIB through a
sparse augmentation relationship."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { gmplsLsrObjects 1 }
gmplsInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies per-interface GMPLS capability and
associated information. It extends the information in the
mplsInterfaceTable of MPLS-LSR-STD-MIB through a
sparse augmentation relationship."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { gmplsLsrObjects 1 }
gmplsInterfaceEntry OBJECT-TYPE SYNTAX GmplsInterfaceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in this table is created automatically by an LSR for each interface that is both capable of supporting GMPLS and configured to support GMPLS. Note that support of GMPLS is not limited to control plane signaling, but may include data-plane-only function configured through SNMP SET commands performed on this MIB module.
gmplsInterfaceEntry对象类型语法gmplsInterfaceEntry MAX-ACCESS不可访问状态当前说明“此表中的一个概念行由LSR为每个接口自动创建，该接口既能够支持GMPLS，又配置为支持GMPLS。请注意，GMPLS的支持不限于控制平面信令，但可能包括通过在此MIB模块上执行的SNMP SET命令配置的仅数据平面功能。
A conceptual row in this table may also be created via SNMP SET commands or automatically by the LSR to supplement a conceptual row in the mplsInterfaceTable where the interface is not capable of GMPLS but where the other objects carried in this row provide useful additional information for an MPLS interface.
此表中的概念行也可以通过SNMP SET命令创建，或由LSR自动创建，以补充MPLSINTERFACTABLE中的概念行，其中接口不能使用GMPLS，但此行中包含的其他对象为MPLS接口提供了有用的附加信息。
A conceptual row in this table will exist if and only if a corresponding entry in the mplsInterfaceTable exists, and a corresponding entry in the ifTable exists with ifType = mpls(166). If the associated entry in the ifTable is operationally disabled (thus removing the GMPLS capabilities on the interface) or the entry in the mplsInterfaceTable is deleted, the corresponding entry in this table MUST be deleted shortly thereafter.
当且仅当mplsInterfaceTable中存在对应条目，且ifType=mpls（166）中存在ifTable中的对应条目时，此表中的概念行才会存在。如果ifTable中的关联条目在操作上被禁用（从而删除接口上的GMPLS功能），或者mplsInterfaceTable中的条目被删除，则必须在此后不久删除此表中的相应条目。
The indexes are the same as for the mplsInterfaceTable. Thus, the
entry with index 0 represents the per-platform label space and
contains parameters that apply to all interfaces that
participate in the per-platform label space."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
INDEX { mplsInterfaceIndex }
::= { gmplsInterfaceTable 1 }
The indexes are the same as for the mplsInterfaceTable. Thus, the
entry with index 0 represents the per-platform label space and
contains parameters that apply to all interfaces that
participate in the per-platform label space."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
INDEX { mplsInterfaceIndex }
::= { gmplsInterfaceTable 1 }
GmplsInterfaceEntry ::= SEQUENCE {
gmplsInterfaceSignalingCaps BITS,
gmplsInterfaceRsvpHelloPeriod Unsigned32
}
GmplsInterfaceEntry ::= SEQUENCE {
gmplsInterfaceSignalingCaps BITS,
gmplsInterfaceRsvpHelloPeriod Unsigned32
}
gmplsInterfaceSignalingCaps OBJECT-TYPE
SYNTAX BITS {
unknown(0),
rsvpGmpls(1),
crldpGmpls(2), -- note the use of CR-LDP is deprecated
otherGmpls(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines the signaling capabilities on this interface. Multiple
bits may legitimately be set at once, but if 'unknown' is set
then no other bit may be set. Setting no bits implies that GMPLS
signaling cannot be performed on this interface and all LSPs
must be manually provisioned or that this table entry is only
present to supplement an entry in the mplsInterfaceTable by
providing the information carried in other objects in this row."
REFERENCE
gmplsInterfaceSignalingCaps OBJECT-TYPE
SYNTAX BITS {
unknown(0),
rsvpGmpls(1),
crldpGmpls(2), -- note the use of CR-LDP is deprecated
otherGmpls(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines the signaling capabilities on this interface. Multiple
bits may legitimately be set at once, but if 'unknown' is set
then no other bit may be set. Setting no bits implies that GMPLS
signaling cannot be performed on this interface and all LSPs
must be manually provisioned or that this table entry is only
present to supplement an entry in the mplsInterfaceTable by
providing the information carried in other objects in this row."
REFERENCE
"1. Generalized MPLS Signaling - CR-LDP Extensions, RFC 3472.
2. The Multiprotocol Label Switching (MPLS) Working Group
decision on MPLS signaling protocols, RFC 3468.
3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473."
DEFVAL { { rsvpGmpls } }
::= { gmplsInterfaceEntry 1 }
"1. Generalized MPLS Signaling - CR-LDP Extensions, RFC 3472.
2. The Multiprotocol Label Switching (MPLS) Working Group
decision on MPLS signaling protocols, RFC 3468.
3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473."
DEFVAL { { rsvpGmpls } }
::= { gmplsInterfaceEntry 1 }
gmplsInterfaceRsvpHelloPeriod OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Period, in milliseconds, between sending Resource Reservation Protocol (RSVP) Hello messages on this interface. A value of 0 indicates that no Hello messages should be sent on this interface.
gmplsInterfaceRsvpHelloPeriod对象类型语法Unsigned32个单位“毫秒”MAX-ACCESS read create STATUS current DESCRIPTION“在此接口上发送资源保留协议（RSVP）Hello消息之间的周期（以毫秒为单位）。值0表示不应在此接口上发送Hello消息。
This object is only valid if gmplsInterfaceSignalingCaps has no
bits set or includes the rsvpGmpls bit."
REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
section 5.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 9.3."
DEFVAL { 3000 }
::= { gmplsInterfaceEntry 2 }
This object is only valid if gmplsInterfaceSignalingCaps has no
bits set or includes the rsvpGmpls bit."
REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
section 5.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 9.3."
DEFVAL { 3000 }
::= { gmplsInterfaceEntry 2 }
gmplsInSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInSegmentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table sparse augments the mplsInSegmentTable of
MPLS-LSR-STD-MIB to provide GMPLS-specific information about
incoming segments to an LSR."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { gmplsLsrObjects 2 }
gmplsInSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInSegmentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table sparse augments the mplsInSegmentTable of
MPLS-LSR-STD-MIB to provide GMPLS-specific information about
incoming segments to an LSR."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { gmplsLsrObjects 2 }
gmplsInSegmentEntry OBJECT-TYPE SYNTAX GmplsInSegmentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table extends the representation of an incoming segment represented by an entry in the mplsInSegmentTable in
gmplsInSegmentEntry对象类型语法gmplsInSegmentEntry MAX-ACCESS不可访问状态当前描述“此表中的条目扩展了中mplsInSegmentTable中的条目表示的传入段的表示形式
MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be created by a network administrator via SNMP SET commands, or in response to signaling protocol events.
通过稀疏扩充实现MPLS-LSR-STD-MIB。网络管理员可以通过SNMP SET命令或响应信令协议事件创建条目。
Note that the storage type for this entry is given by the value
of mplsInSegmentStorageType in the corresponding entry of the
mplsInSegmentTable."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
INDEX { mplsInSegmentIndex }
::= { gmplsInSegmentTable 1 }
Note that the storage type for this entry is given by the value
of mplsInSegmentStorageType in the corresponding entry of the
mplsInSegmentTable."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
INDEX { mplsInSegmentIndex }
::= { gmplsInSegmentTable 1 }
GmplsInSegmentEntry ::= SEQUENCE {
gmplsInSegmentDirection GmplsSegmentDirectionTC,
gmplsInSegmentExtraParamsPtr RowPointer
}
GmplsInSegmentEntry ::= SEQUENCE {
gmplsInSegmentDirection GmplsSegmentDirectionTC,
gmplsInSegmentExtraParamsPtr RowPointer
}
gmplsInSegmentDirection OBJECT-TYPE
SYNTAX GmplsSegmentDirectionTC
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the direction of data flow on this
segment. This object cannot be modified if
mplsInSegmentRowStatus for the corresponding entry in the
mplsInSegmentTable is active(1)."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
DEFVAL { forward }
::= { gmplsInSegmentEntry 1 }
gmplsInSegmentDirection OBJECT-TYPE
SYNTAX GmplsSegmentDirectionTC
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the direction of data flow on this
segment. This object cannot be modified if
mplsInSegmentRowStatus for the corresponding entry in the
mplsInSegmentTable is active(1)."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
DEFVAL { forward }
::= { gmplsInSegmentEntry 1 }
gmplsInSegmentExtraParamsPtr OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Some tunnels will run over transports that can usefully support
technology-specific additional parameters (for example,
Synchronous Optical Network (SONET) resource usage). Such can be
supplied from an external table and referenced from here. A value
of zeroDotZero in this attribute indicates that there is no such
additional information."
DEFVAL { zeroDotZero }
::= { gmplsInSegmentEntry 2 }
gmplsInSegmentExtraParamsPtr OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Some tunnels will run over transports that can usefully support
technology-specific additional parameters (for example,
Synchronous Optical Network (SONET) resource usage). Such can be
supplied from an external table and referenced from here. A value
of zeroDotZero in this attribute indicates that there is no such
additional information."
DEFVAL { zeroDotZero }
::= { gmplsInSegmentEntry 2 }
gmplsOutSegmentTable OBJECT-TYPE
gmplsOutSegmentTable对象类型
SYNTAX SEQUENCE OF GmplsOutSegmentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table sparse augments the mplsOutSegmentTable of
MPLS-LSR-STD-MIB to provide GMPLS-specific information about
outgoing segments from an LSR."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { gmplsLsrObjects 3 }
SYNTAX SEQUENCE OF GmplsOutSegmentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table sparse augments the mplsOutSegmentTable of
MPLS-LSR-STD-MIB to provide GMPLS-specific information about
outgoing segments from an LSR."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
::= { gmplsLsrObjects 3 }
gmplsOutSegmentEntry OBJECT-TYPE SYNTAX GmplsOutSegmentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table extends the representation of an outgoing segment represented by an entry in the mplsOutSegmentTable of MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be created by a network administrator via SNMP SET commands, or in response to signaling protocol events.
gmplsOutSegmentEntry对象类型语法gmplsOutSegmentEntry MAX-ACCESS不可访问状态当前说明“此表中的条目通过稀疏扩充扩展了MPLS-LSR-STD-MIB的mplsOutSegmentTable中的条目表示的传出段的表示。网络管理员可以通过SNMP SET命令或响应信令协议事件创建条目。
Note that the storage type for this entry is given by the value
of mplsOutSegmentStorageType in the corresponding entry of the
mplsOutSegmentTable."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
INDEX { mplsOutSegmentIndex }
::= { gmplsOutSegmentTable 1 }
Note that the storage type for this entry is given by the value
of mplsOutSegmentStorageType in the corresponding entry of the
mplsOutSegmentTable."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
INDEX { mplsOutSegmentIndex }
::= { gmplsOutSegmentTable 1 }
GmplsOutSegmentEntry ::= SEQUENCE {
gmplsOutSegmentDirection GmplsSegmentDirectionTC,
gmplsOutSegmentTTLDecrement Unsigned32,
gmplsOutSegmentExtraParamsPtr RowPointer
}
GmplsOutSegmentEntry ::= SEQUENCE {
gmplsOutSegmentDirection GmplsSegmentDirectionTC,
gmplsOutSegmentTTLDecrement Unsigned32,
gmplsOutSegmentExtraParamsPtr RowPointer
}
gmplsOutSegmentDirection OBJECT-TYPE SYNTAX GmplsSegmentDirectionTC MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the direction of data flow on this segment. This object cannot be modified if mplsOutSegmentRowStatus for the corresponding entry in the mplsOutSegmentTable is active(1)." REFERENCE
gmplsOutSegmentDirection对象类型语法GMPLSOutSegmentDirectionTC MAX-ACCESS read create STATUS current DESCRIPTION“此对象指示此段上的数据流方向。如果mplsOutSegmentTable中相应项的mplsOutSegmentRowStatus处于活动状态（1），则无法修改此对象。”
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
DEFVAL { forward }
::= { gmplsOutSegmentEntry 1 }
"1. Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB), RFC 3813."
DEFVAL { forward }
::= { gmplsOutSegmentEntry 1 }
gmplsOutSegmentTTLDecrement OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the amount by which to decrement the Time to Live (TTL) of any payload packets forwarded on this segment if per-hop decrementing is being done.
gmplsOutSegmentTTLDecrement对象类型语法Unsigned32 MAX-ACCESS read create STATUS current DESCRIPTION“此对象表示如果正在进行每跳递减，则减少在此段上转发的任何有效负载数据包的生存时间（TTL）的量。
A value of zero indicates that no decrement should be made or that per-hop decrementing is not in use.
值为零表示不应进行递减或未使用每跳递减。
See the gmplsTunnelTTLDecrement object in the gmplsTunnelTable of GMPLS-TE-STD-MIB for a value by which to decrement the TTL for the whole of a tunnel.
请参阅GMPLS-TE-STD-MIB的gmplsTunnelTable中的GMPLSTunneltLtdreduction对象，了解用于减少整个隧道的TTL的值。
This object cannot be modified if mplsOutSegmentRowStatus for
the associated entry in the mplsOutSegmentTable is active(1)."
REFERENCE
"1. Time To Live (TTL) Processing in Multi-Protocol Label
Switching (MPLS) Networks, RFC 3443.
2. Generalized Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base, RFC 4802."
DEFVAL { 0 }
::= { gmplsOutSegmentEntry 2 }
This object cannot be modified if mplsOutSegmentRowStatus for
the associated entry in the mplsOutSegmentTable is active(1)."
REFERENCE
"1. Time To Live (TTL) Processing in Multi-Protocol Label
Switching (MPLS) Networks, RFC 3443.
2. Generalized Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base, RFC 4802."
DEFVAL { 0 }
::= { gmplsOutSegmentEntry 2 }
gmplsOutSegmentExtraParamsPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "Some tunnels will run over transports that can usefully support technology-specific additional parameters (for example, SONET resource usage). Such can be supplied from an external table and referenced from here.
gmplsOutSegmentExtraParamsPtr对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“一些隧道将运行在传输上，这些传输可以有效地支持特定于技术的附加参数（例如，SONET资源使用）。这些参数可以从外部表提供并从此处引用。
A value of zeroDotZero in this attribute indicates that there is
no such additional information."
DEFVAL { zeroDotZero }
::= { gmplsOutSegmentEntry 3 }
A value of zeroDotZero in this attribute indicates that there is
no such additional information."
DEFVAL { zeroDotZero }
::= { gmplsOutSegmentEntry 3 }
gmplsLsrGroups
OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 }
gmplsLsrGroups
OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 }
gmplsLsrCompliances
OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 }
gmplsLsrCompliances
OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 }
-- Compliance requirement for fully compliant implementations.
--完全合规实施的合规性要求。
gmplsLsrModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that provide full support for GMPLS-LSR-STD-MIB.
GMPLSLSRModulerCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“为GMPLS-LSR-STD-MIB提供全面支持的代理的合规声明。
The mandatory group has to be implemented by all LSRs that originate, terminate, or act as transit for TE-LSPs/tunnels. In addition, depending on the type of tunnels supported, other groups become mandatory as explained below."
强制组必须由发起、终止或作为TE LSP/隧道中转的所有LSR实施。此外，根据支持的隧道类型，其他组成为强制性组，如下所述。”
MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863.
模块IF-MIB——接口组MIB，RFC 2863。
MANDATORY-GROUPS {
ifGeneralInformationGroup,
ifCounterDiscontinuityGroup
}
MANDATORY-GROUPS {
ifGeneralInformationGroup,
ifCounterDiscontinuityGroup
}
MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813
模块MPLS-LSR-STD-MIB——MPLS-LSR-STD-MIB，RFC3813
MANDATORY-GROUPS {
mplsInterfaceGroup,
mplsInSegmentGroup,
mplsOutSegmentGroup,
mplsXCGroup,
mplsPerfGroup,
mplsLsrNotificationGroup
}
MANDATORY-GROUPS {
mplsInterfaceGroup,
mplsInSegmentGroup,
mplsOutSegmentGroup,
mplsXCGroup,
mplsPerfGroup,
mplsLsrNotificationGroup
}
MODULE -- this module
模块——这个模块
MANDATORY-GROUPS {
gmplsInterfaceGroup,
gmplsInSegmentGroup,
gmplsOutSegmentGroup
}
MANDATORY-GROUPS {
gmplsInterfaceGroup,
gmplsInSegmentGroup,
gmplsOutSegmentGroup
}
OBJECT gmplsInSegmentDirection SYNTAX GmplsSegmentDirectionTC MIN-ACCESS read-only DESCRIPTION "The only valid value for unidirectional LSPs is forward(1)."
对象gmplsInSegmentDirection语法GmplsSegmentDirectionTC MIN-ACCESS只读说明“单向LSP的唯一有效值为forward（1）”
OBJECT gmplsOutSegmentDirection SYNTAX GmplsSegmentDirectionTC MIN-ACCESS read-only DESCRIPTION "The only valid value for unidirectional LSPs is forward(1)."
对象gmplsOutSegmentDirection语法GMPLSSSegmentDirectionTC MIN-ACCESS只读说明“单向LSP的唯一有效值为forward（1）”
OBJECT gmplsOutSegmentTTLDecrement MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsOutSegmentTTLDecrement最小访问只读描述“不需要写访问。”
OBJECT gmplsInSegmentExtraParamsPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT gmplsOutSegmentExtraParamsPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象GMPLSINSEMENTEXTRAPARAMSPTR MIN-ACCESS只读说明“不需要写访问”。对象gmplsOutSegmentExtraParamsPtr MIN-ACCESS只读说明“不需要写访问。”
::= { gmplsLsrCompliances 1 }
::= { gmplsLsrCompliances 1 }
-- Compliance requirement for implementations that provide read-only
-- access.
-- Compliance requirement for implementations that provide read-only
-- access.
gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that only provide read-only support for GMPLS-LSR-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module."
gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS当前描述“仅为GMPLS-LSR-STD-MIB提供只读支持的实施的合规性要求。然后可以监控此类设备，但不能使用此MIB模块进行配置。”
MODULE IF-MIB -- The interfaces Group MIB, RFC 2863
模块IF-MIB——接口组MIB，RFC 2863
MANDATORY-GROUPS {
ifGeneralInformationGroup,
ifCounterDiscontinuityGroup
}
MANDATORY-GROUPS {
ifGeneralInformationGroup,
ifCounterDiscontinuityGroup
}
MODULE MPLS-LSR-STD-MIB
模块MPLS-LSR-STD-MIB
MANDATORY-GROUPS {
mplsInterfaceGroup,
mplsInSegmentGroup,
mplsOutSegmentGroup,
mplsXCGroup,
mplsPerfGroup
}
MANDATORY-GROUPS {
mplsInterfaceGroup,
mplsInSegmentGroup,
mplsOutSegmentGroup,
mplsXCGroup,
mplsPerfGroup
}
MODULE -- this module
模块——这个模块
MANDATORY-GROUPS {
gmplsInterfaceGroup,
gmplsInSegmentGroup,
gmplsOutSegmentGroup
}
MANDATORY-GROUPS {
gmplsInterfaceGroup,
gmplsInSegmentGroup,
gmplsOutSegmentGroup
}
OBJECT gmplsInterfaceSignalingCaps MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsInterfaceSignalingCaps最小访问只读描述“不需要写访问。”
OBJECT gmplsInterfaceRsvpHelloPeriod MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsInterfaceRsvpHelloPeriod最小访问只读描述“不需要写访问。”
OBJECT gmplsInSegmentDirection SYNTAX GmplsSegmentDirectionTC MIN-ACCESS read-only DESCRIPTION "The only valid value for unidirectional LSPs is forward(1)."
对象gmplsInSegmentDirection语法GmplsSegmentDirectionTC MIN-ACCESS只读说明“单向LSP的唯一有效值为forward（1）”
OBJECT gmplsInSegmentExtraParamsPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsInSegmentExtraParamsPtr MIN-ACCESS只读描述“不需要写访问。”
OBJECT gmplsOutSegmentDirection MIN-ACCESS read-only DESCRIPTION "The only valid value for unidirectional LSPs is forward(1)."
对象gmplsOutSegmentDirection最小访问只读说明“单向LSP的唯一有效值为forward（1）”
OBJECT gmplsOutSegmentTTLDecrement MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT gmplsOutSegmentExtraParamsPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsOutSegmentTTLDecrement最小访问只读描述“不需要写访问”。对象gmplsOutSegmentExtraParamsPtr最小访问只读描述“不需要写访问”
::= { gmplsLsrCompliances 2 }
::= { gmplsLsrCompliances 2 }
gmplsInterfaceGroup OBJECT-GROUP OBJECTS { gmplsInterfaceSignalingCaps,
gmplsInterfaceGroup对象组对象{gmplsInterfaceSignalingCaps，
gmplsInterfaceRsvpHelloPeriod
}
STATUS current
DESCRIPTION
"Collection of objects that provide additional
information for an MPLS interface and are needed
for GMPLS interface configuration and performance
information."
::= { gmplsLsrGroups 1 }
gmplsInterfaceRsvpHelloPeriod
}
STATUS current
DESCRIPTION
"Collection of objects that provide additional
information for an MPLS interface and are needed
for GMPLS interface configuration and performance
information."
::= { gmplsLsrGroups 1 }
gmplsInSegmentGroup OBJECT-GROUP
OBJECTS {
gmplsInSegmentDirection,
gmplsInSegmentExtraParamsPtr
}
STATUS current
DESCRIPTION
"Collection of objects that provide additional
information for an MPLS in-segment and are needed
for GMPLS in-segment configuration and performance
information."
::= { gmplsLsrGroups 2 }
gmplsInSegmentGroup OBJECT-GROUP
OBJECTS {
gmplsInSegmentDirection,
gmplsInSegmentExtraParamsPtr
}
STATUS current
DESCRIPTION
"Collection of objects that provide additional
information for an MPLS in-segment and are needed
for GMPLS in-segment configuration and performance
information."
::= { gmplsLsrGroups 2 }
gmplsOutSegmentGroup OBJECT-GROUP
OBJECTS {
gmplsOutSegmentDirection,
gmplsOutSegmentTTLDecrement,
gmplsOutSegmentExtraParamsPtr
}
STATUS current
DESCRIPTION
"Collection of objects that provide additional
information for an MPLS out-segment and are needed
for GMPLS out-segment configuration and performance
information."
::= { gmplsLsrGroups 3 }
END
gmplsOutSegmentGroup OBJECT-GROUP
OBJECTS {
gmplsOutSegmentDirection,
gmplsOutSegmentTTLDecrement,
gmplsOutSegmentExtraParamsPtr
}
STATUS current
DESCRIPTION
"Collection of objects that provide additional
information for an MPLS out-segment and are needed
for GMPLS out-segment configuration and performance
information."
::= { gmplsLsrGroups 3 }
END
This MIB module makes reference to the following documents: [RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC3032], [RFC3289], [RFC3471], [RFC3811], and [RFC4801].
此MIB模块参考以下文档：[RFC2578]、[RFC2579]、[RFC2580]、[RFC2863]、[RFC3032]、[RFC3289]、[RFC3471]、[RFC3811]和[RFC4801]。
GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN
GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Integer32 FROM SNMPv2-SMI -- RFC 2578 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 RowStatus, StorageType FROM SNMPv2-TC -- RFC 2579 InterfaceIndexOrZero FROM IF-MIB -- RFC 2863 IndexIntegerNextFree FROM DIFFSERV-MIB -- RFC 3289 MplsLabel, mplsStdMIB FROM MPLS-TC-STD-MIB -- RFC 3811 GmplsLabelTypeTC, GmplsFreeformLabelTC FROM GMPLS-TC-STD-MIB -- RFC 4801 ;
从SNMPv2 SMI导入MODULE-IDENTITY、OBJECT-TYPE、Unsigned32、Integer32--从SNMPv2 CONF导入RFC 2578 MODULE-COMPLIANCE、从SNMPv2 CONF导入OBJECT-GROUP--从RFC 2580 RowStatus导入RFC 2579 InterfaceIndexOrZero--从IF-MIB导入RFC 2863 IndexIntegerNextFree，从DIFFSERV-MIB导入RFC 3289 MPLSabel，来自MPLS-TC-STD-MIB的mplsStdMIB——RFC 3811 GmplsLabelTypeTC，来自GMPLS-TC-STD-MIB的GmplsFreeformLabelTC——RFC 4801；
gmplsLabelStdMIB MODULE-IDENTITY LAST-UPDATED "200702270000Z" -- 27 February 2007 00:00:00 GMT ORGANIZATION "IETF Common Control and Measurement Plane (CCAMP) Working Group" CONTACT-INFO " Thomas D. Nadeau Cisco Systems, Inc. Email: tnadeau@cisco.com
gmplsLabelStdMIB MODULE-IDENTITY上次更新的“20070227000Z”-2007年2月27日00:00:00 GMT组织“IETF通用控制和测量平面（CCAMP）工作组”联系方式“Thomas D.Nadeau Cisco Systems，Inc.电子邮件：tnadeau@cisco.com
Adrian Farrel Old Dog Consulting Email: adrian@olddog.co.uk
Adrian Farrel老狗咨询电子邮件：adrian@olddog.co.uk
Comments about this document should be emailed directly to the CCAMP working group mailing list at ccamp@ops.ietf.org."
有关本文件的意见应通过电子邮件直接发送至CCAMP工作组邮件列表，地址为ccamp@ops.ietf.org."
DESCRIPTION "Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4803; see the RFC itself for full legal notices.
描述“IETF信托（2007）版权所有。此MIB模块的此版本是RFC 4803的一部分；有关完整的法律通知，请参阅RFC本身。
This MIB module contains managed object definitions for labels
within GMPLS systems as defined in
Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, Berger, L. (Editor), RFC 3471,
January 2003."
REVISION
"200702270000Z" -- 27 February 2007 00:00:00 GMT
DESCRIPTION
"Initial version issued as part of RFC 4803."
::= { mplsStdMIB 16 }
This MIB module contains managed object definitions for labels
within GMPLS systems as defined in
Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, Berger, L. (Editor), RFC 3471,
January 2003."
REVISION
"200702270000Z" -- 27 February 2007 00:00:00 GMT
DESCRIPTION
"Initial version issued as part of RFC 4803."
::= { mplsStdMIB 16 }
-- no notifications are currently defined.
--当前未定义任何通知。
gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 }
gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 }
gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 }
gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 }
gmplsLabelIndexNext OBJECT-TYPE SYNTAX IndexIntegerNextFree MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains an unused value for gmplsLabelIndex, or a zero to indicate that no unused value exists or is available.
gmplsLabelIndexNext对象类型语法IndexIntegerNextFree MAX-ACCESS只读状态当前描述“此对象包含gmplsLabelIndex的未使用值，或零表示不存在或不可用未使用值。
A management application wishing to create a row in the gmplsLabelTable may read this object and then attempt to create a row in the table. If row creation fails (because another application has already created a row with the supplied index), the management application should read this object again to get a new index value.
希望在gmplsLabelTable中创建行的管理应用程序可以读取此对象，然后尝试在表中创建行。如果行创建失败（因为另一个应用程序已使用提供的索引创建了行），管理应用程序应再次读取此对象以获取新的索引值。
When a row is created in the gmplsLabelTable with the
gmplsLabelIndex value held by this object, an implementation
MUST change the value in this object."
::= { gmplsLabelObjects 1 }
When a row is created in the gmplsLabelTable with the
gmplsLabelIndex value held by this object, an implementation
MUST change the value in this object."
::= { gmplsLabelObjects 1 }
gmplsLabelTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsLabelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table of GMPLS Labels. This table allows the representation of the more complex label forms required for GMPLS that cannot be held within the TEXTUAL-CONVENTION MplsLabel; that is, labels that cannot be encoded within 32 bits. It is, nevertheless, also capable of holding 32-bit labels or regular MPLS Labels if desired.
GmplsLabelEntry MAX-ACCESS的gmplsLabelTable对象类型语法序列不可访问状态当前描述“GMPLS标签表。此表允许表示GMPLS所需的更复杂的标签形式，这些形式不能保存在文本约定MplsLabel中；也就是说，不能在32位内编码的标签。然而，如果需要，它也能够保存32位标签或常规MPLS标签。
Each entry in this table represents an individual GMPLS Label value. The representation of Labels in tables in other MIB modules may be achieved by a referrence to an entry in this table by means of a row pointer into this table. The indexing of this table provides for arbitrary indexing and also for concatenation of labels.
此表中的每个条目代表一个单独的GMPLS标签值。其他MIB模块中的表中标签的表示可以通过使用该表中的行指针引用该表中的条目来实现。此表的索引提供了任意索引和标签连接。
For an example of label concatenation, see RFC 3945, section 7.1. In essence, a GMPLS Label may be composite in order to identify a set of resources in the data plane. Practical examples are timeslots and wavelength sets (which are not contiguous like wavebands).
有关标签连接的示例，请参见RFC 3945，第7.1节。本质上，GMPLS标签可以是复合的，以便识别数据平面中的一组资源。实际例子是时隙和波长集（它们不像波段那样是连续的）。
The indexing mechanism allows multiple entries in this table to
be seen as a sequence of labels that should be concatenated.
Ordering is potentially very sensitive for concatenation."
REFERENCE
"1. Generalized Multiprotocol Label Switching (GMPLS)
Architecture, RFC 3945, section 7.1."
::= { gmplsLabelObjects 2 }
The indexing mechanism allows multiple entries in this table to
be seen as a sequence of labels that should be concatenated.
Ordering is potentially very sensitive for concatenation."
REFERENCE
"1. Generalized Multiprotocol Label Switching (GMPLS)
Architecture, RFC 3945, section 7.1."
::= { gmplsLabelObjects 2 }
gmplsLabelEntry OBJECT-TYPE SYNTAX GmplsLabelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a single label value. There are three indexes into the table.
gmplsLabelEntry对象类型语法gmplsLabelEntry MAX-ACCESS not ACCESS STATUS current DESCRIPTION“此表中的条目表示单个标签值。此表中有三个索引。
- The interface index may be helpful to distinguish which labels are in use on which interfaces or to handle cases where there are a very large number of labels in use in the system. When label representation is desired to apply to the whole system or when it is not important to distinguish labels by their interfaces, this index MAY be set to zero.
- 接口索引可能有助于区分哪些标签在哪些接口上使用，或者处理系统中使用大量标签的情况。当需要将标签表示应用于整个系统时，或当通过标签的接口区分标签不重要时，此索引可设置为零。
- The label index provides a way of identifying the label.
- 标签索引提供了标识标签的方法。
- The label sub-index is only used for concatenated labels. It identifies each component label. When non-concatenated labels are used, this index SHOULD be set to zero.
- 标签子索引仅用于连接的标签。它标识每个组件标签。使用非连接标签时，此索引应设置为零。
A storage type object is supplied to control the storage type for each entry, but implementations should note that the storage type of conceptual rows in other tables that include row pointers to an entry in this table SHOULD dictate the storage type of the rows in this table where the row in the other table is more persistent."
提供了一个存储类型对象来控制每个条目的存储类型，但实现时应注意，其他表中概念行的存储类型（包括指向此表中某个条目的行指针）应指示此表中的行的存储类型，其中另一个表中的行更持久。”
INDEX {
gmplsLabelInterface,
gmplsLabelIndex,
gmplsLabelSubindex }
::= { gmplsLabelTable 1 }
INDEX {
gmplsLabelInterface,
gmplsLabelIndex,
gmplsLabelSubindex }
::= { gmplsLabelTable 1 }
GmplsLabelEntry ::= SEQUENCE {
gmplsLabelInterface InterfaceIndexOrZero,
gmplsLabelIndex Unsigned32,
gmplsLabelSubindex Unsigned32,
gmplsLabelType GmplsLabelTypeTC,
gmplsLabelMplsLabel MplsLabel,
gmplsLabelPortWavelength Unsigned32,
gmplsLabelFreeform GmplsFreeformLabelTC,
gmplsLabelSonetSdhSignalIndex Integer32,
gmplsLabelSdhVc Integer32,
gmplsLabelSdhVcBranch Integer32,
gmplsLabelSonetSdhBranch Integer32,
gmplsLabelSonetSdhGroupBranch Integer32,
gmplsLabelWavebandId Unsigned32,
gmplsLabelWavebandStart Unsigned32,
gmplsLabelWavebandEnd Unsigned32,
gmplsLabelStorageType StorageType,
gmplsLabelRowStatus RowStatus
}
GmplsLabelEntry ::= SEQUENCE {
gmplsLabelInterface InterfaceIndexOrZero,
gmplsLabelIndex Unsigned32,
gmplsLabelSubindex Unsigned32,
gmplsLabelType GmplsLabelTypeTC,
gmplsLabelMplsLabel MplsLabel,
gmplsLabelPortWavelength Unsigned32,
gmplsLabelFreeform GmplsFreeformLabelTC,
gmplsLabelSonetSdhSignalIndex Integer32,
gmplsLabelSdhVc Integer32,
gmplsLabelSdhVcBranch Integer32,
gmplsLabelSonetSdhBranch Integer32,
gmplsLabelSonetSdhGroupBranch Integer32,
gmplsLabelWavebandId Unsigned32,
gmplsLabelWavebandStart Unsigned32,
gmplsLabelWavebandEnd Unsigned32,
gmplsLabelStorageType StorageType,
gmplsLabelRowStatus RowStatus
}
gmplsLabelInterface OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The interface on which this label is used. If this object is set
to zero, the label MUST have applicability across the
whole system and not be limited to a single interface."
::= { gmplsLabelEntry 1 }
gmplsLabelInterface OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The interface on which this label is used. If this object is set
to zero, the label MUST have applicability across the
whole system and not be limited to a single interface."
::= { gmplsLabelEntry 1 }
gmplsLabelIndex OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An arbitrary index into the table to identify a label.
gmplsLabelIndex对象类型语法Unsigned32（0..4294967295）MAX-ACCESS不可访问状态当前描述“将任意索引放入表中以标识标签。
Note that implementations that are representing 32-bit labels within this table MAY choose to align this index with the value of the label, and this may result in the use of the value zero since it represents a valid label value. Such implementation should be aware of the implications of sparsely populated
请注意，在此表中表示32位标签的实现可能会选择将此索引与标签的值对齐，这可能会导致使用值零，因为它表示有效的标签值。此类实施应意识到人口稀少的影响
tables.
桌子。
A management application may read the gmplsLabelIndexNext
object to find a suitable value for this object."
::= { gmplsLabelEntry 2 }
A management application may read the gmplsLabelIndexNext
object to find a suitable value for this object."
::= { gmplsLabelEntry 2 }
gmplsLabelSubindex OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION "In conjunction with gmplsLabelInterface and gmplsLabelIndex, this object uniquely identifies this row. This sub-index allows a single GMPLS Label to be defined as a concatenation of labels. This is particularly useful in TDM.
gmplsLabelSubindex对象类型语法Unsigned32（0..4294967295）MAX-ACCESS not accessible STATUS current DESCRIPTION“结合gmplsLabelInterface和gmplsLabelIndex，此对象唯一标识此行。此子索引允许将单个GMPLS标签定义为标签的串联。这在TDM中特别有用。
The ordering of sub-labels is strict with the sub-label with
the lowest gmplsLabelSubindex appearing first. Note that all
sub-labels of a single GMPLS Label must share the same
gmplsLabelInterface and gmplsLabelIndex values. For labels that
are not composed of concatenated sub-labels, this value SHOULD
be set to zero."
::= { gmplsLabelEntry 3 }
The ordering of sub-labels is strict with the sub-label with
the lowest gmplsLabelSubindex appearing first. Note that all
sub-labels of a single GMPLS Label must share the same
gmplsLabelInterface and gmplsLabelIndex values. For labels that
are not composed of concatenated sub-labels, this value SHOULD
be set to zero."
::= { gmplsLabelEntry 3 }
gmplsLabelType OBJECT-TYPE SYNTAX GmplsLabelTypeTC MAX-ACCESS read-create STATUS current DESCRIPTION "Identifies the type of this label. Note that this object does not determine whether MPLS or GMPLS signaling is in use: a value of gmplsMplsLabel(1) denotes that an MPLS Packet Label is present in the gmplsLabelMplsLabel object and encoded using the MplsLabel TEXTUAL-CONVENTION (may be a 20-bit MPLS Label, a 10- or 23-bit Frame Relay Label, or an Asynchronous Transfer Mode (ATM) Label), but does not describe whether this is signaled using MPLS or GMPLS.
gmplsLabelType对象类型语法GmplsLabelTypeTC MAX-ACCESS read create STATUS current DESCRIPTION“标识此标签的类型。请注意，此对象不确定是否正在使用MPLS或GMPLS信令：GMPLSMPLSLSABLE（1）的值表示MPLS数据包标签存在于GMPLSLabel对象中，并使用MPLSabel文本约定（可以是20位MPLS标签、10位或23位帧中继标签或异步传输模式（ATM）标签）进行编码，但不描述这是使用MPLS还是GMPLS发信号。
The value of this object helps determine which of the following
objects are valid. This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3."
::= { gmplsLabelEntry 4 }
The value of this object helps determine which of the following
objects are valid. This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3."
::= { gmplsLabelEntry 4 }
gmplsLabelMplsLabel OBJECT-TYPE SYNTAX MplsLabel
GMPLSLabel对象类型语法MplsLabel
MAX-ACCESS read-create STATUS current DESCRIPTION "The value of an MPLS Label (that is a Packet Label) if this table is used to store it. This may be used in MPLS systems even though the label values can be adequately stored in the MPLS MIB modules (MPLS-LSR-STD-MIB and MPLS-TE-STD-MIB). Furthermore, in mixed MPLS and GMPLS systems, it may be advantageous to store all labels in a single label table. Lastly, in GMPLS systems where Packet Labels are used (that is in systems that use GMPLS signaling and GMPLS Labels for packet switching), it may be desirable to use this table.
MAX-ACCESS read create STATUS current DESCRIPTION“如果使用此表存储MPLS标签（即数据包标签）的值。即使标签值可以充分存储在MPLS MIB模块（MPLS-LSR-STD-MIB和MPLS-TE-STD-MIB）中，也可以在MPLS系统中使用该值。此外，在混合MPLS和GMPLS系统中，将所有标签存储在单个标签表中可能是有利的。最后，在使用分组标签的GMPLS系统中（即使用GMPLS信令和GMPLS标签进行分组交换的系统中），可能需要使用该表。
This object is only valid if gmplsLabelType is set
to gmplsMplsLabel(1). This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. MPLS Label Stack Encoding, RFC 3032."
DEFVAL { 0 }
::= { gmplsLabelEntry 5 }
This object is only valid if gmplsLabelType is set
to gmplsMplsLabel(1). This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. MPLS Label Stack Encoding, RFC 3032."
DEFVAL { 0 }
::= { gmplsLabelEntry 5 }
gmplsLabelPortWavelength OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of a Port or Wavelength Label when carried as a
Generalized Label. Only valid if gmplsLabelType is set to
gmplsPortWavelengthLabel(2). This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.2.1.1."
DEFVAL { 0 }
::= { gmplsLabelEntry 6 }
gmplsLabelPortWavelength OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of a Port or Wavelength Label when carried as a
Generalized Label. Only valid if gmplsLabelType is set to
gmplsPortWavelengthLabel(2). This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.2.1.1."
DEFVAL { 0 }
::= { gmplsLabelEntry 6 }
gmplsLabelFreeform OBJECT-TYPE SYNTAX GmplsFreeformLabelTC MAX-ACCESS read-create STATUS current DESCRIPTION "The value of a Freeform Generalized Label that does not conform to one of the standardized label encodings or that an implementation chooses to represent as an octet string without further decoding. Only valid if gmplsLabelType is set to gmplsFreeformLabel(3). This object cannot be modified if gmplsLabelRowStatus is active(1)." REFERENCE
gmplsLabelFreeform对象类型语法GmplsFreeformLabelTC MAX-ACCESS读取创建状态当前描述“自由形式的通用标签的值，不符合标准化标签编码之一，或实现选择表示为八位字节字符串而无需进一步解码。仅当gmplsLabelType设置为gmplsFreeformLabel（3）时有效。如果gmplsLabelRowStatus处于活动状态（1），则无法修改此对象。“参考
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.2."
DEFVAL { '00'h }
::= { gmplsLabelEntry 7 }
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.2."
DEFVAL { '00'h }
::= { gmplsLabelEntry 7 }
gmplsLabelSonetSdhSignalIndex OBJECT-TYPE
SYNTAX Integer32 (0..4095)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Signal Index value (S) of a SONET or SDH Generalized Label.
Zero indicates that this field is non-significant. Only valid if
gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5).
This object cannot be modified if gmplsLabelRowStatus is
active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 4606, section 3."
DEFVAL { 0 }
::= { gmplsLabelEntry 8 }
gmplsLabelSonetSdhSignalIndex OBJECT-TYPE
SYNTAX Integer32 (0..4095)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Signal Index value (S) of a SONET or SDH Generalized Label.
Zero indicates that this field is non-significant. Only valid if
gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5).
This object cannot be modified if gmplsLabelRowStatus is
active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 4606, section 3."
DEFVAL { 0 }
::= { gmplsLabelEntry 8 }
gmplsLabelSdhVc OBJECT-TYPE
SYNTAX Integer32 (0..15)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The VC Indicator (U) of an SDH Generalized Label. Zero indicates
that this field is non-significant. Only valid if gmplsLabelType
is set to gmplsSdhLabel(5). This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 4606, section 3."
DEFVAL { 0 }
::= { gmplsLabelEntry 9 }
gmplsLabelSdhVc OBJECT-TYPE
SYNTAX Integer32 (0..15)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The VC Indicator (U) of an SDH Generalized Label. Zero indicates
that this field is non-significant. Only valid if gmplsLabelType
is set to gmplsSdhLabel(5). This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 4606, section 3."
DEFVAL { 0 }
::= { gmplsLabelEntry 9 }
gmplsLabelSdhVcBranch OBJECT-TYPE SYNTAX Integer32 (0..15) MAX-ACCESS read-create STATUS current DESCRIPTION "The VC Branch Indicator (K) of an SDH Generalized Label. Zero indicates that this field is non-significant. Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This object cannot be modified if gmplsLabelRowStatus is active(1)." REFERENCE
gmplsLabelSdhVcBranch对象类型语法整数32（0..15）MAX-ACCESS read create STATUS current DESCRIPTION“SDH通用标签的VC分支指示符（K）。零表示此字段不重要。仅当gmplsLabelType设置为gmplsSdhLabel（5）时有效。如果gmplsLabelRowStatus处于活动状态（1），则无法修改此对象。”参考
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 4606, section 3."
DEFVAL { 0 }
::= { gmplsLabelEntry 10 }
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 4606, section 3."
DEFVAL { 0 }
::= { gmplsLabelEntry 10 }
gmplsLabelSonetSdhBranch OBJECT-TYPE
SYNTAX Integer32 (0..15)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Branch Indicator (L) of a SONET or SDH Generalized Label.
Zero indicates that this field is non-significant. Only valid
gmplsLabelType is set to gmplsSonetLabel(4) or
gmplsSdhLabel(5). This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 4606, section 3."
DEFVAL { 0 }
::= { gmplsLabelEntry 11 }
gmplsLabelSonetSdhBranch OBJECT-TYPE
SYNTAX Integer32 (0..15)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Branch Indicator (L) of a SONET or SDH Generalized Label.
Zero indicates that this field is non-significant. Only valid
gmplsLabelType is set to gmplsSonetLabel(4) or
gmplsSdhLabel(5). This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 4606, section 3."
DEFVAL { 0 }
::= { gmplsLabelEntry 11 }
gmplsLabelSonetSdhGroupBranch OBJECT-TYPE
SYNTAX Integer32 (0..15)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Group Branch Indicator (M) of a SONET or SDH Generalized
Label. Zero indicates that this field is non-significant.
Only valid if gmplsLabelType is set to gmplsSonetLabel(4) or
gmplsSdhLabel(5). This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 4606, section 3."
DEFVAL { 0 }
::= { gmplsLabelEntry 12 }
gmplsLabelSonetSdhGroupBranch OBJECT-TYPE
SYNTAX Integer32 (0..15)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Group Branch Indicator (M) of a SONET or SDH Generalized
Label. Zero indicates that this field is non-significant.
Only valid if gmplsLabelType is set to gmplsSonetLabel(4) or
gmplsSdhLabel(5). This object cannot be modified if
gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 4606, section 3."
DEFVAL { 0 }
::= { gmplsLabelEntry 12 }
gmplsLabelWavebandId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "The waveband identifier component of a Waveband Label. Only valid if gmplsLabelType is set to gmplsWavebandLabel(6). This object cannot be modified if gmplsLabelRowStatus is active(1)."
gmplsLabelWavebandId对象类型语法Unsigned32 MAX-ACCESS read create STATUS current DESCRIPTION“波段标签的波段标识符组件。仅当gmplsLabelType设置为gmplsWavebandLabel（6）时有效。如果gmplsLabelRowStatus处于活动状态（1），则无法修改此对象。”
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.3."
DEFVAL { 0 }
::= { gmplsLabelEntry 13 }
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.3."
DEFVAL { 0 }
::= { gmplsLabelEntry 13 }
gmplsLabelWavebandStart OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The starting label component of a Waveband Label. Only valid if
gmplsLabelType is set to gmplsWavebandLabel(6). This object
cannot be modified if gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.3."
DEFVAL { 0 }
::= { gmplsLabelEntry 14 }
gmplsLabelWavebandStart OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The starting label component of a Waveband Label. Only valid if
gmplsLabelType is set to gmplsWavebandLabel(6). This object
cannot be modified if gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.3."
DEFVAL { 0 }
::= { gmplsLabelEntry 14 }
gmplsLabelWavebandEnd OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The end label component of a Waveband Label. Only valid if
gmplsLabelType is set to gmplsWavebandLabel(6). This object
cannot be modified if gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.3."
DEFVAL { 0 }
::= { gmplsLabelEntry 15 }
gmplsLabelWavebandEnd OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The end label component of a Waveband Label. Only valid if
gmplsLabelType is set to gmplsWavebandLabel(6). This object
cannot be modified if gmplsLabelRowStatus is active(1)."
REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.3."
DEFVAL { 0 }
::= { gmplsLabelEntry 15 }
gmplsLabelStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this row. The agent MUST ensure that this object's value remains consistent with the storage type of any rows in other tables that contain pointers to this row. In particular, the storage type of this row must be at least as permanent as that of any row that points to it. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row." REFERENCE
gmplsLabelStorageType对象类型语法StorageType MAX-ACCESS读取创建状态当前描述“此变量表示此行的存储类型。代理必须确保此对象的值与包含指向此行指针的其他表中任何行的存储类型保持一致。特别是，此行的存储类型必须至少与指向它的任何行的存储类型一样永久。值为“permanent”的概念行不需要允许对该行中的任何列对象进行写访问。“引用
"1. Textual Conventions for SMIv2, STD 58, RFC 2579, section 2."
DEFVAL { volatile }
::= { gmplsLabelEntry 16 }
"1. Textual Conventions for SMIv2, STD 58, RFC 2579, section 2."
DEFVAL { volatile }
::= { gmplsLabelEntry 16 }
gmplsLabelRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table. When a row in this table has a row in the active(1) state, no objects in this row can be modified except the gmplsLabelRowStatus and gmplsLabelStorageType.
gmplsLabelRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此变量用于创建、修改和/或删除此表中的行。当此表中的行具有处于活动（1）状态的行时，除gmplsLabelRowStatus和gmplsLabelStorageType外，无法修改此行中的任何对象。
The gmplsLabelType object does not have a default and must be set before a row can become active. The corresponding label objects (dependent on the value of gmplsLabelType) should also be set unless they happen to need to use the specified default values as follows:
gmplsLabelType对象没有默认值，必须在行变为活动状态之前进行设置。还应设置相应的标签对象（取决于gmplsLabelType的值），除非它们碰巧需要使用指定的默认值，如下所示：
gmplsLabelType setting objects to be set
--------------------------------------------------------------
gmplsMplsLabel(1) gmplsLabelMplsLabel
gmplsLabelType setting objects to be set
--------------------------------------------------------------
gmplsMplsLabel(1) gmplsLabelMplsLabel
gmplsPortWavelengthLabel(2) gmplsLabelPortWavelength
GMPLsSportWavelength标签（2）gmplsLabelPortWavelength
gmplsFreeformLabel(3) gmplsLabelFreeform
gmplsFreeformLabel（3）gmplsLabelFreeform
gmplsSonetLabel(4) gmplsLabelSonetSdhSignalIndex gmplsLabelSdhVc gmplsLabelSdhVcBranch gmplsLabelSonetSdhBranch gmplsLabelSonetSdhGroupBranch
gmplsSonetLabel（4）GMPLSLABELSONETSDH信号索引gmplsLabelSdhVc gmplsLabelSdhVc分支GMPLSLABELSONETSDH分支GMPLSLABELSONETSDH分支GMPLSLABELSONETSDH组分支
gmplsSdhLabel(5) gmplsLabelSonetSdhSignalIndex gmplsLabelSdhVc gmplsLabelSdhVcBranch gmplsLabelSonetSdhBranch gmplsLabelSonetSdhGroupBranch
gmplsSdhLabel（5）GMPLSLABELSONETSDH信号索引gmplsLabelSdhVc gmplsLabelSdhVc分支GMPLSLABELSONETSDH分支GMPLSLABELSONETSDH分支GMPLSLABELSONETSDH组分支
gmplsWavebandLabel(6) gmplsLabelWavebandId
gmplsLabelWavebandStart
gmplsLabelWavebandEnd"
::= { gmplsLabelEntry 17 }
gmplsWavebandLabel(6) gmplsLabelWavebandId
gmplsLabelWavebandStart
gmplsLabelWavebandEnd"
::= { gmplsLabelEntry 17 }
gmplsLabelGroups
OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 }
gmplsLabelGroups
OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 }
gmplsLabelCompliances
OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 }
gmplsLabelCompliances
OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 }
gmplsLabelModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that only provide read-only support for GMPLS-LABEL-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module."
gmplsLabelModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS当前描述“仅为GMPLS-LABEL-STD-MIB提供只读支持的实施的合规要求。然后可以监控此类设备，但不能使用此MIB模块进行配置。”
MODULE -- this module
模块——这个模块
-- The mandatory groups have to be implemented by LSRs claiming
-- support for this MIB module. This MIB module is, however, not
-- mandatory for a working implementation of a GMPLS LSR with full
-- MIB support if the GMPLS Labels in use can be represented within
-- a 32-bit quantity.
-- The mandatory groups have to be implemented by LSRs claiming
-- support for this MIB module. This MIB module is, however, not
-- mandatory for a working implementation of a GMPLS LSR with full
-- MIB support if the GMPLS Labels in use can be represented within
-- a 32-bit quantity.
MANDATORY-GROUPS {
gmplsLabelTableGroup
}
MANDATORY-GROUPS {
gmplsLabelTableGroup
}
GROUP gmplsLabelPacketGroup DESCRIPTION "This group extends gmplsLabelTableGroup for implementations that support Packet Labels. It is optional for implementations that do not support Packet Labels."
GROUP gmplsLabelPacketGroup DESCRIPTION“该组扩展了gmplsLabelTableGroup，用于支持数据包标签的实现。对于不支持数据包标签的实现，它是可选的。”
GROUP gmplsLabelPortWavelengthGroup DESCRIPTION "This group extends gmplsLabelTableGroup for implementations that support Port and Wavelength Labels. It is optional for implementations that do not support Wavelength Labels."
GROUP gmplsLabelPortWavelengthGroup DESCRIPTION“此组扩展了gmplsLabelTableGroup，用于支持端口和波长标签的实现。对于不支持波长标签的实现，它是可选的。”
GROUP gmplsLabelFreeformGroup DESCRIPTION "This group extends gmplsLabelTableGroup for implementations that support Freeform Labels. It is optional for implementations that do not support Freeform Labels."
GROUP gmplsLabelFreeformGroup DESCRIPTION“此组扩展了gmplsLabelTableGroup，用于支持自由格式标签的实现。对于不支持自由格式标签的实现，此组是可选的。”
GROUP gmplsLabelSonetSdhGroup DESCRIPTION "This group extends gmplsLabelTableGroup for implementations that support SONET or SDH Labels. It is optional for implementations that do not support SONET or SDH Labels."
GROUP gmplsLabelSonetSdhGroup DESCRIPTION“此组扩展了gmplsLabelTableGroup，用于支持SONET或SDH标签的实现。对于不支持SONET或SDH标签的实现，它是可选的。”
GROUP gmplsLabelWavebandGroup DESCRIPTION
组gmplsLabelWavebandGroup说明
"This group extends gmplsLabelTableGroup for implementations that support Waveband Labels. It is optional for implementations that do not support Waveband Labels." OBJECT gmplsLabelType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
“此组为支持波段标签的实现扩展了gmplsLabelTableGroup。对于不支持波段标签的实现，它是可选的。对象gmplsLabelType MIN-ACCESS只读说明”不需要写访问。“
OBJECT gmplsLabelMplsLabel MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象GMPLSLABELMPLSABEL MIN-ACCESS只读说明“不需要写访问。”
OBJECT gmplsLabelPortWavelength MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsLabelPortWavelength最小访问只读描述“不需要写访问。”
OBJECT gmplsLabelFreeform MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsLabelFreeform最小访问只读描述“不需要写访问。”
OBJECT gmplsLabelSonetSdhSignalIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsLabelSonetSdhSignalIndex最小访问只读说明“不需要写访问。”
OBJECT gmplsLabelSdhVc MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsLabelSdhVc最小访问只读描述“不需要写访问。”
OBJECT gmplsLabelSdhVcBranch MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象GMPLSLABELSDHVCSBRANCH MIN-ACCESS只读说明“不需要写访问。”
OBJECT gmplsLabelSonetSdhBranch MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象GMPLSLABELSONETSDH分支最小访问只读描述“不需要写访问。”
OBJECT gmplsLabelSonetSdhGroupBranch MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsLabelSonetSdhGroupBranch最小访问只读说明“不需要写访问。”
OBJECT gmplsLabelWavebandId MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT gmplsLabelWavebandStart MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsLabelWavebandId最小访问只读说明“不需要写入访问”。对象gmplsLabelWavebandStart最小访问只读说明“不需要写入访问。”
OBJECT gmplsLabelWavebandEnd MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsLabelWavebandEnd最小访问只读说明“不需要写访问。”
OBJECT gmplsLabelStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象gmplsLabelStorageType MIN-ACCESS只读说明“不需要写访问。”
OBJECT gmplsLabelRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, and active(1) is the only status that needs to be supported."
对象gmplsLabelRowStatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问，而active（1）是唯一需要支持的状态。”
::= { gmplsLabelCompliances 1 }
::= { gmplsLabelCompliances 1 }
gmplsLabelModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that support the complete GMPLS-LABEL-STD-MIB module.
GMPLSLabelModulelCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“支持完整GMPLS-LABEL-STD-MIB模块的代理的合规声明。
The mandatory groups have to be implemented by GMPLS LSRs claiming support for this MIB module. This MIB module is, however, not mandatory for a working implementation of a GMPLS LSR with full MIB support if the GMPLS Labels in use can be represented within a 32-bit quantity."
强制组必须由声称支持此MIB模块的GMPLS LSR实现。但是，如果使用中的GMPLS标签可以在32位数量内表示，则对于具有完全MIB支持的GMPLS LSR的工作实现，此MIB模块不是强制性的。”
MODULE -- this module
模块——这个模块
MANDATORY-GROUPS {
gmplsLabelTableGroup
}
MANDATORY-GROUPS {
gmplsLabelTableGroup
}
::= { gmplsLabelCompliances 2 }
::= { gmplsLabelCompliances 2 }
gmplsLabelTableGroup OBJECT-GROUP
OBJECTS {
gmplsLabelIndexNext,
gmplsLabelType,
gmplsLabelStorageType,
gmplsLabelRowStatus
}
gmplsLabelTableGroup OBJECT-GROUP
OBJECTS {
gmplsLabelIndexNext,
gmplsLabelType,
gmplsLabelStorageType,
gmplsLabelRowStatus
}
STATUS current DESCRIPTION "Necessary, but not sufficient, set of objects to implement label table support. In addition, depending on the type of labels supported, the following other groups defined below are mandatory:
STATUS current DESCRIPTION“需要但不足以实现标签表支持的对象集。此外，根据支持的标签类型，以下定义的其他组是必需的：
gmplsLabelWavebandGroup and/or
gmplsLabelPacketGroup and/or
gmplsLabelPortWavelengthGroup and/or
gmplsLabelFreeformGroup and/or
gmplsLabelSonetSdhGroup."
::= { gmplsLabelGroups 1 }
gmplsLabelWavebandGroup and/or
gmplsLabelPacketGroup and/or
gmplsLabelPortWavelengthGroup and/or
gmplsLabelFreeformGroup and/or
gmplsLabelSonetSdhGroup."
::= { gmplsLabelGroups 1 }
gmplsLabelPacketGroup OBJECT-GROUP
OBJECTS {
gmplsLabelMplsLabel
}
STATUS current
DESCRIPTION
"Object needed to implement Packet (MPLS) Labels."
::= { gmplsLabelGroups 2 }
gmplsLabelPacketGroup OBJECT-GROUP
OBJECTS {
gmplsLabelMplsLabel
}
STATUS current
DESCRIPTION
"Object needed to implement Packet (MPLS) Labels."
::= { gmplsLabelGroups 2 }
gmplsLabelPortWavelengthGroup OBJECT-GROUP
OBJECTS {
gmplsLabelPortWavelength
}
STATUS current
DESCRIPTION
"Object needed to implement Port and Wavelength Labels."
::= { gmplsLabelGroups 3 }
gmplsLabelPortWavelengthGroup OBJECT-GROUP
OBJECTS {
gmplsLabelPortWavelength
}
STATUS current
DESCRIPTION
"Object needed to implement Port and Wavelength Labels."
::= { gmplsLabelGroups 3 }
gmplsLabelFreeformGroup OBJECT-GROUP
OBJECTS {
gmplsLabelFreeform
}
STATUS current
DESCRIPTION
"Object needed to implement Freeform Labels."
::= { gmplsLabelGroups 4 }
gmplsLabelFreeformGroup OBJECT-GROUP
OBJECTS {
gmplsLabelFreeform
}
STATUS current
DESCRIPTION
"Object needed to implement Freeform Labels."
::= { gmplsLabelGroups 4 }
gmplsLabelSonetSdhGroup OBJECT-GROUP
OBJECTS {
gmplsLabelSonetSdhSignalIndex,
gmplsLabelSdhVc,
gmplsLabelSdhVcBranch,
gmplsLabelSonetSdhBranch,
gmplsLabelSonetSdhGroupBranch
}
STATUS current
DESCRIPTION
"Objects needed to implement SONET and SDH Labels."
::= { gmplsLabelGroups 5 }
gmplsLabelSonetSdhGroup OBJECT-GROUP
OBJECTS {
gmplsLabelSonetSdhSignalIndex,
gmplsLabelSdhVc,
gmplsLabelSdhVcBranch,
gmplsLabelSonetSdhBranch,
gmplsLabelSonetSdhGroupBranch
}
STATUS current
DESCRIPTION
"Objects needed to implement SONET and SDH Labels."
::= { gmplsLabelGroups 5 }
gmplsLabelWavebandGroup OBJECT-GROUP
OBJECTS {
gmplsLabelWavebandId,
gmplsLabelWavebandStart,
gmplsLabelWavebandEnd
}
STATUS current
DESCRIPTION
"Objects needed to implement Waveband Labels."
::= { gmplsLabelGroups 6 }
gmplsLabelWavebandGroup OBJECT-GROUP
OBJECTS {
gmplsLabelWavebandId,
gmplsLabelWavebandStart,
gmplsLabelWavebandEnd
}
STATUS current
DESCRIPTION
"Objects needed to implement Waveband Labels."
::= { gmplsLabelGroups 6 }
END
终止
It is clear that the MIB modules described in this document in association with MPLS-LSR-STD-MIB [RFC3813] are potentially useful for monitoring of GMPLS LSRs. These MIB modules can also be used for configuration of certain objects, and anything that can be configured can be incorrectly configured, with potentially disastrous results.
很明显，本文件中描述的与MPLS-LSR-STD-MIB[RFC3813]相关的MIB模块可能对GMPLS LSR的监控有用。这些MIB模块还可以用于配置某些对象，任何可以配置的东西都可能被错误配置，从而导致潜在的灾难性后果。
There are a number of management objects defined in these MIB modules with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability:
在这些MIB模块中定义了许多管理对象，其中MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable, and gmplsLabelTable collectively contain objects to provision GMPLS interfaces, LSPs, and their associated parameters on a Label Switching Router (LSR). Unauthorized write access to objects in these tables could result in disruption of
o gmplsInterfaceTable、gmplsInSegmentTable、gmplsOutSegmentTable和gmplsLabelTable共同包含在标签交换路由器（LSR）上提供GMPLS接口、LSP及其相关参数的对象。对这些表中的对象进行未经授权的写访问可能会中断
traffic on the network. This is especially true if an LSP has already been established.
网络上的流量。如果已建立LSP，则尤其如此。
Some of the readable objects in these MIB modules (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
在某些网络环境中，这些MIB模块中的一些可读对象（即具有MAX-ACCESS而非not ACCESS的对象）可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable, and gmplsLabelTable collectively show the LSP network topology and its capabilities. If an administrator does not want to reveal this information, then these tables should be considered sensitive/vulnerable.
o gmplsInterfaceTable、gmplsInSegmentTable、gmplsOutSegmentTable和gmplsLabelTable共同显示LSP网络拓扑及其功能。如果管理员不想透露此信息，则应将这些表视为敏感/易受攻击。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in these MIB modules.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPsec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）这些MIB模块中的对象。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议实施者考虑SNMPv3框架所提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商有责任确保授予访问此MIB模块实例权限的SNMP实体正确配置为仅授予那些拥有合法权限来获取或设置（更改/创建/删除）对象的主体（用户）访问对象的权限。
This document is a product of the CCAMP Working Group.
本文件是CCAMP工作组的成果。
This document extends the MIB tables in [RFC3813]. The authors would like to express their gratitude to all those who worked on that earlier MIB document.
本文档扩展了[RFC3813]中的MIB表。作者要向所有在早期MIB文档中工作的人表示感谢。
The authors would like to express their thanks to Dan Joyle for his careful review and comments on early versions of the label table. Special thanks to Joan Cucchiara and Len Nieman for their help with
作者要感谢Dan Joyle对标签表早期版本的仔细审查和评论。特别感谢Joan Cucchiara和Len Nieman在这方面的帮助
compilation issues. Lars Eggert, Tom Petch, Dan Romascanu, and Bert Wijnen provided useful input in the final stages of review.
汇编问题。Lars Eggert、Tom Petch、Dan Romascanu和Bert Wijnen在审查的最后阶段提供了有用的信息。
Joan Cucchiara provided a helpful and very thorough MIB Doctor review.
琼·库奇亚拉（Joan Cucchiara）提供了一份有用且非常彻底的MIB医生评估报告。
IANA has rooted MIB objects in the two MIB modules contained in this document under the mplsStdMIB subtree.
IANA在本文档中包含的MPLSTDMIB子树下的两个MIB模块中拥有根MIB对象。
IANA has made the following assignments in the "NETWORK MANAGEMENT PARAMETERS" registry located at http://www.iana.org/assignments/ smi-numbers in table:
IANA在位于的“网络管理参数”注册表中进行了以下分配：http://www.iana.org/assignments/ 表中的smi编号：
...mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166)
…mib-2.transmission.mplsStdMIB（1.3.6.1.2.1.10.166）
Decimal Name References
------- ----- ----------
15 GMPLS-LSR-STD-MIB [RFC4803]
16 GMPLS-LABEL-STD-MIB [RFC4803]
Decimal Name References
------- ----- ----------
15 GMPLS-LSR-STD-MIB [RFC4803]
16 GMPLS-LABEL-STD-MIB [RFC4803]
In the future, GMPLS-related standards-track MIB modules should be rooted under the mplsStdMIB (sic) subtree. IANA has been requested to manage that namespace in the SMI Numbers registry [RFC3811]. New assignments can only be made via a Standards Action as specified in [RFC2434].
将来，GMPLS相关标准跟踪MIB模块应植根于MPLSTDMIB（sic）子树下。已请求IANA在SMI编号注册表[RFC3811]中管理该命名空间。新分配只能通过[RFC2434]中规定的标准行动进行。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年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月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[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月。
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Encoding", RFC 3032, January 2001.
[RFC3032]Rosen，E.，Tappan，D.，Fedorkow，G.，Rekhter，Y.，Farinaci，D.，Li，T.，和A.Conta，“MPLS标签堆栈编码”，RFC 3032，2001年1月。
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, December 2001.
[RFC3209]Awduche，D.，Berger，L.，Gan，D.，Li，T.，Srinivasan，V.，和G.Swallow，“RSVP-TE：LSP隧道RSVP的扩展”，RFC 3209，2001年12月。
[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月。
[RFC3443] Agarwal, P. and B. Akyol, "Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks", RFC 3443, January 2003.
[RFC3443]Agarwal，P.和B.Akyol，“多协议标签交换（MPLS）网络中的生存时间（TTL）处理”，RFC 3443，2003年1月。
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description", RFC 3471, January 2003.
[RFC3471]Berger，L.“通用多协议标签交换（GMPLS）信令功能描述”，RFC 3471，2003年1月。
[RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions", RFC 3473, January 2003.
[RFC3473]Berger，L.“通用多协议标签交换（GMPLS）信令资源预留协议流量工程（RSVP-TE）扩展”，RFC 3473，2003年1月。
[RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management", RFC 3811, June 2004.
[RFC3811]Nadeau，T.和J.Cucchiara，“多协议标签交换（MPLS）管理的文本约定（TC）定义”，RFC 3811，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月。
[RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching (GMPLS) Architecture", RFC 3945, October 2004.
[RFC3945]Mannie，E.“通用多协议标签交换（GMPLS）体系结构”，RFC 39452004年10月。
[RFC4606] Mannie, E. and D. Papadimitriou, "Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control", RFC 4606, August 2006.
[RFC4606]Mannie，E.和D.Papadimitriou，“同步光网络（SONET）和同步数字体系（SDH）控制的通用多协议标签交换（GMPLS）扩展”，RFC 4606，2006年8月。
[RFC4801] Nadeau, T., Ed. and A. Farrel, Ed., "Definitions of Textual Conventions for Multiprotocol Label Switching (MPLS) Management", RFC 4801, February 2007.
[RFC4801]Nadeau，T.，Ed.和A.Farrel，Ed.，“多协议标签交换（MPLS）管理的文本约定定义”，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月。
[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月。
[RFC3468] Andersson, L. and G. Swallow, "The Multiprotocol Label Switching (MPLS) Working Group decision on MPLS signaling protocols", RFC 3468, February 2003.
[RFC3468]Andersson，L.和G.Swallow，“多协议标签交换（MPLS）工作组关于MPLS信令协议的决定”，RFC 3468，2003年2月。
[RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions", RFC 3472, January 2003.
[RFC3472]Ashwood Smith，P.和L.Berger，“基于广义多协议标签交换（GMPLS）信令约束的路由标签分发协议（CR-LDP）扩展”，RFC 3472，2003年1月。
[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月。
Contact Information
联系方式
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
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
Cheenu Srinivasan Bloomberg L.P. 731 Lexington Ave. New York, NY 10022
Cheenu Srinivasan Bloomberg L.P.纽约州纽约市列克星敦大道731号，邮编10022
Phone: +1-212-617-3682
EMail: cheenu@bloomberg.net
Phone: +1-212-617-3682
EMail: cheenu@bloomberg.net
Tim Hall Data Connection Ltd. 100 Church Street Enfield, Middlesex, EN2 6BQ, UK
蒂姆·霍尔数据连接有限公司，英国米德尔塞克斯郡恩菲尔德教堂街100号，EN2 6BQ
Phone: +44 20 8366 1177
EMail: tim.hall@dataconnection.com
Phone: +44 20 8366 1177
EMail: tim.hall@dataconnection.com
Ed Harrison Data Connection Ltd. 100 Church Street Enfield, Middlesex, EN2 6BQ, UK
Ed Harrison数据连接有限公司，英国米德尔塞克斯郡恩菲尔德教堂街100号，EN2 6BQ
Phone: +44 20 8366 1177
EMail: ed.harrison@dataconnection.com
Phone: +44 20 8366 1177
EMail: ed.harrison@dataconnection.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
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, THE IETF TRUST 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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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编辑功能的资金目前由互联网协会提供。