[e2e] Google seeks to tweak TCP

[Arjuna Sathiaseelan]

Dear Deltef,
  Even Matt mathis who came up with the notion of TCP-friendliness has
had a change of mind on how TCP should be ;) - and he is in Google now
:)..

TCP is OK - but the way TCP works can be changed IMO...The ICCRG was
exactly looking at this...

I dont see any reason why TCP shouldnt be aggressive - being
aggressive for a few RTTs is ok IMHO - but it should respond well to
any congestion signal...with better network response (ECN, Re-ECN etc)
- TCP could well change its behaviour..

Regards
Arjuna

>   7. Re: Google seeks to tweak TCP (Detlef Bosau)
> Date: Thu, 02 Feb 2012 15:09:14 +0100
> From: Detlef Bosau <detlef.bosau at web.de>
> Subject: Re: [e2e] Google seeks to tweak TCP
> To: end2end-interest at postel.org
> Message-ID: <4F2A990A.8060201 at web.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 01/24/2012 12:01 PM, Jon Crowcroft wrote:
>> well, perhaps - sometimes, i just wish TCP would simply get out of the way...
>
>
> Jon,
>
> as science is usually thinking in alternatives: What is your alternative
> for TCP? Anybody is free to propose one.
>
> In addition, I wonder, why we need Science at all. We already have
> Google and Wikipedia and obviously, research is no longer being done by
> academics or by some huge companies but by Google.
>
> Brave new world.
>
> Lloyd pointed out some criticism, and we should well remember the
> Hippocratic oath: "First do no harm." And thoughtlessly increasing
> initial windows or other "parameter changes" _may_ do harm.
>
> On the quoted blog, we find comments like this one:
>
>> Rich Jones <http://www.blogger.com/profile/05420634711083784817>Jan
>> 23, 2012 12:14 PM
>> <http://googlecode.blogspot.com/2012/01/lets-make-tcp-faster.html?showComment=1327349640021#c7326672375960415062>
>>
>>     This is awesome work. I'm glad that Google is putting their vast
>>     engineering resources to such good use.
>>
>>     Rich, Gun.io
>>
>> Reply
>> Clemens Harten
>> <http://www.blogger.com/profile/06607566431465103036>Jan 23, 2012
>> 12:24 PM
>> <http://googlecode.blogspot.com/2012/01/lets-make-tcp-faster.html?showComment=1327350285920#c7113922870277087622>
>>
>>     It is impressive to see how simple changes (justified by extensive
>>     research) can lead to a great improvement of the protocol. Well done!
>>
>> Reply
>
> And whenever people are exited by simple recipes which save the world,
> we always should keep in mind RFC 1925.
>>     (6)  It is easier to move a problem around (for example, by moving
>>          the problem to a different part of the overall network
>>          architecture) than it is to solve it.
>>
>>
>
> and of course:
>
>>          (7a) (corollary). Good, Fast, Cheap: Pick any two (you can't
>>              have all three).
>
> Or, as H. L. Mencken said:
>
>> "For every complex problem there is a solution that is simple, neat
>> and wrong"
>
> --
> ------------------------------------------------------------------
> Detlef Bosau
> Galileistra?e 30
> 70565 Stuttgart                            Tel.:   +49 711 5208031
>                                            mobile: +49 172 6819937
>                                            skype:     detlef.bosau
>                                            ICQ:          566129673
> detlef.bosau at web.de                     http://www.detlef-bosau.de
> ------------------------------------------------------------------
>
>
>
>
> ------------------------------
>
> _______________________________________________
> end2end-interest mailing list
> end2end-interest at postel.org
> http://mailman.postel.org/mailman/listinfo/end2end-interest
>
>
> End of end2end-interest Digest, Vol 95, Issue 1
> ***********************************************



-- 
http://about.me/arjuna.sathiaseelan