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

Re: HTTP/2 GREASE, Results, and Implications

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Mon, 4 Nov 2019 09:56:13 +0100
Cc: Bence Béky <bnc@chromium.org>, Mike Bishop <mbishop@evequefou.be>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <6F4160E3-D460-4DD9-9931-348479F6437F@greenbytes.de>
To: Willy Tarreau <w@1wt.eu>
Thanks for mitigating this. 

> Am 01.11.2019 um 14:19 schrieb Willy Tarreau <w@1wt.eu>:
> 
> On Fri, Nov 01, 2019 at 07:43:51AM -0400, Bence Béky wrote:
>> Hi Willy,
>> 
>> Yes, I agree with you.  My current plan is to make Chrome send a frame of
>> reserved type
>> * on stream 0, after the SETTINGS frame;
>> * on non-zero streams, after each HEADERS and DATA frame that does not have
>> the END_STREAM flag set;
>> * or alternatively, after each HEADERS and DATA frame, and if the stream
>> should be closed, then send an empty DATA frame with END_STREAM after the
>> reserved frame.
>> 
>> I think this conforms to the state transition requirements you summarized.
> 
> Yes that sounds good.
> 
>> Thank you for the guidance.  I'll keep the list posted.
> 
> Thanks!
> Willy
> 
Received on Monday, 4 November 2019 08:56:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:43 UTC