IETF Logo Mail Archive

Re: [Suit] draft-ietf-suit-firmware-encryption: HPKE for COSE

Benjamin Kaduk <kaduk@mit.edu> Mon, 16 August 2021 16:44 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: suit@ietfa.amsl.com
Delivered-To: suit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8793A10B3 for <suit@ietfa.amsl.com>; Mon, 16 Aug 2021 09:44:43 -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 wdvR_ayb7zIC for <suit@ietfa.amsl.com>; Mon, 16 Aug 2021 09:44:40 -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 DF3103A10A4 for <suit@ietf.org>; Mon, 16 Aug 2021 09:44:39 -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 17GGiUSp009086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 16 Aug 2021 12:44:35 -0400
Date: Mon, 16 Aug 2021 09:44:29 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: suit@ietf.org
Message-ID: <20210816164429.GD96301@kduck.mit.edu>
References: <DBBPR08MB5915A2D3ED245147B68AF7ABFAEF9@DBBPR08MB5915.eurprd08.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DBBPR08MB5915A2D3ED245147B68AF7ABFAEF9@DBBPR08MB5915.eurprd08.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/HQuB4VHTCCtTtH1rXpg7cqprJHg>
Subject: Re: [Suit] draft-ietf-suit-firmware-encryption: HPKE for COSE
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Software Updates for Internet of Things <suit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/suit>, <mailto:suit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/suit/>
List-Post: <mailto:suit@ietf.org>
List-Help: <mailto:suit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/suit>, <mailto:suit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Aug 2021 16:44:44 -0000

On Mon, Aug 02, 2021 at 03:08:44PM +0000, Hannes Tschofenig wrote:
> Hi all,
> 
> Currently we have newly introduced the use of HPKE for COSE in the firmware encryption draft.
> 
> HPKE could, however, be useful for other applications using COSE as well.
> 
> So, the question is: Should the HPKE functionality be defined separately for use with COSE or be defined specifically for use with firmware encryption only?
> 
> The answer to this question is a bit speculative because we have to guess whether HPKE will be useful for other applications using COSE. Currently, HPKE is used in various IETF protocols (MLS, TLS Encrypted ClientHello, Privacypass) but none of those applications utilize COSE.
> 
> Thoughts?

Chiming in super-late, but I agree with Russ about raising this with COSE.

-Ben

v2.8.7 | Report a Bug | By Email