Re: [Cbor] Request for CBOR typeof Tag 15 Registration
Carsten Bormann <cabo@tzi.org> Wed, 29 November 2023 01:43 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 33BC4C1516F8 for <cbor@ietfa.amsl.com>; Tue, 28 Nov 2023 17:43:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 oe1OPEs9CjV0 for <cbor@ietfa.amsl.com>; Tue, 28 Nov 2023 17:43:07 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (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 E27F5C151548 for <cbor@ietf.org>; Tue, 28 Nov 2023 17:43:06 -0800 (PST)
Received: from smtpclient.apple (eduroam-pool10-067.wlan.uni-bremen.de [134.102.90.66]) (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 4Sg2CC3yCyzDCdZ; Wed, 29 Nov 2023 02:43:03 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAJ3m2hDScQrroq9fcOzUpFvA2x78JGWovnZ+hFhZi9CLyg8+eg@mail.gmail.com>
Date: Wed, 29 Nov 2023 02:42:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <98909582-2A20-443C-A219-C205BDC9BE08@tzi.org>
References: <CAJ3m2hDScQrroq9fcOzUpFvA2x78JGWovnZ+hFhZi9CLyg8+eg@mail.gmail.com>
To: cbor@ietf.org
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/gjpWqAJSTuC8tyWdeu5yORXdr4E>
Subject: Re: [Cbor] Request for CBOR typeof Tag 15 Registration
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: Wed, 29 Nov 2023 01:43:15 -0000
Since there already was an off-list discussion, let me try to summarize that:
* I pointed to RFC 8949 (and more generally, RFC 8126) as a source of information about the actual registration process for a tag. (The 1+0 space is under “Standards Action” policy.)
* I mentioned that in any case a high bar would need to be met to allocate one of the 11 remaining 1+0 code points.
(Not only will there need to be a sizable constituency, but also the actual gains from using one of these code points will need to be relevant to the application.
Generally, data descriptions/schemas are not sent around in bulk on constrained environments.)
* When I was pointing out that we already have a data description mechanism in CDDL (RFC 8610), the author said that this took the form of a text string and not a structured tree and thus is harder to process.
I pointed to [1] as an example for how CDDL in a tree can look like (and is being used between tools today) — maybe we want to write this up more formally to make a tree form of CDDL more attractive for interchange.
Grüße, Carsten
[1]: https://www.ietf.org/archive/id/draft-bormann-cbor-cddl-freezer-12.html#name-alternative-representations
> On Nov 29, 2023, at 00:30, 严清 <txr1883@gmail.com> wrote:
>
> Hi,
>
> I am developing some libraries and products using CBOR. I am writing to kindly request the registration of CBOR "typeof" Tag, 15.
>
> Tag 15 describes the type of the data item, used to express CBOR data structures (also known as CBOR Schema) in CBOR.
>
> ```
> Tag: 15
> Data item: any
> Semantics: Describes the type of the data item
> Point of contact: Yan Qing <txr1883@gmail.com>
> Description of semantics: https://github.com/cbor-schema/cbor-typeof-tag
> ```
>
> Because the "typeof" primitive is so basic and important, I hope that the IANA can reserve the numbers in the 1+0 range for the "typeof" primitive, such as 15.
>
> Thank you very much for considering our application. We sincerely appreciate your time and attention towards advancing interoperability within the CBOR community through proper tag registrations.
>
> Yan Qing
> txr1883@gmail.com
>
> --
> LDC Labs
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor