Re: [TLS] PQC key exchange sizes

Martin Thomson <mt@lowentropy.net> Tue, 26 July 2022 15:31 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1964C13C531 for <tls@ietfa.amsl.com>; Tue, 26 Jul 2022 08:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=lksM/lvm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=suuVqw3/
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 S8epE7jD4YqT for <tls@ietfa.amsl.com>; Tue, 26 Jul 2022 08:31:31 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (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 B6B83C136316 for <tls@ietf.org>; Tue, 26 Jul 2022 08:31:31 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id CD66B32005C1 for <tls@ietf.org>; Tue, 26 Jul 2022 11:31:28 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Tue, 26 Jul 2022 11:31:28 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1658849488; x=1658935888; bh=F16nsRYyB3 /yIOiX32jLzZWcDhGMuTKOdFarGcmUxK0=; b=lksM/lvmOa6sTvlXrx5Eq0GfrD uCsR9cuU5cPaCWSvqA3HWcbsNjvni0AqANPPUw2L5KuWv4eDtO0J/ri5l7mRpjBr qQ6Egk0CsKKMJlp8OVln9jpBt/6eXtW6sAwdwDQbSGcBAR7YsjdER0M9EuLB9/bl CdP33sQZnbXTqzgNcOftfwKpWZ7QZpBMpZWJf5uawzEGCeto/dYLEXEGVJX/WeJu PVYuHNeMv+AMOKm7+QmgOTMUbxmljrmJqZEjeW9M/T1eI6lXZsjjHdHjG9rpB/aY Ik3YbDeqUSkPhsT8NdckrirjFWEjJu7F9L9gaJby77lI2i6Tr80mXdWwdDKA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1658849488; x=1658935888; bh=F16nsRYyB3/yIOiX32jLzZWcDhGM uTKOdFarGcmUxK0=; b=suuVqw3/yvI9wRMaK7yKhYcrUWHbQ2ZYdcJ19IZt/7n+ fLokuR75hM6k5ASg7SFeOi5pKGvtPd8R7sJbbgvwKS2boCMyXE394tF3I9EAoNvB VlSpypGM67ogrIEtmnWO0hNiNDTjutRY8qwJuel6SgI2GtCaJmsGrBR6baiXAGWF OkxmRXVDHA5KLX0sXAWaWWbG/a/gGGQG4FXZUmmfw/Vicaqu8mHG8X9i01Pz8KGO lYPups6cZn5MROsY8QI//l8fVhw0cUSuNBqDYF9SdjOUZf5TXGCBGX/+jqtxx0iM R2Xvb3yyD64qq7rzyT7LCYqmZyzMIM5cFCrfxiKz/g==
X-ME-Sender: <xms:zwjgYsUCPdkL3nnHCoB_7r3ik7YoZuNRnn8Qt_ymoHmz6KaUBItdFw> <xme:zwjgYglICftoNtq247l55OYHtUI0SriVBDSFxlGGBGVp18SjZExuuefsfNlPNGWId iG3bmj0J0h4mBjrIOc>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvddutddgleduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpeekteeuieektdekleefke evhfekffevvdevgfekgfeluefgvdejjeegffeigedtjeenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvg ht
X-ME-Proxy: <xmx:0AjgYgYaWGdnOSJTAXwKej1evgF-Cn0xIE_spzcss_lyy4INojAFbA> <xmx:0AjgYrXkT57tPIt_-K4Zn-_8NWZcv1g313rXvcS9HJyDELHAMBqqgg> <xmx:0AjgYmnDnjhk3jsC1-knxf2SzZsKXuXkhvHQ5LOn0BGF8K90XDY9qQ> <xmx:0AjgYiwhXzOpZrohkctF1JdUZmHYdX_6RcysGmdJBPiGnvFVc08h8A>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id DC9AD234007B; Tue, 26 Jul 2022 11:31:27 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.7.0-alpha0-757-gc3ad9c75d3-fm-20220722.001-gc3ad9c75
Mime-Version: 1.0
Message-Id: <9f6b11ba-3649-42bb-87e9-1015be3dc84b@www.fastmail.com>
In-Reply-To: <dafc791e-2224-6af1-ae16-7d6996ea8008@cs.tcd.ie>
References: <CABzBS7nsbEhR-bmHG_ViSJFSH-0_5p0O3vKndS4+wFR=iGQzhw@mail.gmail.com> <dafc791e-2224-6af1-ae16-7d6996ea8008@cs.tcd.ie>
Date: Tue, 26 Jul 2022 11:31:06 -0400
From: Martin Thomson <mt@lowentropy.net>
To: tls@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/vcCpmhxJNLqYD7k1AZPEnIMMmvY>
Subject: Re: [TLS] PQC key exchange sizes
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2022 15:31:36 -0000

On Tue, Jul 26, 2022, at 11:21, Stephen Farrell wrote:
> Be interested in how that'd change the CH if ECH is used too.
> I guess the answer mightn't make us happy;-)

PQ HPKE would not fit, but the Kyber-512 numbers mean that we should be OK for ECH if we stuck with classical security.  For obvious reasons, that might not be OK though.

If we wanted a PQ HPKE (or a Hybrid KEM) then ECH would blow out the size so that we would end up with multiple packets for the CH.  That would be basically unworkable from a performance perspective.