draft-ietf-ccamp-ethernet-traffic-parameters-01.txt   draft-ietf-ccamp-ethernet-traffic-parameters-02.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-01.txt draft-ietf-ccamp-ethernet-traffic-parameters-02.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 37
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.
Copyright Notice
Copyright (C) The IETF Trust (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 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
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 [MEF.10].
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
parameters are applicable non-discriminately to all EVCs crossing a
given port.
For Ethernet Virtual Private Line (EVPL) services [MEF.6], these
traffic parameters are applicable per Ethernet Virtual Connection
(EVC) with single of multiple Class of Service (CoS), independently
of its associated (set of) VLAN ID (VID). Association between EVC and
VIDs is detailed in [MEF.10]. The format and encoding of the (set of)
VIDs are documented in a companion document [MEF-SRV].
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 As the Bandwidth Profile defines the set of traffic parameters
applicable to a sequence of Service Frames, these objects MAY also applicable to a sequence of Service Frames, these objects MAY also
include several bandwidth profile parameters such as: include several bandwidth profile parameters such as:
skipping to change at page 3, line 4 skipping to change at page 3, line 24
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 3, line 37 skipping to change at page 4, line 4
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ 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 1 Ethernet Port (for port-based service)
2 Ethernet Frame 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.
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
skipping to change at page 4, line 44 skipping to change at page 5, line 11
of the value field in octets. A value field whose length is of the value field in octets. A value field whose length is
not a multiple of four MUST be zero-padded (with trailing not a multiple of four MUST be zero-padded (with trailing
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 TBD Reserved Reserved
129 24 see below Ethernet Bandwidth 129 24 see below Ethernet Bandwidth
Profile [MEF10] 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 Ethernet SENDER_TSPEC
object MAY include more than one Ethernet Bandwidth Profile TLV.
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 | Index | Reserved | | Profile | Index | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CIR | | CIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 34 skipping to change at page 5, line 49
| 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)
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 1): coupling flag (CF) Flag 1 (bit 0): coupling flag (CF)
Flag 2 (bit 2): color mode (CM) Flag 2 (bit 1): color mode (CM)
Where bit 1 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.
A flag is set to one to indicate that the corresponding metering A flag is set to one to indicate that the corresponding metering
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.
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 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 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 dedicated index MAY correspond 1:1 for each ClassType included A given index value j can be associated to at most N ClassType
in the extended ClassType object. A given index value can be values CTi (i =< N) of the extended ClassType object. This applies
associated to at most N ClassType values (i =< N). An example of in case a set of one or more CTi maps a single BW profile
index consists in allocating the CTi value to the index field. (shared). An example of value setting consists then in assigning
an arbitrary value (between 0x10 and 0x77) associated to set of
CTi.
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
consists then in allocating the CTi value to the index field
itself (i.e. 0x00,...,0x07). This applies in case a single CTi
maps a single BW profile or multiple BW profiles (dedicated). In
the former case (single BW profile), the Ethernet SENDER_TSPEC
object includes a single Ethernet Bandwidth Profile TLV. In the
second case, the Ethernet SENDER_TSPEC includes a set of more than
one Ethernet Bandwidth Profile TLVs (whose respective index value
is associated to a single CTi value).
Note that the current specification allow for combining shared and
dedicated BW profiles to the same LSP. That is, an Ethernet
SENDER_TSPEC MAY include multiple Ethernet Bandwidth Profile TLVs
whose respective index can be associated on a 1:1 basis to a
single CTi or to a set of multiple CTi.
In the extended classtype object [MCOS], in each of its subobject,
the CTi values SHOULD correspond 1:1 to MEF CE VLAN-CoS. In each
of its subobject, the BW requested per CTi field MAY be used for
bandwidth 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 5 skipping to change at page 7, line 47
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
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 5 skipping to change at page 8, line 44
Error processing of the Extended ClassType object follows rules Error processing of the Extended ClassType 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-classtype 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'. 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:
Two RSVP C-Types in registry: Two RSVP C-Types in registry:
http://www.iana.org/assignments/rsvp-parameters http://www.iana.org/assignments/rsvp-parameters
- 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).
skipping to change at page 9, line 5 skipping to change at page 9, line 46
[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 [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.
11. Author's Addresses 11. Author's Addresses
Dimitri Papadimitriou Dimitri Papadimitriou
Alcatel Alcatel
Francis Wellesplein 1, Copernicuslaan 50
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 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
"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 AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 25 change blocks. 
43 lines changed or deleted 60 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/