[e2e] Google seeks to tweak TCP
Daniel Havey
dhavey at yahoo.com
Tue Jan 24 04:58:03 PST 2012
I have to agree with this. TCP is ugly for Application Layer FEC.
...Daniel
--- On Tue, 1/24/12, Jon Crowcroft <Jon.Crowcroft at cl.cam.ac.uk> wrote:
> From: Jon Crowcroft <Jon.Crowcroft at cl.cam.ac.uk>
> Subject: Re: [e2e] Google seeks to tweak TCP
> To: L.Wood at surrey.ac.uk
> Cc: craig at aland.bbn.com, Jon.Crowcroft at cl.cam.ac.uk, end2end-interest at postel.org
> Date: Tuesday, January 24, 2012, 3:01 AM
> well, perhaps - sometimes, i just
> wish TCP would simply get out of the way...
>
> In missive <FD7B10366AE3794AB1EC5DE97A93A3733E2E70D2E4 at EXMB01CMS.surrey.ac.uk>,
> L.Wood at surrey.ac.uk
> typed:
>
> >>Can it be argued that google is attacking the wrong
> layer?
> >>
> >>TCP was not 'designed to deliver the Web's
> content.' TCP predates the web and http by decades. The
> internet and TCP user base is rather larger than google's
> user base of web customers.
> >>
> >>TCP was indeed designed to operate over 'a huge
> range of network types', and decreasing TCP RTO while
> increasing initial windows decreases TCP's tolerance of the
> range of networks it can support.
> >> I look forward to seeing the knock-on effects of
> decreasing the initial TCP RTO to one second (e.g.
> interactions with Mobile IP).
> >>
> >>Improved and more widely deployed HTTP persistence
> and pipelining would help; Google's SPDY at least nods to
> that. Those are germane to web use, and thus to Google's
> customers. Tweaking (improving?) TCP, not so much.
> >>
> >>
> >>Lloyd Wood
> >>http://sat-net.com/L.Wood/
> >>
> >>
> >>________________________________________
> >>From: end2end-interest-bounces at postel.org
> [end2end-interest-bounces at postel.org]
> On Behalf Of Craig Partridge [craig at aland.bbn.com]
> >>Sent: 23 January 2012 21:18
> >>To: end2end-interest at postel.org
> >>Subject: [e2e] Google seeks to tweak TCP
> >>
> >>Craig
> >>
> >>E-mail: craig at aland.bbn.com
> or craig at bbn.com
> >>
> >>------- Forwarded Message
> >>
> >>Return-Path: privacy-bounces+craig=aland.bbn.com at vortex.com
> >>Delivery-Date: Mon Jan 23 13:58:48 2012
> >>Return-Path: <privacy-bounces+craig=aland.bbn.com at vortex.com>
> >>X-Spam-Checker-Version: SpamAssassin 3.3.2
> (2011-06-06) on aland.bbn.com
> >>X-Spam-Level:
> >>X-Spam-Status: No, score=-1.9 required=4.0
> tests=BAYES_00,T_RP_MATCHES_RCVD
> >> autolearn=ham
> version=3.3.2
> >>X-Original-To: craig at aland.bbn.com
> >>Delivered-To: craig at aland.bbn.com
> >>Received: from moe.vortex.com (moe.vortex.com
> [192.160.193.155])
> >> by aland.bbn.com
> (Postfix) with ESMTP id 25B2D28E135
> >> for <craig at aland.bbn.com>;
> Mon, 23 Jan 2012 13:58:48 -0500 (EST)
> >>Received: from chrome.vortex.com (chrome.vortex.com
> [67.119.61.37])
> >> by neon.vortex.com
> (8.12.6/8.12.6) with ESMTP id q0NIi6P8030599
> >> for
> <privacy-list@[67.119.61.35]>; Mon, 23 Jan 2012
> 10:44:06 -0800 (PST)
> >>Date: Mon, 23 Jan 2012 10:44:06 -0800
> >>To: privacy-list at vortex.com
> >>Message-ID: <20120123184406.GG14662 at vortex.com>
> >>MIME-Version: 1.0
> >>Content-Disposition: inline
> >>X-Loop-Check:
> >>From: PRIVACY Forum mailing list <privacy at vortex.com>
> >>Subject: [ PRIVACY Forum ] Google: Let's Make
> TCP Faster
> >>X-BeenThere: privacy at vortex.com
> >>X-Mailman-Version: 2.1.6b2
> >>Precedence: list
> >>Reply-To: PRIVACY Forum mailing list <privacy at vortex.com>
> >>List-Id: PRIVACY Forum mailing list
> <privacy.vortex.com>
> >>List-Unsubscribe: <http://lists.vortex.com/mailman/listinfo/privacy>,
> >> <mailto:privacy-request at vortex.com?subject=unsubscribe>
> >>List-Post: <mailto:privacy at vortex.com>
> >>List-Help: <mailto:privacy-request at vortex.com?subject=help>
> >>List-Subscribe: <http://lists.vortex.com/mailman/listinfo/privacy>,
> >> <mailto:privacy-request at vortex.com?subject=subscribe>
> >>Content-Type: text/plain; charset="iso-8859-1"
> >>Content-Transfer-Encoding: quoted-printable
> >>Sender: privacy-bounces+craig=aland.bbn.com at vortex.com
> >>Errors-To: privacy-bounces+craig=aland.bbn.com at vortex.com
> >>
> >>
> >>
> >>Google: Let's Make TCP Faster
> >>
> >>http://j.mp/Af4pgb (Google Code Blog)
> >>
> >> "Transmission Control Protocol
> (TCP), the workhorse of the Internet, is
> >> designed to deliver all the Web's
> content and operate over a huge
> >> range of network types. To deliver
> content effectively, Web browsers
> >> typically open several dozen parallel
> TCP connections ahead of making
> >> actual requests. This strategy
> overcomes inherent TCP limitations but
> >> results in high latency in many
> situations and is not scalable. Our
> >> research shows that the key to
> reducing latency is saving round trips.
> >> We're experimenting with several
> improvements to TCP. Here's a summary
> >> of some of our recommendations to
> make TCP faster ..."
> >>
> >> - - -
> >>
> >>- --Lauren--
> >>Lauren Weinstein (lauren at vortex.com):
> http://www.vortex.com/lauren =
> >>
> >>Co-Founder: People For Internet Responsibility: http://www.pfir.org =
> >>
> >>Founder:
> >> - Network Neutrality Squad: http://www.nnsquad.org =
> >>
> >> - Global Coalition for Transparent Internet
> Performance: http://www.gctip.=
> >>org
> >> - PRIVACY Forum: http://www.vortex.com =
> >>
> >>Member: ACM Committee on Computers and Public
> Policy
> >>Blog: http://lauren.vortex.com =
> >>
> >>Google+: http://vortex.com/g+lauren =
> >>
> >>Twitter: https://twitter.com/laurenweinstein =
> >>
> >>Tel: +1 (818) 225-2800 / Skype: vortex.com
> >>
> >>
> >>
> >>_______________________________________________
> >>privacy mailing list
> >>http://lists.vortex.com/mailman/listinfo/privacy
> >>
> >>------- End of Forwarded Message
> >>
> >>
>
> cheers
>
> jon
>
>
More information about the end2end-interest
mailing list