Re: [Cbor] Status of CBOR CRS Specification

Carsten Bormann <cabo@tzi.org> Fri, 03 March 2023 13:09 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 03A60C14CE44 for <cbor@ietfa.amsl.com>; Fri, 3 Mar 2023 05:09:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.886
X-Spam-Level:
X-Spam-Status: No, score=-6.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 AaQMzbVaLe4Y for <cbor@ietfa.amsl.com>; Fri, 3 Mar 2023 05:09:23 -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 7A4EFC14CE4B for <cbor@ietf.org>; Fri, 3 Mar 2023 05:09:21 -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 4PSpG732l6zDCfx; Fri, 3 Mar 2023 14:09:19 +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: <1797252.1677847990@dyas>
Date: Fri, 03 Mar 2023 14:09:18 +0100
Cc: Chris Lemmons <alficles@gmail.com>, cbor@ietf.org
X-Mao-Original-Outgoing-Id: 699541758.770238-21a07f856b99f60ca15a893ca935210a
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE76A0CA-C060-412B-85FE-23CFAD3282A1@tzi.org>
References: <CAJEGKNtpnxr14yn0gcta+7uia4KW=8KdJUs9z7ykUhghv7fwpg@mail.gmail.com> <1797252.1677847990@dyas>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/sqP09bN8RfHNdkr248as_57bOHU>
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 13:09:29 -0000


> On 2023-03-03, at 13:53, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> Signed PGP part
> 
> 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)

If it is useful to have an RFC, this is correct; a mere registration can be done much more quickly.

Grüße, Carsten