Re: 0-RTT Design for HTTP/2

Willy Tarreau <w@1wt.eu> Mon, 21 December 2020 07:12 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 A7EA83A0EAE for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 20 Dec 2020 23:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level:
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 Bo0rhmjRTxhl for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 20 Dec 2020 23:12:19 -0800 (PST)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (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 071DD3A0EAA for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 20 Dec 2020 23:12:18 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1krFJz-0001VR-Tl for ietf-http-wg-dist@listhub.w3.org; Mon, 21 Dec 2020 07:09:32 +0000
Resent-Date: Mon, 21 Dec 2020 07:09:31 +0000
Resent-Message-Id: <E1krFJz-0001VR-Tl@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <w@1wt.eu>) id 1krFJx-0001Ub-Oi for ietf-http-wg@listhub.w3.org; Mon, 21 Dec 2020 07:09:29 +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 1krFJw-00035F-5W for ietf-http-wg@w3.org; Mon, 21 Dec 2020 07:09:29 +0000
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 0BL79CAh000314; Mon, 21 Dec 2020 08:09:12 +0100
Date: Mon, 21 Dec 2020 08:09:12 +0100
From: Willy Tarreau <w@1wt.eu>
To: Martin Thomson <mt@lowentropy.net>
Cc: ietf-http-wg@w3.org
Message-ID: <20201221070912.GB32410@1wt.eu>
References: <126ee381-7828-451f-865a-db6357928243@www.fastmail.com> <20201219171835.GB18787@1wt.eu> <aaddc671-96b9-4a1e-b83b-bb3e77317fd5@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <aaddc671-96b9-4a1e-b83b-bb3e77317fd5@www.fastmail.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 1krFJw-00035F-5W c8123d5b23e8a4a6b2f43edd0ceff080
X-Original-To: ietf-http-wg@w3.org
Subject: Re: 0-RTT Design for HTTP/2
Archived-At: <https://www.w3.org/mid/20201221070912.GB32410@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/38338
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>

Hi Martin,

On Mon, Dec 21, 2020 at 09:39:33AM +1100, Martin Thomson wrote:
> I don't think that you need anything other than an API that allows you to determine whether early data was accepted.
> 
> Ideally, you also have a means of saving data to the session ticket and
> getting that data back when the connection is resumed.  Then you can save the
> settings in the ticket and then you don't have to remember on your own. A
> simple boolean doesn't give you a lot of flexibility in terms of how you
> deploy this.  With just a boolean you have to commit to discarding session
> tickets every time your server configuration changes.

OK, this is the part I didn't understand, thanks! Thus you were speaking
about the server saving its own settings in order to be able to reuse them
in case of config change.

Server-side settings changes are extremely unlikely, unless some serious
trouble are encountered with the current ones, in which case one will not
want to keep them anyway, even less across a whole server farm. In this
case I'd rather suggest users to proceed in two steps :
  - disable advertising of EARLY_DATA_SETTINGS and wait long enough for
    all clients to leave ;
  - perform the actual settings change and re-enable EARLY_DATA_SETTINGS

Just a point however, my understanding then is that EARLY_DATA_SETTINGS
isn't properly named. The purpose is not as much to send settings using
early data as it is to persist settings across connections. What about
PERSISTENT_SETTINGS instead ? Use of early data here is just a byproduct
of not having to wait for the server settings, and even requests can be
sent over early data in this case.

Willy