Re: QUIC v2 and Version Negotiation Needs Your Deployment Feedback

Martin Duke <martin.h.duke@gmail.com> Thu, 01 December 2022 19:41 UTC

Return-Path: <martin.h.duke@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 10AA9C14F74F for <quic@ietfa.amsl.com>; Thu, 1 Dec 2022 11:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjqaAGh1EDoX for <quic@ietfa.amsl.com>; Thu, 1 Dec 2022 11:41:29 -0800 (PST)
Received: from mail-qv1-xf35.google.com (mail-qv1-xf35.google.com [IPv6:2607:f8b0:4864:20::f35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AC9EC14F6EC for <quic@ietf.org>; Thu, 1 Dec 2022 11:41:29 -0800 (PST)
Received: by mail-qv1-xf35.google.com with SMTP id d13so2035501qvj.8 for <quic@ietf.org>; Thu, 01 Dec 2022 11:41:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4u+tfAZj7vsLMAsJWtyu0JpHgLixtetdR3VPnDiJdH8=; b=QSVp7untqFr1XPLgRDQsu87bi0WpQV56k5wjk1KNup9bUcg25AY3LZKRn82MqkiLH4 o0pq9w0RfONbrHpzWcZO76RI/Z0sB/TOKz27hH1iseh1yqKH/mugGjg4JljRWmHpQS9D j4V46ak6y/OeMNbya5OBN3YkxICLgKmtYZU8AepZuoy0TY3P+pJsZbZ/nUVb81u8sK9c n9DIw/lXsbM/SzrcGZAmzZm7YJkVP8+R5ithU18FAjeP/fcwgNxjj/fxH7LwpzS5bR2G egPxWrKrsrVfR+dN+iltzuJuhL0TP+6BdeeBu55yUA8r7EaKUKZYw27pM9M6dk2Sj7Vc vYTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=4u+tfAZj7vsLMAsJWtyu0JpHgLixtetdR3VPnDiJdH8=; b=A/emfDqcDjjswKH4joH3jDmvrtIH5Ci6XE3BSJZwXUD7+lzAWfGwJEI4HPmN8siO9c jsk6nVUcwVEe0WzurXuN7SrL1EynxUHKydXXjMHd+eZZ9kdYPewJZeVhqec/TILqfEly X3ttOCfrNTIiiEkLpjGuEG3Yg3QJfrQQdEPJptv3w1+Qh6270HMbSLw+qVcjBJc3gshS Y5edh1ShyHffgEcQg4Gak3E4n0rPHcs1M9p9JXNQn5Wt5VDhZCqcSAxS7nQUkomtfUe0 mEqX4IZBv2BqiMNHPJ30QMZHMLd3tuy+uWHgrpejX+/KUoQE/cdet88HGbxQFI0FgC0t KVuw==
X-Gm-Message-State: ANoB5pn5PxiIhDAchma7HeSRGW8hJVEUk/xoX/NxPDna1991nfbBbbrZ 89m9qWEmV6F44bcU+5+xz+WpSZAprVC4xGKFPYo=
X-Google-Smtp-Source: AA0mqf5Exh8TDj3wT7ViIWW+xW49WiJREj+c2uv4nBaBxFeLCZcT2nfMgeyxwRmuqAbhmythzsmXSVFq+Z2YKvr/+g0=
X-Received: by 2002:a05:6214:2c1f:b0:4c6:a598:4fba with SMTP id lc31-20020a0562142c1f00b004c6a5984fbamr43763737qvb.109.1669923688201; Thu, 01 Dec 2022 11:41:28 -0800 (PST)
MIME-Version: 1.0
References: <CADdTf+hGE5LGviD7py+3j8SDLUZY9dA=OUkiLQ=DrgcnVK815A@mail.gmail.com>
In-Reply-To: <CADdTf+hGE5LGviD7py+3j8SDLUZY9dA=OUkiLQ=DrgcnVK815A@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Thu, 01 Dec 2022 11:41:15 -0800
Message-ID: <CAM4esxQuzW6GA4WK0s=ieh_7Krsdj1G12K=stepJBUQ4M34tjA@mail.gmail.com>
Subject: Re: QUIC v2 and Version Negotiation Needs Your Deployment Feedback
To: Matt Joras <matt.joras@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003cc5af05eec968b6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SaMr8s11Jtrqkv70mOpC5OwnQWg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
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, 01 Dec 2022 19:41:34 -0000

Relatedly, if I roll a new QUIC version field, should I also rev the salt,
retry key, and so on?

On Thu, Dec 1, 2022 at 8:41 AM Matt Joras <matt.joras@gmail.com> wrote:

> Greetings QUIC WG,
>
> We are currently in a situation where the v2 and Version Negotiation
> documents are stalled pending IANA assignments. MT raised this issue
> recently on the list[1], and we are boosting visibility once again since
> these allocations have implications for anyone who has deployed VN/v2 code,
> as changes will likely cause negotiation failures. We are currently leaning
> towards going with MT's suggestion, which is to allocate new codepoints for
> the VN transport parameter as well as the v2 version. Please provide any
> feedback for/against either in this thread or the original.
>
> Best,
> Matt & Lucas
> QUIC WG Chairs
>
> [1]
> https://mailarchive.ietf.org/arch/msg/quic/f4kdku9pqI6raepT_L3z_pth3Uo/
>
>
>