[ledbat] Fwd: New Version Notification for draft-ietf-ledbat-congestion-07.txt

[Janardhan Iyengar <[e-mail]>]

Hi all,

We've posted a new version of the LEDBAT document that addresses all issues brought up in WGLC but one.  Besides some nits, the main changes are:
1. We changed the text in the Fairness section to more accurately reflect possible issues with LEDBAT's fairness. (Dario's comments)
2. The applicability section now has better articulation about LEDBAT's interactions with with ECN and AQM. (Bob's, Gorry's, Arjuna's comments)

We haven't yet addressed the MIN_CWND issue under extreme congestion;  we hope to resolve this issue at the IETF.  We are planning to not discuss the question of incentivizing ECN within this document.  It seems like a question that is worth considering in a broader context and needs more discussion;  at this late hour (in/after WGLC), it seems like an issue that we may not be able to resolve here.  It can certainly be brought to the table if/when LEDBAT goes from experimental to standards-track.

- jana

-------- Original Message --------
Subject: New Version Notification for draft-ietf-ledbat-congestion-07.txt
Date: Mon, 11 Jul 2011 10:57:51 -0700
From: [e-mail]
To: [e-mail]
CC: [e-mail], [e-mail],	[e-mail], [e-mail]

A new version of I-D, draft-ietf-ledbat-congestion-07.txt has been successfully submitted by Mirja Kuehlewind and posted to the IETF repository.

Filename:	 draft-ietf-ledbat-congestion
Revision:	 07
Title:		 Low Extra Delay Background Transport (LEDBAT)
Creation date:	 2011-07-11
WG ID:		 ledbat
Number of pages: 18

Abstract:
    LEDBAT is an experimental delay-based congestion control algorithm
    that attempts to utilize the available bandwidth on an end-to-end
    path while limiting the consequent increase in queueing delay on the
    path.  LEDBAT uses changes in one-way delay measurements to limit
    congestion that the flow itself induces in the network.  LEDBAT is
    designed for use by background bulk-transfer applications; it is
    designed to be no more aggressive than TCP congestion control and to
    yield in the presence of any competing flows when latency builds,
    thus limiting interference with the network performance of the
    competing flows.

                                                                                   


The IETF Secretariat