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

Hannes Tschofenig <Hannes.Tschofenig@arm.com> Wed, 08 December 2021 14:46 UTC

Return-Path: <Hannes.Tschofenig@arm.com>
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 845143A09D5; Wed, 8 Dec 2021 06:46:04 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=2h+qEbLL; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=2h+qEbLL
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 raf1HJuADhoY; Wed, 8 Dec 2021 06:45:59 -0800 (PST)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80048.outbound.protection.outlook.com [40.107.8.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCDB03A09A3; Wed, 8 Dec 2021 06:45:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bKwUq8/R5Td/L2AzbrNkopl+RET1idTHGeXPbHjNy7k=; b=2h+qEbLLnXFNRrN1XZqmT2b+cDz6F6kwiENpRqZ/ZOazNen1mLZDcMnIzEmlqIUVTGsZP+lVCoP1PGPfHEsBHbGkxc3RchuM8c6DoBCmxHSIDapdZXF4mwdjd7fTAeSPBc1Sll/oSZwswEHzuVDQI48zErxYDXc7tHikUmnH+SY=
Received: from DU2PR04CA0244.eurprd04.prod.outlook.com (2603:10a6:10:28e::9) by AS8PR08MB6184.eurprd08.prod.outlook.com (2603:10a6:20b:29c::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4755.16; Wed, 8 Dec 2021 14:45:54 +0000
Received: from DB5EUR03FT010.eop-EUR03.prod.protection.outlook.com (2603:10a6:10:28e:cafe::38) by DU2PR04CA0244.outlook.office365.com (2603:10a6:10:28e::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4755.16 via Frontend Transport; Wed, 8 Dec 2021 14:45:54 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by DB5EUR03FT010.mail.protection.outlook.com (10.152.20.96) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4755.13 via Frontend Transport; Wed, 8 Dec 2021 14:45:54 +0000
Received: ("Tessian outbound dbb52aec1fa6:v110"); Wed, 08 Dec 2021 14:45:54 +0000
X-CR-MTA-TID: 64aa7808
Received: from c255b6dedce4.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id E52F3F17-F551-4B7A-B12A-A11114C4455C.1; Wed, 08 Dec 2021 14:45:48 +0000
Received: from EUR03-AM5-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id c255b6dedce4.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Wed, 08 Dec 2021 14:45:48 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=B39P7WJkeboBrL6htu20SLINdeWtM86WlkwocZwCYopKS8bwg/f/Bay8T+nF+HURPGZr+b4RLjAYmu9w+HmS97wqo+waUpfcyICuc54zYE9Ig//HzROGapzQ0yA3I9CtH9UZtGkPwsIRR93PlTKBvJ8vZs5dpqtEuwfySrHfwTWyWl79Y9RaI1a3Uy0E1vTUJpUEnUfYxGpJGy6OfRDsboWDA8TnEOkfI2UwVcLy3DruetFeo6i7wXimuMYyDsUI7LWte9794JMRHN0zDStHBNgx0+3MrsBGipfk6SEi767YWVG1f03Tyiaez/VVc7X+4AM7TpT8UzDEF5eGZ16EdQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=bKwUq8/R5Td/L2AzbrNkopl+RET1idTHGeXPbHjNy7k=; b=KmJXUrUY4HnDQvej98SLWYmTRBVDn4QmsCM64iwNii9B9YBZwvMBDhl/s4lNn1sqGBQZiWaI14W+kLNXWSPBzf7Lf4+4dxOCPic9V3FXDFi/GIrJMGzHa6PThubV0BxUKyrx/2Lv/k+/xfatFV1sth79XRNfqmE+PzPAYBN9RCQV0ecg5hqtv10XralOASphwEPNCq8DY1a3cr7+fV08Ci6+cqguG7BujoT6DpgaQmpmzdqQ3PuzNIvMkZ1qvDJd/EDAc5z1LIN9d76O/V09l7XYWZYin5vIcuyv8gWEpyDPzmRNXKd7tR2G0+PJhgAoKd1K6Fc0xdTr9V1YlSW54w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bKwUq8/R5Td/L2AzbrNkopl+RET1idTHGeXPbHjNy7k=; b=2h+qEbLLnXFNRrN1XZqmT2b+cDz6F6kwiENpRqZ/ZOazNen1mLZDcMnIzEmlqIUVTGsZP+lVCoP1PGPfHEsBHbGkxc3RchuM8c6DoBCmxHSIDapdZXF4mwdjd7fTAeSPBc1Sll/oSZwswEHzuVDQI48zErxYDXc7tHikUmnH+SY=
Received: from DBBPR08MB5915.eurprd08.prod.outlook.com (2603:10a6:10:20d::17) by DB8PR08MB5290.eurprd08.prod.outlook.com (2603:10a6:10:a5::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4755.20; Wed, 8 Dec 2021 14:45:46 +0000
Received: from DBBPR08MB5915.eurprd08.prod.outlook.com ([fe80::dd96:eb7:b263:b290]) by DBBPR08MB5915.eurprd08.prod.outlook.com ([fe80::dd96:eb7:b263:b290%4]) with mapi id 15.20.4755.022; Wed, 8 Dec 2021 14:45:46 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Laurence Lundblade <lgl@island-resort.com>
CC: Carsten Bormann <cabo@tzi.org>, cose <cose@ietf.org>, "cbor@ietf.org" <cbor@ietf.org>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Thread-Topic: [Cbor] CDDL for COSE + EAT/CWT + SUIT + CoSIWD
Thread-Index: AQHX67gvNbcS2jfqyUOwtKjobSbIKKwohLpQgAAEVwCAAAJZAIAAHY8AgAAA9dA=
Date: Wed, 08 Dec 2021 14:45:46 +0000
Message-ID: <DBBPR08MB59152F25FC0FC6C23E650F66FA6F9@DBBPR08MB5915.eurprd08.prod.outlook.com>
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>
In-Reply-To: <27539CB9-42E7-4313-8786-58B0A504E7E2@island-resort.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ts-tracking-id: 0924C27BC197D64F8FFBC9E5BB30D3A1.0
x-checkrecipientchecked: true
Authentication-Results-Original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
X-MS-Office365-Filtering-Correlation-Id: c37b42ac-6f5b-4e18-b666-08d9ba59700b
x-ms-traffictypediagnostic: DB8PR08MB5290:EE_|DB5EUR03FT010:EE_|AS8PR08MB6184:EE_
X-Microsoft-Antispam-PRVS: <AS8PR08MB61842C060C47A025224EE7A8FA6F9@AS8PR08MB6184.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:8882;OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: d4DDA80gPPvMhiNh9ZB+Ml94O7pXaskSk5AFGYFuj/Y7pNvPN2V0CwpRg18WKUPS64gflSjhsVhjA61HZzknf+ah9YR3w1inun/Iio9A0Q35kqQHvhR866b1UhN59uZrnZtgFyEMaT28MvkZoUcPjIffvVlwesvTmidcycYauadEt3IIh9byi8lR58aEHAVMNPmU9s5tnF6aDy80bW0qhuiidMWH5NXjJquAUoe37KBd1HaETxlWSilEaWl4lj24L3bw0plssEs/TgiO64PiCK5bVzAYYRaS8o4mfOeONtbdMYF1PoaFLzxr0rz+5j8X+N3+OOj0sqleVhIxR7QaKCzjGFOMbbL/H9p7M5Iu5BVlqGV7Dtpp7hA0GUlFdr/dtX0cvbxGM3JmLAyqE5pxl/LHkoCf99zSdaPeHGkm1GcslHGwKlWVbfqzFgKPcyqF84vMVujCJGJBcBLCOt+sbF5n2a59L6upz0KwAK5tqfor3NdDpqx6C482FUeuOwb5NIqbUCPjqBiOLiTUMWx1jrvxrqXf4mxj43tGTMcQIfgzJBIs5Gr2zGwHM8cdBI+6aD/0nkftFwR+zEuwJupxAMdWOB+VitWTNOeiGfRDURQNz6uvdB+Yw9khg2qgDe3lD8o2ywpWjbEkI0TVRXcB+EoHUvSupuz42fRDy21PXMo3+th+TIb1K6/ZiP3QqGzF0cQw4ksAEdnzpNhMmzvL8JvttWqFI5sV1kXqTDCHlU5YMeIBgLLh6EupFJPkfu7L//Kwb+sz+y4ySpCRAMw5OQ71a1/s/l77UQhdnyFRs4r9OG4xGJrzVTEIQIjiAhir
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DBBPR08MB5915.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(9686003)(55016003)(53546011)(54906003)(26005)(508600001)(38100700002)(122000001)(86362001)(33656002)(66476007)(76116006)(186003)(5660300002)(166002)(71200400001)(38070700005)(83380400001)(6506007)(6916009)(316002)(66556008)(64756008)(2906002)(66446008)(66946007)(4326008)(7696005)(8676002)(9326002)(8936002)(52536014); DIR:OUT; SFP:1101;
Content-Type: multipart/alternative; boundary="_000_DBBPR08MB59152F25FC0FC6C23E650F66FA6F9DBBPR08MB5915eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8PR08MB5290
Original-Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DB5EUR03FT010.eop-EUR03.prod.protection.outlook.com
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id-Prvs: 1775ca5e-ad42-47b3-0bff-08d9ba596b2e
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: KTHl6vZ1Ry0nzXLVl5HO6mIqfWQCZco0w1jSzWO7LiooRBaiubElVCgUJ9/RYDH1T5dxOrbo0hdSO5C0TKJd3flz3++85LJRu+sPThQ8Xy+PrvhUaSGfGM5cdDJgpYtPUel7roFgORNUxxC7wm353uq3isDKBEl0Opbtn8I0L4CKR9oU8gc6UxJfKVBCjSbLpEaVyI4gsCv7F4D7HUEMuISU93p8Oh3vt0HL6zOslAcYCIEgJWtWZyC1Ivg0HbVhHnWJl2S1WX/YLecpiPAJhlT1NHgzRIv3AKGrf+u/IjsrsjB2o97xwjkW+mUfVAiZp+odv5yzWoRVoLEFbLo8ZFVnbW9ptKFqHjLbpzlzpbf3Qx3TXb7u+D0uC1vGI5pSBipu4Vzlj3k28OreQOE202ccJfUM/qKNHicOu4o2ood5IQygWem+DxOo1KpZ3IJtwQyrLjId5lpD5M0MQFtm92ai3csqhCMWBMzFZNV8zkp42caeVyb52rRBF2qlf1Bf178flVjvznqqq7CXKWl4k/o4Y8JjsqTfRyXd8MhQiz18U3c0s1cop1yegstPLLrHY0pgd+5Dyd/ExlTtc6mJla47SggDqhX99BS1mIoTAgjO34sc26Kg1KzWmBrPMeWTakWBkkcRPUSmYKXrC87l99Ueb/Ex3mOHnWIB6yuwrTzh5t5NfKARaZ83a/ntKu0qGgz1/9CqhB9BA35I8XGjgCTYkNq+W0Er4vSx8Jdezj+w25pNVlwtV3QWDXl0i51/ff2VMtmlrSaLoxMD/U4xFVVWjFtMhY6UjxIvhfQ6L9eFVM+ja776AUhseh0x+zhycO1sKT9I8H+kWJ6ILspI2xSXKgmebAmRZkHkCT5h2A9fAjeVxx6/0xd53gE775Cn
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com; PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(36840700001)(46966006)(40470700001)(70586007)(9326002)(336012)(86362001)(55016003)(316002)(70206006)(7696005)(83380400001)(82310400004)(33964004)(356005)(166002)(81166007)(26005)(36860700001)(40460700001)(54906003)(8676002)(4326008)(450100002)(508600001)(5660300002)(9686003)(6506007)(53546011)(52536014)(8936002)(186003)(2906002)(107886003)(6862004)(47076005)(30864003)(33656002); DIR:OUT; SFP:1101;
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Dec 2021 14:45:54.4187 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: c37b42ac-6f5b-4e18-b666-08d9ba59700b
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123]; Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: DB5EUR03FT010.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AS8PR08MB6184
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/YaiPDMK2NZDX3SmdRJCPSRSJtWg>
Subject: Re: [Cbor] 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, 08 Dec 2021 14:46:13 -0000

Hi Laurence,

If you only care about how to use COSE CDDL in your spec then the answer is simple:


  1.  If you are happy with the constructs offered by COSE, then you just use the COSE CDDL constructs.
  2.  If you have to apply additional constraints to the use of COSE primitives, then you have two options:
     *   Describe them in the text of the spec.
     *   Restrict the CDDL (which would correspond to “modifying” the COSE CDDL).

In my experience, if you use anything beyond the most basic COSE primitives then you are in case #2.

In many cases, you are problably going to be interested in authentication/integrity protection (COSE_Sign/COSE_Mac), and encryption. With encryption challenges will arise.


Ciao
Hannes


From: Laurence Lundblade <lgl@island-resort.com>
Sent: Wednesday, December 8, 2021 3:31 PM
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: Carsten Bormann <cabo@tzi.org>; cose <cose@ietf.org>; cbor@ietf.org; Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Subject: Re: [Cbor] CDDL for COSE + EAT/CWT + SUIT + CoSIWD

Hi Hannes,

This is only about a tiny little part of the EAT spec and is not important for EAT publication.

This is only about how to use CDDL with COSE. It’s not about interoperability or what claims there are in the EAT spec.

Hannes, you can probably ignore this thread if you want.


To go further…

I am observing how two different protocols that use COSE specify what the COSE payload should be. I am interested because EAT must specify this too. I noticed that they do it different:
— CoSWID goes to a lot of trouble to use CDDL via a .cbor control
— SUIT just uses simple prose, not CDDL

Note that I am only talking about the CDDL link between COSE and the COSE payload. Clearly SUIT, EAT and CoSWID all of which are COSE payloads are described in CDDL. See details below for what I mean by the link.

I was quite happy with simple prose, but then I saw what CoSWID did. It seemed worth checking in because CoSWID went to a lot of trouble to do what it did.

Right now, I think simple prose is fine and even prefer it.

If I were the CoSWID author I would probably stick with simple prose so the CDDL for COSE doesn’t have to be replicated and to allow for COSE encryption.

If I were the draft-ietf-cose-rfc8152bis-struct author, I’d make an attempt at a CDDL template for COSE so that future standards could do what CoSWID did without replicating COSE CDDL.

If that turned out well, then for future protocols after publication of draft-ietf-cose-rfc8152bis-struct, I’d consider using the CDDL template for COSE messages.

LL


Here’s the link between for COSE payload for CoSWID. It is in blue in this CDDL that is replicated from COSE. It occurs in  section 7 of CoSWID.<https://datatracker.ietf.org/doc/html/draft-ietf-sacm-coswid-19#section-7>


   COSE-Sign1-coswid<payload> = [

       protected: bstr .cbor protected-signed-coswid-header,

       unprotected: unprotected-signed-coswid-header,

       payload: bstr .cbor payload,

       signature: bstr,

   ]


Here it is in prose in SUIT in section 5.2<https://datatracker.ietf.org/doc/html/draft-ietf-suit-manifest-16#section-5.2>:


 These blocks

   are one of:





   *  COSE_Sign_Tagged



   *  COSE_Sign1_Tagged



   *  COSE_Mac_Tagged



   *  COSE_Mac0_Tagged



   Each of these objects is used in detached payload mode.  The payload

   is the bstr-wrapped SUIT_Digest.


Here it is in CWT, section 7.1 in prose<https://datatracker.ietf.org/doc/html/rfc8392#section-7.1>


   1.  Create a CWT Claims Set containing the desired claims.



   2.  Let the Message be the binary representation of the CWT Claims

       Set.



   3.  Create a COSE Header containing the desired set of Header

       Parameters.  The COSE Header MUST be valid per the [RFC8152<https://datatracker.ietf.org/doc/html/rfc8152>]

       specification.



   4.  Depending upon whether the CWT is signed, MACed, or encrypted,

       there are three cases:



       *  If the CWT is signed, create a COSE_Sign/COSE_Sign1 object

          using the Message as the COSE_Sign/COSE_Sign1 Payload; all

          steps specified in [RFC8152<https://datatracker.ietf.org/doc/html/rfc8152>] for creating a COSE_Sign/

          COSE_Sign1 object MUST be followed.


EAT inherits this from CWT so it doesn’t need to say it explicitly.

However EAT uses CDDL so it is a possibility that EAT can do what CoSWID did.



On Dec 8, 2021, at 4:46 AM, Hannes Tschofenig <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>> wrote:

Hi Carsten,

I suspect Laurence is sending this email because of his work on EAT. I am arguing that an attempt to improve the CDDL for the mentioned specs will not lead to any improvement at all because the problem is elsewhere. I am saying that because I have just spent many hours reading the EAT spec.

Ciao
Hannes

-----Original Message-----
From: Carsten Bormann <cabo@tzi.org<mailto:cabo@tzi.org>>
Sent: Wednesday, December 8, 2021 1:37 PM
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>>
Cc: Laurence Lundblade <lgl@island-resort.com<mailto:lgl@island-resort.com>>; cose <cose@ietf.org<mailto:cose@ietf.org>>; cbor@ietf.org<mailto:cbor@ietf.org>; Henk Birkholz <henk.birkholz@sit.fraunhofer.de<mailto:henk.birkholz@sit.fraunhofer.de>>
Subject: Re: [Cbor] CDDL for COSE + EAT/CWT + SUIT + CoSIWD

On 2021-12-08, at 13:30, Hannes Tschofenig <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>> wrote:

EAT by itself is not really an interoperable spec. COSE on its own is not interoperable either.

If I guess about the definition of "interoperable spec” you are using here, ASCII is not an interoperable spec either - you still have to agree on what the text means…  Still, ASCII was kind of useful as the basis for a lot of interoperability, I think.

I think the point here was to shape some CDDL that makes it easier to talk about the way a more specific (interoperable?) spec uses COSE (which does have CDDL, just not in a way that usually can be integrated as-is to express the additional constraints a COSE-using specification typically makes).

Grüße, Carsten

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.