Re: [Tsvwg] Re: HighSpeed TCP for Large Congestion Windows

Mark Allman <mallman@grc.nasa.gov> Wed, 18 September 2002 03:15 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 XAA07573 for <tsvwg-archive@odin.ietf.org>; Tue, 17 Sep 2002 23:15:18 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8I3Ghd27424 for tsvwg-archive@odin.ietf.org; Tue, 17 Sep 2002 23:16:43 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8I3Fwv27403; Tue, 17 Sep 2002 23:15:58 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8I3Dxv27360 for <tsvwg@optimus.ietf.org>; Tue, 17 Sep 2002 23:13:59 -0400
Received: from mx7.mx.voyager.net (mx7.mx.voyager.net [216.93.66.86]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07538 for <tsvwg@ietf.org>; Tue, 17 Sep 2002 23:12:03 -0400 (EDT)
Received: from lawyers.ir.bbn.com (d251.as1.clev.oh.voyager.net [209.81.166.252]) by mx7.mx.voyager.net (8.11.6/8.10.2) with ESMTP id g8I3Dlu85351; Tue, 17 Sep 2002 23:13:47 -0400 (EDT)
Received: from lawyers (mallman@localhost) by lawyers.ir.bbn.com (8.9.3/8.9.3) with ESMTP id XAA14169; Tue, 17 Sep 2002 23:13:36 -0400
Message-Id: <200209180313.XAA14169@lawyers.ir.bbn.com>
To: Marco Mellia <mellia@prezzemolo.polito.it>
From: Mark Allman <mallman@grc.nasa.gov>
Reply-To: mallman@grc.nasa.gov
cc: Sally Floyd <floyd@icir.org>, Reiner Ludwig <Reiner.Ludwig@ericsson.com>, tsvwg@ietf.org
Subject: Re: [Tsvwg] Re: HighSpeed TCP for Large Congestion Windows
In-Reply-To: <200208201426.53467.mellia@mail.tlc.polito.it>
Organization: BBN Technologies/NASA GRC
Song-of-the-Day: Stairway to Heavan
Date: Tue, 17 Sep 2002 23:13:36 -0400
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>

[Clearly I can't keep up very well.  So, sorry for the delayed
 response.] 

> Do you think it could be problematic to recover from a cwnd of
> thousand of packets?  What happen in a scenario (unrealistic?)
> where 1 HighSpeed TCP if filling a pipe of 10Gb/s, 100ms RTT, and
> then a second HS-TCP starts? How many packets are going to be
> lost?  Even if only 1/10 of cwnd packets are going to be lost,
> about 800 packets will be dropped.  Will sack be able to handle
> that? Probably not... and how many RTT will be necessary to
> successfully terminate a Fast (?) Recovery?  

I'm interested in knowing why you think SACK-based recovery will not
work effectively in this case?  I think it should work just fine in
the case when 10% of the packets are lost (regardless of how many
losses that happens to be).

(FYI: My mental model of SACK is draft-allman-tcp-sack-12.txt)

> And what will happen if a RTO expires? How many duplicated
> segments will be carried by the network?  Do you believe that this
> can be an issue?

Hopefully with SACK we will not send needless retransmits into the
network.  Or, at least not that many.

On the other hand, if you end up using Reno we have some recent
measurements that suggest about 1 out of every 3 retransmits is
needless.  So, given Reno's grossness this *might* be an issue with
huge windows.  

allman


--
Mark Allman -- NASA GRC/BBN -- http://roland.grc.nasa.gov/~mallman/
_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg