draft-ietf-ccamp-ethernet-traffic-parameters-03.txt   draft-ietf-ccamp-ethernet-traffic-parameters-04.txt 
Network Working Group D. Papadimitriou
Network Working Group Dimitri Papadimitriou
Internet Draft Internet Draft
Category: Standards Track Category: Standards Track
Expires: April 2008 November 2007 Created: April 14, 2008
Expires: October 13, 2008
Ethernet Traffic Parameters Ethernet Traffic Parameters
draft-ietf-ccamp-ethernet-traffic-parameters-03.txt draft-ietf-ccamp-ethernet-traffic-parameters-04.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 39 skipping to change at page 1, line 38
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 April 2008. This Internet-Draft will expire on October 13, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
Ethernet Traffic Parameters Nov. 2007
Abstract Abstract
This document described 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 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 [RFC2119].
Moreover, the reader is assumed to be familiar with the terminology Moreover, the reader is assumed to be familiar with the terminology
MEF10 as well as [RFC3471] and [RFC3473]. [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 describes 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 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 [MEF6], 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 [MEF6], 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 or multiple Class of Service (CoS), independently (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 format
and encoding of the (set of) VIDs are documented in a companion and encoding of the (set of) VIDs is documented in a companion
document [GMPLS-ESVCS]. 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.
Ethernet Traffic Parameters Nov. 2007 The Bandwidth Profile defines the set of traffic parameters
applicable to a sequence of Service Frames, referred to as bandwidth
Bandwidth Profile defines the set of traffic parameters applicable to profile parameters:
a sequence of Service Frames, referred to as bandwidth profile
parameters:
- Committed Rate: indicates the rate at which traffic commits to - 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 its 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: indicates the extent by which the traffic sent on a - 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), 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
interface speed to remain EIR-conformant. interface speed to remain EIR-conformant.
- The color mode (CM) parameter indicates whether the "color- - The color mode (CM) parameter indicates whether the "color-
aware" or "color-blind" property is employed by the bandwidth aware" or "color-blind" property is employed by the bandwidth
profile. profile.
- The coupling flag (CF) parameter allows the choice between two - The coupling flag (CF) parameter allows the choice between two
modes of operations of the rate enforcement algorithm. modes of operations of the rate enforcement algorithm.
3. Ethernet SENDER_TSPEC object 3. 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) has the following format: IANA 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 are:
Value Switching Granularity Value Switching Granularity
----- --------------------- ----- ---------------------
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)
Value 0 is reserved. Values 1 through 127 are assigned by IANA via Value 0 is reserved. Values 1 through 127 are assigned by IANA via
IETF Standards Track RFC action. IETF Standards Track RFC action.
Values 128 through 255 are reserved for vendor specific usage. Values 128 through 255 are reserved for vendor specific usage.
skipping to change at page 4, line 41 skipping to change at page 4, line 33
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 more than one TLV. and MAY include more than one TLV.
Each TLV has the following format (in accordance to [RFC4420]): Each 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Value ~ ~ Value ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 4, line 52 skipping to change at page 5, line 4
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
Ethernet Traffic Parameters Nov. 2007
Defined values are: Defined values are:
Type Length Format Description Type Length Format Description
-------------------------------------------------- --------------------------------------------------
1 TBD Reserved Reserved 1 TBD Reserved Reserved
2 20 see Section 3.1 Ethernet Bandwidth 2 20 see Section 3.1 Ethernet Bandwidth
Profile [MEF10.1] Profile [MEF10.1]
3 4 [GMPLS-ESVCS] Layer 2 Control 3 4 [GMPLS-ESVCS] Layer 2 Control
Processing (L2CP) Processing (L2CP)
Value 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 value length of the TLV, i.e., the length of Indicates the length of the whole TLV including the Type and
the value field in octets. A value field whose length is not Length fields. A value field whose length is not a multiple
a multiple of four MUST be zero-padded (with trailing zeros) of four MUST be zero-padded (with trailing zeros) so that
so that the TLV is four-octet aligned. the TLV is four-octet aligned.
3.1 Ethernet Bandwidth Profile TLV 3.1 Ethernet Bandwidth Profile TLV
The Type 2 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 2 TLV has the following format: The Type 2 TLV has the following format:
skipping to change at page 5, line 54 skipping to change at page 6, line 4
| 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 7, line 4 skipping to change at page 7, line 6
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.
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 - each CTi value SHOULD correspond 1:1 to MEF CE VLAN-CoS
- the BW requested per CTi field MAY be used for bandwidth - the BW requested per CTi field MAY be used for bandwidth
accounting purposes. accounting purposes.
skipping to change at page 7, line 28 skipping to change at page 7, line 27
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
(see [RFC1832]). (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
[RFC1832]). [RFC4506]).
When CIR is strictly greater than 0 (CIR > 0), the CBS MUST be When CIR is strictly greater than 0 (CIR > 0), the CBS MUST be
greater than or equal to the maximum frame size. greater than or equal to the maximum frame size.
EIR (Excess Information Rate): 32 bits EIR (Excess Information Rate): 32 bits
The value of the EIR is in units of bytes per second. The EIR The value of the EIR is in units of bytes per second. The EIR
is encoded as a 32-bit IEEE single-precision floating-point is encoded as a 32-bit IEEE single-precision floating-point
number (see [RFC1832]). number (see [RFC4506]).
The EIR value MUST be greater than or equal to 0. The EIR value MUST be greater than or equal to 0.
EBS (Excess Burst Size): 32 bits EBS (Excess Burst Size): 32 bits
The value of the EBS is in units of bytes. The EBS is encoded The value of the EBS is in units of bytes. The EBS is encoded
as a 32-bit IEEE single-precision floating-point number (see as a 32-bit IEEE single-precision floating-point number (see
[RFC1832]). [RFC4506]).
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 - recommended value 6) 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
skipping to change at page 9, line 5 skipping to change at page 9, line 5
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 towards the sender with the error code "Extended
Class-Type Error" and the error value "Class-Type mismatch" (see Class-Type Error" and the error value "Class-Type mismatch" (see
[RFC2205]). [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. Further details of MPLS-TE and GMPLS security
can be found in [MPLS-SEC].
8. IANA Considerations 8. IANA Considerations
Two values have been defined by IANA for this document: IANA maintain registries and sub-registries for RSVP-TE as used by
GMPLS. IANA is requested to make allocations from these registries as
set out in the following scetions.
Two RSVP C-Types in registry: 8.1. RSVP Objects Class Types
http://www.iana.org/assignments/rsvp-parameters
- An Ethernet SENDER_TSPEC object: Class = 12, C-Type = TBA (see This document introduces two new Class Types for existing RSVP
Section 3). objects. IANA is requested to make allocations from the "Resource
ReSerVation Protocol (RSVP) Parameters" registry using the "Class
Names, Class Numbers, and Class Types" sub-registry.
- An Ethernet FLOWSPEC object: Class = 9, C-Type = TBA (see Class
Section 4). Number Class Name Reference
------ ----------------------- ---------
9 FLOWSPEC [RFC2205]
Class Types or C-Types:
6 Ethernet SENDER_TSPEC [This.I-D]
12 SENDER_TSPEC [RFC2205]
Class Types or C-Types:
6 Ethernet SENDER_TSPEC [This.I-D]
8.2. Ethernet Switching Granularities
IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters". IANA is
requested to create a new sub-registry called "Ethernet Switching
Granularities" to contain the values that may be carried in the
Switching Granularity field of the Ethernet SENDER_TSPEC object.
Values may be assigned as follows:
0 Reserved
1-127 IETF Standards Track RFC action
128-255 Vendor Specific Usage
Initial entries in this sub-registry are as follows:
Value Switching Granularity Reference
----- -------------------------------------- ---------
0 Reserved [This.I-D]
1 Ethernet Port (for port-based service) [This.I-D]
2 Ethernet Frame (for EVC-based service) [This.I-D]
8.3. Ethernet Sender TSpec TLVs
IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters". IANA is
requested to create a new sub-registry called "Ethernet Sender TSpec
TLVs" to contain the TLV type values for TLVs carried in the Ethernet
SENDER_TSPEC object.
Values may be assigned as follows:
0 Reserved
1-239 IETF Standards Track RFC action
240-254 Vendor Specific Usage
255 Reserved
Initial entries in this sub-registry are as follows:
Type Description Reference
----- -------------------------------- ---------
0 Reserved [This.I-D]
1 Reserved [This.I-D]
2 Ethernet Bandwidth Profile [This.I-D]
3 Layer 2 Control Processing (L2CP) [This.I-D]
255 Reserved [This.I-D]
8.4. Ethernet Bandwidth Profiles
IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters". 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 Track RFC action.
Bits are numbered from bit 0 as the low order bit.
Bit Hex Description Reference
--- ---- -------------------------- -------------
0 0x01 Coupling flag (CF) [This.I-D]
1 0x02 Color mode (CM) [This.I-D]
9. References 9. References
9.1. Normative References 9.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-00.txt, Services", draft-berger-ccamp-gmpls-ether-svcs, work
Internet-draft, Work in progress, November 2007. in progress.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
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.
[RFC4506] Eisler, M., Ed. "XDR: External Data Representation
Standard", RFC 4506, STD 67, May 2006.
9.2. Informative References 9.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 - Phase I", MEF 6, June 2004. Definitions - Phase I", MEF 6, June 2004.
[MEF11] The Metro Ethernet Forum , "User Network [MEF11] The Metro Ethernet Forum , "User Network
Interface (UNI) Requirements and Framework", Interface (UNI) Requirements and Framework",
MEF 11, November 2004. 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.
[MPLS-SEC] Fang, L., " Security Framework for MPLS and GMPLS
Networks", draft-ietf-mpls-mpls-and-gmpls-security-
framework, work in progress.
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 provided
the input on control traffic processing. 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
E-mail: dimitri.papadimitriou@alcatel-lucent.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 (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
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
 End of changes. 50 change blocks. 
77 lines changed or deleted 132 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/