Re: [Cbor] Concise Binary Object Representation Maintenance and Extensions (cbor) WG Virtual Meeting: 2022-01-12

Carsten Bormann <cabo@tzi.org> Wed, 12 January 2022 14:41 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 9B8143A1055 for <cbor@ietfa.amsl.com>; Wed, 12 Jan 2022 06:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-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 RORqLFp5iNVs for <cbor@ietfa.amsl.com>; Wed, 12 Jan 2022 06:41:14 -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 7CC6F3A1057 for <cbor@ietf.org>; Wed, 12 Jan 2022 06:41:14 -0800 (PST)
Received: from [192.168.217.118] (p5089a436.dip0.t-ipconnect.de [80.137.164.54]) (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 4JYqxh0fNRzDCbr; Wed, 12 Jan 2022 15:41:12 +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: <F9C04692-8453-4017-BF16-4A1C7593CD29@tzi.org>
Date: Wed, 12 Jan 2022 15:41:11 +0100
X-Mao-Original-Outgoing-Id: 663691271.684298-ac1b81e7a7f53ecd72500714d4f5a060
Content-Transfer-Encoding: quoted-printable
Message-Id: <49640167-89E1-42F5-BF6C-90026042841E@tzi.org>
References: <163707704647.12273.10546338474691368537@ietfa.amsl.com> <F9C04692-8453-4017-BF16-4A1C7593CD29@tzi.org>
To: cbor@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/xWOey7MLrdc7awQE_LWcWT5Mwj8>
Subject: Re: [Cbor] Concise Binary Object Representation Maintenance and Extensions (cbor) WG Virtual Meeting: 2022-01-12
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, 12 Jan 2022 14:41:19 -0000

On 2022-01-11, at 18:28, Carsten Bormann <cabo@tzi.org> wrote:
> 
> The 800-pound gorilla right now is the description of data than can go both into JSON and into CBOR.  Of course that whole set of issues can be avoided by using CBOR only, but sometimes people are stubborn and want both.  RFC 9165 has one proposal:

Zoologists have alerted me that I was talking about an elephant in the room, and those are > 800 lb.

Anyway:  For a worked example of how this could look like in action, please see:

https://www.ietf.org/archive/id/draft-ietf-rats-uccs-02.html#name-cddl

Grüße, Carsten