W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2015

Re: Last Call: <draft-ietf-httpbis-http2-16.txt> (Hypertext Transfer Protocol version 2) to Proposed Standard

From: Willy Tarreau <w@1wt.eu>
Date: Tue, 13 Jan 2015 01:30:55 +0100
To: "Constantine A. Murenin" <cnst@NetBSD.org>
Cc: ietf-http-wg@w3.org, ietf@ietf.org, iesg@ietf.org, iesg-secretary@ietf.org, mouse@NetBSD.org, djb@cr.yp.to
Message-ID: <20150113003055.GB30295@1wt.eu>
Hello,

On Sat, Jan 10, 2015 at 12:09:38AM -0800, Constantine A. Murenin wrote:
> I am sincerely asking for the IETF to not approve HTTP/2 as a standard 
> without the compatibility issues as above being addressed first.  The 
> policy to abandon the http:// address scheme and adopt https:// will 
> only promote a significant link rot for the future generations to 
> experience well into the future (didn't we think TLS 1.0 was good 
> enough?), and will curtail independent and hobbyist operators.

Please note that the protocol *does* support http:// address scheme, it's
only that two browsers decided that they will not implement it. Let's hope
that they'll change their mind when HTTP/2 starts reaching normal users and
is no more limited to huge sites with lots of people to manage certificates.

To their defense, the last reported connection upgrade success rates were
rather low (80-90% or something like this) and it can take a few years for
broken intercepting proxies to be upgraded/fixed at ISPs. I don't remember
when that measure was done, I guess it was 3 years ago for WebSocket. But
I do still hope we'll see support for http:// over HTTP/2 in all browsers
when HTTP/2 becomes the most commonly deployed version.

Best regards,
Willy
Received on Tuesday, 13 January 2015 00:31:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:42 UTC