Re: HTTP/2 GREASE, Results, and Implications

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

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 202081200F1 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 1 Nov 2019 06:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WSrcpWi_xZ0w for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 1 Nov 2019 06:22:08 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16C461200B6 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 1 Nov 2019 06:22:07 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1iQWpf-0002Xb-Jg for ietf-http-wg-dist@listhub.w3.org; Fri, 01 Nov 2019 13:19:15 +0000
Resent-Date: Fri, 01 Nov 2019 13:19:15 +0000
Resent-Message-Id: <E1iQWpf-0002Xb-Jg@frink.w3.org>
Received: from mimas.w3.org ([2603:400a:ffff:804:801e:34:0:4f]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <w@1wt.eu>) id 1iQWpd-0002Wk-Gu for ietf-http-wg@listhub.w3.org; Fri, 01 Nov 2019 13:19:13 +0000
Received: from wtarreau.pck.nerim.net ([62.212.114.60] helo=1wt.eu) by mimas.w3.org with esmtp (Exim 4.92) (envelope-from <w@1wt.eu>) id 1iQWpb-0000Hu-Ca for ietf-http-wg@w3.org; Fri, 01 Nov 2019 13:19:13 +0000
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id xA1DJ33l001991; Fri, 1 Nov 2019 14:19:03 +0100
Date: Fri, 1 Nov 2019 14:19:03 +0100
From: Willy Tarreau <w@1wt.eu>
To: Bence =?iso-8859-1?Q?B=E9ky?= <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
X-W3C-Hub-Spam-Status: No, score=-7.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1iQWpb-0000Hu-Ca d62080845a72b3d1292b9b4aa6288ce1
X-Original-To: ietf-http-wg@w3.org
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
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37102
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

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