IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Wed, 14 August 2019 16:22 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4106F120A99 for <cbor@ietfa.amsl.com>; Wed, 14 Aug 2019 09:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 rYlG5efYD6HM for <cbor@ietfa.amsl.com>; Wed, 14 Aug 2019 09:22:47 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1379F120AA1 for <cbor@ietf.org>; Wed, 14 Aug 2019 09:22:47 -0700 (PDT)
Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 467vxx58KQzytJ; Wed, 14 Aug 2019 18:22:45 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <12deba80-20ba-cf55-162f-a9852ad7ab26@seantek.com>
Date: Wed, 14 Aug 2019 18:22:45 +0200
Cc: cbor@ietf.org
X-Mao-Original-Outgoing-Id: 587492563.116491-b1cc6c7f5012475ee057d5739f712d7b
Content-Transfer-Encoding: quoted-printable
Message-Id: <261994BA-150C-44FC-95FD-A5C8429B395A@tzi.org>
References: <12deba80-20ba-cf55-162f-a9852ad7ab26@seantek.com>
To: Sean Leonard <dev+ietf@seantek.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/KdY33y0vjnaQ8wvWrWq1Oj3Hfc0>
Subject: Re: [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:22:50 -0000

On Aug 14, 2019, at 18:07, Sean Leonard <dev+ietf@seantek.com> wrote:
> 
>    New entries in the range 24 to 255 are assigned by RFC Required.

Based on previous WG discussions, I think that was a slightly higher hurdle than we wanted here.
Specification required + designated expert considerations that only provide this space for high-value allocations (which needs to be defined better than I just did).

Grüße, Carsten

v2.23.0 | Report a Bug | By Email