Re: Constraining transport parameter allocations

Matt Joras <matt.joras@gmail.com> Tue, 11 May 2021 21:32 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 784803A2739 for <quic@ietfa.amsl.com>; Tue, 11 May 2021 14:32:44 -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, 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 p5Fe8aWugxpJ for <quic@ietfa.amsl.com>; Tue, 11 May 2021 14:32:39 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 A26BF3A273A for <quic@ietf.org>; Tue, 11 May 2021 14:32:39 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id e11so13443488ljn.13 for <quic@ietf.org>; Tue, 11 May 2021 14:32:39 -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=yhJVmITXsYQz11fM8YUDI65F7Elzol4OwT+1qHUUbVo=; b=KID45pRpgH76k8AhW7YtRqD9/Zrbm64PtSAXbC+6pa6+aDEjPIJI6wd4+QnNpo8Ap0 mPuKtJHoDulzYVHGh50O0pFdcz6MuE+kdZ+LqRiZEzyKxJp0aQkwmvFww08Jv/wAv4yb xJdbx4yt7R8kjWQ6ar2qAFrRg6e5J2/4i4Xhnq+Be0OrJhUVoTaMbb54r9J2NQhED2TY y5L12efnTRFLHHWpgiac2n/+4a4owcwrCzRW8Kmku3B84l/Mr3mwke6631KB1nrxYwYP s9zubkq7q7zOz9YGI/vPJU/Rcw2/lwDwN2ZKvXjXfHn08yhXH4xv1rYufbgFObSuvrm7 tnig==
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=yhJVmITXsYQz11fM8YUDI65F7Elzol4OwT+1qHUUbVo=; b=H/BdzZzFgbnD8NIdydz6lbSptos8avCxmKYith0oZvdjyOx5cVdFVf71fpBtNkpI3s VJIYtvHzWyFRuzM6yZUtFhL1KxmyK4pzNkW8z0Q98cv8D11IT9Xczp+jTE1V8VRkG1d/ EuOgEkkzJIu3yN0xUKQKzpFfMjao2I/pG+cz3mdK5bM6CWVY/0KzHskdpDV9N3HQFIXe FeYHBlTsFL85JLPHOftVaOJL8yUI2tsLM4bCYTyUjeSh26zy7+H4sD0StlndTzoI6yMQ HBLgUVnCeDyrmr/r925TFBOJxGP4D/4x9ApRZV4KfBa3CUZ7FfooKK5g7vKoc2P4z+n/ 6TGg==
X-Gm-Message-State: AOAM533UKF2vNXefnPoySOZWHvsZEwYnkD7KHFY5QDsh6SncrCZbf3eN 5R5S6M7VW/ZcP1F7yS6fITOhaePQT19tJvMvRL1gPR/Sd1M=
X-Google-Smtp-Source: ABdhPJyLwm+8u7XovCuAZQ7OQ4dmVQVLCBOpPqLtKxs5YdNWg2GTNR12uJo51OD1H0TM/xZsbqXPMYaPdj7FfGSg1g8=
X-Received: by 2002:a2e:5045:: with SMTP id v5mr26330584ljd.270.1620768756294; Tue, 11 May 2021 14:32:36 -0700 (PDT)
MIME-Version: 1.0
References: <dbfae589-7552-4dc4-a3a2-230edaba40e1@www.fastmail.com> <CADdTf+jQa1z-y1ttt2soMmyJY6zuCo0m4SBLGT4E68pO8emhzQ@mail.gmail.com>
In-Reply-To: <CADdTf+jQa1z-y1ttt2soMmyJY6zuCo0m4SBLGT4E68pO8emhzQ@mail.gmail.com>
From: Matt Joras <matt.joras@gmail.com>
Date: Tue, 11 May 2021 14:32:25 -0700
Message-ID: <CADdTf+iuLJ4hTKMubgLu15UCze3t=+LRO6+cvS7wp=SKmZJX=g@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/Ts9gHxTqoFt9jnWPa8DnCp32o4o>
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 21:32:45 -0000

Hello all,

Hearing no objections or further discussion, we consider there to be
consensus that this is alright to do.

Thanks,
QUIC Chairs

On Tue, May 4, 2021 at 3:33 PM Matt Joras <matt.joras@gmail.com> wrote:
>
> 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).
> >