IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 17 December 2021 21:48 UTC

Return-Path: <mcr@sandelman.ca>
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 318153A08C1; Fri, 17 Dec 2021 13:48:17 -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 iOT7crWlb15I; Fri, 17 Dec 2021 13:48:12 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03BF33A08FA; Fri, 17 Dec 2021 13:46:54 -0800 (PST)
Received: from dooku.sandelman.ca (desktop4.sandelman.ca [209.87.249.16]) by relay.sandelman.ca (Postfix) with ESMTPS id 3185B1F479; Fri, 17 Dec 2021 21:46:52 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 2471C1A0232; Fri, 17 Dec 2021 16:46:51 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "rats\@ietf.org" <rats@ietf.org>, Laurence Lundblade <lgl@island-resort.com>, cose@ietf.org
cc: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
In-reply-to: <366755AA-727A-4319-863B-687FFADEED93@island-resort.com>
References: <DBBPR08MB5915F7205E4289169047704AFA769@DBBPR08MB5915.eurprd08.prod.outlook.com> <366755AA-727A-4319-863B-687FFADEED93@island-resort.com>
Comments: In-reply-to Laurence Lundblade <lgl@island-resort.com> message dated "Thu, 16 Dec 2021 14:43:57 -0800."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Fri, 17 Dec 2021 16:46:51 -0500
Message-ID: <74372.1639777611@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/9XWnttrEjhSpsXZVyue7or_O8oo>
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:48:17 -0000

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.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.8.7 | Report a Bug | By Email