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

RE: Please don't block HTTP/2 on the "http:// schemed URIs over TLS" issue

From: Appanasamy, Palanivelan <palanivelan.appanasamy@in.verizon.com>
Date: Mon, 10 Mar 2014 09:17:25 +0530
To: James Cloos <cloos@jhcloos.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
CC: Julian Reschke <julian.reschke@gmx.de>, Brian Smith <brian@briansmith.org>
Message-ID: <70AEAEC90FCAE0408586E94F491A07EC5962BC19@MS-BAN-E7MB01.intl1.one.verizon.com>
This is little more complicated than what it looks to be :)
Let us get 2.0 rolled out  and Focus on all "MUST" adds for the immediate future.

Regards,
Palanivelan
-----Original Message-----
From: James Cloos [mailto:cloos@jhcloos.com] 
Sent: Saturday, March 08, 2014 5:09 AM
To: ietf-http-wg@w3.org
Cc: Julian Reschke; Brian Smith
Subject: Re: Please don't block HTTP/2 on the "http:// schemed URIs over TLS" issue

>>>>> "JR" == Julian Reschke <julian.reschke@gmx.de> writes:

JR> If it can't do HTTP URIs, it's not a replacement. What we need to 
JR> argue about is not *whether* to support HTTP URIs, but *how*.

The draft specifies http upgrade to support http/2 for http:// URIs.

TLS has nothing to do with that issue.  (Nor should it.)

-JimC
--
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6
Received on Monday, 10 March 2014 03:48:07 UTC

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