[quicwg/base-drafts] 54ed6d: Allow provisional registrations for all registries

Martin Thomson <noreply@github.com> Wed, 30 October 2019 06:43 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CDE812008F for <quic-issues@ietfa.amsl.com>; Tue, 29 Oct 2019 23:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 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, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oowKOWBxQq-Z for <quic-issues@ietfa.amsl.com>; Tue, 29 Oct 2019 23:43:15 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 581B3120043 for <quic-issues@ietf.org>; Tue, 29 Oct 2019 23:43:15 -0700 (PDT)
Received: from github-lowworker-e8b54ca.ac4-iad.github.net (github-lowworker-e8b54ca.ac4-iad.github.net [10.52.23.39]) by smtp.github.com (Postfix) with ESMTP id A81856A006F for <quic-issues@ietf.org>; Tue, 29 Oct 2019 23:43:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1572417794; bh=NiLHH+Kd++OoYtVXBUuWNeSmZKN6As3WDmk8mvU0sv8=; h=Date:From:To:Subject:From; b=mrgsO0W2QOX4ia7ac8k7mjQdtk6XYoOmyWXU/8pH0KUzE4PJN8WPopsD9cQY0EGlo LwhYbvg9mmkRmsCc5aCF0Htcw9NwtYH4mipkHAIxhYrJyrOZr/EQ5yi1xBdsIjq94p AolHe5j2QkG1EqZ5x93MlVKnu4/0VZQfwMbeM7iA=
Date: Tue, 29 Oct 2019 23:43:14 -0700
From: Martin Thomson <noreply@github.com>
To: quic-issues@ietf.org
Message-ID: <quicwg/base-drafts/push/refs/heads/provisional/000000-54ed6d@github.com>
Subject: [quicwg/base-drafts] 54ed6d: Allow provisional registrations for all registries
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-Auto-Response-Suppress: All
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/XAJWy9HS5zOXD_q4KocTzh4hJmg>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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:43:17 -0000

  Branch: refs/heads/provisional
  Home:   https://github.com/quicwg/base-drafts
  Commit: 54ed6dc0572c3b88f05c8eaa8ef5b520eb00dc21
      https://github.com/quicwg/base-drafts/commit/54ed6dc0572c3b88f05c8eaa8ef5b520eb00dc21
  Author: Martin Thomson <mt@lowentropy.net>
  Date:   2019-10-30 (Wed, 30 Oct 2019)

  Changed paths:
    M draft-ietf-quic-transport.md

  Log Message:
  -----------
  Allow provisional registrations for all registries

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't agreed to that in the past.

I'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 "live".

Closes #3109. Closes #3020.