Re: [tcpm] informal poll about initial cwnd

Jerry Chu <hkchu@google.com> Thu, 06 January 2011 20:56 UTC

Return-Path: <hkchu@google.com>
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 3F2B93A6C9F for <tcpm@core3.amsl.com>; Thu, 6 Jan 2011 12:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.13
X-Spam-Level:
X-Spam-Status: No, score=-104.13 tagged_above=-999 required=5 tests=[AWL=-1.154, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 aGjtezPLY48c for <tcpm@core3.amsl.com>; Thu, 6 Jan 2011 12:56:28 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 62BE93A6A94 for <tcpm@ietf.org>; Thu, 6 Jan 2011 12:56:28 -0800 (PST)
Received: from hpaq12.eem.corp.google.com (hpaq12.eem.corp.google.com [172.25.149.12]) by smtp-out.google.com with ESMTP id p06KwY8t015038 for <tcpm@ietf.org>; Thu, 6 Jan 2011 12:58:34 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1294347515; bh=VnYp/SqeMdhA/3Xiy5pkTeikxTo=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=YPHaS1oIV1VmU7058Rem3eqDozey7Ulu6vJgsKp5GYpvFw7Tn0wMygBNkDiv/5H5g 7ZxKsGDK8q0maU8m2ifQg==
Received: from gyd12 (gyd12.prod.google.com [10.243.49.204]) by hpaq12.eem.corp.google.com with ESMTP id p06KwLGA004982 for <tcpm@ietf.org>; Thu, 6 Jan 2011 12:58:32 -0800
Received: by gyd12 with SMTP id 12so7079806gyd.17 for <tcpm@ietf.org>; Thu, 06 Jan 2011 12:58:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=LUuc/ruc5Qj/S0hB9EbHBFs14O57b8I3IGGDUH+GHF0=; b=jNF9zosM0nCw+33hi/dQtx5vSYwl5OWpuY5yvX2WhAfUynSl7gALHFRqhcBffdsLnR IB51FmLemrh2nuSa5XFA==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LFCE7dhsTZbt9TjuoL9U4eI5+0pBM0N81g4VPIkZ3rQzx5tORRYonWmu80QrXg5AN8 v8hPEcDiOdamL4B8T9Tw==
MIME-Version: 1.0
Received: by 10.151.158.7 with SMTP id k7mr23607736ybo.405.1294347512187; Thu, 06 Jan 2011 12:58:32 -0800 (PST)
Received: by 10.151.26.9 with HTTP; Thu, 6 Jan 2011 12:58:32 -0800 (PST)
In-Reply-To: <C304DB494AC0C04C87C6A6E2FF5603DB4826AE1579@NDJSSCC01.ndc.nasa.gov>
References: <20110106181946.F0ECD2A38D2A@lawyers.icir.org> <C304DB494AC0C04C87C6A6E2FF5603DB4826AE1579@NDJSSCC01.ndc.nasa.gov>
Date: Thu, 06 Jan 2011 12:58:32 -0800
Message-ID: <AANLkTikO5n0+9MtbKoQ_qvr84-8+CTeXQD-w=oX_cfOC@mail.gmail.com>
From: Jerry Chu <hkchu@google.com>
To: "Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]" <wesley.m.eddy@nasa.gov>
Content-Type: multipart/alternative; boundary="0015174ff4faae0d48049933c3ae"
X-System-Of-Record: true
Cc: "tcpm@ietf.org" <tcpm@ietf.org>, "mallman@icir.org" <mallman@icir.org>
Subject: Re: [tcpm] informal poll about initial cwnd
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, 06 Jan 2011 20:56:31 -0000

On Thu, Jan 6, 2011 at 10:34 AM, Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE
CORP] <wesley.m.eddy@nasa.gov> wrote:

> I've been thinking we might wind up with some set of A/B/C in conjunction.
>  It seems like they don't have to be mutually exclusive since different
> hosts could implement different Experimenal policies, as long as each is
> felt to be reasonable for Experimental.  Of course, it would probably be
> better to have one Proposed Standard.
>

Agreed 100%.

To me it's an obvious choice if C) proves to be feasible, i.e., translating
into say,
no more than 50 lines of simple code, not inflicting any noticeable
performance
penalty, without any external dependencies, and actually works as expected
(i.e., attaining its goals of allowing a timely growth path for IW without
causing
significant more global congestions) then who would say no to that magic?

But it is still a long IF IMO. (Note I'm not saying I don't believe C) will
work.
It's just I still have my doubt.)

Also it seems to me a combination of A) and B) may serve those hosts that
just
can't do C) (e.g., either w/o persistent storage or having one but not
usable
for C)'s purpose).

Jerry


> ________________________________________
> From: tcpm-bounces@ietf.org [tcpm-bounces@ietf.org] On Behalf Of Mark
> Allman [mallman@icir.org]
> Sent: Thursday, January 06, 2011 1:19 PM
> To: tcpm@ietf.org
> Subject: [tcpm] informal poll about initial cwnd
>
> Given that there are three proposals put down in I-D form in some matter
> of baked-ness I am wondering if there is any sort of clear WG preference
> on the *approach* to changing the initial window.  So, putting aside the
> particulars for a moment and just thinking about the approach I'd like
> to take a quick, informal, absolutely non-binding in any way (obviously)
> poll to take the WG's pulse.
>
> So, do you prefer ...
>
> (A) To increase the current static IW definition to a single updated
>    value.
>
>    (Current proposal: draft-ietf-tcpm-initcwnd-00.txt, but I am
>    explicitly not asking about IW=10, just IW=some_X.)
>
> (B) To increase the current static IW definition with a schedule of IW
>    updates to play out over some period of time.
>
>    (Current proposal: draft-allman-tcpm-bump-initcwnd-00.txt, but I am
>    explicitly not asking if you like the given schedule.)
>
> (C) To define a procedure for hosts to figure out how to adapt their IW
>    over time.
>
>    (Current proposal: draft-touch-tcpm-automatic-iw-00.txt, but I am
>    explicitly not asking if you buy the particulars of this, just the
>    overall approach.)
>
> (D) The current IW seems OK and I haven't seen a good reason to think it
>    needs changed.
>
> Thanks!
>
> allman
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
>