IETF Logo Mail Archive

Re: [COSE] [Rats] Defining CWT, and JWT in UCCS in EAT

Carsten Bormann <cabo@tzi.org> Fri, 17 December 2021 21:58 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: cose@ietfa.amsl.com
Delivered-To: cose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B2B13A08FE; Fri, 17 Dec 2021 13:58:32 -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 uRrF3uGkqjY1; Fri, 17 Dec 2021 13:58:27 -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 8C20C3A083C; Fri, 17 Dec 2021 13:58:27 -0800 (PST)
Received: from smtpclient.apple (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 4JG2t71R22zDCbw; Fri, 17 Dec 2021 22:58:22 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <74372.1639777611@dooku>
Date: Fri, 17 Dec 2021 22:58:19 +0100
Cc: "rats@ietf.org" <rats@ietf.org>, Laurence Lundblade <lgl@island-resort.com>, cose@ietf.org, Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <98B70A96-C17E-4974-9F99-76DA6D020835@tzi.org>
References: <DBBPR08MB5915F7205E4289169047704AFA769@DBBPR08MB5915.eurprd08.prod.outlook.com> <366755AA-727A-4319-863B-687FFADEED93@island-resort.com> <74372.1639777611@dooku>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/qIFGFj5O9i86nAMToviXRhY4DQI>
Subject: Re: [COSE] [Rats] Defining CWT, and JWT in UCCS in EAT
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cose>, <mailto:cose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose/>
List-Post: <mailto:cose@ietf.org>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cose>, <mailto:cose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Dec 2021 21:58:33 -0000

On 17. Dec 2021, at 22:46, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Laurence Lundblade <lgl@island-resort.com> wrote:
>> So the question is: where should the CDDL for a CWT go? Here’s the main options I can think of:
>> - EAT
>> - UCCS
>> - CWTbis (a revision of CWT to include CDDL)
>> - Some other new standard
>> - no where, never create it
> 
> I'd say that it should go into RFC8152bis. (bis-bis. There is another german
> term here).    

??

> It's still in AUTH48 right now.  Maybe an appeal to put it in
> could occur in cose@
> 
> If it too late for that, then in an errata, or another document.

There is no errata.

There is a missing feature — making it easy to interact with the COSE specification via CDDL.
Missing features are addressed in new documents, not in AUTH48.
Certainly not in AUTH48 if there is considerable leeway for designing it and nothing in the original document depends on it.

Grüße, Carsten

v2.8.7 | Report a Bug | By Email