Internet Engineering Task Force (IETF) D. Papadimitriou
Request for Comments: 6003 Alcatel-Lucent
Updates: 3471, 3473 October 2010
Category: Standards Track
ISSN: 2070-1721
Internet Engineering Task Force (IETF) D. Papadimitriou
Request for Comments: 6003 Alcatel-Lucent
Updates: 3471, 3473 October 2010
Category: Standards Track
ISSN: 2070-1721
Ethernet Traffic Parameters
以太网流量参数
Abstract
摘要
This document describes the support of Metro Ethernet Forum (MEF) Ethernet traffic parameters as described in MEF10.1 when using Generalized Multi-Protocol Label Switching (GMPLS) Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling.
本文件描述了在使用通用多协议标签交换（GMPLS）资源预留协议-流量工程（RSVP-TE）信令时，对MEF10.1中所述的城域以太网论坛（MEF）以太网流量参数的支持。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6003.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6003.
Copyright Notice
版权公告
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2010 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Per [RFC3471], Generalized Multi-Protocol Label Switching (GMPLS) allows the inclusion of technology-specific parameters in signaling. This document introduces Ethernet SENDER_TSPEC and FLOWSPEC-specific objects in support of Metro Ethernet Forum (MEF) Ethernet traffic parameters as specified in [MEF10.1] and ITU-T Ethernet Service Switching as discussed in [RFC6004]. For example:
根据[RFC3471]，通用多协议标签交换（GMPLS）允许在信令中包含特定于技术的参数。本文件介绍以太网发送器_TSPEC和FLOWSPEC特定对象，以支持[MEF10.1]中规定的Metro Ethernet Forum（MEF）以太网流量参数和[RFC6004]中讨论的ITU-T以太网服务交换。例如：
o For Ethernet Private Line (EPL) services [MEF6], these traffic parameters are applicable to each Ethernet Virtual Connection (EVC) crossing a given port.
o 对于以太网专用线（EPL）服务[MEF6]，这些流量参数适用于通过给定端口的每个以太网虚拟连接（EVC）。
o For Ethernet Virtual Private Line (EVPL) services [MEF6], these traffic parameters are applicable per Ethernet Virtual Connection (EVC) with a single or multiple Class of Service (CoS), independent of its associated Virtual LAN ID (VID) or set of VIDs.
o 对于以太网虚拟专用线（EVPL）服务[MEF6]，这些流量参数适用于具有单个或多个服务类别（CoS）的每个以太网虚拟连接（EVC），独立于其关联的虚拟LAN ID（VID）或一组VID。
Association between EVC and VIDs is detailed in [MEF10.1]. The format and encoding of the VID (or set of VIDs) is documented in a companion document [RFC6004].
EVC和VID之间的关联详见[MEF10.1]。VID（或一组VID）的格式和编码记录在配套文件[RFC6004]中。
This does not preclude broader usage of the Ethernet SENDER_TSPEC and FLOWSPEC-specific objects specified this document. For instance, they may also be used for signaling Ethernet Label Switched Paths (LSPs), in the Generalized Label Request (see [RFC3471]), the Switching Type field is set to Layer 2 Switching Capability (L2SC) and the LSP Encoding Type field to Ethernet.
这并不排除更广泛地使用本文档中指定的以太网发送器_TSPEC和FLOWSPEC特定对象。例如，它们还可用于向以太网标签交换路径（LSP）发送信号，在通用标签请求（参见[RFC3471]）中，交换类型字段设置为第2层交换能力（L2SC），LSP编码类型字段设置为以太网。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
Moreover, the reader is assumed to be familiar with the terminology in [MEF10.1] as well as in [RFC3471] and [RFC3473].
此外，假定读者熟悉[MEF10.1]以及[RFC3471]和[RFC3473]中的术语。
In GMPLS RSVP-TE [RFC3473], the SENDER_TSPEC object is used on a Path message to indicate the bandwidth that is requested for the LSP being established, and the FLOWSPEC object is used on a Resv message to indicate the bandwidth actually reserved for the LSP. The Ethernet SENDER_TSPEC/FLOWSPEC object includes the Ethernet link type (switching granularity) of the requested LSP and the MTU value for
在GMPLS RSVP-TE[RFC3473]中，发送方_TSPEC对象用于Path消息，以指示为正在建立的LSP请求的带宽，而FLOWSPEC对象用于Resv消息，以指示为LSP实际保留的带宽。Ethernet SENDER_TSPEC/FLOWSPEC对象包括所请求LSP的以太网链路类型（交换粒度）和所请求LSP的MTU值
the LSP. Other information about the requested bandwidth characteristics of the LSP are carried in the Bandwidth Profile as a TLV within the Ethernet SENDER_TSPEC/FLOWSPEC object.
LSP。关于请求的LSP带宽特性的其他信息在带宽配置文件中作为TLV携带在Ethernet SENDER_TSPEC/FLOWSPEC对象中。
The Ethernet SENDER_TSPEC/FLOWSPEC object includes the Ethernet link type (switching granularity) of the requested LSP and the MTU value for the LSP.
Ethernet SENDER_TSPEC/FLOWSPEC对象包括所请求LSP的以太网链路类型（交换粒度）和LSP的MTU值。
The Bandwidth Profile defines the set of traffic parameters applicable to a sequence of Service Frames, referred to as bandwidth profile parameters (as specified in [MEF10.1]):
带宽配置文件定义了一组适用于一系列服务帧的流量参数，称为带宽配置文件参数（如[MEF10.1]中规定）：
o Committed Rate: indicates the rate at which traffic commits to be sent to the Ethernet LSP. The committed rate is described in terms of the CIR (Committed Information Rate) and CBS (Committed Burst Size) traffic parameters.
o 提交速率：表示将流量提交到以太网LSP的速率。提交速率根据CIR（提交信息速率）和CBS（提交突发大小）流量参数来描述。
o CIR is defined as the average rate (in bytes per unit of time) up to which the network is committed to transfer frames and meets its performance objectives.
o CIR定义为网络传输帧并满足其性能目标的平均速率（单位时间字节）。
o CBS defines a limit on the maximum number of information units (e.g., bytes) available for a burst of frames sent at the interface speed to remain CIR-conformant.
o CBS对以接口速度发送的突发帧的最大可用信息单元数（如字节）进行了限制，以保持CIR一致。
o Excess Rate: indicates the extent by which the traffic sent on an Ethernet LSP exceeds the committed rate. The Excess Rate is described in terms of the EIR (Excess Information Rate) and EBS (Excess Burst Size) traffic parameters.
o 超额速率：指示以太网LSP上发送的流量超过提交速率的程度。根据EIR（超额信息速率）和EBS（超额突发大小）业务参数来描述超额速率。
o EIR is defined as the average rate (in bytes per unit of time), in excess of the CIR, up to which the network may transfer frames without any performance objectives.
o EIR被定义为超过CIR的平均速率（单位时间的字节数），网络可以在没有任何性能目标的情况下传输帧。
o EBS defines a limit on the maximum number of information units (e.g., bytes) available for a burst of frames sent at the interface speed to remain EIR-conformant.
o EBS定义了以接口速度发送的突发帧的最大可用信息单元数（例如字节）限制，以保持EIR一致。
o Color mode (CM): indicates whether the "color-aware" or "color-blind" property is employed by the bandwidth profile.
o 颜色模式（CM）：指示带宽配置文件是否使用“颜色感知”或“色盲”属性。
o Coupling flag (CF): allows the choice between two modes of operation of the rate enforcement algorithm.
o 耦合标志（CF）：允许在速率强制算法的两种操作模式之间进行选择。
The Ethernet SENDER_TSPEC object (Class-Num = 12, Class-Type = 6) has the following format:
Ethernet SENDER_TSPEC对象（类Num=12，类类型=6）具有以下格式：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | Class-Num (12)| C-Type (6) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switching Granularity | MTU |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | Class-Num (12)| C-Type (6) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switching Granularity | MTU |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Switching Granularity (SG): 16 bits
交换粒度（SG）：16位
This field indicates the type of link that comprises the requested Ethernet LSP.
此字段指示包含请求的以太网LSP的链路类型。
The permitted Ethernet Link Type values are:
允许的以太网链路类型值为：
Value Switching Granularity
----- ---------------------
0 Provided in signaling. See [RFC6004].
1 Ethernet Port (for port-based service)
2 Ethernet Frame (for EVC-based service)
255 Reserved
Value Switching Granularity
----- ---------------------
0 Provided in signaling. See [RFC6004].
1 Ethernet Port (for port-based service)
2 Ethernet Frame (for EVC-based service)
255 Reserved
Values 0 to 2 are specified by the present document. Values 3 through 239 are to be assigned by IANA via Standards Action [RFC5226]. Value 255 is reserved by the present document (its Length is to be determined by the RFC that will specify it).
值0到2由本文档指定。IANA将通过标准行动[RFC5226]分配值3至239。值255由当前文档保留（其长度由指定它的RFC确定）。
Values 240 through 254 are reserved for vendor-specific use.
值240到254保留供供应商特定使用。
Values 256 through 65535 are not assigned at this time.
此时未分配值256到65535。
MTU: 16 bits
MTU:16位
This is a two-octet value indicating the MTU in octets.
这是一个以八位字节表示MTU的双八位字节值。
The MTU field MUST NOT take a value smaller than 46 bytes for Ethernet v2 [ETHv2] and 38 bytes for IEEE 802.3 [IEEE802.3].
MTU字段的值不得小于以太网v2[ETHv2]的46字节和IEEE 802.3[IEEE802.3]的38字节。
TLV (Type-Length-Value):
TLV（类型长度值）：
The Ethernet SENDER_TSPEC object MUST include at least one TLV and MAY include more than one TLV.
Ethernet SENDER_TSPEC对象必须至少包含一个TLV，并且可能包含多个TLV。
Each TLV MUST have the following format:
每个TLV必须具有以下格式：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Value ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Value ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 16 bits
类型：16位
Defined values are:
定义值为：
Type Length Format Description
------------------------------------------------------
0 - Reserved Reserved value
1 - Reserved Reserved value
2 24 see Section 3.1 Ethernet Bandwidth
Profile [MEF10.1]
3 8 [RFC6004] Layer 2 Control
Protocol (L2CP)
255 - Reserved Reserved value
Type Length Format Description
------------------------------------------------------
0 - Reserved Reserved value
1 - Reserved Reserved value
2 24 see Section 3.1 Ethernet Bandwidth
Profile [MEF10.1]
3 8 [RFC6004] Layer 2 Control
Protocol (L2CP)
255 - Reserved Reserved value
Values 0, 1, and 255 are reserved by the present document. Values 2 and 3 are specified by the present document.
值0、1和255由当前文档保留。本文件规定了值2和3。
Values 4 through 239 are to be assigned by IANA via Standards Action [RFC5226].
IANA将通过标准行动[RFC5226]分配值4至239。
Values 240 through 254 are reserved for vendor-specific use.
值240到254保留供供应商特定使用。
Values 256 through 65535 are not assigned at this time.
此时未分配值256到65535。
Length: 16 bits
长度：16位
Indicates the length in bytes of the whole TLV including the Type and Length fields. A value field whose length is not a multiple of four MUST be zero-padded (with trailing zeros) so that the TLV is four-octet aligned.
指示整个TLV的长度（以字节为单位），包括类型和长度字段。长度不是四的倍数的值字段必须加零（带尾随零），以便TLV与四个八位组对齐。
The Type 2 TLV specifies the Ethernet Bandwidth Profile (BW profile). It defines an upper bound on the volume of the expected service frames belonging to a particular Ethernet service instance. The Ethernet SENDER_TSPEC object MAY include more than one Ethernet Bandwidth Profile TLV.
类型2 TLV指定以太网带宽配置文件（BW配置文件）。它定义了属于特定以太网服务实例的预期服务帧数量的上限。以太网发送器\u TSPEC对象可以包括多个以太网带宽配置文件TLV。
The Type 2 TLV has the following format:
类型2 TLV具有以下格式：
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Profile | Index | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Profile | Index | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Profile: 8 bits
配置文件：8位
This field is defined as a bit vector of binary flags. The following flags are defined:
此字段定义为二进制标志的位向量。定义了以下标志：
Flag 1 (bit 0): Coupling Flag (CF) Flag 2 (bit 1): Color Mode (CM)
标志1（位0）：耦合标志（CF）标志2（位1）：颜色模式（CM）
Where bit 0 is the low order bit. Other flags are reserved, they SHOULD be set to zero when sent, and SHOULD be ignored when received.
其中，位0是低阶位。其他标志是保留的，发送时应设置为零，接收时应忽略。
A flag is set to value 1 to indicate that the corresponding metering profile is requested.
将标志设置为值1，以指示请求了相应的计量配置文件。
The Flag 1 (CF) allows the choice between two modes of operation of the rate enforcement algorithm.
标志1（CF）允许在速率强制算法的两种操作模式之间进行选择。
The Flag 2 (CM) indicates whether the color-aware or color-blind property [MEF10.2] is employed by the bandwidth profile. When Flag 2 is set to value 0 (1), the bandwidth profile algorithm is said to be in color-blind (color-aware) mode.
标志2（CM）指示带宽配置文件是否使用颜色感知或色盲属性[MEF10.2]。当标志2设置为值0（1）时，带宽配置文件算法被称为处于色盲（颜色感知）模式。
Index: 8 bits
索引：8位
The Index field is used to reference bandwidth allocated for a given traffic class in case a multiple-class LSP is being requested. The Index field value MUST correspond to at least one of the Class-Type values included either in the CLASSTYPE object [RFC4124] or in the EXTENDED_CLASSTYPE object [MCOS].
索引字段用于在请求多类LSP的情况下引用为给定通信量类别分配的带宽。索引字段值必须至少对应于类类型对象[RFC4124]或扩展类类型对象[MCOS]中包含的一个类类型值。
A given index value j can be associated to at most N Class-Type values CTi (i =< N) of the EXTENDED_CLASSTYPE object. This association applies when a set of one or more CTIs maps to a single (shared) BW profile. An example of value setting consists in assigning an arbitrary value comprised within the range [0x08,0xF8] associated to a set of CTi, the values in the range [0xF8,0xFF] being selected for reserved sets. This allows mapping to one of 248 predefined CTi sets.
给定的索引值j最多可以与扩展的类类型对象的N个类类型值CTi（i=<N）相关联。当一组或多个CTI映射到单个（共享）BW配置文件时，此关联适用。值设置的一个示例包括分配与一组CTi关联的[0x08,0xF8]范围内的任意值，为保留集选择[0xF8,0xFF]范围内的值。这允许映射到248个预定义CTi集之一。
A given index value j can be associated to a single CTi (1:1 correspondence). In this case, the index value setting consists in assigning the 3 least significant bits of the Index field itself to the CTi value itself (comprised in the range [0x00,0x07]). This applies in case a single CTi maps a single (dedicated) BW profile or multiple (dedicated) BW profiles. In the former case, the Ethernet SENDER_TSPEC object includes a single Ethernet Bandwidth Profile TLV. In the latter case, the Ethernet SENDER_TSPEC includes a set of more than one Ethernet Bandwidth Profile TLVs (whose respective index value is associated to a single CTi value).
给定的索引值j可以与单个CTi关联（1:1对应）。在这种情况下，索引值设置包括将索引字段本身的3个最低有效位分配给CTi值本身（包含在范围[0x00,0x07]中）。这适用于单个CTi映射单个（专用）BW配置文件或多个（专用）BW配置文件的情况。在前一种情况下，以太网发送器_TSPEC对象包括单个以太网带宽配置文件TLV。在后一种情况下，以太网发送器_TSPEC包括一组多个以太网带宽配置文件tlv（其各自的索引值与单个CTi值相关联）。
Note that the current specification allows for combining shared and dedicated BW profiles to the same LSP. That is, an Ethernet SENDER_TSPEC object MAY include multiple Ethernet Bandwidth Profile TLVs whose respective index can be associated on a 1:1 basis to a single CTi or to a set of multiple CTis.
请注意，当前规范允许将共享和专用BW配置文件组合到同一LSP。也就是说，以太网发送器_TSPEC对象可以包括多个以太网带宽配置文件tlv，其各自的索引可以以1:1的基础与单个CTi或多个CTi的集合相关联。
For each subobject of the EXTENDED_CLASSTYPE object [MCOS]:
对于扩展类类型对象[MCOS]的每个子对象：
o Each CTi value SHOULD correspond 1:1 to the MEF Customer Edge VLAN CoS (CE-VLAN CoS).
o 每个CTi值应与MEF客户边缘VLAN CoS（CE-VLAN CoS）1:1对应。
o The BW requested per CTi field MAY be used for bandwidth accounting purposes.
o 每个CTi请求的BW字段可用于带宽计费目的。
By default, the value of the Index field MUST be set to 0.
默认情况下，索引字段的值必须设置为0。
Reserved: 16 bits
保留：16位
These bits SHOULD be set to zero when sent and MUST be ignored when received.
这些位在发送时应设置为零，在接收时必须忽略。
CIR (Committed Information Rate): 32 bits
CIR（提交信息速率）：32位
The value of the CIR is in units of bytes per second. The CIR is encoded as a 32-bit IEEE single-precision floating-point number (see [RFC4506]).
CIR的值以字节/秒为单位。CIR编码为32位IEEE单精度浮点数（参见[RFC4506]）。
The CIR value MUST be greater than or equal to 0.
CIR值必须大于或等于0。
CBS (Committed Burst Size): 32 bits
CBS（提交的突发大小）：32位
The value of the CBS is in units of bytes. The CBS is encoded as a 32-bit IEEE single-precision floating-point number (see [RFC4506]).
CBS的值以字节为单位。CBS编码为32位IEEE单精度浮点数（参见[RFC4506]）。
When CIR is strictly greater than 0 (CIR > 0), the CBS MUST be greater than or equal to the maximum frame size.
当CIR严格大于0（CIR>0）时，CBS必须大于或等于最大帧大小。
EIR (Excess Information Rate): 32 bits
EIR（超额信息率）：32位
The value of the EIR is in units of bytes per second. The EIR is encoded as a 32-bit IEEE single-precision floating-point number (see [RFC4506]).
EIR的值以字节/秒为单位。EIR编码为32位IEEE单精度浮点数（参见[RFC4506]）。
The EIR value MUST be greater than or equal to 0.
EIR值必须大于或等于0。
EBS (Excess Burst Size): 32 bits
EBS（超出突发大小）：32位
The value of the EBS is in units of bytes. The EBS is encoded as a 32-bit IEEE single-precision floating-point number (see [RFC4506]).
EBS的值以字节为单位。EBS编码为32位IEEE单精度浮点数（参见[RFC4506]）。
When EIR is strictly greater than 0 (EIR > 0), the EBS MUST be greater than or equal to the maximum frame size.
当EIR严格大于0（EIR>0）时，EBS必须大于或等于最大帧大小。
The Ethernet FLOWSPEC object (Class-Num = 9, Class-Type = 6) has the same format as the Ethernet SENDER_TSPEC object.
Ethernet FLOWSPEC对象（类Num=9，类类型=6）的格式与Ethernet SENDER_TSPEC对象的格式相同。
There is no ADSPEC object associated with the Ethernet SENDER_TSPEC object.
没有与Ethernet SENDER_TSPEC对象关联的ADSPEC对象。
Either the ADSPEC object is omitted or an IntServ ADSPEC with the Default General Characterization Parameters and Guaranteed Service fragment is used, see [RFC2210].
要么省略ADSPEC对象，要么使用具有默认常规特征参数和保证服务片段的IntServ ADSPEC，请参见[RFC2210]。
The Ethernet SENDER_TSPEC and FLOWSPEC objects specified in this document MAY be used for signaling Ethernet LSP. For signaling such an LSP, in the Generalized LABEL_REQUEST object (see [RFC3471]), the Switching Type field MUST be set to the value 51 (L2SC) and the LSP Encoding Type field MUST be set to the value 2 (Ethernet).
本文档中指定的Ethernet SENDER_TSPEC和FLOWSPEC对象可用于向Ethernet LSP发送信号。为了向这样的LSP发送信号，在通用标签_请求对象（参见[RFC3471]）中，交换类型字段必须设置为值51（L2SC），LSP编码类型字段必须设置为值2（以太网）。
The Ethernet SENDER_TSPEC object carries the traffic specification generated by the RSVP session sender. The Ethernet SENDER_TSPEC object SHOULD be forwarded and delivered unchanged to both intermediate and egress nodes.
Ethernet SENDER_TSPEC对象携带由RSVP会话发送方生成的流量规范。Ethernet SENDER_TSPEC对象应该被转发，并原封不动地传递到中间节点和出口节点。
The Ethernet FLOWSPEC object carries reservation request information generated by receivers. As with any FLOWSPEC object, the Ethernet FLOWSPEC object flows upstream toward the ingress node.
Ethernet FLOWSPEC对象携带由接收方生成的预订请求信息。与任何FLOWSPEC对象一样，Ethernet FLOWSPEC对象向上游流向入口节点。
Intermediate and egress nodes MUST verify that the node itself and the interfaces on which the LSP will be established can support the requested Switching Granularity, MTU and values included in subobject TLVs. These nodes MUST be configured with the same predefined CT sets as the index value signaled as part of the Index field of the Ethernet Bandwidth Profile TLV (see Section 4.1). If the requested value(s) cannot be supported, the receiver node MUST generate a PathErr message with the error code "Traffic Control Error" and the error value "Service unsupported" (see [RFC2205]).
中间和出口节点必须验证节点本身和将在其上建立LSP的接口是否能够支持请求的交换粒度、MTU和子对象TLV中包含的值。这些节点必须配置与作为以太网带宽配置文件TLV索引字段的一部分发出信号的索引值相同的预定义CT集（见第4.1节）。如果请求的值不受支持，则接收方节点必须生成一条PathErr消息，错误代码为“Traffic Control error”，错误值为“Service unsupported”（参见[RFC2205]）。
In addition, if the MTU field is received with a value smaller than the minimum transfer unit size of the Ethernet frame (e.g., 46 bytes for Ethernet v2, 38 bytes for IEEE 802.3), the node MUST generate a PathErr message with the error code "Traffic Control Error" and the error value "Bad Tspec value" (see [RFC2205]).
此外，如果接收到的MTU字段值小于以太网帧的最小传输单元大小（例如，以太网v2为46字节，IEEE 802.3为38字节），则节点必须生成一条PathErr消息，错误代码为“Traffic Control error”，错误值为“Bad Tspec value”（参见[RFC2205]）。
Error processing of the CLASSTYPE object follows rules defined in [RFC4124]. Error processing of the EXTENDED_CLASSTYPE object follows rules defined in [MCOS]. Moreover, a Label Switching Router (LSR) receiving a Path message with the EXTENDED_CLASSTYPE object, which recognizes the object and the particular Class-Type but does detect a mismatch in the index values, MUST send a PathErr message towards the sender with the error code "Extended Class-Type Error" and the error value "Class-Type mismatch" (see [RFC2205]).
CLASSTYPE对象的错误处理遵循[RFC4124]中定义的规则。扩展类类型对象的错误处理遵循[MCOS]中定义的规则。此外，标签交换路由器（LSR）接收带有扩展类类型对象的路径消息时，必须向发送方发送路径错误消息，错误代码为“EXTENDED Class Type error”，错误值为“Class Type mismatch”（见[RFC2205]）。
This document introduces no new security considerations to [RFC3473].
本文档未向[RFC3473]引入新的安全注意事项。
GMPLS security is described in Section 11 of [RFC3471] and refers to [RFC3209] for RSVP-TE. Further details of MPLS-TE and GMPLS security can be found in [RFC5920].
[RFC3471]第11节描述了GMPLS安全性，RSVP-TE参考[RFC3209]。有关MPLS-TE和GMPLS安全性的更多详细信息，请参见[RFC5920]。
IANA maintains registries and sub-registries for RSVP-TE as used by GMPLS. IANA has made allocations from these registries as set out in the following sections.
IANA为GMPLS使用的RSVP-TE维护登记册和子登记册。IANA已从这些登记处进行分配，如下节所述。
This document introduces two new Class Types for existing RSVP objects. IANA has made allocations from the "Resource ReSerVation Protocol (RSVP) Parameters" registry using the "Class Names, Class Numbers, and Class Types" sub-registry.
本文档为现有RSVP对象介绍了两种新的类类型。IANA使用“类名、类号和类类型”子注册表从“资源保留协议（RSVP）参数”注册表进行分配。
Class Number Class Name Reference
------------ ----------------------- ---------
9 FLOWSPEC [RFC2205]
Class Number Class Name Reference
------------ ----------------------- ---------
9 FLOWSPEC [RFC2205]
Class Type (C-Type):
类别类型（C类）：
6 Ethernet SENDER_TSPEC [RFC6003]
6以太网发送器\u TSPEC[RFC6003]
Class Number Class Name Reference
------------ ----------------------- ---------
12 SENDER_TSPEC [RFC2205]
Class Number Class Name Reference
------------ ----------------------- ---------
12 SENDER_TSPEC [RFC2205]
Class Type (C-Type):
类别类型（C类）：
6 Ethernet SENDER_TSPEC [RFC6003]
6以太网发送器\u TSPEC[RFC6003]
IANA maintains a registry of GMPLS parameters called "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Parameters".
IANA维护一个名为“通用多协议标签交换（GMPLS）信令参数”的GMPLS参数注册表。
IANA has created a new sub-registry called "Ethernet Switching Granularities" to contain the values that may be carried in the Switching Granularity field of the Ethernet SENDER_TSPEC object.
IANA创建了一个名为“Ethernet Switching Granularity”的新子注册表，以包含Ethernet SENDER_TSPEC对象的交换粒度字段中可能包含的值。
Values are as follows:
数值如下：
0-2 See below. 3-239 Unassigned 240-254 Reserved for Vendor-Specific Use 255 Reserved 256-65535 Not assigned at this time
0-2见下文。3-239未分配240-254保留供供应商特定使用255保留256-65535此时未分配
The registration procedure is Standards Action.
注册程序是标准行动。
Initial entries in this sub-registry are as follows:
此子注册表中的初始条目如下：
Value Switching Granularity Reference
----- -------------------------------------- ------------------
0 Provided in signaling. [RFC6003][RFC6004]
1 Ethernet Port (for port-based service) [RFC6003]
2 Ethernet Frame (for EVC-based service) [RFC6003]
255 Reserved [RFC6003]
Value Switching Granularity Reference
----- -------------------------------------- ------------------
0 Provided in signaling. [RFC6003][RFC6004]
1 Ethernet Port (for port-based service) [RFC6003]
2 Ethernet Frame (for EVC-based service) [RFC6003]
255 Reserved [RFC6003]
IANA maintains a registry of GMPLS parameters called "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Parameters".
IANA维护一个名为“通用多协议标签交换（GMPLS）信令参数”的GMPLS参数注册表。
IANA has created a new sub-registry called "Ethernet Sender TSpec TLVs / Ethernet Flowspec TLVs" to contain the TLV type values for TLVs carried in the Ethernet SENDER_TSPEC object.
IANA已经创建了一个名为“Ethernet Sender TSpec TLV/Ethernet Flowspec TLV”的新子注册表，以包含Ethernet Sender_TSpec对象中携带的TLV的TLV类型值。
Values are as follows:
数值如下：
0-3 See below. 4-239 Unassigned 240-254 Reserved for Vendor-Specific Use 255 Reserved 256-65535 Not assigned at this time
0-3见下文。4-239未分配240-254保留供供应商特定使用255保留256-65535此时未分配
The registration procedure is Standards Action.
注册程序是标准行动。
Initial entries in this sub-registry are as follows:
此子注册表中的初始条目如下：
Type Description Reference
----- -------------------------------- ---------
0 Reserved [RFC6003]
1 Reserved [RFC6003]
2 Ethernet Bandwidth Profile [RFC6003]
3 Layer 2 Control Protocol (L2CP) [RFC6003]
255 Reserved [RFC6003]
Type Description Reference
----- -------------------------------- ---------
0 Reserved [RFC6003]
1 Reserved [RFC6003]
2 Ethernet Bandwidth Profile [RFC6003]
3 Layer 2 Control Protocol (L2CP) [RFC6003]
255 Reserved [RFC6003]
IANA maintains a registry of GMPLS parameters called "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Parameters".
IANA维护一个名为“通用多协议标签交换（GMPLS）信令参数”的GMPLS参数注册表。
IANA has created a new sub-registry called "Ethernet Bandwidth Profiles" to contain bit flags carried in the Ethernet Bandwidth Profile TLV of the Ethernet SENDER_TSPEC object.
IANA创建了一个名为“Ethernet带宽配置文件”的新子注册表，以包含Ethernet SENDER_TSPEC对象的Ethernet带宽配置文件TLV中携带的位标志。
Bits are to be allocated by IETF Standards Action. Bits are numbered from bit 0 as the low order bit. Initial entries are as follows:
比特由IETF标准行动分配。位从位0开始编号为低位。初始条目如下：
Bit Hex Description Reference
--- ---- -------------------------- -------------
0 0x01 Coupling Flag (CF) [RFC6003]
1 0x02 Color Mode (CM) [RFC6003]
Bit Hex Description Reference
--- ---- -------------------------- -------------
0 0x01 Coupling Flag (CF) [RFC6003]
1 0x02 Color Mode (CM) [RFC6003]
Many thanks to Adrian Farrel for his comments. Lou Berger provided the input on control traffic processing.
非常感谢阿德里安·法雷尔的评论。Lou Berger提供了关于控制流量处理的输入。
[MEF10.1] The MEF Technical Specification, "Ethernet Services Attributes Phase 2", MEF 10.1, November 2006.
[MEF10.1]MEF技术规范，“以太网服务属性第2阶段”，MEF 10.12006年11月。
[RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S. Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification", RFC 2205, September 1997.
[RFC2205]Braden，R.，Ed.，Zhang，L.，Berson，S.，Herzog，S.，和S.Jamin，“资源预留协议（RSVP）——版本1功能规范”，RFC 22052997年9月。
[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated Services", RFC 2210, September 1997.
[RFC2210]Wroclawski，J.，“RSVP与IETF集成服务的使用”，RFC 2210，1997年9月。
[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月。
[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月。
[RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description", RFC 3471, January 2003.
[RFC3471]Berger，L.，Ed.“通用多协议标签交换（GMPLS）信令功能描述”，RFC 3471，2003年1月。
[RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions", RFC 3473, January 2003.
[RFC3473]Berger，L.，Ed.“通用多协议标签交换（GMPLS）信令资源预留协议流量工程（RSVP-TE）扩展”，RFC 3473，2003年1月。
[RFC4124] Le Faucheur, F., Ed., "Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering", RFC 4124, June 2005.
[RFC4124]Le Faucheur，F.，编辑，“支持区分服务感知MPLS流量工程的协议扩展”，RFC 41242005年6月。
[RFC4506] Eisler, M., Ed., "XDR: External Data Representation Standard", STD 67, RFC 4506, May 2006.
[RFC4506]艾斯勒，M.，编辑，“XDR：外部数据表示标准”，STD 67，RFC 4506，2006年5月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC6004] Berger, L. and D. Fedyk, "Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Services", RFC 6004, October 2010.
[RFC6004]Berger，L.和D.Fedyk，“对城域以太网论坛和G.8011以太网服务的通用MPLS（GMPLS）支持”，RFC 60042010年10月。
[ETHv2] Digital, Intel, and Xerox, "The Ethernet -- A Local Area Network: Data Link Layer and Physical Layer Specifications", Version 2.0, November 1982.
[ETHv2]Digital、Intel和Xerox，“以太网——局域网：数据链路层和物理层规范”，版本2.0，1982年11月。
[IEEE802.3] IEEE 802.3 LAN/MAN CSMA/CD (Ethernet) Access Method, IEEE Standard for Information technology- Specific requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CMSA/CD) Access Method and Physical Layer Specifications, IEEE 802.3-2008.
[IEEE802.3]IEEE 802.3 LAN/MAN CSMA/CD（以太网）访问方法，IEEE信息技术标准-特定要求-第3部分：带冲突检测的载波侦听多址（CMSA/CD）访问方法和物理层规范，IEEE 802.3-2008。
[MCOS] Minei, I., Gan, D., Kompella, K., and X. Li, "Extensions for Differentiated Services-aware Traffic Engineered LSPs", Work in Progress, June 2006.
[MCOS]Minei，I.，Gan，D.，Kompella，K.，和X.Li，“区分服务感知流量工程LSP的扩展”，正在进行的工作，2006年6月。
[MEF6] The Metro Ethernet Forum, "Ethernet Services Definitions - Phase I", MEF 6, June 2004.
[MEF6]Metro Ethernet论坛，“以太网服务定义-第一阶段”，MEF6，2004年6月。
[MEF10.2] The MEF Technical Specification, "Ethernet Services Attributes Phase 2", MEF 10.2, October 2009.
[MEF10.2]MEF技术规范，“以太网服务属性第2阶段”，MEF 10.22009年10月。
[RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS Networks", RFC 5920, July 2010.
[RFC5920]方，L.，编辑，“MPLS和GMPLS网络的安全框架”，RFC 5920，2010年7月。
Author's Address
作者地址
Dimitri Papadimitriou Alcatel-Lucent Bell Copernicuslaan 50 B-2018 Antwerpen, Belgium Phone: +32 3 2408491 EMail: dimitri.papadimitriou@alcatel-lucent.be
Dimitri Papadimitriou Alcatel-Lucent Bell Copernicuslaan 50 B-2018比利时安特卫普电话：+32 3 2408491电子邮件：Dimitri。papadimitriou@alcatel-朗讯