From owner-freebsd-current@FreeBSD.ORG Fri Jun 25 00:12:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C967516A4CE; Fri, 25 Jun 2004 00:12:20 +0000 (GMT) Received: from robbins.dropbear.id.au (045.a.005.mel.iprimus.net.au [210.50.40.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3BE243D1F; Fri, 25 Jun 2004 00:12:17 +0000 (GMT) (envelope-from tim@robbins.dropbear.id.au) Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 7BF2E41F6; Fri, 25 Jun 2004 10:14:18 +1000 (EST) Date: Fri, 25 Jun 2004 10:14:18 +1000 From: Tim Robbins To: "Wilkinson, Alex" Message-ID: <20040625001418.GA12712@cat.robbins.dropbear.id.au> References: <20040623210825.GA19715@elvis.mu.org> <20040624221612.A30E35D08@ptavv.es.net> <20040624234634.GA15795@squirm.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040624234634.GA15795@squirm.dsto.defence.gov.au> User-Agent: Mutt/1.4.1i cc: Paul Saab cc: current@freebsd.org Subject: Re: HEADS UP: SACK committed to HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 00:12:21 -0000 On Fri, Jun 25, 2004 at 09:16:38AM +0930, Wilkinson, Alex wrote: > erm .... what is SACK ? I'm assuming ACK is 'acknowledgment ? > Quick summary anyone ? >From RFC 2018: TCP may experience poor performance when multiple packets are lost from one window of data. With the limited information available from cumulative acknowledgments, a TCP sender can only learn about a single lost packet per round trip time. An aggressive sender could choose to retransmit packets early, but such retransmitted segments may have already been successfully received. A Selective Acknowledgment (SACK) mechanism, combined with a selective repeat retransmission policy, can help to overcome these limitations. The receiving TCP sends back SACK packets to the sender informing the sender of data that has been received. The sender can then retransmit only the missing data segments. Tim