Re: [quicwg/base-drafts] Allow provisional registrations for all registries (#3170)

Mike Bishop <> Tue, 05 November 2019 23:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6BB0F1200C3 for <>; Tue, 5 Nov 2019 15:21:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id meN_1iy5j_xF for <>; Tue, 5 Nov 2019 15:21:26 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C8796120072 for <>; Tue, 5 Nov 2019 15:21:25 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id D0BE48C0545 for <>; Tue, 5 Nov 2019 15:21:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572996084; bh=YLsJbH9iMOUA9Qu8x6g/zkPuhjOieVRmpT8BDHjFPe8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mP24ai3J1t36/MrXkUUQwF6H+0B9BPezVVSXbZTGWpf3tTbi17k41IfWisce4aMIb EPNUMsTEp+JIDVuR9414VE96cH6xAmata8tAb99aZO8T1+t07smmz7MwEL58r9C5DK 9bRmb2Z9t0c6YNFgI6kvBNn5c0beOjreTJPl+E1k=
Date: Tue, 05 Nov 2019 15:21:24 -0800
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3170/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Allow provisional registrations for all registries (#3170)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc203f4c1b17_10423facd82cd96c23912d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 05 Nov 2019 23:21:30 -0000

MikeBishop approved this pull request.

Minor nits; otherwise looks good.

> +{{!RFC8126}}.  Designated expert(s) are advised that only registrations for an
+excessive proportion of remaining codepoint space or the very first unassigned
+value (see {{iana-random}}) can be rejected.
+Provisional registrations will include a date field that indicates when the
+registration was last updated.  A request to update the date on any provisional
+registration can be made without review from the designated expert(s).
+All QUIC registries include the following fields to support provisional
+: The assigned codepoint.
+: "Permanent" or "Provisional".

The others here don't have a blank line between them.

> +New uses of codepoints from QUIC registries SHOULD use a randomly selected
+codepoint that excludes both existing allocations and the first unallocated
+codepoint in the selected space.  This minimizes the risk that differing
+semantics are attributed to the same codepoint by different implementations.
+Use of the first codepoint in a range is intended for use by specifications that
+are developed through the standards process {{?STD=RFC2026}} and its allocation
+MUST be negotiated with IANA before use.
+For codepoints that are encoded in variable-length integers
+({{integer-encoding}}), such as frame types, codepoints that encode to four or
+eight bytes (that is, values 2^14 and above) SHOULD be used unless the usage is
+especially sensitive to having a longer encoding.
+Applications to register codepoints in QUIC registries MAY include a codepoint
+as part of the registration.  IANA MUST allocate the selected codepoint unless
+that codepoint is already assigned or the codepoints is the first unallocated

that codepoint is already assigned or the codepoint is the first unallocated

> +
+### Reclaiming Provisional Codepoints
+A request might be made to remove an unused provisional registration from the
+registry to reclaim space in a registry, or portion of the registry (such as the
+64-16383 range for codepoints that use variable-length encodings).  This SHOULD
+be done only for the codepoints with the earliest recorded date and entries that
+have been updated less than a year prior SHOULD NOT be reclaimed.
+A request to remove a codepoint MUST be reviewed by the designated expert(s).
+The expert(s) MUST attempt to determine whether the codepoint is still in use.
+Experts are advised to contact the listed contacts for the registration, plus as
+wide a set of protocol implementers as possible in order to determine whether
+any use of the codepoint is known.  The expert(s) are advised to allow at least
+four weeks for this search.

four weeks for responses.

> +the registration is made, the codepoint MUST NOT be reclaimed.  Instead, the
+date on the registration is updated.  A note might be added for the registration
+recording relevant information that was learned.
+If no use of the codepoint was identified and no request was made to update the
+registration, the codepoint MAY be removed from the registry.
+This process also applies to requests to change a provisional registration into
+a permanent registration, except that the goal is not to determine whether there
+is no use of the codepoint, but to determine that the registration is an
+accurate representation of any deployed usage.
+### Permanent Registrations {#iana-permanent}
+Permanent registrations in QUIC registries require Specification Required policy

Permanent registrations in QUIC registries use the Specification Required policy

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: