Re: [COSE] COSE HPKE Public Key Format Consensus Call

Russ Housley <housley@vigilsec.com> Tue, 27 September 2022 18:01 UTC

Return-Path: <housley@vigilsec.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 F3207C159823 for <cose@ietfa.amsl.com>; Tue, 27 Sep 2022 11:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DqxDO1n1wyIG for <cose@ietfa.amsl.com>; Tue, 27 Sep 2022 11:01:37 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34D06C15AE1A for <cose@ietf.org>; Tue, 27 Sep 2022 11:01:37 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id DB2CF1A31EC; Tue, 27 Sep 2022 14:01:35 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-108-56-234-133.washdc.fios.verizon.net [108.56.234.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id BF8BD1A370E; Tue, 27 Sep 2022 14:01:35 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2CD19F33-7CB7-4BFC-8D02-F2069FE3D4DC"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Tue, 27 Sep 2022 14:01:35 -0400
References: <CO1PR00MB130824EBDD7C1420E9D3065CF54E9@CO1PR00MB1308.namprd00.prod.outlook.com>
To: Mike Jones <Michael.Jones@microsoft.com>, "cose@ietf.org" <cose@ietf.org>
In-Reply-To: <CO1PR00MB130824EBDD7C1420E9D3065CF54E9@CO1PR00MB1308.namprd00.prod.outlook.com>
Message-Id: <D429F1F2-6C44-4B9B-818C-F2811B512DB5@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.21)
X-Scanned-By: mailmunge 3.09 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/qzYaUCkogRSt53A3oCaTe-IwQDI>
Subject: Re: [COSE] COSE HPKE Public Key Format Consensus Call
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 27 Sep 2022 18:01:41 -0000

I think we have caused unnecessary controversy.  I think we should have used a different I-D file name.  We want HPKE-like features but using as much of the existing COSE specifications (including COSE_Key) as possible.

I vote for #1.

Russ

> On Sep 22, 2022, at 1:09 PM, Mike Jones <Michael.Jones=40microsoft.com@dmarc.ietf.org> wrote:
> 
> As discussed at IETF 114, the HPKE draft uses the COSE_Key public key representation.  The authors described that Ilari Liusvaara had proposed using a different public key representation, which is detailed in Slide 2 of https://datatracker.ietf.org/meeting/114/materials/slides-114-cose-cose-hpke-00 <https://datatracker.ietf.org/meeting/114/materials/slides-114-cose-cose-hpke-00>.  As recorded in the minutes <https://datatracker.ietf.org/doc/minutes-114-cose/>, consensus during the meeting appeared to be in favor of continuing to use COSE_Key.
>  
> This note initiates a consensus call by the chairs on the topic of what public key format the COSE HPKE specification will use.  Working group members are requested to express their preferences within two weeks of this note (by Thursday, September 6th) for either:
>  
> 1.  Continuing to use COSE_Key
> 2.  Using the different format proposed by Ilari Liusvaara
> 3.  Other (please describe in sufficient detail to enable its specification)
>  
>                                                        Thank you,
>                                          -- Mike (for the COSE chairs)
>  
> _______________________________________________
> COSE mailing list
> COSE@ietf.org <mailto:COSE@ietf.org>
> https://www.ietf.org/mailman/listinfo/cose <https://www.ietf.org/mailman/listinfo/cose>