IETF Logo Mail Archive

Re: [Cbor] [COSE] CDDL for COSE + EAT/CWT + SUIT + CoSIWD

Carsten Bormann <cabo@tzi.org> Wed, 15 December 2021 21:57 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 E876F3A0770; Wed, 15 Dec 2021 13:57:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 hfuzVjkmNT5l; Wed, 15 Dec 2021 13:57:21 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 59B923A076C; Wed, 15 Dec 2021 13:57:21 -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 4JDpxn3VMgzDCbR; Wed, 15 Dec 2021 22:57:17 +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: <792A0E49-9C4A-4817-BF0A-2B76EBE6EDED@island-resort.com>
Date: Wed, 15 Dec 2021 22:57:17 +0100
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "cbor@ietf.org" <cbor@ietf.org>, cose <cose@ietf.org>
X-Mao-Original-Outgoing-Id: 661298236.994526-0c1a1ec93f4425104d06097ca8455e6d
Content-Transfer-Encoding: quoted-printable
Message-Id: <E0A27ABE-DE65-4C4A-A204-19F8C85F85E6@tzi.org>
References: <85278E84-AD34-4F68-94DC-437BABCCD621@island-resort.com> <DBBPR08MB591541267172A49382892483FA6F9@DBBPR08MB5915.eurprd08.prod.outlook.com> <75C33F50-0C92-47B9-80DB-050499F51630@tzi.org> <DBBPR08MB5915DCAD539AD2CA4770515BFA6F9@DBBPR08MB5915.eurprd08.prod.outlook.com> <27539CB9-42E7-4313-8786-58B0A504E7E2@island-resort.com> <9912.1639076050@localhost> <792A0E49-9C4A-4817-BF0A-2B76EBE6EDED@island-resort.com>
To: Laurence Lundblade <lgl@island-resort.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/k2kD-hwamDuJJu0pPoPbMsJAOg4>
Subject: Re: [Cbor] [COSE] CDDL for COSE + EAT/CWT + SUIT + CoSIWD
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, 15 Dec 2021 21:57:26 -0000

Hi Laurence,

I hope that the CBOR WG takes good note of these observations:

> On 2021-12-15, at 22:28, Laurence Lundblade <lgl@island-resort.com> wrote:
> 
> - CDDL seems just fine for protocol messages
> - CDDL is missing some pieces when combining CDDL-defined protocols (name spaces, a publication and reference mechanism)

Right, and that is what the 2.0 work is trying to address (at least partially).
Workarounds do exist.

> - CDDL is missing some pieces for specifying encryption payloads and maybe draft-ietf-cose-rfc8152bis-struct is not using what is available now for signing/MAC

Indeed.  Some of this could be added easily by defining control operators in drafts that need extended functionality for CDDL.  Some of this is just conventional usage that simply needs to be worked out.  I’m sure the CBOR WG is interested in doing just that, and the COSE WG should be interested, too (with the caveat that this must not slow down current publication processes).

A separate document that describes how to best use CDDL with COSE would be optimal, but simply defining the CDDL conventions needed inside a spec that uses CDDL also works.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email