Re: HTTP/2 GREASE, Results, and Implications

Willy Tarreau <w@1wt.eu> Fri, 01 November 2019 13:22 UTC

Resent-Date: Fri, 01 Nov 2019 13:19:15 +0000
Resent-Message-Id: <E1iQWpf-0002Xb-Jg@frink.w3.org>
Date: Fri, 01 Nov 2019 14:19:03 +0100
From: Willy Tarreau <w@1wt.eu>
To: Bence Béky <bnc@chromium.org>
Cc: Mike Bishop <mbishop@evequefou.be>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20191101131903.GA1988@1wt.eu>
References: <BN6PR2201MB1700D10A34C72213C78E09A6DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <20191031155259.GC30674@1wt.eu> <CACMu3trL5UMukoPd8Nr4W-bMsyH+WKUnwg16yxu3tN5D=uZt8w@mail.gmail.com> <20191031203458.GA31017@1wt.eu> <CACMu3toue60Y_6Qxpzsqw-fOByc3Qjv=AG8Ed_DGvkR1EYn+4w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CACMu3toue60Y_6Qxpzsqw-fOByc3Qjv=AG8Ed_DGvkR1EYn+4w@mail.gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Received-SPF: pass client-ip=62.212.114.60; envelope-from=w@1wt.eu; helo=1wt.eu
Subject: Re: HTTP/2 GREASE, Results, and Implications
Archived-At: <https://www.w3.org/mid/20191101131903.GA1988@1wt.eu>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

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

HTTP/2 GREASE, Results, and Implications Mike Bishop
Re: HTTP/2 GREASE, Results, and Implications Lucas Pardue
Re: HTTP/2 GREASE, Results, and Implications Willy Tarreau
RE: HTTP/2 GREASE, Results, and Implications Mike Bishop
Re: HTTP/2 GREASE, Results, and Implications Ian Swett
Re: HTTP/2 GREASE, Results, and Implications Bence Béky
Re: HTTP/2 GREASE, Results, and Implications Willy Tarreau
RE: HTTP/2 GREASE, Results, and Implications Mike Bishop
Re: HTTP/2 GREASE, Results, and Implications Lucas Pardue
Re: HTTP/2 GREASE, Results, and Implications Willy Tarreau
Re: HTTP/2 GREASE, Results, and Implications David Benjamin
Re: HTTP/2 GREASE, Results, and Implications Willy Tarreau
Re: HTTP/2 GREASE, Results, and Implications David Benjamin
Re: HTTP/2 GREASE, Results, and Implications Willy Tarreau
Re: HTTP/2 GREASE, Results, and Implications Willy Tarreau
Re: HTTP/2 GREASE, Results, and Implications Bence Béky
Re: HTTP/2 GREASE, Results, and Implications Willy Tarreau
Re: HTTP/2 GREASE, Results, and Implications Stefan Eissing
Re: HTTP/2 GREASE, Results, and Implications Bence Béky
Re: HTTP/2 GREASE, Results, and Implications Willy Tarreau
Re: HTTP/2 GREASE, Results, and Implications Tom Bergan
Re: HTTP/2 GREASE, Results, and Implications Bence Béky
Re: HTTP/2 GREASE, Results, and Implications Willy Tarreau
Re: HTTP/2 GREASE, Results, and Implications Willy Tarreau
Re: HTTP/2 GREASE, Results, and Implications Tom Bergan
Re: HTTP/2 GREASE, Results, and Implications Willy Tarreau
Re: HTTP/2 GREASE, Results, and Implications Dmitri Tikhonov
Re: HTTP/2 GREASE, Results, and Implications Stefan Eissing