Re: Constraining transport parameter allocations

Matt Joras <matt.joras@gmail.com> Tue, 04 May 2021 22:33 UTC

Return-Path: <matt.joras@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 2A2973A1818 for <quic@ietfa.amsl.com>; Tue, 4 May 2021 15:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 11RPYw6A3dci for <quic@ietfa.amsl.com>; Tue, 4 May 2021 15:33:15 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 510333A181A for <quic@ietf.org>; Tue, 4 May 2021 15:33:15 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id v5so4404227ljg.12 for <quic@ietf.org>; Tue, 04 May 2021 15:33:14 -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=fwCWlCd/9w07/2JygkbV17IWpuzRSK6/I/TtfSCpziI=; b=CwK5iORmprDcVuuh4W7TWpp43L+HfS4OsNW8FHaUWKZDcZqR8dyGsa6grlbTXBJ5QV n2kzNrsE1rzaWmIW/id6wxZzy014HNwTnkUlr+h2ZzkKw9LPBr7FilRXD5UYVNDqX0bR q2s/bJsc/soh3HqUdfG/o625cE3+kUSx8LOC++6Wz3J3UoVn0inR8q2FmBFiJ6BPIcr2 HiRUImnGJ8+m1kpkRRsTTFV3Uyq4PbY2xxjERJ0/tsZwxb1jgKQs/0wgsV/E97tYkwIr 8eS6y43bg2MiBfMfRSDXyJq+wWPDIksrlKgotJhkk9WqRsTgY8ApLsCPFWClLLoENhEN lOkA==
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=fwCWlCd/9w07/2JygkbV17IWpuzRSK6/I/TtfSCpziI=; b=b9pIY3Vvou4QwPJ/NLMluicS4/ilnah+RlOyIemzJ7X6K/3LWdr/tXDXxlMoO0rJx5 2o1W5AgbpmHtBVi9PscCU5LGAG+ILMM8iJKuMo5UEHzL9CHlTya6q5MsSPljCq9scpKc lDlBvaLVQirzRmZv1kUKjpmc9jMv7O6y9PE6+jcjPIse48CHhwWVOB88C54DVWKHT7cg AvgKD2lQrYy/Hx99H8s++uua5yybcpFgoOL0jBKUQsrDs2bohMtkCIzLuVdP4SeS/DPm NvemAoIDhbGnBzYJNZhFNjp0AARgI3yGFiLbspoKR9kI3wVlXT2W4yH/2uvQZk4Es86I xyVg==
X-Gm-Message-State: AOAM532kPBISqHCvNXbuGgxhqifnV7icmszr8xC0rPCuAJ9GiVELml07 ZLDXXA+BteMYeMKhpJefAoHey5lS2zGGLWL8bJqGroW6kPc=
X-Google-Smtp-Source: ABdhPJwpJoV7Zt5hll85NXJ7jHLfrBkvOsUgFgthI8Wfb6nYKkC4e/99xbtU3+rbmzmrJ5Yy4mg+IP14owHQgAyywTU=
X-Received: by 2002:a2e:b4f3:: with SMTP id s19mr15583940ljm.229.1620167591413; Tue, 04 May 2021 15:33:11 -0700 (PDT)
MIME-Version: 1.0
References: <dbfae589-7552-4dc4-a3a2-230edaba40e1@www.fastmail.com>
In-Reply-To: <dbfae589-7552-4dc4-a3a2-230edaba40e1@www.fastmail.com>
From: Matt Joras <matt.joras@gmail.com>
Date: Tue, 4 May 2021 15:33:00 -0700
Message-ID: <CADdTf+jQa1z-y1ttt2soMmyJY6zuCo0m4SBLGT4E68pO8emhzQ@mail.gmail.com>
Subject: Re: Constraining transport parameter allocations
To: IETF QUIC WG <quic@ietf.org>
Cc: Martin Thomson <mt@lowentropy.net>, Martin Duke <martin.h.duke@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/e-Vq4jCviC1J_ys3YYRTz3ubabM>
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, 04 May 2021 22:33:20 -0000

Hello all,

It is the opinion of the chairs and the editors that this is something
worth fixing with IANA. We are using this email to make a call for any
objections to this change at this stage. This call will run through
May 11th. Please reply with any concerns or further discussion.

Thanks,
QUIC Chairs

On Mon, May 3, 2021 at 5:55 PM Martin Thomson <mt@lowentropy.net> wrote:
>
> Most of our registries reserve the short varint values (0x00-0x3f) for RFCs.  We didn't do that for transport parameters.
>
> Is there any reason why we should not ask IANA to change this?  The RFC editor noted the discrepancy and I can't say that it was deliberate.
>
> It is probably an accident.  Remember that we only changed the format of transport parameters fairly late in the process and so we probably missed this when that happened.
>
> I would like to ask IANA to tweak the registry policies here, but that means we need to be careful.  Minimally, that means AD approval (Hi Zahed).
>
> See https://github.com/quicwg/base-drafts/issues/4880 for an issue.
>
> https://github.com/quicwg/base-drafts/pull/4887/commits/7e4f0f1ee11db09d7bda5617de51ec06f1b34d24 does this (it's attached to https://github.com/quicwg/base-drafts/pull/4887 but that pulls in other changes).
>