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

Sally Floyd <floyd@icir.org> Sun, 11 August 2002 15:37 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15987 for <tsvwg-archive@odin.ietf.org>; Sun, 11 Aug 2002 11:37:41 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA04892 for tsvwg-archive@odin.ietf.org; Sun, 11 Aug 2002 11:38:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA03993; Sun, 11 Aug 2002 11:18:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA07840 for <tsvwg@optimus.ietf.org>; Fri, 9 Aug 2002 12:52:12 -0400 (EDT)
Received: from cougar.icir.org (cougar.icir.org [192.150.187.76]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03016 for <tsvwg@ietf.org>; Fri, 9 Aug 2002 12:50:55 -0400 (EDT)
Received: from cougar.icir.org (localhost [127.0.0.1]) by cougar.icir.org (8.11.6/8.11.3) with ESMTP id g79Gq8X01723; Fri, 9 Aug 2002 09:52:08 -0700 (PDT) (envelope-from floyd@cougar.icir.org)
Message-Id: <200208091652.g79Gq8X01723@cougar.icir.org>
To: Reiner Ludwig <Reiner.Ludwig@ericsson.com>
cc: tsvwg@ietf.org
From: Sally Floyd <floyd@icir.org>
Subject: Re: [Tsvwg] Re: HighSpeed TCP for Large Congestion Windows
Date: Fri, 09 Aug 2002 09:52:08 -0700
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
X-BeenThere: tsvwg@ietf.org

Reiner -

>Such applications would have to move *terra* bytes *back-to-back* to start 
>having that problem. I'm not convinced that such applications are running 
>on the *public* Internet today or in the foreseeable future. Please, 
>convince me if you think otherwise.
...
>As it stands, it seems that the ID describes a solution for a problem that 
>nobody has today or will could have tomorrow. Also, my understanding is 
>that IETF WGs only deal with *real world* problems, and that the more 
>academic problems are dealt with in the research community.

My understanding had been that the IETF was the right place to
bring proposed changes to TCP congestion control, whether the
changes were motivated by the needs of what is currently a small
subset of the community with underutilyzed high-bandwidth pipes at
their disposal, or whether the changes were motivated by pressing
concerns that affect the vast majority of users.  But I assume 
that the tsvwg co-chairs can clarify this for us.

My own understanding is that the HighSpeed draft describes a solution
for a problem that a small subset of people have today, and that
is not a very pressing problem at any rate (given the alternate
solution of opening N parallel TCP connections).  However, my own
view would be that this issue is clearly approriate to bring to the
IETF.  If people judge otherwise, that is fine by me.

My own *personal* view is that HighSpeed TCP would be an appropriate
work item for tsvwg, and further, that it would make perfect sense
for the HighSpeed TCP draft, and the related Limited Slow-Start
draft, to become Experimental RFCs, in the fullness of time, and
then to sink or swim on the basis of further experimental evaluation.
But if the IESG, the ADs, or the rough consensus of the working
group judge otherwise, again, that is certainly fine by me.
I am certainly not trying to argue that this is one of the more
pressing or earth-shattering issues on the table, just that it
strikes me as a appropriate issue to bring to the IETF, as the
standards body responsible for the standardization of TCP.

- Sally
http://www.icir.org/floyd/


_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg