Re: [COSE] x5chain & co. + COSE_Key
Benjamin Kaduk <kaduk@mit.edu> Sat, 17 July 2021 17:05 UTC
Return-Path: <kaduk@mit.edu>
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 6340A3A1860 for <cose@ietfa.amsl.com>; Sat, 17 Jul 2021 10:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 9EyFMg7d-Uu9 for <cose@ietfa.amsl.com>; Sat, 17 Jul 2021 10:04:58 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 7B8533A1861 for <cose@ietf.org>; Sat, 17 Jul 2021 10:04:58 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 16HH4lCo019094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 17 Jul 2021 13:04:52 -0400
Date: Sat, 17 Jul 2021 10:04:47 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Thomas Fossati <Thomas.Fossati@arm.com>
Cc: "cose@ietf.org" <cose@ietf.org>
Message-ID: <20210717170447.GD74365@kduck.mit.edu>
References: <EAB7959F-F7F7-4BB8-AFC7-6FB42D742E34@arm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <EAB7959F-F7F7-4BB8-AFC7-6FB42D742E34@arm.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/nBEl6Vlz0717aVGCzinPn2xD3KY>
Subject: Re: [COSE] x5chain & co. + COSE_Key
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: Sat, 17 Jul 2021 17:05:01 -0000
On Mon, Jun 21, 2021 at 12:46:08PM +0000, Thomas Fossati wrote: > Hi all, > > Reading draft-ietf-cose-x509 I understand x5chain & co are only found in > COSE_Signature, COSE_Sign1 and COSE_recipient objects. > > Is there any reason not to allow them in COSE_Keys - similar to JWK (*)? There is a reason to not modify draft-ietf-cose-x509 to specify this behavior, namely that that draft is overdue for publication and has external consumers waiting on it. Offhand, I'm not sure that there's a generic reason why this information would not be appropriate in a COSE_Key. You should probably write up a draft to talk about doing it and why it's useful, which would hopefully then elicit feedback about it. -Ben
- [COSE] x5chain & co. + COSE_Key Thomas Fossati
- Re: [COSE] x5chain & co. + COSE_Key Benjamin Kaduk