Re: Consensus on Deploying QUIC v1 with HTTP/3

Lucas Pardue <lucaspardue.24.7@gmail.com> Thu, 06 May 2021 14:54 UTC

Return-Path: <lucaspardue.24.7@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DF573A24FC for <quic@ietfa.amsl.com>; Thu, 6 May 2021 07:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KvSE0zqE0GVZ for <quic@ietfa.amsl.com>; Thu, 6 May 2021 07:54:22 -0700 (PDT)
Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E97E03A24FA for <quic@ietf.org>; Thu, 6 May 2021 07:54:21 -0700 (PDT)
Received: by mail-ej1-x632.google.com with SMTP id r9so8714892ejj.3 for <quic@ietf.org>; Thu, 06 May 2021 07:54:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/7CPGPamCvBtJjo5qSM2A0P+ikVhNqn7nd33UUvtCec=; b=p0DuImFKAhxzfoHBnBdrNdqiNoJEWMQorF4kxPmdKHidV5Enc+akbblfNP4/iHwRsv fGHNGxTB2LdJ0l8CC+1UiAu9K9LYS+wH1wan7b4014En+kRD0ar4IkwE2S/Fya+IIGC9 6JDeHy4jp604wAia/Dnhlk6/uNrLd86lYRxOBWE6CzOaBaZrxix6ShRaxbHu6oYc8fBo Zx1Lv1Sx6vaLf79PoluerWE7+CoXFQUiuM6w3QKT7Zfbp2650qFKEb/T5xe8EbIj9qKe 3J4z07l6AJhOVRp1WgcFRv4IuGrmL7bHMlZPzj5HF4+L+odwsZMICU5Xq82rZnMHIpLu h1hA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/7CPGPamCvBtJjo5qSM2A0P+ikVhNqn7nd33UUvtCec=; b=gILyo3l3vBlmczAIjyMV82W/VrgXASnOLB0qoYIl/ezIJ6kr63LkibMJ22aVnhShMO VZtVGClqX+muh7rDs7V/UHpqKVfp2h1BKuP7jDi2UImf0JQLPhXfYeKPTn0BH69Mbkyi d0mbgFetDf0X5RE+v4VxVbC1F6MBHN9k4/VdqO9hXObPw4zT/ZtqLqFdUOj/IDcWoaG6 CAio7HfZtaFiIIu8co+sWiV0bmE5WL4yRGU8wrBRBmgezLe82BRRkTEl4WwiDtHIeXqB glvCZNwWEHpnswlrhBiGQnxSn+FAPEIvlvMSc7Y1zrROFRiXDXwa+JipOZBHGO6jH77+ hDXg==
X-Gm-Message-State: AOAM5337lkKPl4d/itzMOXegQ96RVdRG4bR1dPlnD0oufX/djsv2j3Bb 6n37UPXt/ombVqluNM8k9xmGELWXOYku/NRzzOY=
X-Google-Smtp-Source: ABdhPJw/3ThoPE89TmWuT6yL61nPgt+bnMQOGjIWicF2bctg+GNvn0udwoUoBcWtd3kLNDoGi6mTxwIZ7GRg5dXB5t8=
X-Received: by 2002:a17:907:3f06:: with SMTP id hq6mr4972925ejc.46.1620312855275; Thu, 06 May 2021 07:54:15 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9obE-Dbm5Rwmr=h_34vaps1pcv36Jg0MTS_o0mZHEF1FvA@mail.gmail.com> <6740dcaa-3c43-faf2-826e-1cb3bb113aff@gmx.de> <CADdTf+gKZwcZD12he2YaGpWpOePZp_EB4J0QoXL6ozfx0BgJDg@mail.gmail.com> <CADdTf+h=iEjJ6k6FmDBOhYY7iLTjyDPWBejdU+ocyUCiGA09yQ@mail.gmail.com> <6b0ce1c8-bbe4-f8cd-b9c9-8e2eb378bd6d@gmx.de>
In-Reply-To: <6b0ce1c8-bbe4-f8cd-b9c9-8e2eb378bd6d@gmx.de>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Thu, 6 May 2021 15:54:04 +0100
Message-ID: <CALGR9oag_Q-yj2jVvqrKfswAJn4FiNQ_A4H20_dHxmrrCPV80A@mail.gmail.com>
Subject: Re: Consensus on Deploying QUIC v1 with HTTP/3
To: Julian Reschke <julian.reschke@gmx.de>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000029ec7d05c1aa7c7c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1tWp34RuZX7VIoG7h0dysTnfuCc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2021 14:54:27 -0000

Hi Julian.

On Thu, May 6, 2021 at 3:24 PM Julian Reschke <julian.reschke@gmx.de> wrote:

> Am 06.05.2021 um 06:11 schrieb Matt Joras:
> > ...
> >         You may want to clarify what *exactly* you mean by "the QUIC
> RFCs".
> >
> >
> >     Lucas was referring to C430:
> >     https://www.rfc-editor.org/cluster_info.php?cid=C430
> >     <https://www.rfc-editor.org/cluster_info.php?cid=C430>
> >
> > ...Excepting the qpack and http documents. I hit the send button too
> > quickly.
>
> See? That's why I was asking.
>
> So we're discussing just -invariants, -transport, -tls, and -recovery,
> right?
>

Thanks for pointing this out. The email was written from a position
familiar with the current documents' status. I should have been more clear
and explicit.

Yes, the -invariants, -transport, -tls, and -recovery, are the QUIC
documents that are presently in AUTH48 and we expect to be published as
RFCs before -http and -qpack. Other documents adopted by the QUIC WG are
not in scope for this discussion (the applicability drafts, datagram
extension, etc.). So to restate the original position more clearly:

This email commences a formal consensus call for permitting the deployment
of QUIC "0x00000001" with HTTP/3 ALPN identifier "h3" *after* -invariants,
-transport, -tls, and -recovery have been published as RFCs but *before *-http
and -qpack are published as RFC. The call will end on May 13.

Cheers,
Lucas