draft-ietf-ccamp-ethernet-traffic-parameters-04.txt   draft-ietf-ccamp-ethernet-traffic-parameters-05.txt 
Network Working Group D. Papadimitriou Network Working Group D. Papadimitriou
Internet Draft Internet Draft Alcatel-Lucent
Category: Standards Track Category: Standards Track
Created: April 14, 2008 Created: July 12, 2008
Expires: October 13, 2008 Expires: January 11, 2009
Ethernet Traffic Parameters Ethernet Traffic Parameters
draft-ietf-ccamp-ethernet-traffic-parameters-04.txt draft-ietf-ccamp-ethernet-traffic-parameters-05.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 38 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 October 13, 2008. This Internet-Draft will expire on January 11, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document describes the Metro Ethernet Forum (MEF) - specific This document describes the Metro Ethernet Forum (MEF) - specific
Ethernet Traffic Parameters as described in MEF10.1 when using Ethernet Traffic Parameters as described in MEF10.1 when using
Generalized Multi-Protocol Label Switching (GMPLS) Resource Generalized Multi-Protocol Label Switching (GMPLS) Resource
skipping to change at page 4, line 13 skipping to change at page 4, line 13
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 are: The permitted Ethernet Link Type values are:
Value Switching Granularity Value Switching Granularity
----- --------------------- ----- ---------------------
0 Provided in signaling. See [GMPLS-ESVCS]
1 Ethernet Port (for port-based service) 1 Ethernet Port (for port-based service)
2 Ethernet Frame (for EVC-based service) 2 Ethernet Frame (for EVC-based service)
Value 0 is reserved. Values 1 through 127 are assigned by IANA via Values 0 through 127 are assigned by IANA via IETF Standards
IETF Standards Track RFC action. Track RFC action.
Values 128 through 255 are reserved for vendor specific usage. Values 128 through 255 are reserved for vendor specific usage.
MTU: 16 bits MTU: 16 bits
This is a two-octet value indicating the MTU in octets. This is a two-octet value indicating the MTU in octets.
The MTU MUST NOT take a value smaller than 46 bytes for Ethernet The MTU 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.
skipping to change at page 5, line 11 skipping to change at page 5, line 11
~ Value ~ ~ Value ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 16 bits Type: 16 bits
Defined values are: Defined values are:
Type Length Format Description Type Length Format Description
-------------------------------------------------- --------------------------------------------------
1 TBD Reserved Reserved 1 TBD Reserved Reserved
2 20 see Section 3.1 Ethernet Bandwidth 2 24 see Section 3.1 Ethernet Bandwidth
Profile [MEF10.1] Profile [MEF10.1]
3 4 [GMPLS-ESVCS] Layer 2 Control 3 8 [GMPLS-ESVCS] Layer 2 Control
Processing (L2CP) Processing (L2CP)
Values 0 and 255 are reserved. Values 0 and 255 are reserved.
Values 1 through 239 are assigned by IANA via IETF Standards Values 1 through 239 are assigned by IANA via IETF Standards
Track RFC Action. Track RFC Action.
Values 240 through 254 are reserved for vendor specific Values 240 through 254 are reserved for vendor specific
usage. usage.
Length: 16 bits Length: 16 bits
Indicates the length of the whole TLV including the Type and Indicates the length in bytes of the whole TLV including the
Length fields. A value field whose length is not a multiple Type and Length fields. A value field whose length is not a
of four MUST be zero-padded (with trailing zeros) so that multiple of four MUST be zero-padded (with trailing zeros)
the TLV is four-octet aligned. so that 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 12, line 21 skipping to change at page 12, line 21
framework, work in progress. 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-Lucent Bell
Copernicuslaan 50 Copernicuslaan 50
B-2018 Antwerpen, Belgium B-2018 Antwerpen, Belgium
Phone: +32 3 2408491 Phone: +32 3 2408491
E-mail: dimitri.papadimitriou@alcatel-lucent.be E-mail: dimitri.papadimitriou@alcatel-lucent.be
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
 End of changes. 10 change blocks. 
14 lines changed or deleted 15 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/