Re: [Cbor] [Cacao] Public Comment for CACAO Draft

Carsten Bormann <cabo@tzi.org> Tue, 15 December 2020 23:44 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 526113A08D9; Tue, 15 Dec 2020 15:44:50 -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_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 T-E7OBre1lSL; Tue, 15 Dec 2020 15:44:47 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24A4B3A08D6; Tue, 15 Dec 2020 15:44:46 -0800 (PST)
Received: from [192.168.217.118] (p548dca87.dip0.t-ipconnect.de [84.141.202.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4CwZcF0ZShzyWc; Wed, 16 Dec 2020 00:44:45 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAF5ktP1OVzX9oF8LQcEeU2DuBoTmAzicuLg_tNbT3Rjoj_oP7g@mail.gmail.com>
Date: Wed, 16 Dec 2020 00:44:44 +0100
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, cacao <cacao@ietf.org>, Bret Jordan <jordan.ietf@gmail.com>, fdt@ietf.org, cbor@ietf.org
X-Mao-Original-Outgoing-Id: 629768684.647931-8efd37c50387e50e7ca509144aa04431
Content-Transfer-Encoding: quoted-printable
Message-Id: <D82B98D5-AA74-41BE-84FA-89EAA392BDA9@tzi.org>
References: <F72C1EB3-CFC6-4E4D-AB5E-1AB2A83B7311@gmail.com> <1493.1601060690@localhost> <6DCC3CC5-3906-47E4-8186-C419518B0951@tzi.org> <CAF5ktP1OVzX9oF8LQcEeU2DuBoTmAzicuLg_tNbT3Rjoj_oP7g@mail.gmail.com>
To: Bret Jordan <bret.jordan=40broadcom.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/5tFLv2L57AvgF7TlSoe8pc3t72o>
Subject: Re: [Cbor] [Cacao] Public Comment for CACAO Draft
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: Tue, 15 Dec 2020 23:44:50 -0000

Hi Bret,

On 2020-12-15, at 21:38, Bret Jordan <bret.jordan=40broadcom.com@dmarc.ietf.org> wrote:
> 
> Or can we get a working group for this kind of work.

I would consider a document that defines vocabulary like this to be a good component for CDDL, which the CBOR WG already is chartered to evolve.  A bit like a modern version of the good parts of part 2 of WSD [1], which is probably still the best document of that kind that we have.

(Clearly, I’m not suggesting that CACAO wait for this to spring up, I just see the CACAO document as another item to look at that motivates finally doing this.)

Grüße, Carsten

[1]: https://www.w3.org/TR/xmlschema-2/

(Oh, and the difference between a 54-bit two's-complement signed integer and an I-JSON integer is that the former includes an INT54_MIN of -2**53, while the latter doesn’t (*), which you correctly copied from I-JSON — int54 may be vernacular for the latter, but this is off-by-one.  This little factoid is pretty much inconsequential (**) for CACAO, but a document like the above would get this detail right.)

(*) because it actually does include both +0 and -0.
(**) INT54_MIN *can* be represented in the typical JSON implementation number systems that I-JSON was accommodating, as can be 2**53 — it’s just no longer uniquely distinguishable from INT54_MIN-1 or 2**53+1.  So this little mistake is even more innocuous.