IETF Logo Mail Archive

Re: [CFRG] compact representation and HPKE

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 12 February 2021 22:18 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D30E3A0FFA for <cfrg@ietfa.amsl.com>; Fri, 12 Feb 2021 14:18:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 TeSdOTP_CbpC for <cfrg@ietfa.amsl.com>; Fri, 12 Feb 2021 14:18:56 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A48D3A0FF4 for <cfrg@irtf.org>; Fri, 12 Feb 2021 14:18:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id CFC39BFBA; Fri, 12 Feb 2021 22:18:54 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AjaJcTVPHrrH; Fri, 12 Feb 2021 22:18:53 +0000 (GMT)
Received: from [10.244.2.119] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 3A49FBFAB; Fri, 12 Feb 2021 22:18:53 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1613168333; bh=E097aQ0buk7XJvXaSAPK7wFSqkYbCQMza6PqPGcvDNY=; h=Subject:From:To:Cc:References:Date:In-Reply-To:From; b=tnMnLgFn2mXtS6m3jHXqmda8NvCT6DdgEyqv8WSuxm0rTe40pTvfenRhZnfQy/HbL 6zV/+Q/vMvOjYbQOO0FXHy+32LoDWDe6EsQZrM+8IKw0N/m7CRloD7Qpl/tnCs1Bjc A8zZ1WbMox4gBCZtRMDiyRPlm+XHRzSQoFI6BcQs=
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Dan Harkins <dharkins@lounge.org>, Eric Rescorla <ekr@rtfm.com>
Cc: CFRG <cfrg@irtf.org>
References: <0fcfb0ed-249b-7cd3-09ba-ed1c73122383@lounge.org> <CABcZeBMGJQ7sAKovy3japXVVLWRB8ydpsDzZxhijvFCtXptsZQ@mail.gmail.com> <b7bd5286-ccc1-c753-9d09-c647619581b5@lounge.org> <e09c73e0-27f4-cfdc-efab-3cdb8686d5b0@cs.tcd.ie>
Message-ID: <c5370019-e801-fe01-dcf6-daf020240a4f@cs.tcd.ie>
Date: Fri, 12 Feb 2021 22:18:50 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <e09c73e0-27f4-cfdc-efab-3cdb8686d5b0@cs.tcd.ie>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="GND2ewAbHbQKNZ4bPhFRH2OFN9xmxkf2i"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/M7W7DE-bHl9Siu_D-ZgslAU72AQ>
Subject: Re: [CFRG] compact representation and HPKE
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2021 22:18:58 -0000

Probably obvious but...

On 12/02/2021 22:11, Stephen Farrell wrote:
> 
> I need to check (and haven't) but IIRC for an earlier draft
> I had a problem that the OpenSSL APIs didn't support the
> compressed form for NIST curves, so it'd have been both a
> PITA to use those and would mean you could do HPKE with a

s/could/couldn't/ above ;-)

> FIPS compliant implementation IIUC. (Note: I could be
> recalling wrong, and if so, apologies, but if not...) for
> me, this isn't a case of encouraging cfrg curves but rather
> one of enabling simpler and more broad implementation.

v2.23.0 | Report a Bug | By Email