From owner-freebsd-net@FreeBSD.ORG  Tue Mar  9 01:20:01 2004
Return-Path: <owner-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 C78BB16A4D0
	for <freebsd-net@freebsd.org>; Tue,  9 Mar 2004 01:20:01 -0800 (PST)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 3E3FB43D1F
	for <freebsd-net@freebsd.org>; Tue,  9 Mar 2004 01:20:01 -0800 (PST)
	(envelope-from silby@silby.com)
Received: (qmail 85349 invoked from network); 9 Mar 2004 09:19:59 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 9 Mar 2004 09:19:59 -0000
X-pair-Authenticated: 209.68.2.70
Date: Tue, 9 Mar 2004 03:19:58 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: Brooks Davis <brooks@one-eyed-alien.net>
In-Reply-To: <20040308202210.GB485@Odin.AC.HMC.Edu>
Message-ID: <20040309031549.L49735@odysseus.silby.com>
References: <404BA723.C8141806@freebsd.org>
	<20040308182431.4FA6D5D08@ptavv.es.net>
	<20040308202210.GB485@Odin.AC.HMC.Edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: David Malone <dwmalone@maths.tcd.ie>
cc: freebsd-net@freebsd.org
cc: freebsd-current@freebsd.org
cc: Andre Oppermann <andre@freebsd.org>
cc: Kevin Oberman <oberman@es.net>
Subject: Re: My planned work on networking stack
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2004 09:20:01 -0000


On Mon, 8 Mar 2004, Brooks Davis wrote:

> I've got a co-worker who is part of a research group at ISI that
> is doing research on long fat pipes with large streams.  They are
> intrested in doing a SACK implementation.  I hope to have some more
> information later this week.
>
> -- Brooks

In order to make SACK easier to digest, perhaps it should be suggested
that SACK be implemented in stages:

1.  Internal structures are updated to handle SACK, and the stack handles
the receive side of SACK properly.  (The stack advertises itself as SACK
capable, of course.)

2.  The transmit side of SACK is implemented.

>From what I recall about SACK, the implementation of part 1 would be
straightforward to verify and therefore easy to integrate.  The send side
would, of course, require more attention, and it would be more likely to
get it if it could be reviewed seperately.

Mike "Silby" Silbersack