Re: Ambiguity on HTTP/3 HEADERS and QUIC STREAM FIN requirement

David Schinazi <dschinazi.ietf@gmail.com> Fri, 17 June 2022 17:34 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 107A7C14CF05 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 17 Jun 2022 10:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.76
X-Spam-Level:
X-Spam-Status: No, score=-7.76 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BCLI_NPcUMnT for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 17 Jun 2022 10:34:47 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B81A7C14F726 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 17 Jun 2022 10:34:47 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1o2FpF-0000o6-BD for ietf-http-wg-dist@listhub.w3.org; Fri, 17 Jun 2022 17:32:05 +0000
Resent-Date: Fri, 17 Jun 2022 17:32:05 +0000
Resent-Message-Id: <E1o2FpF-0000o6-BD@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 <dschinazi.ietf@gmail.com>) id 1o2FpD-0000n2-Rd for ietf-http-wg@listhub.w3.org; Fri, 17 Jun 2022 17:32:03 +0000
Received: from mail-pj1-x102a.google.com ([2607:f8b0:4864:20::102a]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <dschinazi.ietf@gmail.com>) id 1o2FpC-0000hF-LV for ietf-http-wg@w3.org; Fri, 17 Jun 2022 17:32:03 +0000
Received: by mail-pj1-x102a.google.com with SMTP id g10-20020a17090a708a00b001ea8aadd42bso4772131pjk.0 for <ietf-http-wg@w3.org>; Fri, 17 Jun 2022 10:32:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qWVkj5jgn3RsC1yl3k7ULtTgZDquqhxIXCxsNORvRHc=; b=bgn/VmTsi0TJphhzCN6pkqh34OUCQvj+Krz72U9QFsx+af5vbDC/lM5Hbp0nAbvska 4mg2cvjhfhiilf7zGbwatQPeGiO9qiiKAkUp6kQ/kcC2+Hx3/SiZbuPnc61GzHjmcklQ O4KxoCYhWuPgEEOM90AlqRh6pBCqLzr7/Z7Uy3S/DkLyLIjPj4sR6mD4U3j/N9RrzJdV 0nTJMQe1s/EIftbIXmUjOFjmziAV3qtYgCTbexg99qrEO01nUGm1Jy6guB0/WOv71aWp 5igTGO4WrOiTyTBa9JUcIIxK9IyNv9M1oyUJpNtxEt1SAk7QTqiMPbBVy8cIu0WyGtxF 5NMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qWVkj5jgn3RsC1yl3k7ULtTgZDquqhxIXCxsNORvRHc=; b=egWx7NUImgcfan8Zgvwjrjn2j1Qec2YzWUVJ9CnlFnGDSSFytgoWWt8KBy/nBxXCgB 9wgp3olkdPI2FiQlFu6tEHx5rVYL/6iew9BKGxbQCmJolvMlO7IPpr5uMXaLXf48mLOA wJ5mgIFHIN5gXskhx2oVeomT1JxlhhBR6y7TIIrdCnBxaSVQlKpkFQTW+ZlrpSBVaN3n oSj/iSeCmy27LHDm8Ra9/T7tvbcbS/46Q4JvIu+VYNZZNMv4erbKRXToWRJaHuFb8Yeu 4sT7ElX9Ef+hEW7z6BFd56Tny2N3v58v6rxGxZu80uiicJT+QNfdiaZi8bTPTZol54+S gkEw==
X-Gm-Message-State: AJIora9lZWc4YJSG5TzirL8zcbtUleW7rBTPzL/Lf60PI7J08QIwruAT 3E7jSkkSEioAZUa3SOZzGiXEZVv3pwH/mA39Oi4/rQEK
X-Google-Smtp-Source: AGRyM1sqXOY8PnRWbOZHqNYw6WBsvgFr1sRE/49mHB7BHsy9mC/TaE/ZW7Aw4mBjvblxHM0+pg1nMGwsd5yS65x55Ek=
X-Received: by 2002:a17:902:8502:b0:16a:34a:e477 with SMTP id bj2-20020a170902850200b0016a034ae477mr4950451plb.40.1655487111232; Fri, 17 Jun 2022 10:31:51 -0700 (PDT)
MIME-Version: 1.0
References: <CAJ_4DfRD9ktc1cmDd8GmQDx8iX6s=NYj3C9MW-3-yU+SZYxkEQ@mail.gmail.com> <CALGR9obvYB-2vYXYgwSMpS3s8uSbLKn0ZF39piYQ_ROt8DAXJg@mail.gmail.com> <CAPDSy+5-+L_F8gOYht2OWmWHnp4JtWt4tfPbM_TN799AgK7H1A@mail.gmail.com> <71b309c9-0220-4e14-8be5-13f2cb1d1278@beta.fastmail.com> <20220617045330.GB30314@1wt.eu> <d2a71dca-1c0d-416e-8f94-700114266aaf@beta.fastmail.com> <20220617053700.GD30314@1wt.eu> <b5e21b22-e447-4ba1-b907-e2785deb2d5d@beta.fastmail.com> <20220617101722.GA30560@1wt.eu> <CALGR9oba=7Ajf2p+hf+yNVGiaQ1=Vwarq5iPxCmUxLMT_7m0AQ@mail.gmail.com> <20220617104853.GA30707@1wt.eu>
In-Reply-To: <20220617104853.GA30707@1wt.eu>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Fri, 17 Jun 2022 10:31:39 -0700
Message-ID: <CAPDSy+59E4MJ+OkEEEUN_XykEg8qy7AQPTUs5J0XuKOhomCXLQ@mail.gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, Martin Thomson <mt@lowentropy.net>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="00000000000032014e05e1a821c5"
Received-SPF: pass client-ip=2607:f8b0:4864:20::102a; envelope-from=dschinazi.ietf@gmail.com; helo=mail-pj1-x102a.google.com
X-W3C-Hub-DKIM-Status: validation passed: (address=dschinazi.ietf@gmail.com domain=gmail.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-6.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1o2FpC-0000hF-LV 1b57d789aea7d5b1e3dd8f6cbaead3c0
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Ambiguity on HTTP/3 HEADERS and QUIC STREAM FIN requirement
Archived-At: <https://www.w3.org/mid/CAPDSy+59E4MJ+OkEEEUN_XykEg8qy7AQPTUs5J0XuKOhomCXLQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40155
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>

Since it's Friday and we're exploring crazy thoughts, instead of
":no-content" why not simply content-length=0?
David

On Fri, Jun 17, 2022 at 3:49 AM Willy Tarreau <w@1wt.eu> wrote:

> Hi Lucas,
>
> On Fri, Jun 17, 2022 at 11:41:43AM +0100, Lucas Pardue wrote:
> > Which leads me to a wild thought*. One could attempt to solve this
> problem
> > in the HTTP framing layer, by introducing, via extension, a new
> > pseudo-header ":no-content", which modifies the message exchange sequence
> > in H2 and H3 such that no DATA frames are allowed after the first flight
> of
> > header section. That solves the disjoin between the headers section and
> the
> > ES flag or FIN bit. And would allow the receiving peer to make more
> > concrete choices about whether to process a request early or wait a bit.
>
> I think that it's an excellent idea to explore! The pseudo-header fields
> were created to fill a gap and this is a perfect example of such a gap
> where the HTTP framing doesn't sufficiently permit an agent to express
> its intent anymore, and your proposal addresses this. The only thing is
> that if we wanted to do something clean, it would have to be advertised
> with the vast majority of GET requests, which is unlikely to happen in
> the foreseable future. Regardless, I think it's worth continuing to
> think around this.
>
> > * It's Friday, so it's the day of the week I'm allowed to have these :-P
>
> You're right ;-)
>
> Willy
>
>