Re: [Cbor] Chair review of cbor-file-magic 08

Carsten Bormann <cabo@tzi.org> Wed, 09 March 2022 15:56 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 022823A07AC for <cbor@ietfa.amsl.com>; Wed, 9 Mar 2022 07:56:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 gfT6tOKPilFr for <cbor@ietfa.amsl.com>; Wed, 9 Mar 2022 07:56:32 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7C543A0BED for <cbor@ietf.org>; Wed, 9 Mar 2022 07:56:32 -0800 (PST)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4KDGyk3l1XzDCd9; Wed, 9 Mar 2022 16:56:30 +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: <YijLmFCAhTRvrsZC@hephaistos.amsuess.com>
Date: Wed, 9 Mar 2022 16:56:30 +0100
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, cbor@ietf.org
X-Mao-Original-Outgoing-Id: 668534189.933118-3b5623b1641c2b773f4cab09a9b7375f
Content-Transfer-Encoding: quoted-printable
Message-Id: <16A12125-6AE2-4117-8F4D-A7B7358379E3@tzi.org>
References: <YijLmFCAhTRvrsZC@hephaistos.amsuess.com>
To: =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/kVucGSXEcF5UsMof729M2cawxEc>
Subject: Re: [Cbor] Chair review of cbor-file-magic 08
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, 09 Mar 2022 15:56:38 -0000

> 
> Speaking of the registry: The shepherd writeup form makes a point of
> asking that the used registry be identified, and 'Concise Binary Object
> Representation (CBOR) Tags' doe snot show up once in the IANA
> considerations. (It talks of 'registering CBOR tags', which is obvious
> to us with the context, but not necessarily to an editor who does not
> have all the lists indexed by abbreviations).

Yes, I normally do a full reference to a registry (and have one to IANA.core-parameters); no idea why this isn’t in here.

The full kramdown-rfc liturgy:

Registry {{cbor-tags (CBOR Tags)<IANA.cbor-tags}} of {{!IANA.cbor-tags}}

(I need to invent special syntax for that…)

The registry (sometimes called subregistry (*)) is actually called “CBOR Tags”, btw.; but the web page that combines the registries (sometimes called registry) is called “Concise Binary Object Representation (CBOR) Tags”.

https://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml#cbor-tags

Grüße, Carsten

(*) No, I don’t know why RFC 8126 didn’t nail down one consistent terminology here.