[99068] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Congestion control train-wreck workshop at Stanford: Call for

daemon@ATHENA.MIT.EDU (Sean Donelan)
Mon Sep 3 23:29:17 2007

Date: Mon, 3 Sep 2007 23:23:46 -0400 (EDT)
From: Sean Donelan <sean@donelan.com>
To: "Steven M. Bellovin" <smb@cs.columbia.edu>
cc: nanog <nanog@merit.edu>
In-Reply-To: <20070904014439.D71B4766105@berkshire.machshav.com>
Errors-To: owner-nanog@merit.edu


On Mon, 3 Sep 2007, Steven M. Bellovin wrote:
>> Is there a groundswell of *operators* who think TCP should be
>> replaced, and believe it can be replaced?
>>
>> Or is the motivation for replacing TCP mainly felt by those who spend
>> a lot of time trying to get maximum performance out of single flows
>> over high bandwidth-delay product paths?
>
> Operators speak IP, not TCP -- not your problem...

Operators like inefficient protocols :-)

Operators are probably more interested in the "fairness" part of
"congestion" than the "efficiency" part of "congestion."  And of course
the dreaded congestive collapse.

> More seriously -- the question is whether new services will cause
> operator congestion problems that today's mechanisms don't handle.
> It's also possible, per the note that some solutions will have operator
> implications, such as new tuning knobs for routers and/or new funky new
> DNS records to make it clear which hosts support TCP++.  Beyond that,
> there are likely implications for things like firewalls, ACLs, and
> service measurements.

I think its interesting because its an attempt to define what the problem 
is, and demostrate that problem exists.  The next phase would be can those
conditions actually occur in the real world.



home help back first fref pref prev next nref lref last post