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

Martin Thomson <notifications@github.com> Wed, 30 October 2019 06:45 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6A37212008F for <quic-issues@ietfa.amsl.com>; Tue, 29 Oct 2019 23:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id naWD-VEG3Qi8 for <quic-issues@ietfa.amsl.com>; Tue, 29 Oct 2019 23:45:32 -0700 (PDT)
Received: from out-17.smtp.github.com (out-17.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65824120043 for <quic-issues@ietf.org>; Tue, 29 Oct 2019 23:45:32 -0700 (PDT)
Date: Tue, 29 Oct 2019 23:45:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1572417931; bh=N1WyOR4xDzoOT1JKH05Efoj5KCIe4OKN3hpnJ8v2V1I=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=hK8AQ17ablRyFbM2emdm3/N4S467xmncPp5oZyWBdh13GH+eR9gDjIAJRCjxHYpPF p8c+VO6/3mhfweM6s99F1btmSP2nWYfnCZCIlO/ANd9lapNb9vesv5F7rl9/qzowmL CxjTpBI+3VST8f9uSOWtUIPRQozihGcodgE6nrYk=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZZF6GHK37ZEZVAD653YZSAXEVBNHHB5KNIHE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3170@github.com>
Subject: [quicwg/base-drafts] Allow provisional registrations for all registries (#3170)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db9318b5b1fb_5f643fefeeecd95c2137e5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Sf7W9YAtPG3Tq90oAB0N0lhG5Hw>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2019 06:45:34 -0000

This overhauls the system for IANA registries to use a unified scheme that allows provisional registration.  This seems pretty complicated in terms of nailing down all the corner cases, but it is fairly simple in practice:

* Provisional registration is easy, it only requires that the requester provide contact information and (ideally) the codepoint they want. They could provide more, but at their discretion.

* Permanent registration requires that you fill out the fields. 

Experts are required for both, but only really to prevent spam.  We have a few more requirements for permanent registrations of frame types, but that is more for the purposes of advice, because sending an new frame leads to protocol errors if you haven&#39;t agreed to that in the past.

I&#39;ve sketched out a strawman for a codepoint reclamation process.  That advises that experts try to find some use of the codepoint.  There is a date on registrations that can guide the selection of codepoints to reclaim, but these can be updated any time by anyone who wants to keep the registration &quot;live&quot;.

I wanted to sketch this out for transport first, but I intend to update this PR with changes to the HTTP draft if these policies are agreeable.

Closes #3109. Closes #3020.
You can view, comment on, or merge this pull request online at:


-- Commit Summary --

  * Allow provisional registrations for all registries

-- File Changes --

    M draft-ietf-quic-transport.md (226)

-- Patch Links --


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