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

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