draft-ietf-ccamp-ethernet-traffic-parameters-00.txt   draft-ietf-ccamp-ethernet-traffic-parameters-01.txt 
Network Working Group Dimitri Papadimitriou Network Working Group Dimitri Papadimitriou
Internet Draft Internet Draft
Category: Informational Category: Informational
Expires: April 2007 October 2006
MEF Ethernet Traffic Parameters MEF Ethernet Traffic Parameters
draft-ietf-ccamp-ethernet-traffic-parameters-00.txt draft-ietf-ccamp-ethernet-traffic-parameters-01.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 2, line 5 skipping to change at page 2, line 5
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
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 MEF.10 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.
MEF Ethernet Traffic Parameters October 2006
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]. MEF.10 as well as [RFC3471] and [RFC3473].
1. Introduction 1. Introduction
skipping to change at page 3, line 4 skipping to change at page 3, line 4
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: defines 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),
MEF Ethernet Traffic Parameters October 2006
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.
skipping to change at page 4, line 5 skipping to change at page 4, line 5
Value Switching Granularity Value Switching Granularity
----- --------------------- ----- ---------------------
1 Ethernet Port 1 Ethernet Port
2 Ethernet Frame 2 Ethernet Frame
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.
MEF Ethernet Traffic Parameters October 2006
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 optional TLV. and MAY include one or more than one TLV.
Each TLV has the following format: 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 44 skipping to change at page 4, line 46
zeros) so that the TLV is four-octet aligned. zeros) so that the TLV is four-octet aligned.
Type: 16 bits Type: 16 bits
Defined values are: Defined values are:
Type Length Format Description Type Length Format Description
-------------------------------------------------- --------------------------------------------------
128 20 Reserved Reserved 128 20 Reserved Reserved
129 24 see below Ethernet Bandwidth 129 24 see below Ethernet Bandwidth
Profile [MEF.10] Profile [MEF10]
Value 0 is reserved. Values 1 through 127 are assigned by Value 0 is reserved. Values 1 through 127 are assigned by
IANA via IETF Standards Track RFC Action. IANA via IETF Standards Track RFC Action.
Values 128 through 255 are reserved for vendor specific Values 128 through 255 are reserved for vendor specific
usage. usage.
MEF Ethernet Traffic Parameters October 2006
3.1 Ethernet Bandwidth Profile TLV 3.1 Ethernet Bandwidth Profile TLV
Type 129 TLV indicates the Ethernet Bandwidth Profile. It defines Type 129 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. to a particular Ethernet service instance.
The Type 129 TLV has the following format: The Type 129 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 | Reserved | | Profile | Index | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CIR | | CIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CBS | | CBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EIR | | EIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EBS | | EBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 50 skipping to change at page 5, line 52
is requested. 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 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.
Reserved: 24 bits Index: 8 bits
The index field is used to reference bandwidth allocated for a
given class of service (CoS) in case a multiple CoS LSP is being
MEF Ethernet Traffic Parameters October 2006
requested. The index field value MUST correspond to at least one
of the index value included in the extended ClassType object ([DS-
TE], [MCOS]).
A dedicated index MAY correspond 1:1 for each ClassType included
in the extended ClassType object. A given index value can be
associated to at most N ClassType values (i =< N). An example of
index consists in allocating the CTi value to the index field.
By default, the value of the index field MUST be set to 0.
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 [RFC1832]).
skipping to change at page 6, line 39 skipping to change at page 7, line 5
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]).
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.
MEF Ethernet Traffic Parameters October 2006
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
skipping to change at page 7, line 30 skipping to change at page 7, line 45
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 a "Traffic
Control Error/Service unsupported" indication (see [RFC2205]). Control Error/Service unsupported" indication (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 a "Traffic Control Error/ Bad Tspec value"
indication (see [RFC2205]). indication (see [RFC2205]).
Error processing of the Extended ClassType object follows rules
defined in [MCOS]. Moreover, an LSR receiving a Path message with the
extended-classtype object, which recognizes the object and the
particular Class-Type but does detect a mismatch in the index values,
MUST send a PathErr towards the sender with the error code 'extended-
classtype Error' and an error value of 'Class-Type mismatch'.
7. Security Considerations 7. Security Considerations
MEF Ethernet Traffic Parameters October 2006
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
Two values have been defined by IANA for this document: Two values have been defined by IANA for this document:
skipping to change at page 8, line 31 skipping to change at page 9, line 5
[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.
MEF Ethernet Traffic Parameters October 2006
9.2. Informative References 9.2. Informative References
[MEF.10] MEF Technical Specification, "Ethernet Services [MEF.10] MEF Technical Specification, "Ethernet Services
Attributes Phase 1", MEF 10, November 2004. Attributes Phase 1", MEF 10, November 2004.
[MCOS] I.Minei et al., "Extensions for Differentiated
Services-aware Traffic Engineered LSPs", draft-minei-
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.
11. Author's Addresses 11. Author's Addresses
Dimitri Papadimitriou Dimitri Papadimitriou
Alcatel Alcatel
Francis Wellesplein 1, Francis Wellesplein 1,
B-2018 Antwerpen, Belgium B-2018 Antwerpen, Belgium
Phone: +32 3 2408491 Phone: +32 3 2408491
EMail: dimitri.papadimitriou@alcatel.be EMail: dimitri.papadimitriou@alcatel.be
MEF Ethernet Traffic Parameters October 2006
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
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
 End of changes. 16 change blocks. 
5 lines changed or deleted 53 lines changed or added

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