draft-ietf-ccamp-ethernet-traffic-parameters-02.txt   draft-ietf-ccamp-ethernet-traffic-parameters-03.txt 
Network Working Group Dimitri Papadimitriou Network Working Group Dimitri Papadimitriou
Internet Draft Internet Draft
Category: Informational Category: Standards Track
MEF Ethernet Traffic Parameters Expires: April 2008 November 2007
draft-ietf-ccamp-ethernet-traffic-parameters-02.txt Ethernet Traffic Parameters
draft-ietf-ccamp-ethernet-traffic-parameters-03.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 any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. 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
skipping to change at page 1, line 37 skipping to change at page 1, line 39
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: For potential updates to the above required-text see:
http://www.ietf.org/ietf/1id-guidelines.txt http://www.ietf.org/ietf/1id-guidelines.txt
This Internet-Draft will expire on November 2007. This Internet-Draft will expire on April 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Ethernet Traffic Parameters Nov. 2007
Abstract Abstract
This document described the Metro Ethernet Forum (MEF) - specific This document described the Metro Ethernet Forum (MEF) - specific
Ethernet Traffic Parameters as described in MEF.10 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 Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [1]. document are to be interpreted as described in RFC-2119 [1].
Moreover, the reader is assumed to be familiar with the terminology Moreover, the reader is assumed to be familiar with the terminology
MEF.10 as well as [RFC3471] and [RFC3473]. MEF10 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 describes Metro Ethernet objects are introduced in this document that describes Metro Ethernet
Forum (MEF) Ethernet traffic parameters as specified in [MEF.10]. 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 L2SC is specified in the
LSP Switching Type field of a Generalized Label Request (see LSP Switching Type field of a Generalized Label Request (see
[RFC3471]) and the LSP encoding type is Ethernet. [RFC3471]) and the LSP encoding type is Ethernet.
For Ethernet Private Line (EPL) services [MEF.6], these traffic 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 [MEF.6], these 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 of multiple Class of Service (CoS), independently (EVC) with single or multiple Class of Service (CoS), independently
of its associated (set of) VLAN ID (VID). Association between EVC and of its associated (set of) VLAN ID (VID).
VIDs is detailed in [MEF.10]. The format and encoding of the (set of)
VIDs are documented in a companion document [MEF-SRV]. Association between EVC and VIDs is detailed in [MEF10.1]. The format
and encoding of the (set of) VIDs are documented in a companion
document [GMPLS-ESVCS].
2. Overview 2. 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.
As the Bandwidth Profile defines the set of traffic parameters Ethernet Traffic Parameters Nov. 2007
applicable to a sequence of Service Frames, these objects MAY also
include several bandwidth profile parameters such as:
- Committed Rate: defines the rate at which traffic commits to Bandwidth Profile defines the set of traffic parameters applicable to
a sequence of Service Frames, referred to as bandwidth profile
parameters:
- Committed Rate: indicates the rate at which traffic commits to
be sent to the Ethernet LSP. The Committed Rate is described in be sent to the Ethernet LSP. The Committed Rate is described in
terms of the CIR (Committed Information Rate) and CBS (Committed terms of the CIR (Committed Information Rate) and CBS (Committed
Burst Size) traffic parameters. Burst Size) traffic parameters.
CIR is defined as the average rate (in bytes per unit of time) CIR is defined as the average rate (in bytes per unit of time)
up to which the network is committed to transfer frames and up to which the network is committed to transfer frames and
meets performance objectives. meets its performance objectives.
CBS defines a limit on the maximum number of information units 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: defines the extent by which the traffic sent on a - Excess Rate: indicates the extent by which the traffic sent on a
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), 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 without any performance objectives. frames without any performance objectives.
EBS defines a limit on the maximum number of information units EBS 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
skipping to change at page 3, line 50 skipping to change at page 4, line 4
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) has the following format: IANA) 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Ethernet Traffic Parameters Nov. 2007
| | | |
~ 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 Ethernet LSP. requested Ethernet LSP.
The permitted Ethernet Link Type values: The permitted Ethernet Link Type values:
Value Switching Granularity Value Switching Granularity
----- --------------------- ----- ---------------------
1 Ethernet Port (for port-based service) 1 Ethernet Port (for port-based service)
skipping to change at page 4, line 31 skipping to change at page 4, line 39
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 MUST NOT take a value smaller than 46 bytes for Ethernet
v2 and 38 bytes for IEEE 802.3. v2 and 38 bytes for IEEE 802.3.
TLV: TLV:
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 one or more than one TLV. and MAY include more than one TLV.
Each TLV has the following format: Each TLV has the following format (in accordance to [RFC4420]):
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 ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length: 16 bits
Indicates the total length of the TLV, i.e., 4 + the length
of the value field in octets. 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.
Type: 16 bits Type: 16 bits
Ethernet Traffic Parameters Nov. 2007
Defined values are: Defined values are:
Type Length Format Description Type Length Format Description
-------------------------------------------------- --------------------------------------------------
128 TBD Reserved Reserved 1 TBD Reserved Reserved
129 24 see below Ethernet Bandwidth 2 20 see Section 3.1 Ethernet Bandwidth
Profile [MEF10] Profile [MEF10.1]
3 4 [GMPLS-ESVCS] Layer 2 Control
Processing (L2CP)
Value 0 is reserved. Values 1 through 127 are assigned by Value 0 and 255 are reserved.
IANA via IETF Standards Track RFC Action.
Values 128 through 255 are reserved for vendor specific Values 1 through 239 are assigned by IANA via IETF Standards
Track RFC Action.
Values 240 through 254 are reserved for vendor specific
usage. usage.
Length: 16 bits
Indicates the value length of the TLV, i.e., the length of
the value field in octets. 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.
3.1 Ethernet Bandwidth Profile TLV 3.1 Ethernet Bandwidth Profile TLV
Type 129 TLV indicates the Ethernet Bandwidth Profile. It defines The Type 2 TLV indicates 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 129 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)
Ethernet Traffic Parameters Nov. 2007
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 SHOULD be set to zero when sent, and SHOULD be ignored when they SHOULD be set to zero when sent, and SHOULD be ignored when
received. received.
skipping to change at page 6, line 21 skipping to change at page 6, line 31
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 set
to 0 (1), the bandwidth profile algorithm is said to be in to 0 (1), the bandwidth profile algorithm is said to be in
color blind (color aware) mode. 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 class of service (CoS) in case a multiple CoS 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 ClassType A given index value j can be associated to at most N Class-Type
values CTi (i =< N) of the extended ClassType object. This applies values CTi (i =< N) of the extended Class-Type object. This
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 BW profile
(shared). An example of value setting consists then in assigning (shared). An example of value setting consists then in assigning
an arbitrary value (between 0x10 and 0x77) associated to set of an arbitrary value (between 0x10 and 0x77) associated to set of
CTi. CTi.
As a particular case, a given index value j can be associated to a As a particular case, a given index value j can be associated to a
single CTi (1:1 correspondence). An example of index value setting single CTi (1:1 correspondence). An example of index value setting
consists then in allocating the CTi value to the index field consists then in allocating the CTi value to the index field
itself (i.e. 0x00,...,0x07). This applies in case a single CTi itself (i.e. 0x00,...,0x07). This applies in case a single CTi
maps a single BW profile or multiple BW profiles (dedicated). In maps a single BW profile or multiple BW profiles (dedicated). In
the former case (single BW profile), the Ethernet SENDER_TSPEC the former case (single BW profile), the Ethernet SENDER_TSPEC
object includes a single Ethernet Bandwidth Profile TLV. In the object includes a single Ethernet Bandwidth Profile TLV. In the
second case, the Ethernet SENDER_TSPEC includes a set of more than second case, the Ethernet SENDER_TSPEC includes a set of more than
one Ethernet Bandwidth Profile TLVs (whose respective index value one Ethernet Bandwidth Profile TLVs (whose respective index value
is associated to a single CTi 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
Ethernet Traffic Parameters Nov. 2007
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 MAY include multiple Ethernet Bandwidth Profile TLVs
whose respective index can be associated on a 1:1 basis to a whose respective index can be associated on a 1:1 basis to a
single CTi or to a set of multiple CTi. single CTi or to a set of multiple CTi.
In the extended classtype object [MCOS], in each of its subobject, For each subobject of the extended Class-Type object [MCOS]:
the CTi values SHOULD correspond 1:1 to MEF CE VLAN-CoS. In each - each CTi value SHOULD correspond 1:1 to MEF CE VLAN-CoS
of its subobject, the BW requested per CTi field MAY be used for - the BW requested per CTi field MAY be used for bandwidth
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
skipping to change at page 7, line 44 skipping to change at page 8, line 5
number (see [RFC1832]). number (see [RFC1832]).
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 a 32-bit IEEE single-precision floating-point number (see as a 32-bit IEEE single-precision floating-point number (see
[RFC1832]). [RFC1832]).
Ethernet Traffic Parameters Nov. 2007
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 4. Ethernet FLOWSPEC format
The Ethernet FLOWSPEC object (Class-Num = 12, Class-Type = TBA by The Ethernet FLOWSPEC object (Class-Num = 12, Class-Type = TBA by
IANA) has the same format as the Ethernet SENDER_TSPEC object. IANA) has the same format as the Ethernet SENDER_TSPEC object.
5. ADSPEC considerations 5. ADSPEC considerations
There is no ADSPEC associated with the Ethernet SENDER_TSPEC object. There is no ADSPEC associated with the Ethernet SENDER_TSPEC object.
Either the ADSPEC is omitted or an Int-serv ADSPEC with the Default Either the ADSPEC is omitted or an Int-serv ADSPEC with the Default
General Characterization Parameters and Guaranteed Service fragment General Characterization Parameters and Guaranteed Service fragment
is used, see [RFC2210]. is used, see [RFC2210].
6. Processing 6. 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
skipping to change at page 8, line 18 skipping to change at page 8, line 31
is used, see [RFC2210]. is used, see [RFC2210].
6. Processing 6. 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, the information generated by receivers. As with any FLOWSPEC object, Ethernet
content of the Ethernet FLOWSPEC object flows upstream toward the FLOWSPEC object flows upstream toward the ingress node.
ingress node.
Intermediate and egress nodes MUST verify that the node itself and Intermediate and egress nodes MUST verify that the node itself and
the interfaces on which the LSP will be established can support the the interfaces on which the LSP will be established can support the
requested Switching Granularity, MTU and values included in sub- requested Switching Granularity, MTU and values included in sub-
object TLVs. If the requested value(s) can not be supported, the object TLVs. If the requested value(s) can not be supported, the
receiver node MUST generate a PathErr message with a "Traffic receiver node MUST generate a PathErr message with the error code
Control Error/Service unsupported" indication (see [RFC2205]). "Traffic Control Error" and the error value "Service unsupported"
(see [RFC2205]).
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 a "Traffic Control Error/ Bad Tspec value" PathErr message with the error code "Traffic Control Error" and the
indication (see [RFC2205]). error value "Bad Tspec value" (see [RFC2205]).
Error processing of the Extended ClassType 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-classtype 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 towards the sender with the error code "Extended
classtype Error' and an error value of 'Class-Type mismatch'. Class-Type Error" and the error value "Class-Type mismatch" (see
[RFC2205]).
Ethernet Traffic Parameters Nov. 2007
7. Security Considerations 7. 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. [RFC3209] for RSVP-TE.
8. IANA Considerations 8. IANA Considerations
skipping to change at page 9, line 19 skipping to change at page 9, line 32
- An Ethernet SENDER_TSPEC object: Class = 12, C-Type = TBA (see - An Ethernet SENDER_TSPEC object: Class = 12, C-Type = TBA (see
Section 3). Section 3).
- An Ethernet FLOWSPEC object: Class = 9, C-Type = TBA (see - An Ethernet FLOWSPEC object: Class = 9, C-Type = TBA (see
Section 4). Section 4).
9. References 9. References
9.1. Normative References 9.1. Normative References
[GMPLS-ESVCS] Berger, L., et al., "Generalized MPLS (GMPLS) Support
For Metro Ethernet Forum and G.8011 Ethernet
Services", draft-berger-ccamp-gmpls-ether-svcs-00.txt,
Internet-draft, Work in progress, November 2007.
[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.
[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.
[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.
[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.
Ethernet Traffic Parameters Nov. 2007
[RFC3471] Berger, L., "Generalized Multi-Protocol Label [RFC3471] Berger, L., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Functional Description", Switching (GMPLS) Signaling Functional Description",
RFC 3471, 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", Protocol-Traffic Engineering (RSVP-TE) Extensions",
RFC 3473, January 2003. RFC 3473, January 2003.
9.2. Informative References 9.2. Informative References
[MEF.10] MEF Technical Specification, "Ethernet Services [MEF10.1] The MEF Technical Specification, "Ethernet Services
Attributes Phase 1", MEF 10, November 2004. Attributes Phase 2", MEF 10.1, November 2006.
[MEF6] The Metro Ethernet Forum, "Ethernet Services
Definitions - Phase I", MEF 6, June 2004.
[MEF11] The Metro Ethernet Forum , "User Network
Interface (UNI) Requirements and Framework",
MEF 11, November 2004.
[MCOS] I.Minei et al., "Extensions for Differentiated [MCOS] I.Minei 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, June 2006. diffserv-te-multi-class, Work in progress, June 2006.
10. Acknowledgments 10. Acknowledgments
Many thanks to Adrian Farrel for his comments. Many thanks to Adrian Farrel for his comments. Lou Berger provided
the input on control traffic processing.
11. Author's Addresses 11. Author's Addresses
Dimitri Papadimitriou Dimitri Papadimitriou
Alcatel Alcatel
Copernicuslaan 50 Copernicuslaan 50
B-2018 Antwerpen, Belgium B-2018 Antwerpen, Belgium
Phone: +32 3 2408491 Phone: +32 3 2408491
EMail: dimitri.papadimitriou@alcatel.be E-mail: dimitri.papadimitriou@alcatel-lucent.be
Ethernet Traffic Parameters Nov. 2007
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
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
 End of changes. 44 change blocks. 
59 lines changed or deleted 105 lines changed or added

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