From owner-freebsd-net@FreeBSD.ORG Tue Apr 11 20:19:20 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE0C516A402 for ; Tue, 11 Apr 2006 20:19:20 +0000 (UTC) (envelope-from mallman@icir.org) Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA91143D6B for ; Tue, 11 Apr 2006 20:19:18 +0000 (GMT) (envelope-from mallman@icir.org) Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by wyvern.icir.org (8.12.11/8.12.11) with ESMTP id k3BKJ7fj083835; Tue, 11 Apr 2006 13:19:07 -0700 (PDT) (envelope-from mallman@icir.org) Received: from lawyers.icir.org (guns.icir.org [69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id 7DEA377AB77; Tue, 11 Apr 2006 16:19:05 -0400 (EDT) Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id C000B3F3E41; Tue, 11 Apr 2006 16:18:14 -0400 (EDT) To: Andrea Campi From: Mark Allman In-Reply-To: <20060409223246.GA1747@webcom.it> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Mrs. Robinson MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_bOundary"; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Tue, 11 Apr 2006 16:18:14 -0400 Sender: mallman@icir.org Message-Id: <20060411201814.C000B3F3E41@lawyers.icir.org> Cc: freebsd-net@freebsd.org Subject: Re: TCP Daytona in userland X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mallman@icir.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2006 20:19:20 -0000 --=_bOundary Content-Type: text/plain Content-Disposition: inline > Lastly, if anybody already worked on this: do you have any additional > suggestion? In particular regarding the testing methodology: since a > few years have passed, I'm not quite sure whether different OSs have > implemented any countermeasure. I'm mainly testing against a FreeBSD > box I control, and I don't think we have any defence against this yet. It would seem that some hosts are using byte counting to increase cwnd these days (that is, increasing cwnd based on the number of bytes ACKed and not the number of ACK packets that arrive). There are some measurements given in: Alberto Medina, Mark Allman, Sally Floyd. Measuring the Evolution of Transport Protocols in the Internet. ACM Computer Communication Review, 35(2), April 2005. http://www.icir.org/mallman/papers/tcp-evo-ccr2005.ps Also, I think there is wide community consensus that cwnd should be increased by min (number_of_bytes_acked, MSS) on each incoming ACK. RFC2581 is currently being revised and this will be the recommended way path in the revision (in 2581 it notes that an implementation may count bytes instead of packets). allman --=_bOundary Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEPA8GWyrrWs4yIs4RAimkAKCHcZdpJH/LnEDX3Sj7QHr5dWNRawCfbKeE LGIFbMnNGuv9DZT1h7OZV0M= =AqT6 -----END PGP SIGNATURE----- --=_bOundary--