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

Re: Moving 2817 to Historic

From: Michael Sweet <msweet@apple.com>
Date: Wed, 13 Feb 2019 12:59:06 -0500
Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-id: <3291DAB7-9BAD-4A9A-B1C9-8C0F112DF615@apple.com>
To: Willy Tarreau <w@1wt.eu>
Willy,

RFC 2616 also defined the Upgrade header and 101 status code, but it doesn't cover the specific TLS upgrade case (which is why RFC 2817 exists).


> On Feb 13, 2019, at 11:33 AM, Willy Tarreau <w@1wt.eu> wrote:
> 
> Hi Mike,
> 
> On Wed, Feb 13, 2019 at 10:05:03AM -0500, Michael Sweet wrote:
>> Mark,
>> 
>> HTTP Upgrade is used by IPP/1.1 [STD92] and IPP/2.0 [PWG Standard 5100.12]
>> for opportunistic TLS and has been supported and used by CUPS for about 20
>> years.  I would NOT be in favor of marking it historic.
> 
> It's also used by Websocket and even h1->h2 upgrade as well.
> However I think it is completely covered by RFC7230 #6.7 :
> 
>     https://tools.ietf.org/html/rfc7230#section-6.7
> 
> Regards,
> Willy
> 

_________________________________________________________
Michael Sweet, Senior Printing System Engineer
Received on Wednesday, 13 February 2019 18:00:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 13 February 2019 18:00:03 UTC