W3C home > Mailing lists > Public > www-tag@w3.org > January 2012

Re: Mark Nottingham endorses IETF work on new versions of HTTP

From: Mark Nottingham <mnot@mnot.net>
Date: Thu, 26 Jan 2012 10:07:32 +1100
Cc: "www-tag@w3.org" <www-tag@w3.org>
Message-Id: <DC2D2014-1596-4100-BDAE-3D658D57063F@mnot.net>
To: Noah Mendelsohn <nrm@arcanedomain.com>
Thanks, Noah.

FWIW, I found this much more balanced:

> More far-reaching than these SSL tweaks is Google’s proposed alternative to the HTTP protocol that underpins the web: SPDY.
> 
> Initially, SPDY was a proprietary Google protocol implemented only in Google’s Chrome browser. That’s changing, however. Amazon’s Silk browser includes SPDY support, and Firefox 11 will include preliminary SPDY support. Partially motivated by SPDY’s uptake, the IETF’s HTTPbis Working Group — the team of industry experts tasked with maintaining and developing the HTTP specification — is considering the development of a new specification, HTTP/2.0, with the goal of improving the performance of HTTP connections. The working group will solicit suggestions from the industry, and with two, soon to be three implementations already, SPDY is likely to be well placed among those suggestions.


<http://www.webmonkey.com/2012/01/google-works-on-internet-standards-with-tcp-proposals-spdy-standardization/>



On 26/01/2012, at 9:22 AM, Noah Mendelsohn wrote:

> Of likely interest to the TAG: in a note [1] posted to the HTTP working group mailing list, Mark Nottingham discusses SPDY, points out that there are other attempts out there at optimizing HTTP, and suggests that:
> 
> "There seems to be broad agreement that the time is ripe to start work on a new version of HTTP in the IETF, and that it should happen in this Working Group."
> 
> He also mentions his discussions with the TAG.
> 
> Perhaps not surprisingly, the press today is full of reports with headlines like [2]:
> 
> "Google's SPDY Incorporated Into Next-Gen HTML, Offers TCP Enhancements"
> 
> I don't read Mark's note as specifically endorsing SPDY, except as a potential starting point, but [2] is linked from a Slashdot posting [3] that says:
> 
> "Mark Nottingham, called for it [SPDY]to be included in the HTTP 2.0 standard."
> 
> Anyway, the announcement by Mark at [1] seems to me very consistent with the direction he discussed with us at the TAG F2F earlier this month, and speaking for myself, it seems like very good news.
> 
> Noah
> 
> [1] http://lists.w3.org/Archives/Public/ietf-http-wg/2012JanMar/0098.html
> 
> [2] http://hothardware.com/News/Googles-SPDY-Incorporated-Into-NextGen-HTML-Company-Offers-TCP-Enhancements/
> 
> [3] http://tech.slashdot.org/story/12/01/25/027200/googles-spdy-could-be-incorporated-into-next-gen-http

--
Mark Nottingham   http://www.mnot.net/
Received on Wednesday, 25 January 2012 23:08:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:44 GMT