From owner-freebsd-net@FreeBSD.ORG Tue May 23 13:08:51 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 2C48916A424 for ; Tue, 23 May 2006 13:08:51 +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 D02AC43D45 for ; Tue, 23 May 2006 13:08:50 +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 k4ND8jQL034162; Tue, 23 May 2006 06:08:45 -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 1524F77AC21; Tue, 23 May 2006 09:08:44 -0400 (EDT) Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id 94E5D41696D; Tue, 23 May 2006 09:07:45 -0400 (EDT) To: mag@intron.ac From: Mark Allman In-Reply-To: Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Jungle Love MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_bOundary"; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Tue, 23 May 2006 09:07:45 -0400 Sender: mallman@icir.org Message-Id: <20060523130745.94E5D41696D@lawyers.icir.org> Cc: freebsd-net@freebsd.org, Marcin Jessa Subject: Re: How to Quicken TCP Re-transmission? 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, 23 May 2006 13:08:51 -0000 --=_bOundary Content-Type: text/plain Content-Disposition: inline > 1. Receiver should tell sender to re-send as soon as possible. > (But TCP makes receiver purely passive) This isn't really going to help you at all. With SACK (especially, but even without it) the receiver isn't really in a whole lot better position than the sender to judge when a packet is actually lost. Some people have worked on SNACKs (selective NEGATIVE acknowledgments), but my opinion is that the results (that I have seen) show them to be fairly equivalent to SACK in terms of performance. > 2. Receiver should tell sender what is really necessary to re-send. > (Sometimes only a single ACK number of TCP cannot include enough > information) RFC2018. (Which provides more than a single ACK number. But, this doesn't make the receiver tell the sender what to resend. The logic still resides at the sender.) allman --=_bOundary Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEcwkhWyrrWs4yIs4RArY+AJ9RBNZY2RfckhsKe6ta+wryZIN/4ACfVho7 6jTPBvZ2AFgnZc7KjWoHx1I= =yR/N -----END PGP SIGNATURE----- --=_bOundary--