Re: [tcpm] Tuning TCP parameters for the 21st century

Joe Touch <touch@ISI.EDU> Wed, 15 July 2009 14:34 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 396A73A6B43 for <tcpm@core3.amsl.com>; Wed, 15 Jul 2009 07:34:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level:
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096, 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 iP-43NWSsj7q for <tcpm@core3.amsl.com>; Wed, 15 Jul 2009 07:34:42 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 751DE3A6947 for <tcpm@ietf.org>; Wed, 15 Jul 2009 07:34:42 -0700 (PDT)
Received: from [192.168.1.45] (pool-71-105-84-152.lsanca.dsl-w.verizon.net [71.105.84.152]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n6FEP32T002143; Wed, 15 Jul 2009 07:25:05 -0700 (PDT)
Message-ID: <4A5DE6BC.3090904@isi.edu>
Date: Wed, 15 Jul 2009 07:25:00 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Jerry Chu <hkchu@google.com>
References: <d1c2719f0907131619t1a80997ep4080a3a721ef3627@mail.gmail.com> <4A5C540E.9070104@sun.com> <4A5C9309.8030704@isi.edu> <d1c2719f0907141241p73e605adqc1d2e6f0db4eb3aa@mail.gmail.com> <4A5CE3D0.5000904@isi.edu> <d1c2719f0907141532i31d2b740hfa32209a8ccb156@mail.gmail.com> <4A5D0E8F.1040402@isi.edu> <d1c2719f0907141743n4952c9far54e3be36668577ed@mail.gmail.com>
In-Reply-To: <d1c2719f0907141743n4952c9far54e3be36668577ed@mail.gmail.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tcpm@ietf.org" <tcpm@ietf.org>
Subject: Re: [tcpm] Tuning TCP parameters for the 21st century
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, 15 Jul 2009 14:34:43 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Jerry Chu wrote:
...
>> We're taking one more look at T/TCP as well (probably need to start a different
>> mail thread on T/TCP too).

T/TCP is deprecated due to a fairly large security issue that has not
been solved, AFAIK. It'd be useful to have a solution to that issue
before proceeding with it as an approach.

...
>> The SYN/SYN-ACK retransmission rate we measured turned out to be >> 1%
>> in many cases (a bit surprising to us) hence the benefit.

That points to some other problem going on. As a packet loss rate,
that's quite high and causes problems elsewhere in TCP. It would be
useful to understand where the drops are and why. Retransmitting SYNs to
a busy endpoint whose queue is overflowing doesn't help things, e.g.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpd5rwACgkQE5f5cImnZrslfgCfVmHxe6fxfD7nCq/S5mn8S0Bt
mwMAnRZPyVGbsvU9x6G1M+hbbR0AnCGn
=Kghy
-----END PGP SIGNATURE-----