Re: [Tsvwg] TCP SACK/FACK implementations on BSD
Ethan Blanton <eblanton@cs.ohiou.edu> Fri, 24 January 2003 17:11 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25124 for <tsvwg-archive@odin.ietf.org>; Fri, 24 Jan 2003 12:11:30 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0OHUa314454 for tsvwg-archive@odin.ietf.org; Fri, 24 Jan 2003 12:30:36 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OHU5J14424; Fri, 24 Jan 2003 12:30:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0OHT9J14378 for <tsvwg@optimus.ietf.org>; Fri, 24 Jan 2003 12:29:09 -0500
Received: from localhost.localdomain (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25103 for <tsvwg@ietf.org>; Fri, 24 Jan 2003 12:09:32 -0500 (EST)
Received: (from elb@localhost) by localhost.localdomain (8.11.6/8.11.6) id h0OHCnd21789; Fri, 24 Jan 2003 12:12:49 -0500
Date: Fri, 24 Jan 2003 12:12:49 -0500
From: Ethan Blanton <eblanton@cs.ohiou.edu>
To: Janardhan Iyengar <iyengar@mail.eecis.udel.edu>
Cc: tsvwg@ietf.org, "Armando L. Caro Jr." <acaro@mail.eecis.udel.edu>, Sourabh Ladha <ladha@mail.eecis.udel.edu>, keyur shah <shah@mail.eecis.udel.edu>, "Paul D. Amer" <amer@mail.eecis.udel.edu>
Subject: Re: [Tsvwg] TCP SACK/FACK implementations on BSD
Message-ID: <20030124171249.GA4853@paco.resnet.purdue.edu>
Mail-Followup-To: Janardhan Iyengar <iyengar@mail.eecis.udel.edu>, tsvwg@ietf.org, "Armando L. Caro Jr." <acaro@mail.eecis.udel.edu>, Sourabh Ladha <ladha@mail.eecis.udel.edu>, keyur shah <shah@mail.eecis.udel.edu>, "Paul D. Amer" <amer@mail.eecis.udel.edu>
References: <Pine.GSO.4.33.0301241143550.3879-100000@ren.eecis.udel.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS"
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.33.0301241143550.3879-100000@ren.eecis.udel.edu>
User-Agent: Mutt/1.4i
X-GnuPG-Fingerprint: A290 14A8 C682 5C88 AE51 4787 AFD9 00F4 883C 1C14
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Janardhan Iyengar spake unto us the following wisdom:
> We are doing some experiments using the OpenBSD implementation of TCP SACK
> and FACK. Could anyone validate for us whether these are the docs that
> these implementations conform to (or are closest to)?
>
> OpenBSD TCP-SACK: A Conservative SACK-based Loss Recovery Algorithm for
> TCP (draft-allman-tcp-sack-13.txt)
We have not heard anything about the OpenBSD people trying to
implement our algorithm. That doesn't preclude that they might have
done so, but I suspect that their SACK support predates
draft-allman-tcp-sack-13.
> Further, do the ns-2 implementations of TCP-SACK/FACK conform to the docs
> above?
The ns-2 SACK algorithm is similar to draft-allman-tcp-sack-13 (and is
in fact the basis we worked from), but it is not the same.
Ethan
--
And if I claim to be a wise man / it surely means that I don't know.
-- Kansas, "Carry on Wayward Son"
- [Tsvwg] TCP SACK/FACK implementations on BSD Janardhan Iyengar
- Re: [Tsvwg] TCP SACK/FACK implementations on BSD Ethan Blanton