IETF Logo Mail Archive

Re: [COSE] Key identifier of type bstr / int

Laurence Lundblade <lgl@island-resort.com> Fri, 13 August 2021 01:01 UTC

Return-Path: <lgl@island-resort.com>
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 7497A3A128B for <cose@ietfa.amsl.com>; Thu, 12 Aug 2021 18:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 2eZCV7H4xTAY for <cose@ietfa.amsl.com>; Thu, 12 Aug 2021 18:01:42 -0700 (PDT)
Received: from p3plsmtpa06-08.prod.phx3.secureserver.net (p3plsmtpa06-08.prod.phx3.secureserver.net [173.201.192.109]) (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 1B4CD3A1287 for <cose@ietf.org>; Thu, 12 Aug 2021 18:01:42 -0700 (PDT)
Received: from [172.20.7.246] ([50.125.30.3]) by :SMTPAUTH: with ESMTPSA id ELZtmibiXWMe9ELZtmIsqP; Thu, 12 Aug 2021 18:01:41 -0700
X-CMAE-Analysis: v=2.4 cv=Uoumi88B c=1 sm=1 tr=0 ts=6115c475 a=HDq/oGp5D7QgKInbiSp5pw==:117 a=HDq/oGp5D7QgKInbiSp5pw==:17 a=48vgC7mUAAAA:8 a=gJzD2ls_7so3aXa4DcMA:9 a=QEXdDO2ut3YA:10 a=tTNzG0yJQaIKPBsoLDcA:9 a=vqm2CSZNjNgrqUyy:21 a=_W_S_7VecoQA:10 a=w1C3t2QeGrPiZgrLijVG:22
X-SECURESERVER-ACCT: lgl@island-resort.com
From: Laurence Lundblade <lgl@island-resort.com>
Message-Id: <823C00C2-4F6C-4DF5-99B0-87D8524D4A9C@island-resort.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9D0334B4-2F79-4591-A85A-6CAE58F54778"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Thu, 12 Aug 2021 18:01:41 -0700
In-Reply-To: <EDFDB6E4-2BDE-4E2E-9CF0-D771E2DEF3C6@ericsson.com>
Cc: "cose@ietf.org" <cose@ietf.org>
To: Göran Selander <goran.selander=40ericsson.com@dmarc.ietf.org>
References: <95B75634-B147-4756-A950-C6B139CF3ADD@ericsson.com> <9DF382AC-12A8-47A5-AAE7-2B0D75EAA669@island-resort.com> <EDFDB6E4-2BDE-4E2E-9CF0-D771E2DEF3C6@ericsson.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-CMAE-Envelope: MS4xfOcyLOqI2XHhO4m8aG2xYW9Iqbje1N3IeaDwvzsIBJrqQ0nAgb3iTAvqEQTOydicbr4egvJdNfy/CT0X6jOl+DLIqY7MhOMUBeCi4IIh1+ShuR9+Ch7v fPHSNLyZtJftLxblK8JAxUN8QXbGpLifb59S1UPIgZO2hnw4DhZoMhdmFZhqsx4Vsd3NJX7Sxl4EUZ+geDRTtYe2nsrCx+2Z6ra5GBBR3BFCFTuCY54Y9g4P y0h3pm2n+MoymHwcGp5FcQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/p-7mUCX7uXWVGs_STOv1mgTKgyQ>
Subject: Re: [COSE] Key identifier of type bstr / int
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, 13 Aug 2021 01:01:48 -0000

Understood about the use case. Thx for the background.

> On Aug 10, 2021, at 3:13 AM, Göran Selander <goran.selander=40ericsson.com@dmarc.ietf.org> wrote:
> 
> Assume that we do want to allow key identifiers to be CBOR ints in certain settings,  what is the best (least intrusive) way to allow this while still maintain compatibility with 'kid's supporting the type bstr? Another alternative to what has been listed below is to define 'kid2' to only be of type int - is that a better option?

I didn’t write actual code to check, but they about the same to me.

‘kid' as int/bstr seems less confusing to me than ‘kid2’. It tells you it does exactly the same thing whether it is an int or a bstr.

So my pick is ‘kid’, but ‘kid2’ is OK too.

LL

v2.23.0 | Report a Bug | By Email