Re: HTTP/2 GREASE, Results, and Implications

Willy Tarreau <w@1wt.eu> Thu, 31 October 2019 18:58 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 B832C120947 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 31 Oct 2019 11:58:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=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 0djnsjqk4ktU for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 31 Oct 2019 11:58:11 -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 9D21E120865 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 31 Oct 2019 11:58:11 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1iQFbv-0001vj-IA for ietf-http-wg-dist@listhub.w3.org; Thu, 31 Oct 2019 18:55:55 +0000
Resent-Date: Thu, 31 Oct 2019 18:55:55 +0000
Resent-Message-Id: <E1iQFbv-0001vj-IA@frink.w3.org>
Received: from titan.w3.org ([2603:400a:ffff:804:801e:34:0:4c]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <w@1wt.eu>) id 1iQFbt-0001uh-Um for ietf-http-wg@listhub.w3.org; Thu, 31 Oct 2019 18:55:53 +0000
Received: from wtarreau.pck.nerim.net ([62.212.114.60] helo=1wt.eu) by titan.w3.org with esmtp (Exim 4.92) (envelope-from <w@1wt.eu>) id 1iQFbr-00069J-Lj for ietf-http-wg@w3.org; Thu, 31 Oct 2019 18:55:53 +0000
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id x9VIthoD030948; Thu, 31 Oct 2019 19:55:43 +0100
Date: Thu, 31 Oct 2019 19:55:43 +0100
From: Willy Tarreau <w@1wt.eu>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Mike Bishop <mbishop@evequefou.be>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20191031185543.GB30937@1wt.eu>
References: <BN6PR2201MB1700D10A34C72213C78E09A6DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <CALGR9oZUHDbsvWUJ=r0TBDaKOwchWux5gEF+EH0cpb6hqcs-xA@mail.gmail.com> <BN6PR2201MB1700996BA38EC2FED189E876DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <BN6PR2201MB1700DA200AA4C756558170A6DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <CALGR9oY033EM9hgxOFeWZ8=1S-N662dm7u-P-5RCwWBZakT-xw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALGR9oY033EM9hgxOFeWZ8=1S-N662dm7u-P-5RCwWBZakT-xw@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: titan.w3.org 1iQFbr-00069J-Lj a9aecc40663f624260047d0ef3291119
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP/2 GREASE, Results, and Implications
Archived-At: <https://www.w3.org/mid/20191031185543.GB30937@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37092
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 Thu, Oct 31, 2019 at 06:10:33PM +0000, Lucas Pardue wrote:
> On Thu, Oct 31, 2019 at 5:49 PM Mike Bishop <mbishop@evequefou.be>; wrote:
> 
> > Upon further investigation, it appears that Akamai hosts most of the sites
> > where the connection gets closed, and Cloudflare hosts the sites which
> > close the stream but leave the connection open (I'm guessing, from what the
> > dev tools show).  Given that we're both represented here, it seems likely
> > that we should be able to drive some internal bugfixes and improve the
> > state of the ecosystem.
> >
> 
> It's possible the Cloudflare closures are related to the client-oriented
> half-closed issue that Willy and Bence have discussed.

Maybe, but regardless, if we have to accept any frame type, half-closed
makes no difference. For haproxy I still purposely decided not to accept
to create a new stream from a unknown frame type (i.e. a frame type
designating an idle stream must be either HEADERS or PRIORITY as stated
in the spec). Because if we start to let such things pass through, we
can't really count on the other end's behavior for subsequent frames :-/

> We'd be happy to
> coordinate with other members of the group on a rerun of the experiment in
> order to come to a more definitive answer.

It would be nice to retest at world scale and be a bit more prepared to
assist users who report breakage.

Willy