draft-ietf-ccamp-ethernet-traffic-parameters-05.txt   draft-ietf-ccamp-ethernet-traffic-parameters-06.txt 
Network Working Group D. Papadimitriou Network Working Group D. Papadimitriou
Internet Draft Alcatel-Lucent Internet Draft Alcatel-Lucent
Category: Standards Track Intended status: Standards Track October 31, 2008
Created: July 12, 2008 Expires: April 30, 2009
Expires: January 11, 2009
Ethernet Traffic Parameters Ethernet Traffic Parameters
draft-ietf-ccamp-ethernet-traffic-parameters-05.txt draft-ietf-ccamp-ethernet-traffic-parameters-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that
applicable patent or other IPR claims of which he or she is aware any applicable patent or other IPR claims of which he or she is
have been or will be disclosed, and any of which he or she becomes aware have been or will be disclosed, and any of which he or she
aware will be disclosed, in accordance with Section 6 of BCP 79. becomes aware will be disclosed, in accordance with Section 6 of
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 months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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
For potential updates to the above required-text see:
http://www.ietf.org/ietf/1id-guidelines.txt
This Internet-Draft will expire on January 11, 2009. This Internet-Draft will expire on April 30, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document describes the Metro Ethernet Forum (MEF) - specific This document describes the Metro Ethernet Forum (MEF) - specific
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.
Conventions Used In This Document
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].
Moreover, the reader is assumed to be familiar with the terminology
[MEF10.1] as well as [RFC3471] and [RFC3473].
1. Introduction 1. Introduction
Per [RFC3471], GMPLS allows the inclusion of technology specific Per [RFC3471], GMPLS allows the inclusion of technology specific
parameters in signaling. Ethernet SENDER_TSPEC and FLOWSPEC specific parameters in signaling. Ethernet SENDER_TSPEC and FLOWSPEC specific
objects are introduced in this document that describe Metro Ethernet objects are introduced in this document that describe Metro Ethernet
Forum (MEF) 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 L2SC is specified in the These traffic parameters MUST be used when the L2SC value is
LSP Switching Type field of a Generalized Label Request (see specified in the LSP Switching Type field of a Generalized Label
[RFC3471]) and the LSP encoding type is Ethernet. Request (see [RFC3471]) and the LSP encoding type is Ethernet. For
example:
For Ethernet Private Line (EPL) services [MEF6], these traffic o For Ethernet Private Line (EPL) services [MEF6], these traffic
parameters are applicable non-discriminately to all EVCs crossing a parameters are applicable non-discriminately to all EVCs crossing a
given port. given port.
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 Connection
(EVC) with single or multiple Class of Service (CoS), independent (EVC) with single or multiple Class of Service (CoS), independent
of its associated (set of) VLAN ID (VID). of its associated (set of) VLAN ID (VID).
Association between EVC and VIDs is detailed in [MEF10.1]. The format Association between EVC and VIDs is detailed in [MEF10.1]. The
and encoding of the (set of) VIDs is documented in a companion format and encoding of the (set of) VIDs is documented in a
document [GMPLS-ESVCS]. companion document [GMPLS-ESVCS].
2. Overview This does not prevent broader usage for Ethernet LSP of the traffic
parameters specified in this document.
2. Conventions used in this document
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].
Moreover, the reader is assumed to be familiar with the terminology
[MEF10.1] as well as [RFC3471] and [RFC3473].
3. Overview
The Ethernet SENDER_TSPEC/FLOWSPEC object includes the Ethernet link The Ethernet SENDER_TSPEC/FLOWSPEC object includes the Ethernet link
type (switching granularity) of the requested LSP, and the MTU value type (switching granularity) of the requested LSP, and the MTU value
for the LSP. 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 bandwidth
profile parameters: profile parameters:
- Committed Rate: Indicates the rate at which traffic commits to o Committed Rate: indicates the rate at which traffic commits to be
be sent to the Ethernet LSP. The Committed Rate is described in sent to the Ethernet LSP. The Committed Rate is described in terms
terms of the CIR (Committed Information Rate) and CBS (Committed of the CIR (Committed Information Rate) and CBS (Committed Burst
Burst Size) traffic parameters. Size) traffic parameters.
CIR is defined as the average rate (in bytes per unit of time) o CIR is defined as the average rate (in bytes per unit of time) up
up to which the network is committed to transfer frames and to which the network is committed to transfer frames and meets
meets its performance objectives. its performance objectives.
CBS defines a limit on the maximum number of information units o CBS defines a limit on the maximum number of information units
(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 CIR-conformant. interface speed to remain CIR-conformant.
- Excess Rate: Indicates the extent by which the traffic sent on an o Excess Rate: indicates the extent by which the traffic sent on an
Ethernet LSP exceeds the committed rate. The Excess Rate is 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.
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 time),
in excess of the CIR, up to which the network may transfer in excess of the CIR, up to which the network may transfer frames
frames without any performance objectives. without any performance objectives.
EBS defines a limit on the maximum number of information units 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.
- The color mode (CM) parameter indicates whether the "color- o Color mode (CM): indicates whether the "color-aware" or "color-
aware" or "color-blind" property is employed by the bandwidth blind" property is employed by the bandwidth profile.
profile.
- The coupling flag (CF) parameter allows the choice between two o Coupling flag (CF): allows the choice between two modes of
modes of operations of the rate enforcement algorithm. operations of the rate enforcement algorithm.
3. 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 = TBA by
IANA recommended value 6) has the following format: 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 ~
skipping to change at page 4, line 4 skipping to change at page 4, line 5
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 This field indicates the type of link that comprises the requested
requested Ethernet LSP. 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)
Values 0 through 127 are assigned by IANA via IETF Standards Values 0 through 127 are assigned by IANA via IETF Standards
Track RFC action. Track RFC action.
Values 128 through 255 are reserved for vendor specific usage. Values 128 through 255 are reserved for vendor specific usage.
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 MUST NOT take a value smaller than 46 bytes for Ethernet The MTU field MUST NOT take a value smaller than 46 bytes for
v2 and 38 bytes for IEEE 802.3. Ethernet v2 and 38 bytes for IEEE 802.3.
TLV: 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 has 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 ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 4 skipping to change at page 4, line 47
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
-------------------------------------------------- ------------------------------------------------------
1 TBD Reserved Reserved 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)
Values 0 and 255 are reserved. Values 0 and 255 are reserved.
Values 1 through 239 are assigned by IANA via IETF Standards Values 1 through 239 are assigned by IANA via IETF Standards
Track RFC Action. Track RFC Action.
Values 240 through 254 are reserved for vendor specific Values 240 through 254 are reserved for vendor specific
usage. usage.
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 the
Type and Length fields. A value field whose length is not a Type and Length fields. A value field whose length is not a
multiple of four MUST be zero-padded (with trailing zeros) multiple of four MUST be zero-padded (with trailing zeros)
so that the TLV is four-octet aligned. so that the TLV is four-octet aligned.
3.1 Ethernet Bandwidth Profile TLV 4.1. Ethernet Bandwidth Profile TLV
The Type 2 TLV indicates the Ethernet Bandwidth Profile. It defines The Type 2 TLV specifies the Ethernet Bandwidth Profile. It defines
an upper bound on the volume of the expected service frames belonging an upper bound on the volume of the expected service frames belonging
to a particular Ethernet service instance. The Ethernet SENDER_TSPEC to a particular Ethernet service instance. The Ethernet SENDER_TSPEC
object MAY include more than one Ethernet Bandwidth Profile TLV. 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 |
skipping to change at page 6, line 12 skipping to change at page 6, line 12
| 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 vector of binary flags. The following
flags are defined: 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, Where bit 0 is the low order bit. Other flags are reserved, they
they SHOULD be set to zero when sent, and SHOULD be ignored when SHOULD be set to zero when sent, and SHOULD be ignored when
received. received.
A flag is set to one to indicate that the corresponding metering A flag is set to value 1 to indicate that the corresponding
is requested. metering is requested.
The Flag 1 allows the choice between two modes of operations of The Flag 1 allows the choice between two modes of operations of
the rate enforcement algorithm. the rate enforcement algorithm.
The Flag 2 indicates whether the color-aware or color-blind The Flag 2 indicates whether the color-aware or color-blind
property is employed by the bandwidth profile. When Flag 2 is set property is employed by the bandwidth profile. When Flag 2 is
to 0 (1), the bandwidth profile algorithm is said to be in set to value 0 (1), the bandwidth profile algorithm is said to
color blind (color aware) mode. 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 one
of the index value included in the extended ClassType object ([DS- of the index value included in the extended ClassType object ([DS-
TE], [MCOS]). TE], [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-Type
values CTi (i =< N) of the extended Class-Type object. This values CTi (i =< N) of the extended Class-Type object. This
applies in case a set of one or more CTi maps a single BW profile applies in case a set of one or more CTi maps a single (shared) BW
(shared). An example of value setting consists then in assigning profile. An example of value setting consists then in assigning
an arbitrary value (between 0x10 and 0x77) associated to set of an arbitrary value (comprised within the range [0x08,0xF8],
CTi. defined by the 5 MSB of the Index field) associated to a set of
CTi. This allows mapping to one of 248 pre-defined CTi sets.
As a particular case, a given index value j can be associated to a A given index value j can be associated to a single CTi (1:1
single CTi (1:1 correspondence). An example of index value setting correspondence). In this case, the index value setting consists
consists then in allocating the CTi value to the index field then in assigning the 3 LSB of the index field itself to the CTi
itself (i.e. 0x00,...,0x07). This applies in case a single CTi value itself (comprised in the range [0x00,0x07]). This applies in
maps a single BW profile or multiple BW profiles (dedicated). In case a single CTi maps a single (dedicated) BW profile or multiple
the former case (single BW profile), the Ethernet SENDER_TSPEC (dedicated) BW profiles. In the former case (single BW profile),
object includes a single Ethernet Bandwidth Profile TLV. In the the Ethernet SENDER_TSPEC object includes a single Ethernet
second case, the Ethernet SENDER_TSPEC includes a set of more than Bandwidth Profile TLV. In the second case, the Ethernet
one Ethernet Bandwidth Profile TLVs (whose respective index value SENDER_TSPEC includes a set of more than one Ethernet Bandwidth
is associated to a single CTi value). Profile TLVs (whose respective Index value is associated to a
single CTi value).
Note that the current specification allow for combining shared and Note that the current specification allow for combining shared and
dedicated BW profiles to the same LSP. That is, an Ethernet dedicated BW profiles to the same LSP. That is, an Ethernet
SENDER_TSPEC MAY include multiple Ethernet Bandwidth Profile TLVs SENDER_TSPEC object MAY include multiple Ethernet Bandwidth
whose respective index can be associated on a 1:1 basis to a Profile TLVs whose respective index can be associated on a 1:1
single CTi or to a set of multiple CTi. 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 Class-Type object [MCOS]:
- 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
- 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 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 encoded as a 32-bit IEEE single-precision floating-point number
skipping to change at page 8, line 8 skipping to change at page 8, line 14
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 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.
4. Ethernet FLOWSPEC Format 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 - recommended value 6) has the same format as the Ethernet IANA, with recommended value 6) has the same format as the Ethernet
SENDER_TSPEC object. SENDER_TSPEC object.
5. ADSPEC Considerations 6. Ethernet ADSPEC Object
There is no ADSPEC associated with the Ethernet SENDER_TSPEC object. There is no ADSPEC object associated with the Ethernet SENDER_TSPEC
object.
Either the ADSPEC is omitted or an Int-serv ADSPEC with the Default Either the ADSPEC object is omitted or an IntServ ADSPEC with the
General Characterization Parameters and Guaranteed Service fragment Default General Characterization Parameters and Guaranteed Service
is used, see [RFC2210]. fragment is used, see [RFC2210].
6. Processing 7. Processing
The Ethernet SENDER_TSPEC object carries the traffic specification The Ethernet SENDER_TSPEC object carries the traffic specification
generated by the RSVP session sender. The Ethernet SENDER_TSPEC generated by the RSVP session sender. The Ethernet SENDER_TSPEC
object SHOULD be forwarded and delivered unchanged to both object SHOULD be forwarded and delivered unchanged to both
intermediate and egress nodes. intermediate and egress nodes.
The Ethernet FLOWSPEC object carries reservation request information The Ethernet FLOWSPEC object carries reservation request information
generated by receivers. As with any FLOWSPEC object, Ethernet generated by receivers. As with any FLOWSPEC object, Ethernet
FLOWSPEC object flows upstream toward the ingress node. FLOWSPEC object flows upstream toward the ingress node.
skipping to change at page 8, line 51 skipping to change at page 9, line 11
In addition, if the MTU field is received with a value smaller than 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 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 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 PathErr message with the error code "Traffic Control Error" and the
error value "Bad Tspec value" (see [RFC2205]). error value "Bad Tspec value" (see [RFC2205]).
Error processing of the Extended Class-Type object follows rules Error processing of the Extended Class-Type object follows rules
defined in [MCOS]. Moreover, an LSR receiving a Path message with the defined in [MCOS]. Moreover, an LSR receiving a Path message with the
Extended Class-Type object, which recognizes the object and the Extended Class-Type object, which recognizes the object and the
particular Class-Type but does detect a mismatch in the index values, particular Class-Type but does detect a mismatch in the index values,
MUST send a PathErr towards the sender with the error code "Extended MUST send a PathErr message towards the sender with the error code
Class-Type Error" and the error value "Class-Type mismatch" (see "Extended Class-Type Error" and the error value "Class-Type mismatch"
[RFC2205]). (see [RFC2205]).
7. 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 to
[RFC3209] for RSVP-TE. Further details of MPLS-TE and GMPLS security [RFC3209] for RSVP-TE. Further details of MPLS-TE and GMPLS security
can be found in [MPLS-SEC]. can be found in [MPLS-SEC].
8. IANA Considerations 9. IANA Considerations
IANA maintain registries and sub-registries for RSVP-TE as used by IANA maintain registries and sub-registries for RSVP-TE as used by
GMPLS. IANA is requested to make allocations from these registries as GMPLS. IANA is requested to make allocations from these registries as
set out in the following scetions. set out in the following sections.
8.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 Class Number Class Name Reference
Number Class Name Reference ------------ ---------- ---------
------ ----------------------- ---------
9 FLOWSPEC [RFC2205] 9 FLOWSPEC [RFC2205]
Class Types or C-Types: Class Type (C-Type):
6 Ethernet SENDER_TSPEC [This.I-D] 6 Ethernet SENDER_TSPEC [This.I-D]
Class Number Class Name Reference
------------ ---------- ---------
12 SENDER_TSPEC [RFC2205] 12 SENDER_TSPEC [RFC2205]
Class Types or C-Types: Class Type (C-Type):
6 Ethernet SENDER_TSPEC [This.I-D] 6 Ethernet SENDER_TSPEC [This.I-D]
8.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". IANA is
requested to create a new sub-registry called "Ethernet Switching requested to create a new sub-registry called "Ethernet Switching
Granularities" to contain the values that may be carried in the Granularities" to contain the values that may be carried in the
Switching Granularity field of the Ethernet SENDER_TSPEC object. Switching Granularity field of the Ethernet SENDER_TSPEC object.
Values may be assigned as follows: Values shall be assigned as follows:
0 Reserved
1-127 IETF Standards Track RFC action 000 Reserved
001-127 IETF Standards Track RFC action
128-255 Vendor Specific Usage 128-255 Vendor Specific Usage
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 Reserved [This.I-D] 0 Reserved [This.I-D]
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]
8.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". IANA is
requested to create a new sub-registry called "Ethernet Sender TSpec requested to create a new sub-registry called "Ethernet SENDER_TSPEC
TLVs" to contain the TLV type values for TLVs carried in the Ethernet TLVs" to contain the TLV type values for TLVs carried in the Ethernet
SENDER_TSPEC object. SENDER_TSPEC object.
Values may be assigned as follows: Values shall be assigned as follows:
0 Reserved
1-239 IETF Standards Track RFC action 000 Reserved
001-239 IETF Standards Track RFC action
240-254 Vendor Specific Usage 240-254 Vendor Specific Usage
255 Reserved 255 Reserved
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 [This.I-D] 0 Reserved [This.I-D]
1 Reserved [This.I-D] 1 Reserved [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 [This.I-D] 255 Reserved [This.I-D]
8.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". IANA is
requested to create a new sub-registry called "Ethernet Bandwidth requested to create a new sub-registry called "Ethernet Bandwidth
Profiles" to contain bit flags carried in the Ethernet Bandwidth Profiles" to contain bit flags carried in the Ethernet 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 Track RFC action. Bits are to be allocated by IETF Standards Track RFC action. Bits are
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]
9. References 10. Acknowledgments
9.1. Normative References Many thanks to Adrian Farrel for his comments. Lou Berger provided
the input on control traffic processing.
11. References
11.1. Normative References
[GMPLS-ESVCS] Berger, L., et al., "Generalized MPLS (GMPLS) Support [GMPLS-ESVCS] Berger, L., et al., "Generalized MPLS (GMPLS) Support
For Metro Ethernet Forum and G.8011 Ethernet For Metro Ethernet Forum and G.8011 Ethernet
Services", draft-berger-ccamp-gmpls-ether-svcs, work Services", draft-berger-ccamp-gmpls-ether-svcs, work
in progress. in progress.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[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
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 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
Switching (GMPLS) Signaling Functional Description", (GMPLS) Signaling Functional Description", RFC 3471,
RFC 3471, January 2003. 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", Protocol-Traffic Engineering (RSVP-TE) Extensions", RFC
RFC 3473, January 2003. 3473, January 2003.
[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.
9.2. Informative References 11.2. Informative References
[MEF10.1] The MEF Technical Specification, "Ethernet Services [MEF10.1] The MEF Technical Specification, "Ethernet Services
Attributes Phase 2", MEF 10.1, November 2006. Attributes Phase 2", MEF 10.1, November 2006.
[MEF6] The Metro Ethernet Forum, "Ethernet Services [MEF6] The Metro Ethernet Forum, "Ethernet Services Definitions
Definitions - Phase I", MEF 6, June 2004. - Phase I", MEF 6, June 2004.
[MEF11] The Metro Ethernet Forum , "User Network [MEF11] The Metro Ethernet Forum, "User Network Interface (UNI)
Interface (UNI) Requirements and Framework", Requirements and Framework", MEF 11, November 2004.
MEF 11, November 2004.
[MCOS] I.Minei et al., "Extensions for Differentiated [MCOS] Minei, I., et al., "Extensions for Differentiated
Services-aware Traffic Engineered LSPs", draft-minei- Services-aware Traffic Engineered LSPs", draft-minei-
diffserv-te-multi-class, work in progress. diffserv-te-multi-class, work in progress.
[MPLS-SEC] Fang, L., " Security Framework for MPLS and GMPLS [MPLS-SEC] Fang, L. et al., "Security Framework for MPLS and GMPLS
Networks", draft-ietf-mpls-mpls-and-gmpls-security- Networks", draft-ietf-mpls-mpls-and-gmpls-security-
framework, work in progress. framework, work in progress.
10. Acknowledgments Author's Addresses
Many thanks to Adrian Farrel for his comments. Lou Berger provided
the input on control traffic processing.
11. 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
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
skipping to change at page 13, line 5 skipping to change at page 13, line 20
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
 End of changes. 81 change blocks. 
150 lines changed or deleted 157 lines changed or added

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