[Cbor] Draft text for pull request for tag range IANA allocation policy

Sean Leonard <dev+ietf@seantek.com> Wed, 14 August 2019 16:08 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 24AC212082B for <cbor@ietfa.amsl.com>; Wed, 14 Aug 2019 09:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.101
X-Spam-Level: *
X-Spam-Status: No, score=1.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEXHASH_WORD=2.999, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id mbjMyB6-Vo9C for <cbor@ietfa.amsl.com>; Wed, 14 Aug 2019 09:08:46 -0700 (PDT)
Received: from smtp-out-4.mxes.net (smtp-out-4.mxes.net []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1768E120806 for <cbor@ietf.org>; Wed, 14 Aug 2019 09:08:46 -0700 (PDT)
Received: from Customer-MUA (mua.mxes.net []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7CC64273C3 for <cbor@ietf.org>; Wed, 14 Aug 2019 12:08:42 -0400 (EDT)
To: cbor@ietf.org
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <12deba80-20ba-cf55-162f-a9852ad7ab26@seantek.com>
Date: Wed, 14 Aug 2019 09:07:57 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Sent-To: <Y2JvckBpZXRmLm9yZw==>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/4-2n7MAqBxfcyBHjxmQkNWBRDZQ>
Subject: [Cbor] Draft text for pull request for tag range IANA allocation policy
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2019 16:08:47 -0000

Was thread with Subject: "[Cbor] CBOR tag range IANA allocation policy"

Three notes to WG:

#1: Specification Required includes Expert Review. Section 4.6 of RFC 
8126. The only way to get Specification Required *without* Expert Review 
under the RFC 8126 framework is basically to have First Come First 
Served with a mandatory field in the registration template for the 
specification. In contrast, RFC 7049 provides a registration template 
where the specification reference is optional.

#2: CBOR implementations need to be able to handle 64-bit tags, although 
they do not need to perform any mathematical operations on them.

#3: The term "generically useful" is from Thiago's 


9.2.  Tags Registry

    IANA has created the "Concise Binary Object Representation (CBOR)
    Tags" registry at [IANA.cbor-tags].  The tags that were defined in
    [RFC7049] are described in detail in Section 3.4, but other tags have
    already been defined.

    New entries in the range 0 to 23 are assigned by Standards Action.
    New entries in the range 24 to 255 are assigned by RFC Required.
    New entries in the range 256 to 4095 are assigned by Specification 
    with an additional consideration that tags in this range
    be considered "generically useful".
    New entries in the range 4096 to 32767 are assigned by Expert Review.
    New entries in the range 32768 to 18446744073709551615 are
    assigned by First Come First Served.

Designers developing or experimenting with tags privately are encouraged 
to use the range 9223372036854775808-18446744073709551615 by picking a 
random tag or block of tags in that range. However, there is no formal 
reservation of that range for any particular purpose, and a tag MAY be 
assigned there at any time consistent with the above policy.

The template for registration requests is:

    o  Data item
    o  Semantics (short form)
    o  (Optional) References to published specifications that describe
        the syntax or semantics of the data item. The references do not
        need to mention CBOR or this tag registration.

    In addition, First Come First Served requests should include:

    o  Point of contact

    o (Optional) Description of semantics (URI) - The
       URI can point to something like an Internet-Draft or a web page.