Re: [Cbor] CBOR tag IANA registration request

Carsten Bormann <cabo@tzi.org> Fri, 03 March 2023 07:36 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 1D45DC14CEFE for <cbor@ietfa.amsl.com>; Thu, 2 Mar 2023 23:36:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.186
X-Spam-Level:
X-Spam-Status: No, score=-4.186 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QDmtacOGQ7C6 for <cbor@ietfa.amsl.com>; Thu, 2 Mar 2023 23:36:21 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06DC0C14CEE3 for <cbor@ietf.org>; Thu, 2 Mar 2023 23:36:19 -0800 (PST)
Received: from [192.168.217.124] (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4PSfsr5V6vzDCbK; Fri, 3 Mar 2023 08:36:16 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <d981a8cb-ef14-72ee-8daf-b7dea9644231@gmail.com>
Date: Fri, 03 Mar 2023 08:36:16 +0100
Cc: Christian Amsüss <christian@amsuess.com>, cbor@ietf.org
X-Mao-Original-Outgoing-Id: 699521776.303013-6a04932e51443234e21669308efe7251
Content-Transfer-Encoding: quoted-printable
Message-Id: <ACBD0387-EBCD-4345-96EF-9BF08CF28949@tzi.org>
References: <9a7befb3-8410-78f7-f7fc-6aeee90100b6@gmail.com> <21bb85c3-cd05-2ba2-205b-df9ec061346d@gmail.com> <8A5C7DB9-3E76-43BB-8195-0B9211670755@tzi.org> <d981a8cb-ef14-72ee-8daf-b7dea9644231@gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/1vIrFhY0zdsNN49SsfAAkCVmHho>
Subject: Re: [Cbor] CBOR tag IANA registration request
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 03 Mar 2023 07:36:27 -0000

Hi Anders,

> On 2023-03-03, at 08:24, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
> 
> On 2023-03-03 7:32, Carsten Bormann wrote:
>> On 3. Mar 2023, at 03:46, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
>>> 
>>> Would it be possible to process this request?
>> Sure.
> 
> Good, when could that happen?

Once you fill in the form at https://www.iana.org/form/protocol-assignment

>> The specification would be improved if it could make up its mind whether the id is an object identifier or a type identifier.
>> (Both can be useful.)
> 
> Just for my information, is this the difference you refer to?
> 
> Object ID: Object instance ID, unrelated to the type/structure of the CBOR data item.
> 
> Object Type: Identifier associatd with the actual definition/structure of the object (CBOR data item).
> 
> Although both are useful, the intention was making COTX holding Object Type. Instance IDs are usually a part of the object (CBOR data item) itself.

Good.  I was somewhat expecting that, but the text oscillates between “type identifier” and “object identifier”; maybe you should bring this in line by consistently using “object type identifier” or some such.

Oh, and I would be excited if in the IANA Considerations table you could specify the type as

array [id: text, obj: any]

(This should be readable even if you don’t know CDDL.)

Grüße, Carsten