draft-ietf-mpls-over-l2tpv3-02.txt   draft-ietf-mpls-over-l2tpv3-03.txt 
Network Working Group M. Townsley Network Working Group M. Townsley
Internet-Draft C. Pignataro Internet-Draft C. Pignataro
Expiration Date: April 2007 S. Wainner Expiration Date: May 2007 S. Wainner
cisco Systems cisco Systems
T. Seely T. Seely
Sprint Nextel Sprint Nextel
J. Young J. Young
October 2006 November 2006
Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3 Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3
draft-ietf-mpls-over-l2tpv3-02.txt draft-ietf-mpls-over-l2tpv3-03.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 6, line 23 skipping to change at page 6, line 23
This document specifies an encapsulation method for MPLS inside the This document specifies an encapsulation method for MPLS inside the
L2TPv3 tunnel payload. MPLS can carry a number of different protocols L2TPv3 tunnel payload. MPLS can carry a number of different protocols
as payloads. When an MPLS/L2TPv3 flow carries IP-based traffic, the as payloads. When an MPLS/L2TPv3 flow carries IP-based traffic, the
aggregate traffic is assumed to be TCP friendly due to the congestion aggregate traffic is assumed to be TCP friendly due to the congestion
control mechanisms used by the payload traffic. Packet loss will control mechanisms used by the payload traffic. Packet loss will
trigger the necessary reduction in offered load, and no additional trigger the necessary reduction in offered load, and no additional
congestion avoidance action is necessary. congestion avoidance action is necessary.
When an MPLS/L2TPv3 flow carries payload traffic that is not known to When an MPLS/L2TPv3 flow carries payload traffic that is not known to
be TCP friendly and the flow runs across an unprovisioned path, the be TCP friendly and the flow runs across an unprovisioned path that
application that uses the encapsulation specified in this document could potentially become congested, the application that uses the
MUST employ additional mechanisms to ensure that the offered load is encapsulation specified in this document MUST employ additional
reduced appropriately during periods of congestion. The MPLS/L2TPv3 mechanisms to ensure that the offered load is reduced appropriately
flow should not exceed the average bandwidth that a TCP flow across during periods of congestion. The MPLS/L2TPv3 flow should not exceed
the same network path and experiencing the same network conditions the average bandwidth that a TCP flow across the same network path
would achieve, measured on a reasonable timescale. and experiencing the same network conditions would achieve, measured
on a reasonable timescale. This is not necessary in the case of an
unprovisioned path through an overprovisioned network, where the
potential for congestion is avoided through the overprovisioning of
the network.
The comparison to TCP cannot be specified exactly but is intended as The comparison to TCP cannot be specified exactly but is intended as
an "order-of-magnitude" comparison in timescale and throughput. The an "order-of-magnitude" comparison in timescale and throughput. The
timescale on which TCP throughput is measured is the round-trip time timescale on which TCP throughput is measured is the round-trip time
of the connection. In essence, this requirement states that it is not of the connection. In essence, this requirement states that it is not
acceptable to deploy an application using the encapsulation specified acceptable to deploy an application using the encapsulation specified
in this document on the best-effort Internet, which consumes in this document on the best-effort Internet, which consumes
bandwidth arbitrarily and does not compete fairly with TCP within an bandwidth arbitrarily and does not compete fairly with TCP within an
order of magnitude. One method of determining an acceptable bandwidth order of magnitude. One method of determining an acceptable bandwidth
is described in [RFC3448]. Other methods exist, but are outside the is described in [RFC3448]. Other methods exist, but are outside the
 End of changes. 4 change blocks. 
10 lines changed or deleted 14 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/