Re: [tcpm] [Tmrg] Increasing the Initial Window - Notes

Joe Touch <touch@isi.edu> Thu, 18 November 2010 21:16 UTC

Return-Path: <touch@isi.edu>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36F9828C117 for <tcpm@core3.amsl.com>; Thu, 18 Nov 2010 13:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.961
X-Spam-Level:
X-Spam-Status: No, score=-101.961 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_00=-2.599, FB_YOU_CAN_BECOME=1.258, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mhxJagKablAy for <tcpm@core3.amsl.com>; Thu, 18 Nov 2010 13:16:28 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 6411B3A68E6 for <tcpm@ietf.org>; Thu, 18 Nov 2010 13:16:28 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id oAILGRg2022851 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 18 Nov 2010 13:16:27 -0800 (PST)
Message-ID: <4CE597AB.1020306@isi.edu>
Date: Thu, 18 Nov 2010 13:16:27 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: John Heffner <johnwheffner@gmail.com>
References: <20101110152857.GA5094@hell> <804D02FE-39AF-4437-BB15-C2247842E120@mac.com> <20101110170017.GF5094@hell> <97C75EA8-6CC7-444C-A19D-370148B81918@mac.com> <20101110174056.GH5094@hell> <AANLkTim7g=XqfSMHpHVbw1qqPOL-oNApt2i_2RCt0SCi@mail.gmail.com> <AD2BFE84-CA5B-4CDC-8822-1FC2713E3AE0@cisco.com> <alpine.DEB.2.00.1011161345170.11898@wel-95.cs.helsinki.fi> <E798B9A8-29BB-425B-B0C2-2B2735C49948@cisco.com> <5FDC413D5FA246468C200652D63E627A0B7BD0DF@LDCMVEXC1-PRD.hq.netapp.com> <686EBD23-7B65-455F-9348-196BBFD88ECD@comsys.rwth-aachen.de> <931FAE2C-F66E-43B2-8EE1-CFEB17DABD5E@windriver.com> <7309FCBCAE981B43ABBE69B31C8D213909B72A7B1F@EUSAACMS0701.eamcs.ericsson.se> <36F89B79-EABA-4C38-A59E-023D9A630832@windriver.com> <4CE585E9.6060203@isi.edu> <6B25AF56-AFED-4085-AF42-F8AD47CB9F41@windriver.com> <4CE58FED.608@isi.edu> <0C53DCFB700D144284A584F54711EC580B36940A@xmb-sjc-21c.amer.cisco.com> <4CE595E3.3010109@isi.edu> <AANLkTik3MpEyOZ+EWdtD8C+e2m3BrgKXK0KJrSoF=DMO@mail.gmail.com>
In-Reply-To: <AANLkTik3MpEyOZ+EWdtD8C+e2m3BrgKXK0KJrSoF=DMO@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: David Borman <david.borman@windriver.com>, tcpm <tcpm@ietf.org>, "Anantha Ramaiah (ananth)" <ananth@cisco.com>
Subject: Re: [tcpm] [Tmrg] Increasing the Initial Window - Notes
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Nov 2010 21:16:29 -0000

Maybe it should have been for IW=3 too, but it didn't occur to me at the 
time.

The benefit is that had we used this mechanism then, we wouldn't be 
asking for a new IW now, though.

Joe

On 11/18/2010 1:11 PM, John Heffner wrote:
> Why is this mechanism required for IW=10 but not for IW=3?
>
>    -John
>
>
> On Thu, Nov 18, 2010 at 4:08 PM, Joe Touch<touch@isi.edu>  wrote:
>> That's basically what I'm suggesting; it can easily be per subnet, per
>> interface, or per the entire machine as desired.
>>
>> The ultimate point is:
>>
>>         - put something in the end node that notices if/when
>>         it fails objectively, and fixes it
>>
>>         - that same thing can allow the IW to increase
>>         over time if there are no problems
>>
>> I'll be glad to write this up if people need a more concrete proposal.
>>
>> Joe
>>
>> On 11/18/2010 1:05 PM, Anantha Ramaiah (ananth) wrote:
>>>
>>> Why can't you do something like this :
>>>
>>> - If any one of the TCP connections egressing out of that interface
>>> (this can determined in TCP layer) is in the TCP retransmit state (or
>>> has experienced congestion in the past xxx secs/mins), then go back to a
>>> lower IW for new TCP connections which are using the same output
>>> interface..
>>>
>>> - When you want to start a connection, use the connection history (Joe's
>>> RFC)
>>>
>>> Well, there may be some gotchas of this scheme, but you can become
>>> conservative when there is some concrete information.
>>>
>>> Thanks,
>>> -Anantha
>>>>
>>>> To be more clear, here's the case:
>>>>
>>>>         start 1000 connections in a row.
>>>>
>>>>         during the first connection, lose some packets and do
>>>>         normal TCP backoff
>>>>
>>>>         so what do the other 999 connections start with?
>>>>         ans: 10 packets
>>>>
>>>> The point is that subsequent connections don't do anything different.
>>>> If
>>>> you have 1000 connections, you're sending a certain amount of data
>>>
>>> into
>>>>
>>>> the network without reacting. We're tripling that.
>>>>
>>>> That can easily cause congestion. At which point the *existing*
>>>> connections will backoff, but new connections keep making problems.
>>>>
>>>> Joe
>>>> _______________________________________________
>>>> tcpm mailing list
>>>> tcpm@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/tcpm
>>
>> _______________________________________________
>> tcpm mailing list
>> tcpm@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcpm
>>