IETF Logo Mail Archive

Re: Consensus on Deploying QUIC v1 with HTTP/3

Lucas Pardue <lucaspardue.24.7@gmail.com> Tue, 11 May 2021 10:55 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 C043C3A0FFD for <quic@ietfa.amsl.com>; Tue, 11 May 2021 03:55:17 -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, RCVD_IN_DNSWL_BLOCKED=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 v6o7wW_DN70F for <quic@ietfa.amsl.com>; Tue, 11 May 2021 03:55:16 -0700 (PDT)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 4A6F73A0FFB for <quic@ietf.org>; Tue, 11 May 2021 03:55:16 -0700 (PDT)
Received: by mail-ed1-x535.google.com with SMTP id j26so18648735edf.9 for <quic@ietf.org>; Tue, 11 May 2021 03:55:16 -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=La6+hThEkoNQnz74EJcYKd5B3gsHF4GstW4tcfAxSwo=; b=Y+0fzrPHlk+3mF7sn7USTE1Y7ijVCl/+TINKXHxyFQv9U9cnO1QdzHqgcFBapZP8+h 0plac6cGqUlrKLNDZUCsN3d6VsQvJBB5W/Qa1WnzPAA+xLFjMFFR6mb9UqSFX7W3u/MC JcsK3Ln5QPrBDFpMQUv6/nw5NtYo/RYe31M24BVKoNSEP084mbImc209aNMhW58l+2Gp AX80tqBzAClnJ5Vf3umjIttYULUr+j6ZiaK+KtYE1jGHGYLNKsFpNiZq7lAXbNgGEJpa Y3Nom9sygSYMm70Qlj19p6a8UzqXPQs5J7MqjlAswxDyFo7Y6CJfS1gTMLDNYCrvl+1C 22TA==
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=La6+hThEkoNQnz74EJcYKd5B3gsHF4GstW4tcfAxSwo=; b=e9iPmDI+cG2+d0IuGpr5tEbFkYffTQ1vcT/jeXYpfPMO+i3Tc9trXbO/WCwcgr6NER pviJ5NgdmXDEQa0bHU0uO3DgsLFt8+9KVKea2VsFnDZEsuZIJ0gdUE8yqNxdQR8UwkMK nY4Y+C6eu4WQt78nq8tD76FKYT7CEKw36VNZLffO+Y8OTvKhLx7FK2gd5sVvcFcbtu5G svSe8dr3cFJ/nw/P90Tove658wUnTV49Jl1/UmWo6vz2JmX/cwLZhRxBHrMq7YBVCgyA 9PL3H31p74ZbzF9wknbWkhdiTG975e0EM80DeIx9pCm0Zzv1Q4O45b2eV4actX6b7I4a zshA==
X-Gm-Message-State: AOAM5334SfTKCvW6lF+lkHvNZ61yA1swIvgkMScvkmyK3VwanRErhKc7 S3WSNRME/MAFIlzSfuIUIaK7dDNqw8mgnUT7k7bxhiEd
X-Google-Smtp-Source: ABdhPJx9vTJmFvZx/NNBFAxv3GJL4fBus602JA5wvA5oc7vAzD02qdqDNl897NWZiu6YFtSZ+hb3rS+qRC9+vKBMDCI=
X-Received: by 2002:aa7:db95:: with SMTP id u21mr35323715edt.152.1620730513760; Tue, 11 May 2021 03:55:13 -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> <CALGR9obNLjWeD_+SxfhjbckPHS7u1nUHUta0aFRNzfzgbbD6WQ@mail.gmail.com> <CAPDSy+7DxJcaKd9e_hCgxcZbk3dwSALT8uu2QxCUjJUcUeoJ9Q@mail.gmail.com>
In-Reply-To: <CAPDSy+7DxJcaKd9e_hCgxcZbk3dwSALT8uu2QxCUjJUcUeoJ9Q@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Tue, 11 May 2021 11:55:01 +0100
Message-ID: <CALGR9obvQZWbU0Yh5yMwbHc+RWYUxpR1DdL-p0P9R=XuycDL0Q@mail.gmail.com>
Subject: Re: Consensus on Deploying QUIC v1 with HTTP/3
To: QUIC WG <quic@ietf.org>
Cc: David Schinazi <dschinazi.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000008ca34c05c20bbad5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/D_wP6QvflSdPRW2LR1CENkTJhl4>
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: Tue, 11 May 2021 10:55:18 -0000

WG members,

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

> My personal opinion is that once we open the floodgates we can't close
> them. More specifically, if someone ships an implementation to production
> in a way that they cannot guarantee that it can be updated, then the
> version used is now immutable. In practice, that means that if you ship a
> client device that uses software updates, because some users do not update,
> then that would lock us in. In that regards, I could see a world where:
>
> 1) Deploying on your server today is OK as long as you can guarantee that
> if the protocol changes you'll be able to disable h3 or deploy a fix in
> under 14 days
> 2) Deploying a client-side experiment today is OK as long as that
> experiment will automatically stop after 14 days if the client device stops
> hearing confirmation that the protocol is still OK to use
> 3) Once -invariants, -transport, -tls, and -recovery have all been
> published as RFCs, then deploying everywhere is OK
> 4) Lack of Alt-Svc doesn't change points 1-3
>
> Thoughts?
>

Does anyone have any additional thoughts wrt to David's posits?

Cheers
Lucas

v2.23.0 | Report a Bug | By Email