draft-ietf-ccamp-ethernet-traffic-parameters-10.txt   rfc6003.txt 
Network Working Group D. Papadimitriou Internet Engineering Task Force (IETF) D. Papadimitriou
Internet Draft Alcatel-Lucent Request for Comments: 6003 Alcatel-Lucent
Updates: 3471, 3473 January 20, 2010 Updates: 3471, 3473 October 2010
Intended status: Standards Track Category: Standards Track
Expires: July 19, 2010 ISSN: 2070-1721
Ethernet Traffic Parameters Ethernet Traffic Parameters
draft-ietf-ccamp-ethernet-traffic-parameters-10.txt Abstract
Status of this Memo 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.
This Internet-Draft is submitted to IETF in full conformance with Status of This Memo
the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six This document is a product of the Internet Engineering Task Force
months and may be updated, replaced, or obsoleted by other (IETF). It represents the consensus of the IETF community. It has
documents at any time. It is inappropriate to use Internet-Drafts received public review and has been approved for publication by the
as reference material or to cite them other than as "work in Internet Engineering Steering Group (IESG). Further information on
progress." Internet Standards is available in Section 2 of RFC 5741.
The list of current Internet-Drafts can be accessed at Information about the current status of this document, any errata,
http://www.ietf.org/ietf/1id-abstracts.txt. and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6003.
The list of Internet-Draft Shadow Directories can be accessed at Copyright Notice
http://www.ietf.org/shadow.html.
Copyright and License Notice Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
Copyright (c) 2010 IETF Trust and the persons identified as the This document is subject to BCP 78 and the IETF Trust's Legal
document authors. All rights reserved. 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.
This document is subject to BCP 78 and the IETF Trust's Legal 1. Introduction
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 BSD License.
Abstract 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:
This document describes the support of Metro Ethernet Forum (MEF) o For Ethernet Private Line (EPL) services [MEF6], these traffic
Ethernet Traffic Parameters as described in MEF10.1 when using parameters are applicable to each Ethernet Virtual Connection
Generalized Multi-Protocol Label Switching (GMPLS) Resource (EVC) crossing a given port.
ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling.
1. Introduction 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.
Per [RFC3471], Generalized Multi-Protocol Label Switching (GMPLS) Association between EVC and VIDs is detailed in [MEF10.1]. The
allows the inclusion of technology specific parameters in format and encoding of the VID (or set of VIDs) is documented in a
signaling. Ethernet SENDER_TSPEC and FLOWSPEC specific objects companion document [RFC6004].
are introduced in this document that supports Metro Ethernet
Forum (MEF) Ethernet traffic parameters as specified in [MEF10.1]
and ITU-T Ethernet Service Switching as discussed in [GMPLS-
ESVCS]. For example:
o For Ethernet Private Line (EPL) services [MEF6], these traffic This does not preclude broader usage of the Ethernet SENDER_TSPEC and
parameters are applicable to each Ethernet Virtual Connection FLOWSPEC-specific objects specified this document. For instance,
(EVC) crossing a given port. 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.
o For Ethernet Virtual Private Line (EVPL) services [MEF6], these 2. Conventions Used in This Document
traffic parameters are applicable per Ethernet Virtual
Connection (EVC) with single or multiple Class of Service
(CoS), independent of its associated (set of) Virtual LAN ID
(VID).
Association between EVC and VIDs is detailed in [MEF10.1]. The The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
format and encoding of the (set of) VIDs is documented in a "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
companion document [GMPLS-ESVCS]. document are to be interpreted as described in RFC 2119 [RFC2119].
This does not preclude broader usage of the Ethernet SENDER_TSPEC Moreover, the reader is assumed to be familiar with the terminology
and FLOWSPEC specific objects specified this document. For in [MEF10.1] as well as in [RFC3471] and [RFC3473].
instance, they may also be used for signaling Ethernet Label
Switched Paths (LSP): 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.
2. Conventions used in this document 3. Overview
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL In GMPLS RSVP-TE [RFC3473], the SENDER_TSPEC object is used on a Path
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and message to indicate the bandwidth that is requested for the LSP being
"OPTIONAL" in this document are to be interpreted as described in established, and the FLOWSPEC object is used on a Resv message to
RFC-2119 [RFC2119]. 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
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.
Moreover, the reader is assumed to be familiar with the The Ethernet SENDER_TSPEC/FLOWSPEC object includes the Ethernet link
terminology [MEF10.1] as well as [RFC3471] and [RFC3473]. type (switching granularity) of the requested LSP and the MTU value
for the LSP.
3. Overview 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]):
In GMPLS RSVP-TE [RFC3473] the SENDER_TSPEC object is used on a o Committed Rate: indicates the rate at which traffic commits to be
Path message to indicate the bandwidth that is requested for the sent to the Ethernet LSP. The committed rate is described in
LSP being established, and the FLOWSPEC object is used on a Resv terms of the CIR (Committed Information Rate) and CBS (Committed
message to indicate the bandwidth actually reserved for the LSP. Burst Size) traffic parameters.
The Ethernet SENDER_TSPEC/FLOWSPEC object includes the Ethernet
link type (switching granularity) of the requested LSP and the
MTU value for 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.
The Ethernet SENDER_TSPEC/FLOWSPEC object includes the Ethernet o CIR is defined as the average rate (in bytes per unit of time)
link type (switching granularity) of the requested LSP and the up to which the network is committed to transfer frames and
MTU value for the LSP. meets its performance objectives.
The Bandwidth Profile defines the set of traffic parameters o CBS defines a limit on the maximum number of information units
applicable to a sequence of Service Frames, referred to as (e.g., bytes) available for a burst of frames sent at the
bandwidth profile parameters (as specified in [MEF10.1]): interface speed to remain CIR-conformant.
o Committed Rate: indicates the rate at which traffic commits to o Excess Rate: indicates the extent by which the traffic sent on an
be sent to the Ethernet LSP. The Committed Rate is described in Ethernet LSP exceeds the committed rate. The Excess Rate is
terms of the CIR (Committed Information Rate) and CBS described in terms of the EIR (Excess Information Rate) and EBS
(Committed Burst Size) traffic parameters. (Excess Burst Size) traffic parameters.
o CIR is defined as the average rate (in bytes per unit of o EIR is defined as the average rate (in bytes per unit of time),
time) up to which the network is committed to transfer frames in excess of the CIR, up to which the network may transfer
and meets its performance objectives. frames without any performance objectives.
o CBS defines a limit on the maximum number of information o EBS defines a limit on the maximum number of information units
units (e.g., bytes) available for a burst of frames sent at (e.g., bytes) available for a burst of frames sent at the
the interface speed to remain CIR-conformant. interface speed to remain EIR-conformant.
o Excess Rate: indicates the extent by which the traffic sent on o Color mode (CM): indicates whether the "color-aware" or "color-
an Ethernet LSP exceeds the committed rate. The Excess Rate is blind" property is employed by the bandwidth profile.
described in terms of the EIR (Excess Information Rate) and EBS
(Excess Burst Size) traffic parameters.
o EIR is defined as the average rate (in bytes per unit of o Coupling flag (CF): allows the choice between two modes of
time), in excess of the CIR, up to which the network may operation of the rate enforcement algorithm.
transfer frames without any performance objectives.
o EBS defines a limit on the maximum number of information unit 4. Ethernet SENDER_TSPEC Object
(e.g., bytes) available for a burst of frames sent at the
interface speed to remain EIR-conformant.
o Color mode (CM): indicates whether the "color-aware" or "color- The Ethernet SENDER_TSPEC object (Class-Num = 12, Class-Type = 6) has
blind" property is employed by the bandwidth profile. the following format:
o Coupling flag (CF): allows the choice between two modes of 0 1 2 3
operation of the rate enforcement algorithm. 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 ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4. Ethernet SENDER_TSPEC Object Switching Granularity (SG): 16 bits
The Ethernet SENDER_TSPEC object (Class-Num = 12, Class-Type = This field indicates the type of link that comprises the requested
TBA by IANA, with recommended value 6) has the following format: Ethernet LSP.
0 1 2 3 The permitted Ethernet Link Type values are:
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 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
This field indicates the type of link that comprises the Values 0 to 2 are specified by the present document. Values 3
requested Ethernet LSP. 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).
The permitted Ethernet Link Type values are: Values 240 through 254 are reserved for vendor-specific use.
Value Switching Granularity Values 256 through 65535 are not assigned at this time.
----- ---------------------
0 Provided in signaling. See [GMPLS-ESVCS]
1 Ethernet Port (for port-based service)
2 Ethernet Frame (for EVC-based service)
255 Reserved value
Values 0 through 239, and 255 are assigned by IANA via IETF MTU: 16 bits
Standards Action. Value 255 is reserved by the
present document.
Values 240 through 254 are reserved for Private Use. This is a two-octet value indicating the MTU in octets.
Values 256 through 65535 are not to be assigned at this time. 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: 16 bits TLV (Type-Length-Value):
This is a two-octet value indicating the MTU in octets. The Ethernet SENDER_TSPEC object MUST include at least one TLV and
MAY include more than one TLV.
The MTU field MUST NOT take a value smaller than 46 bytes for Each TLV MUST have the following format:
Ethernet V2 [ETHv2] and 38 bytes for IEEE 802.3 [IEEE802.3].
TLV (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 ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Ethernet SENDER_TSPEC object MUST include at least one TLV Type: 16 bits
and MAY include more than one TLV.
Each TLV MUST have the following format: Defined values are:
0 1 2 3 Type Length Format Description
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 ------------------------------------------------------
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 0 - Reserved Reserved value
| Type | Length | 1 - Reserved Reserved value
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2 24 see Section 3.1 Ethernet Bandwidth
| | Profile [MEF10.1]
~ Value ~ 3 8 [RFC6004] Layer 2 Control
| | Protocol (L2CP)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 - Reserved Reserved value
Type: 16 bits Values 0, 1, and 255 are reserved by the present document. Values
2 and 3 are specified by the present document.
Defined values are: Values 4 through 239 are to be assigned by IANA via Standards
Action [RFC5226].
Type Length Format Description Values 240 through 254 are reserved for vendor-specific use.
------------------------------------------------------
0 TBD Reserved Reserved value
1 TBD Reserved Reserved value
2 24 see Section 3.1 Ethernet Bandwidth
Profile [MEF10.1]
3 8 [GMPLS-ESVCS] Layer 2 Control
Processing (L2CP)
255 TBD Reserved Reserved value
Values 0 through 239, and 255 are assigned by IANA via IETF Values 256 through 65535 are not assigned at this time.
Standards Action. Values 0 and 255 are reserved
by the present document.
Values 240 through 254 are reserved for Private Use. Length: 16 bits
Values 256 through 65535 are not to be assigned at this Indicates the length in bytes of the whole TLV including the Type
time. 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.
Length: 16 bits 4.1. Ethernet Bandwidth Profile TLV
Indicates the length in bytes of the whole TLV including The Type 2 TLV specifies the Ethernet Bandwidth Profile (BW profile).
the Type and Length fields. A value field whose length is It defines an upper bound on the volume of the expected service
not a multiple of four MUST be zero-padded (with trailing frames belonging to a particular Ethernet service instance. The
zeros) so that the TLV is four-octet aligned. Ethernet SENDER_TSPEC object MAY include more than one Ethernet
Bandwidth Profile TLV.
4.1. Ethernet Bandwidth Profile TLV The Type 2 TLV has the following format:
The Type 2 TLV specifies the Ethernet Bandwidth Profile (BW 0 1 2 3
profile). It defines an upper bound on the volume of the expected 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
service frames belonging to a particular Ethernet service +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
instance. The Ethernet SENDER_TSPEC object MAY include more than | Profile | Index | Reserved |
one Ethernet Bandwidth Profile TLV. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Type 2 TLV has the following format: Profile: 8 bits
0 1 2 3 This field is defined as a bit vector of binary flags. The
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 following flags are defined:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Profile | Index | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Profile: 8 bits (this field is to be registered by IANA) Flag 1 (bit 0): Coupling Flag (CF)
Flag 2 (bit 1): Color Mode (CM)
This field is defined as a bit vector of binary flags. The Where bit 0 is the low order bit. Other flags are reserved, they
following flags are defined: SHOULD be set to zero when sent, and SHOULD be ignored when
received.
Flag 1 (bit 0): coupling flag (CF) A flag is set to value 1 to indicate that the corresponding
Flag 2 (bit 1): color mode (CM) metering profile is requested.
Where bit 0 is the low order bit. Other flags are reserved, The Flag 1 (CF) allows the choice between two modes of operation
they SHOULD be set to zero when sent, and SHOULD be ignored of the rate enforcement algorithm.
when received.
A flag is set to value 1 to indicate that the corresponding The Flag 2 (CM) indicates whether the color-aware or color-blind
metering profile is requested. 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.
The Flag 1 (CF) allows the choice between two modes of Index: 8 bits
operation of the rate enforcement algorithm.
The Flag 2 (CM) indicates whether the color-aware or color- The Index field is used to reference bandwidth allocated for a
blind property is employed by the bandwidth profile. When Flag given traffic class in case a multiple-class LSP is being
2 is set to value 0 (1), the bandwidth profile algorithm is requested. The Index field value MUST correspond to at least one
said to be in color blind (color aware) mode. of the Class-Type values included either in the CLASSTYPE object
[RFC4124] or in the EXTENDED_CLASSTYPE object [MCOS].
Index: 8 bits 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.
The index field is used to reference bandwidth allocated for a A given index value j can be associated to a single CTi (1:1
given traffic class in case a multiple-class LSP is being correspondence). In this case, the index value setting consists
requested. The index field value MUST correspond to at least in assigning the 3 least significant bits of the Index field
one of the Class-Type values included either in the CLASSTYPE itself to the CTi value itself (comprised in the range
object [RFC4124] or in the EXTENDED_CLASSTYPE object [MCOS]. [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).
A given index value j can be associated to at most N Class- Note that the current specification allows for combining shared
Type values CTi (i =< N) of the EXTENDED_CLASSTYPE object. and dedicated BW profiles to the same LSP. That is, an Ethernet
This applies in case a set of one or more CTi maps a single SENDER_TSPEC object MAY include multiple Ethernet Bandwidth
(shared) BW profile. An example of value setting consists then Profile TLVs whose respective index can be associated on a 1:1
in assigning an arbitrary value comprised within the range basis to a single CTi or to a set of multiple CTis.
[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 pre-defined CTi sets.
A given index value j can be associated to a single CTi (1:1 For each subobject of the EXTENDED_CLASSTYPE object [MCOS]:
correspondence). In this case, the index value setting
consists then in assigning the 3 LSB 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 (single BW profile), the Ethernet SENDER_TSPEC object
includes a single Ethernet Bandwidth Profile TLV. In the
second 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).
Note that the current specification allows for combining o Each CTi value SHOULD correspond 1:1 to the MEF Customer
shared and dedicated BW profiles to the same LSP. That is, an Edge VLAN CoS (CE-VLAN CoS).
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 CTi.
For each subobject of the EXTENDED_CLASSTYPE object [MCOS]: o The BW requested per CTi field MAY be used for bandwidth
o Each CTi value SHOULD correspond 1:1 to MEF CE VLAN-CoS accounting purposes.
o The BW requested per CTi field MAY be used for bandwidth
accounting purposes.
By default, the value of the Index field MUST be set to 0. By default, the value of the Index field MUST be set to 0.
Reserved: 16 bits Reserved: 16 bits
These bits SHOULD be set to zero when sent and MUST be ignored These bits SHOULD be set to zero when sent and MUST be ignored
when received. when received.
CIR (Committed Information Rate): 32 bits CIR (Committed Information Rate): 32 bits
The value of the CIR is in units of bytes per second. The CIR The value of the CIR is in units of bytes per second. The CIR is
is encoded as a 32-bit IEEE single-precision floating-point encoded as a 32-bit IEEE single-precision floating-point number
number (see [RFC4506]). (see [RFC4506]).
The CIR value MUST be greater than or equal to 0. The CIR value MUST be greater than or equal to 0.
CBS (Committed Burst Size): 32 bits CBS (Committed Burst Size): 32 bits
The value of the CBS is in units of bytes. The CBS is encoded The value of the CBS is in units of bytes. The CBS is encoded as
as a 32-bit IEEE single-precision floating-point number (see a 32-bit IEEE single-precision floating-point number (see
[RFC4506]). [RFC4506]).
When CIR is strictly greater than 0 (CIR > 0), the CBS MUST be When CIR is strictly greater than 0 (CIR > 0), the CBS MUST be
greater than or equal to the maximum frame size. greater than or equal to the maximum frame size.
EIR (Excess Information Rate): 32 bits EIR (Excess Information Rate): 32 bits
The value of the EIR is in units of bytes per second. The EIR The value of the EIR is in units of bytes per second. The EIR is
is encoded as a 32-bit IEEE single-precision floating-point encoded as a 32-bit IEEE single-precision floating-point number
number (see [RFC4506]). (see [RFC4506]).
The EIR value MUST be greater than or equal to 0. The EIR value MUST be greater than or equal to 0.
EBS (Excess Burst Size): 32 bits EBS (Excess Burst Size): 32 bits
The value of the EBS is in units of bytes. The EBS is encoded The value of the EBS is in units of bytes. The EBS is encoded as
as a 32-bit IEEE single-precision floating-point number (see a 32-bit IEEE single-precision floating-point number (see
[RFC4506]). [RFC4506]).
When EIR is strictly greater than 0 (EIR > 0), the EBS MUST be When EIR is strictly greater than 0 (EIR > 0), the EBS MUST be
greater than or equal to the maximum frame size. greater than or equal to the maximum frame size.
5. Ethernet FLOWSPEC Object 5. Ethernet FLOWSPEC Object
The Ethernet FLOWSPEC object (Class-Num = 12, Class-Type = TBA by The Ethernet FLOWSPEC object (Class-Num = 9, Class-Type = 6) has the
IANA, with recommended value 6) has the same format as the same format as the Ethernet SENDER_TSPEC object.
Ethernet SENDER_TSPEC object.
6. Ethernet ADSPEC Object 6. Ethernet ADSPEC Object
There is no ADSPEC object associated with the Ethernet There is no ADSPEC object associated with the Ethernet SENDER_TSPEC
SENDER_TSPEC object. object.
Either the ADSPEC object is omitted or an IntServ ADSPEC with the Either the ADSPEC object is omitted or an IntServ ADSPEC with the
Default General Characterization Parameters and Guaranteed Default General Characterization Parameters and Guaranteed Service
Service fragment is used, see [RFC2210]. fragment is used, see [RFC2210].
7. Processing 7. Processing
The Ethernet SENDER_TSPEC and FLOWSPEC objects specified in this The Ethernet SENDER_TSPEC and FLOWSPEC objects specified in this
document MAY be used for signaling Ethernet LSP. For signaling document MAY be used for signaling Ethernet LSP. For signaling such
such LSP, in the Generalized LABEL_REQUEST object (see an LSP, in the Generalized LABEL_REQUEST object (see [RFC3471]), the
[RFC3471]), the Switching Type field MUST be set to the value 51 Switching Type field MUST be set to the value 51 (L2SC) and the LSP
(L2SC) and the LSP Encoding Type field MUST be set to the value 2 Encoding Type field MUST be set to the value 2 (Ethernet).
(Ethernet).
The Ethernet SENDER_TSPEC object carries the traffic The Ethernet SENDER_TSPEC object carries the traffic specification
specification generated by the RSVP session sender. The Ethernet generated by the RSVP session sender. The Ethernet SENDER_TSPEC
SENDER_TSPEC object SHOULD be forwarded and delivered unchanged object SHOULD be forwarded and delivered unchanged to both
to both intermediate and egress nodes. intermediate and egress nodes.
The Ethernet FLOWSPEC object carries reservation request The Ethernet FLOWSPEC object carries reservation request information
information generated by receivers. As with any FLOWSPEC object, generated by receivers. As with any FLOWSPEC object, the Ethernet
Ethernet FLOWSPEC object flows upstream toward the ingress node. FLOWSPEC object flows upstream toward the ingress node.
Intermediate and egress nodes MUST verify that the node itself Intermediate and egress nodes MUST verify that the node itself and
and the interfaces on which the LSP will be established can the interfaces on which the LSP will be established can support the
support the requested Switching Granularity, MTU and values requested Switching Granularity, MTU and values included in subobject
included in sub-object TLVs. These nodes MUST be configured with TLVs. These nodes MUST be configured with the same predefined CT
the same pre-defined CT sets as the index value signaled as part sets as the index value signaled as part of the Index field of the
of the index field of the Ethernet Bandwidth Profile TLV (see Ethernet Bandwidth Profile TLV (see Section 4.1). If the requested
Section 4.1). If the requested value(s) can not be supported, the value(s) cannot be supported, the receiver node MUST generate a
receiver node MUST generate a PathErr message with the error code PathErr message with the error code "Traffic Control Error" and the
"Traffic Control Error" and the error value "Service unsupported" error value "Service unsupported" (see [RFC2205]).
(see [RFC2205]).
In addition, if the MTU field is received with a value smaller In addition, if the MTU field is received with a value smaller than
than the minimum transfer unit size of the Ethernet frame (e.g. the minimum transfer unit size of the Ethernet frame (e.g., 46 bytes
46 bytes for Ethernet V2, 38 bytes for IEEE 802.3), the node MUST for Ethernet v2, 38 bytes for IEEE 802.3), the node MUST generate a
generate a PathErr message with the error code "Traffic Control PathErr message with the error code "Traffic Control Error" and the
Error" and the error value "Bad Tspec value" (see [RFC2205]). error value "Bad Tspec value" (see [RFC2205]).
Error processing of the CLASSTYPE object follows rules defined in Error processing of the CLASSTYPE object follows rules defined in
[RFC4124]. Error processing of the EXTENDED_CLASSTYPE object [RFC4124]. Error processing of the EXTENDED_CLASSTYPE object follows
follows rules defined in [MCOS]. Moreover, an LSR receiving a rules defined in [MCOS]. Moreover, a Label Switching Router (LSR)
Path message with the EXTENDED_CLASSTYPE object, which recognizes receiving a Path message with the EXTENDED_CLASSTYPE object, which
the object and the particular Class-Type but does detect a recognizes the object and the particular Class-Type but does detect a
mismatch in the index values, MUST send a PathErr message towards mismatch in the index values, MUST send a PathErr message towards the
the sender with the error code "Extended Class-Type Error" and sender with the error code "Extended Class-Type Error" and the error
the error value "Class-Type mismatch" (see [RFC2205]). value "Class-Type mismatch" (see [RFC2205]).
8. Security Considerations 8. Security Considerations
This document introduces no new security considerations to either This document introduces no new security considerations to [RFC3473].
[RFC3473].
GMPLS security is described in section 11 of [RFC3471] and refers GMPLS security is described in Section 11 of [RFC3471] and refers to
to [RFC3209] for RSVP-TE. Further details of MPLS-TE and GMPLS [RFC3209] for RSVP-TE. Further details of MPLS-TE and GMPLS security
security can be found in [MPLS-SEC]. can be found in [RFC5920].
9. IANA Considerations 9. IANA Considerations
IANA maintain registries and sub-registries for RSVP-TE as used IANA maintains registries and sub-registries for RSVP-TE as used by
by GMPLS. IANA is requested to make allocations from these GMPLS. IANA has made allocations from these registries as set out in
registries as set out in the following sections. the following sections.
9.1. RSVP Objects Class Types 9.1. RSVP Objects Class Types
This document introduces two new Class Types for existing RSVP This document introduces two new Class Types for existing RSVP
objects. IANA is requested to make allocations from the "Resource objects. IANA has made allocations from the "Resource ReSerVation
ReSerVation Protocol (RSVP) Parameters" registry using the "Class Protocol (RSVP) Parameters" registry using the "Class Names, Class
Names, Class Numbers, and Class Types" sub-registry. Numbers, and Class Types" sub-registry.
Class Number Class Name Reference Class Number Class Name Reference
------------ ----------------------- --------- ------------ ----------------------- ---------
9 FLOWSPEC [RFC2205] 9 FLOWSPEC [RFC2205]
Class Type (C-Type): Class Type (C-Type):
6 Ethernet SENDER_TSPEC [This.I-D] 6 Ethernet SENDER_TSPEC [RFC6003]
Class Number Class Name Reference Class Number Class Name Reference
------------ ----------------------- --------- ------------ ----------------------- ---------
12 SENDER_TSPEC [RFC2205] 12 SENDER_TSPEC [RFC2205]
Class Type (C-Type): Class Type (C-Type):
6 Ethernet SENDER_TSPEC [This.I-D] 6 Ethernet SENDER_TSPEC [RFC6003]
9.2. Ethernet Switching Granularities 9.2. Ethernet Switching Granularities
IANA maintains a registry of GMPLS parameters called "Generalized IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters". Multi-Protocol Label Switching (GMPLS) Signaling Parameters".
IANA is requested to create a new sub-registry called "Ethernet IANA has created a new sub-registry called "Ethernet Switching
Switching Granularities" to contain the values that may be Granularities" to contain the values that may be carried in the
carried in the Switching Granularity field of the Ethernet Switching Granularity field of the Ethernet SENDER_TSPEC object.
SENDER_TSPEC object.
Values shall be assigned as follows: Values are as follows:
000-239,255 Assigned by IANA via IETF Standards Action 0-2 See below.
240-254 Reserved for Vendor Specific Usage 3-239 Unassigned
256-65535 Not assigned at this point in time 240-254 Reserved for Vendor-Specific Use
255 Reserved
256-65535 Not assigned at this time
Values 256 through 65535 are not to be assigned at this time. The registration procedure is Standards Action.
Before any assignments can be made in this range, there MUST be a
Standards Action that specifies IANA Considerations that covers
the range being assigned.
Initial entries in this sub-registry are as follows: Initial entries in this sub-registry are as follows:
Value Switching Granularity Reference Value Switching Granularity Reference
----- -------------------------------------- ---------- ----- -------------------------------------- ------------------
0 Provided in signaling. [GMPLS-ESVCS] 0 Provided in signaling. [RFC6003][RFC6004]
1 Ethernet Port (for port-based service) [This.I-D] 1 Ethernet Port (for port-based service) [RFC6003]
2 Ethernet Frame (for EVC-based service) [This.I-D] 2 Ethernet Frame (for EVC-based service) [RFC6003]
255 Reserved Value [This.I-D] 255 Reserved [RFC6003]
9.3. Ethernet Sender TSpec TLVs 9.3. Ethernet Sender TSpec TLVs
IANA maintains a registry of GMPLS parameters called "Generalized IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters". Multi-Protocol Label Switching (GMPLS) Signaling Parameters".
IANA is requested to create a new sub-registry called "Ethernet IANA has created a new sub-registry called "Ethernet Sender TSpec
SENDER_TSPEC TLVs" to contain the TLV type values for TLVs TLVs / Ethernet Flowspec TLVs" to contain the TLV type values for
carried in the Ethernet SENDER_TSPEC object. TLVs carried in the Ethernet SENDER_TSPEC object.
Values shall be assigned as follows: Values are as follows:
000-239,255 Assigned by IANA via IETF Standards Action 0-3 See below.
240-254 Reserved for Private Use 4-239 Unassigned
256-65535 Not assigned at this point in time 240-254 Reserved for Vendor-Specific Use
255 Reserved
256-65535 Not assigned at this time
Values 256 through 65535 are not to be assigned at this time. The registration procedure is Standards Action.
Before any assignments can be made in this range, there MUST be a
Standards Action that specifies IANA Considerations that covers
the range being assigned.
Initial entries in this sub-registry are as follows: Initial entries in this sub-registry are as follows:
Type Description Reference Type Description Reference
----- -------------------------------- --------- ----- -------------------------------- ---------
0 Reserved Value [This.I-D] 0 Reserved [RFC6003]
1 Reserved Value [This.I-D] 1 Reserved [RFC6003]
2 Ethernet Bandwidth Profile [This.I-D] 2 Ethernet Bandwidth Profile [RFC6003]
3 Layer 2 Control Processing (L2CP) [This.I-D] 3 Layer 2 Control Protocol (L2CP) [RFC6003]
255 Reserved Value [This.I-D] 255 Reserved [RFC6003]
9.4. Ethernet Bandwidth Profiles 9.4. Ethernet Bandwidth Profiles
IANA maintains a registry of GMPLS parameters called "Generalized IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters". Multi-Protocol Label Switching (GMPLS) Signaling Parameters".
IANA is requested to create a new sub-registry called "Ethernet IANA has created a new sub-registry called "Ethernet Bandwidth
Bandwidth Profiles" to contain bit flags carried in the Ethernet Profiles" to contain bit flags carried in the Ethernet Bandwidth
Bandwidth Profile TLV of the Ethernet SENDER_TSPEC object. Profile TLV of the Ethernet SENDER_TSPEC object.
Bits are to be allocated by IETF Standards Action. Bits are Bits are to be allocated by IETF Standards Action. Bits are numbered
numbered from bit 0 as the low order bit. from bit 0 as the low order bit. Initial entries are as follows:
Bit Hex Description Reference Bit Hex Description Reference
--- ---- -------------------------- ------------- --- ---- -------------------------- -------------
0 0x01 Coupling flag (CF) [This.I-D] 0 0x01 Coupling Flag (CF) [RFC6003]
1 0x02 Color mode (CM) [This.I-D] 1 0x02 Color Mode (CM) [RFC6003]
10. Acknowledgments 10. Acknowledgments
Many thanks to Adrian Farrel for his comments. Lou Berger Many thanks to Adrian Farrel for his comments. Lou Berger provided
provided the input on control traffic processing. the input on control traffic processing.
11. References 11. References
11.1. Normative References 11.1. Normative References
[GMPLS-ESVCS] Berger, L., et al., "Generalized MPLS (GMPLS) [MEF10.1] The MEF Technical Specification, "Ethernet Services
Support for Metro Ethernet Forum and G.8011 Attributes Phase 2", MEF 10.1, November 2006.
Ethernet Services", draft-berger-ccamp-gmpls-
ether-svcs, work in progress.
[RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. [RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Version 1 Functional Specification", RFC 2205, Functional Specification", RFC 2205, September 1997.
September 1997.
[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated [RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated
Services", RFC 2210, September 1997. Services", RFC 2210, September 1997.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
V., and G. Swallow, "RSVP-TE: Extensions to RSVP for and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
LSP Tunnels", RFC 3209, December 2001. Tunnels", RFC 3209, December 2001.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label [RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Functional Description", Switching (GMPLS) Signaling Functional Description", RFC
RFC 3471, January 2003. 3471, January 2003.
[RFC3473] Berger, L., "Generalized Multi-Protocol Label [RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Resource ReserVation Switching (GMPLS) Signaling Resource ReserVation Protocol-
Protocol-Traffic Engineering (RSVP-TE) Extensions", Traffic Engineering (RSVP-TE) Extensions", RFC 3473,
RFC 3473, January 2003. January 2003.
[RFC4124] Le Faucheur, F. et al, "Protocol extensions for [RFC4124] Le Faucheur, F., Ed., "Protocol Extensions for Support of
support of Diff-Serv-aware MPLS Traffic Engineering", Diffserv-aware MPLS Traffic Engineering", RFC 4124, June
RFC 4124, June 2005. 2005.
[RFC4506] Eisler, M., Ed. "XDR: External Data Representation [RFC4506] Eisler, M., Ed., "XDR: External Data Representation
Standard", RFC 4506, STD 67, May 2006. Standard", STD 67, RFC 4506, May 2006.
11.2. Informative References [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[ETHv2] Digital, Intel, and Xerox, "The Ethernet -- A Local [RFC6004] Berger, L. and D. Fedyk, "Generalized MPLS (GMPLS) Support
Area Network: Data Link Layer and Physical Layer for Metro Ethernet Forum and G.8011 Ethernet Services",
Specifications", Version 2.0, November 1982. RFC 6004, October 2010.
[IEEE802.3] IEEE 802.3 LAN/MAN CSMA/CD (Ethernet) Access 11.2. Informative References
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.
[MEF10.1] The MEF Technical Specification, "Ethernet Services [ETHv2] Digital, Intel, and Xerox, "The Ethernet -- A Local Area
Attributes Phase 2", MEF 10.1, November 2006. Network: Data Link Layer and Physical Layer
Specifications", Version 2.0, November 1982.
[MEF6] The Metro Ethernet Forum, "Ethernet Services [IEEE802.3]
Definitions - Phase I", MEF 6, June 2004. 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.
[MCOS] Minei, I., et al., "Extensions for Differentiated [MCOS] Minei, I., Gan, D., Kompella, K., and X. Li, "Extensions
Services-aware Traffic Engineered LSPs", draft-minei- for Differentiated Services-aware Traffic Engineered
diffserv-te-multi-class, work in progress. LSPs", Work in Progress, June 2006.
[MPLS-SEC] Fang, L. et al., "Security Framework for MPLS and [MEF6] The Metro Ethernet Forum, "Ethernet Services Definitions -
GMPLS Networks", draft-ietf-mpls-mpls-and-gmpls- Phase I", MEF 6, June 2004.
security-framework, work in progress.
Author's Addresses [MEF10.2] The MEF Technical Specification, "Ethernet Services
Attributes Phase 2", MEF 10.2, October 2009.
Dimitri Papadimitriou [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Alcatel-Lucent Bell Networks", RFC 5920, July 2010.
Copernicuslaan 50
B-2018 Antwerpen, Belgium Author's Address
Phone: +32 3 2408491
E-mail: dimitri.papadimitriou@alcatel-lucent.be Dimitri Papadimitriou
Alcatel-Lucent Bell
Copernicuslaan 50
B-2018 Antwerpen, Belgium
Phone: +32 3 2408491
EMail: dimitri.papadimitriou@alcatel-lucent.be
 End of changes. 160 change blocks. 
459 lines changed or deleted 441 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/