IETF Logo Mail Archive

Re: Consensus on Deploying QUIC v1 with HTTP/3

Lucas Pardue <lucaspardue.24.7@gmail.com> Thu, 06 May 2021 17:29 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 E89D13A2A09 for <quic@ietfa.amsl.com>; Thu, 6 May 2021 10:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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] 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 uOwzPGV7uOQK for <quic@ietfa.amsl.com>; Thu, 6 May 2021 10:29:41 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (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 91BB73A2A08 for <quic@ietf.org>; Thu, 6 May 2021 10:29:41 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id zg3so9454157ejb.8 for <quic@ietf.org>; Thu, 06 May 2021 10:29:41 -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=yd6qDxA3GKPBHlPLt77TuKLgQF8EJTBVPY4vlbzkbPk=; b=aI9fBAmpmRA0i8jQzLqM3Qmudt3pdTAXJn4jZNUxmuQAOU+Zjxc0Hb77TJOPk2mQca wJE+pS0gRn2tpJ/ADlvqIaBVcvfMZSm7m/0r5dL6qpkEAPStHh6qPaTUeJS8TNzADwF8 JXuxWmtxQ2h0guZasxnppPuEQ3U1j/B/pkVmiM8/SlI+k5DSnwecN5irkMakxXryP2Uj mnOhzsFs9nM73qyoSsUxuSkO3hZ158gnNTHwMK1sYErXA4OzwaAvszyuYzX5AQ+6bus7 d4JbC6VI6tQfOx11q67+GoNJsOc9vaZFWaxasPJyUEls6vZ1KHNAFcR9WgcshUa+Yi0Z DTbA==
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=yd6qDxA3GKPBHlPLt77TuKLgQF8EJTBVPY4vlbzkbPk=; b=hKpVVkyowUylmioBa6zrWuQbQWt/KeCHoUQU2MgQDBzu9TaJUxSkqLCdgv+MKA++04 4sjZhBy7werF5Q/ypUlzcDRgY5sUczTDPgLtev4V2KFlbnXBVwwnnWuEXPPwIY4x42wi amIWoXJqjeXIM70eJv2Z57w4rkqYiIbch9aiBFK1iMKRI0X9mEZjnbkUw9skCxboDtk0 bYzD7a+Xp7O16h80/0MqcWwuZ9Fe7LHG1ZImiIWGFCb6DleHsuzsTlppdBlqoMKk0lod hlHB1+pDCrCDBJKBqtETAJE1r6+B7S9Dl271+uEf00yk+NVsb/FQVM7L+GRjQL08zJg6 E+Qw==
X-Gm-Message-State: AOAM533A5X8awzxTkmYX7mYX5eMqQlfnC7vPX9WHB2Yv00md6sFdahuW BkZctzr7pMMbiNhhyyKbGfUWiWzZIYT/WpVKnEgFrxmRais=
X-Google-Smtp-Source: ABdhPJwEP5s/8SYXcnb5uvFurEtFkDBr90Xct1tQK/5+KfuF21+TlCkzIL96yVmujnzjIcw35+KOo0rk5uQzdL6jUx8=
X-Received: by 2002:a17:906:7c82:: with SMTP id w2mr5775889ejo.448.1620322178498; Thu, 06 May 2021 10:29:38 -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> <CALGR9oag_Q-yj2jVvqrKfswAJn4FiNQ_A4H20_dHxmrrCPV80A@mail.gmail.com> <CAPDSy+5Ce2NgnUFtHHO0FoEue7t9zph1HZQRe3_Yf3yzncAD9A@mail.gmail.com>
In-Reply-To: <CAPDSy+5Ce2NgnUFtHHO0FoEue7t9zph1HZQRe3_Yf3yzncAD9A@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Thu, 06 May 2021 18:29:27 +0100
Message-ID: <CALGR9obNLjWeD_+SxfhjbckPHS7u1nUHUta0aFRNzfzgbbD6WQ@mail.gmail.com>
Subject: Re: Consensus on Deploying QUIC v1 with HTTP/3
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000df05dd05c1aca753"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/y46yDqS7YkD3wtU3-LjaNUmgbHM>
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 17:29:44 -0000

Hi David,

On Thu, May 6, 2021 at 5:38 PM David Schinazi <dschinazi.ietf@gmail.com>
wrote:

>
>
> On Thu, May 6, 2021 at 7:54 AM Lucas Pardue <lucaspardue.24.7@gmail.com>
> wrote:
>
>> 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.
>>
>
> Hi Lucas, since this is a formal consensus call, can you formally define
> what you meant by "deployment"? Some clarifying questions:
> - Is running a 1% experiment on clients before then OK?
> - Is running a 1% experiment on servers before then OK?
> - Is running 0x00000001+h3 on your main production server today OK if you
> don't use Alt-Svc?
> What we're describing is effectively a flag day, and it would be good to
> define its parameters clearly.
>

These are excellent questions. So far the WG discussion has focused on the
0x00000001+h3 question. There is ambiguity in the transport-34 and http-34
definition of deployment and to date there wasn't much discussion of that.
The chairs would appreciate the WG to respond specifically to this point.

Cheers
Lucas

v2.23.0 | Report a Bug | By Email