Re: [tcpm] TCP tuning

Jerry Chu <hkchu@google.com> Wed, 03 February 2010 23:48 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 C313D28C0CF for <tcpm@core3.amsl.com>; Wed, 3 Feb 2010 15:48:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.341
X-Spam-Level:
X-Spam-Status: No, score=-102.341 tagged_above=-999 required=5 tests=[AWL=-0.364, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 WJaoi1lT92X0 for <tcpm@core3.amsl.com>; Wed, 3 Feb 2010 15:48:08 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id BD60228B23E for <tcpm@ietf.org>; Wed, 3 Feb 2010 15:48:07 -0800 (PST)
Received: from wpaz17.hot.corp.google.com (wpaz17.hot.corp.google.com [172.24.198.81]) by smtp-out.google.com with ESMTP id o13Nmouj006139 for <tcpm@ietf.org>; Wed, 3 Feb 2010 15:48:50 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1265240931; bh=g7cADu/2kP9qyyYI5lcmxB1ySHY=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=ukgvydggCN7A9ET8azB+YtkER3LLclnjAXDz1ZqGpGxZgYk6+it4BKeTdQbfWBXt2 SwQgMVaVp45eG3aYPogDQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=WIbD5LcsQ2pWd+w9vslobsahN1u6OJV5EzqlqGFILwIioOztfX8Q9Ur5z/spCjRbO hR6dhaP/JwFz50l6psgfw==
Received: from pzk4 (pzk4.prod.google.com [10.243.19.132]) by wpaz17.hot.corp.google.com with ESMTP id o13NmnL3003796 for <tcpm@ietf.org>; Wed, 3 Feb 2010 15:48:50 -0800
Received: by pzk4 with SMTP id 4so2103724pzk.28 for <tcpm@ietf.org>; Wed, 03 Feb 2010 15:48:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.141.23.20 with SMTP id a20mr215673rvj.193.1265240929158; Wed, 03 Feb 2010 15:48:49 -0800 (PST)
In-Reply-To: <4B6A0264.1050700@isi.edu>
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> <4B6A0264.1050700@isi.edu>
Date: Wed, 03 Feb 2010 15:48:49 -0800
Message-ID: <d1c2719f1002031548n18a9fb6ancedf496c0952ad5e@mail.gmail.com>
From: Jerry Chu <hkchu@google.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
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:48:08 -0000

On Wed, Feb 3, 2010 at 3:10 PM, Joe Touch <touch@isi.edu> wrote:
>
>
> 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).

Yes that's our target date (3/1) for both the I-D and the paper detailing our
experimental results. We've been working hard on this for the past 6+
months, with a focus on studying the negative impact, which has been
a challenge both due to its small scale, and the limitation imposed by
passive measurements.

>
> 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...

Ok,

Jerry

>
> Joe
>
>