draft-ietf-ccamp-ethernet-traffic-parameters-06.txt   draft-ietf-ccamp-ethernet-traffic-parameters-07.txt 
Network Working Group D. Papadimitriou Network Working Group Dimitri Papadimitriou
Internet Draft Alcatel-Lucent Internet Draft Alcatel-Lucent
Intended status: Standards Track October 31, 2008 Intended status: Standards Track April 7, 2009
Expires: April 30, 2009 Expires: October 6, 2009
Ethernet Traffic Parameters Ethernet Traffic Parameters
draft-ietf-ccamp-ethernet-traffic-parameters-06.txt draft-ietf-ccamp-ethernet-traffic-parameters-07.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that This Internet-Draft is submitted to IETF in full conformance with the
any applicable patent or other IPR claims of which he or she is provisions of BCP 78 and BCP 79.
aware 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.
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.
This Internet-Draft will expire on April 30, 2009.
Copyright Notice
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.
1. Introduction 1. Introduction
Per [RFC3471], GMPLS allows the inclusion of technology specific Per [RFC3471], Generalized Multi-Protocol Label Switching (GMPLS)
parameters in signaling. Ethernet SENDER_TSPEC and FLOWSPEC specific allows the inclusion of technology specific parameters in signaling.
objects are introduced in this document that describe Metro Ethernet Ethernet SENDER_TSPEC and FLOWSPEC specific objects are introduced in
Forum (MEF) Ethernet traffic parameters as specified in [MEF10.1]. this document that describe Metro Ethernet Forum (MEF) Ethernet
traffic parameters as specified in [MEF10.1].
These traffic parameters MUST be used when the L2SC value is These traffic parameters MUST be used when the L2SC value is
specified in the LSP Switching Type field of a Generalized Label specified in the LSP Switching Type field of a Generalized Label
Request (see [RFC3471]) and the LSP encoding type is Ethernet. For Request (see [RFC3471]) and the LSP encoding type is Ethernet. For
example: example:
o 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 each EVC crossing a
given port. given port.
o For Ethernet Virtual Private Line (EVPL) services [MEF6], these o For Ethernet Virtual Private Line (EVPL) services [MEF6], these
traffic parameters are applicable per Ethernet Virtual Connection traffic parameters are applicable per Ethernet Virtual 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 Association between EVC and VIDs is detailed in [MEF10.1]. The
format and encoding of the (set of) VIDs is documented in a format and encoding of the (set of) VIDs is documented in a
companion document [GMPLS-ESVCS]. companion document [GMPLS-ESVCS].
skipping to change at page 3, line 10 skipping to change at page 2, line 50
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:
o Committed Rate: indicates the rate at which traffic commits to be o Committed Rate: indicates the rate at which traffic commits to be
sent to the Ethernet LSP. The Committed Rate is described in terms sent to the Ethernet LSP. The Committed Rate is described in terms
of the CIR (Committed Information Rate) and CBS (Committed Burst of the CIR (Committed Information Rate) and CBS (Committed Burst
Size) traffic parameters. Size) traffic parameters.
o CIR is defined as the average rate (in bytes per unit of time) up . CIR is defined as the average rate (in bytes per unit of time) up
to which the network is committed to transfer frames and meets to which the network is committed to transfer frames and meets
its performance objectives. its performance objectives.
o 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.
o Excess Rate: indicates the extent by which the traffic sent on an o Excess Rate: indicates the extent by which the traffic sent on 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.
o 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 frames in excess of the CIR, up to which the network may transfer frames
without any performance objectives. without any performance objectives.
o EBS defines a limit on the maximum number of information unit . EBS defines a limit on the maximum number of information unit
(e.g., bytes) available for a burst of frames sent at the (e.g., bytes) available for a burst of frames sent at the
interface speed to remain EIR-conformant. interface speed to remain EIR-conformant.
o Color mode (CM): indicates whether the "color-aware" or "color- o Color mode (CM): indicates whether the "color-aware" or "color-
blind" property is employed by the bandwidth profile. blind" property is employed by the bandwidth profile.
o Coupling flag (CF): allows the choice between two modes of o Coupling flag (CF): allows the choice between two modes of
operations of the rate enforcement algorithm. operations of the rate enforcement algorithm.
4. Ethernet SENDER_TSPEC Object 4. Ethernet SENDER_TSPEC Object
skipping to change at page 6, line 32 skipping to change at page 6, line 24
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 property is employed by the bandwidth profile. When Flag 2 is
set to value 0 (1), the bandwidth profile algorithm is said to set to value 0 (1), the bandwidth profile algorithm is said to
be in 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 values included in the CLASSTYPE object [RFC4124] or
TE], [MCOS]). EXTENDED_CLASSTYPE object [MCOS].
A given index value j can be associated to at most N Class-Type A given index value j can be associated to at most N Class-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 (shared) BW applies in case a set of one or more CTi maps a single (shared) BW
profile. An example of value setting consists then in assigning profile. An example of value setting consists then in assigning
an arbitrary value (comprised within the range [0x08,0xF8], an arbitrary value comprised within the range [0x08,0xF8[
defined by the 5 MSB of the Index field) associated to a set of associated to a set of CTi, the values in the range [0xF8,0xFF]
CTi. This allows mapping to one of 248 pre-defined CTi sets. being selected for reserved sets. This allows mapping to one of
248 pre-defined CTi sets.
A given index value j can be associated to a single CTi (1:1 A given index value j can be associated to a single CTi (1:1
correspondence). In this case, the index value setting consists correspondence). In this case, the index value setting consists
then in assigning the 3 LSB of the index field itself to the CTi then in assigning the 3 LSB of the index field itself to the CTi
value itself (comprised in the range [0x00,0x07]). This applies in value itself (comprised in the range [0x00,0x07]). This applies in
case a single CTi maps a single (dedicated) BW profile or multiple case a single CTi maps a single (dedicated) BW profile or multiple
(dedicated) BW profiles. In the former case (single BW profile), (dedicated) BW profiles. In the former case (single BW profile),
the Ethernet SENDER_TSPEC object includes a single Ethernet the Ethernet SENDER_TSPEC object includes a single Ethernet
Bandwidth Profile TLV. In the second case, the Ethernet Bandwidth Profile TLV. In the second case, the Ethernet
SENDER_TSPEC includes a set of more than one Ethernet Bandwidth SENDER_TSPEC includes a set of more than one Ethernet Bandwidth
skipping to change at page 9, line 38 skipping to change at page 9, line 31
set out in the following sections. set out in the following sections.
9.1. RSVP Objects Class Types 9.1. RSVP Objects Class Types
This document introduces two new Class Types for existing RSVP This document introduces two new Class Types for existing RSVP
objects. IANA is requested to make allocations from the "Resource objects. IANA is requested to make allocations from the "Resource
ReSerVation Protocol (RSVP) Parameters" registry using the "Class ReSerVation Protocol (RSVP) Parameters" registry using the "Class
Names, Class Numbers, and Class Types" sub-registry. Names, Class Numbers, and Class Types" sub-registry.
Class Number Class Name Reference Class Number Class Name Reference
------------ ---------- --------- ------------ ----------------------- ---------
9 FLOWSPEC [RFC2205] 9 FLOWSPEC [RFC2205]
Class Type (C-Type): Class Type (C-Type):
6 Ethernet SENDER_TSPEC [This.I-D] 6 Ethernet SENDER_TSPEC [This.I-D]
Class Number Class Name Reference Class Number Class Name Reference
------------ ---------- --------- ------------ ----------------------- ---------
12 SENDER_TSPEC [RFC2205] 12 SENDER_TSPEC [RFC2205]
Class Type (C-Type): Class Type (C-Type):
6 Ethernet SENDER_TSPEC [This.I-D] 6 Ethernet SENDER_TSPEC [This.I-D]
9.2. Ethernet Switching Granularities 9.2. Ethernet Switching Granularities
IANA maintains a registry of GMPLS parameters called "Generalized IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters". IANA is Multi-Protocol Label Switching (GMPLS) Signaling Parameters". IANA is
skipping to change at page 10, line 24 skipping to change at page 10, line 17
Values shall be assigned as follows: Values shall be assigned as follows:
000 Reserved 000 Reserved
001-127 IETF Standards Track RFC action 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]
9.3. Ethernet Sender TSpec TLVs 9.3. Ethernet Sender TSpec TLVs
IANA maintains a registry of GMPLS parameters called "Generalized IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters". IANA is Multi-Protocol Label Switching (GMPLS) Signaling Parameters". 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
skipping to change at page 10, line 47 skipping to change at page 10, line 40
Values shall be assigned as follows: Values shall be assigned as follows:
000 Reserved 000 Reserved
001-239 IETF Standards Track RFC action 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]
9.4. Ethernet Bandwidth Profiles 9.4. Ethernet Bandwidth Profiles
IANA maintains a registry of GMPLS parameters called "Generalized IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters". IANA is Multi-Protocol Label Switching (GMPLS) Signaling Parameters". 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 Bits are to be allocated by IETF Standards Track RFC action. Bits are
numbered from bit 0 as the low order bit. numbered from bit 0 as the low order bit.
Bit Hex Description Reference Bit Hex Description Reference
--- ---- ----------- --------- --- ---- -------------------------- -------------
0 0x01 Coupling flag (CF) [This.I-D] 0 0x01 Coupling flag (CF) [This.I-D]
1 0x02 Color mode (CM) [This.I-D] 1 0x02 Color mode (CM) [This.I-D]
10. Acknowledgments 10. Acknowledgments
Many thanks to Adrian Farrel for his comments. Lou Berger provided Many thanks to Adrian Farrel for his comments. Lou Berger provided
the input on control traffic processing. the input on control traffic processing.
11. References 11. References
skipping to change at page 12, line 14 skipping to change at page 12, line 7
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", 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", RFC Protocol-Traffic Engineering (RSVP-TE) Extensions", RFC
3473, January 2003. 3473, January 2003.
[RFC4124] Le Faucheur et al, "Protocol extensions for support of
Diff-Serv-aware MPLS Traffic Engineering", RFC4124.
[RFC4506] Eisler, M., Ed. "XDR: External Data Representation [RFC4506] Eisler, M., Ed. "XDR: External Data Representation
Standard", RFC 4506, STD 67, May 2006. Standard", RFC 4506, STD 67, May 2006.
11.2. Informative References 11.2. Informative References
[MEF10.1] The MEF Technical Specification, "Ethernet Services [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 Definitions [MEF6] The Metro Ethernet Forum, "Ethernet Services Definitions
- Phase I", MEF 6, June 2004. - Phase I", MEF 6, June 2004.
skipping to change at page 13, line 6 skipping to change at page 13, line 6
Author's Addresses Author's Addresses
Dimitri Papadimitriou Dimitri Papadimitriou
Alcatel-Lucent Bell Alcatel-Lucent Bell
Copernicuslaan 50 Copernicuslaan 50
B-2018 Antwerpen, Belgium B-2018 Antwerpen, Belgium
Phone: +32 3 2408491 Phone: +32 3 2408491
E-mail: dimitri.papadimitriou@alcatel-lucent.be E-mail: dimitri.papadimitriou@alcatel-lucent.be
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
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
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any This document is subject to BCP 78 and the IETF Trust's Legal
copyrights, patents or patent applications, or other proprietary Provisions Relating to IETF Documents in effect on the date of
rights that may cover technology that may be required to implement publication of this document (http://trustee.ietf.org/license-info).
this standard. Please address the information to the IETF at Please review these documents carefully, as they describe your rights
ietf-ipr@ietf.org. and restrictions with respect to this document.
 End of changes. 22 change blocks. 
67 lines changed or deleted 34 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/