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

Joe Touch <touch@isi.edu> Fri, 19 November 2010 01:29 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 064933A68AC for <tcpm@core3.amsl.com>; Thu, 18 Nov 2010 17:29:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level:
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, 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 Pu963y1jwgG3 for <tcpm@core3.amsl.com>; Thu, 18 Nov 2010 17:29:46 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id 27B753A63CB for <tcpm@ietf.org>; Thu, 18 Nov 2010 17:29:46 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id oAJ1UChY025220 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 18 Nov 2010 17:30:12 -0800 (PST)
Message-ID: <4CE5D324.1050609@isi.edu>
Date: Thu, 18 Nov 2010 17:30:12 -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: Andrew Yourtchenko <ayourtch@cisco.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> <Pine.GSO.4.64.1011190001550.27897@sweet-brew-4.cisco.com>
In-Reply-To: <Pine.GSO.4.64.1011190001550.27897@sweet-brew-4.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: oAJ1UChY025220
X-ISI-4-69-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: Fri, 19 Nov 2010 01:29:47 -0000

Hi, Andrew,

On 11/18/2010 4:47 PM, Andrew Yourtchenko wrote:
>
>
> On Thu, 18 Nov 2010, Joe Touch 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 think this is a very viable idea.
>
> However, I think there is a catch due to which it would need tweaking -
> there should be a signaling mechanism whereby a node on the
> "conservative" side of the connection would be able to signal the node
> on the "eager" side of the connection not to be too aggressive, in case
> the data flow is mostly from from "eager" to "conservative" side.

I think the rest of your argument boils down to how the client decides 
to aggregate it's idea of the best IW. That's up to the client to decide 
what it is willing to support - coarse or fine-grained.

An IW=10 as a static proposal is the coarsest possible; anything else we 
could do can't be any worse.

...
> If the above logic is right, then the peers during the 3whs should
> communicate their memorized values and pick up the minimum of theirs and
> the communicated by the peer.

Congestion isn't often bidirectional, so it's unlikely IMO that a peer 
would know what to suggest to its counterpart (if I understand your 
proposal). However, your suggestion is that there could be additional 
input if someone - anyone - knew 'better' what to do. That's fine - 
that's just an out-of-band hint to the algorithm.

Joe