Re: [Cbor] Status of CBOR CRS Specification

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 03 March 2023 12:53 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 B2AC7C14CF1E for <cbor@ietfa.amsl.com>; Fri, 3 Mar 2023 04:53:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 aeXE6ok0CBIy for <cbor@ietfa.amsl.com>; Fri, 3 Mar 2023 04:53:15 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 D7F91C14F749 for <cbor@ietf.org>; Fri, 3 Mar 2023 04:53:14 -0800 (PST)
Received: from dyas.sandelman.ca (unknown [77.241.232.19]) by relay.sandelman.ca (Postfix) with ESMTPS id A67291F455; Fri, 3 Mar 2023 12:53:11 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id A846FA0131; Fri, 3 Mar 2023 07:53:10 -0500 (EST)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id A53B2A0130; Fri, 3 Mar 2023 13:53:10 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Chris Lemmons <alficles@gmail.com>, cbor@ietf.org
In-reply-to: <CAJEGKNtpnxr14yn0gcta+7uia4KW=8KdJUs9z7ykUhghv7fwpg@mail.gmail.com>
References: <CAJEGKNtpnxr14yn0gcta+7uia4KW=8KdJUs9z7ykUhghv7fwpg@mail.gmail.com>
Comments: In-reply-to Chris Lemmons <alficles@gmail.com> message dated "Thu, 02 Mar 2023 14:14:29 -0700."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 03 Mar 2023 13:53:10 +0100
Message-ID: <1797252.1677847990@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Au-UyQTqG9bDT7awsqGkEgFDywM>
Subject: Re: [Cbor] Status of CBOR CRS Specification
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 12:53:18 -0000

Chris Lemmons <alficles@gmail.com> wrote:
    > This leaves me with two options: define a new tag fit for precisely the
    > purpose I need, or see if there's interest in finishing the work that
    > was started with Tag 104. It does seem like having two tags, especially
    > with one in the low-numbered space, is not ideal.

    > The draft is here:
    > https://datatracker.ietf.org/doc/draft-clarke-cbor-crs/

    > For context, I need a CRS tag that can "wrap" other content to describe
    > the CRS for that which it encloses. I can define it as necessary, but
    > reuse is usually better. Is there any interest in picking up the work
    > of Tag 104? Is this even an appropriate venue for that?

I think that CBOR is the right place for this.
Try reaching out to the author, T.Clarke @ Ball.  If he doesn't have time to
pursue this document and make you a co-author, then we have the XML for it,
and could just take it over.  Once adopted, document authors serve at the
pleasure of the wg chairs, so changing authors isn't a problem.
(just have to give credit where it is due)

It's possible to do new tags in ~1 year as evidenced by RFC9164 and 9277.
(Actually, I think they could have happened even faster)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-