Re: [tcpm] taking RFC 2861 (Congestion Window Validation) to Proposed Standard?

Salman Abdul Baset <salman@cs.columbia.edu> Thu, 14 June 2007 22:02 UTC

Return-path: <tcpm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyxOE-0000YG-9A; Thu, 14 Jun 2007 18:02:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyxOD-0000YB-8f for tcpm@ietf.org; Thu, 14 Jun 2007 18:02:01 -0400
Received: from serrano.cc.columbia.edu ([128.59.29.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyxOB-0006JU-V9 for tcpm@ietf.org; Thu, 14 Jun 2007 18:02:01 -0400
Received: from flame.cs.columbia.edu (flame.cs.columbia.edu [128.59.16.145]) (user=sa2086 mech=PLAIN bits=0) by serrano.cc.columbia.edu (8.13.7/8.13.6) with ESMTP id l5EM13nE017252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 14 Jun 2007 18:01:03 -0400 (EDT)
Date: Thu, 14 Jun 2007 18:01:03 -0400
From: Salman Abdul Baset <salman@cs.columbia.edu>
To: Sally Floyd <sallyfloyd@mac.com>
Subject: Re: [tcpm] taking RFC 2861 (Congestion Window Validation) to Proposed Standard?
In-Reply-To: <b1e79256f18fcb6f81ae417fde5ca646@mac.com>
Message-ID: <Pine.GSO.4.64.0706141750150.15874@flame.cs.columbia.edu>
References: <b1e79256f18fcb6f81ae417fde5ca646@mac.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.6
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: Jitu Padhye <padhye@microsoft.com>, tcpm <tcpm@ietf.org>, Eli Brosh <elibrosh@cs.columbia.edu>, Mark Handley <M.Handley@cs.ucl.ac.uk>
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Errors-To: tcpm-bounces@ietf.org

For application limited workloads such as streaming over TCP, we have 
found that the CW validation mechanism, which decays CW for a sufficiently 
long application-limited period, can increase sensitivity to timeouts.
-s


On Thu, 14 Jun 2007, Sally Floyd wrote:

> This email is to ask the working group if RFC 2861 on Congestion
> Window Validation (CWV) should be left at Experimental, or whether
> it is time to start the process of moving it to Proposed Standard.
>
> RFC 2861, from June 2000, "describes a simple modification to TCP's
> congestion control algorithms to decay the congestion window cwnd
> after the transition from a sufficiently-long application-limited
> period, while using the slow-start threshold ssthresh to save
> information about the previous value of the congestion window.
>
> RFC 2861 also recommends that "the TCP sender should not increase
> the congestion window when the TCP sender has been application-limited
> (and therefore has not fully used the current congestion window)".
>
> My understanding is that CWV has been included in Linux since
> Linux 2.4, but that it is not included in Microsoft.
>
> Are there any experience reports about CWV (positive or negative),
> or experience reports of problems (or the absence of problems) for
> TCP connections without CWV?  Or are there other opinions about
> whether it is time to start the process of moving RFC 2861 to
> Proposed Standard?  Any feedback would be welcome.
>
> - Sally
> http://www.icir.org/floyd/
>
> In the spirit of doing due diligence with old Experimental RFCs...
>
>
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www1.ietf.org/mailman/listinfo/tcpm
>

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm