Re: [tcpm] TCP tuning

Joe Touch <touch@ISI.EDU> Wed, 03 February 2010 23:11 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 3C40A3A6996 for <tcpm@core3.amsl.com>; Wed, 3 Feb 2010 15:11:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 MHXIzcHLtQHn for <tcpm@core3.amsl.com>; Wed, 3 Feb 2010 15:11:19 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id 5720B3A6916 for <tcpm@ietf.org>; Wed, 3 Feb 2010 15:11:19 -0800 (PST)
Received: from [70.213.251.114] (114.sub-70-213-251.myvzw.com [70.213.251.114]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id o13NASvQ023746 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 3 Feb 2010 15:10:30 -0800 (PST)
Message-ID: <4B6A0264.1050700@isi.edu>
Date: Wed, 03 Feb 2010 15:10:28 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Jerry Chu <hkchu@google.com>
References: <7BE9742D-6EDC-43FE-84FC-D22C52D23152@nokia.com> <133D9897FB9C5E4E9DF2779DC91E947C025F1861@SLFSNX.rcs.alcatel-research.de> <d1c2719f1002031110v3b76ca9eu14c9a110847548e7@mail.gmail.com> <4B69CDD7.6060802@isi.edu> <d1c2719f1002031339u14709270k6452c05f0dd3c39e@mail.gmail.com> <4B69F7BC.3000204@isi.edu> <d1c2719f1002031505t734fcea7va9b13022985145dd@mail.gmail.com>
In-Reply-To: <d1c2719f1002031505t734fcea7va9b13022985145dd@mail.gmail.com>
X-Enigmail-Version: 0.96.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="------------enig2B3A7D532326776EF9745D86"
X-MailScanner-ID: o13NASvQ023746
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: nanditad@google.com, tcpm@ietf.org, "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>
Subject: Re: [tcpm] TCP tuning
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: Wed, 03 Feb 2010 23:11:21 -0000


Jerry Chu wrote:
...
>> We've seen initial work on this before, and had a number of questions
>> that remain unanswered. A good start would be to put this all in a tech
>> report. Presentations at the IETF should not get into deep technical
>> detail; they ought to summarize work available before the meeting and
>> provided on the list IMO.
> 
> I'm 100% with you on this, and have been working hard on a detailed report
> on our experiments done so far to be published in the next few weeks.

It would be very useful if that work could be available in advance of
the IETF, e.g., by the 00 cutoff date (to give us time to take a look at
it).

It would also be useful, IMO, if the presentation summarized that work,
and expected those present to be familiar with it, rather than going
through it in detail, FWIW...

Joe