[TLS] Re: [External] Re: Working Group Last Call for Post-quantum Hybrid ECDHE-MLKEM Key Agreement for TLSv1.3

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Sat, 11 October 2025 12:23 UTC

Return-Path: <muhammad_usama.sardar@tu-dresden.de>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 08BAF7161A34 for <tls@mail2.ietf.org>; Sat, 11 Oct 2025 05:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.395
X-Spam-Level:
X-Spam-Status: No, score=-4.395 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=tu-dresden.de
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hEf11LkIoEWz for <tls@mail2.ietf.org>; Sat, 11 Oct 2025 05:23:09 -0700 (PDT)
Received: from mailout4.zih.tu-dresden.de (mailout4.zih.tu-dresden.de [141.30.67.75]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id C390C7161A22 for <tls@ietf.org>; Sat, 11 Oct 2025 05:23:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tu-dresden.de; s=dkim2022; h=Content-Type:In-Reply-To:From:References:To: Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=aRELoch6F8/ywmDcxhhHMen3w0buyOb37U2/uh9YuvM=; b=GcRe7+sWTWngOLisa0SM4ghaqt /sjvK66PUirpsuqjtcwKeGn7NG+uwzmOZnsvbgkMMkImTmgpHHZaBr6aB9Evm3+VfhMbNLU2hbi2d bnkcO8H9aR8F882jVWF0PwPO1/S0KWX92WfKElzk3SzEHx3BhzUABTw6d8RWWk+Ywyp1bYWBG+D36 CuW7nhjFy4e20FQpu6BE8Q6RHrH6KLZVW20w41wFY48drEmF5cVkm/vTr1ZLfetY1sDoUFMsuSzYA h6SwQ7MQy/I+OYbQukDwgH8/l1U1kbwjiHxyAYX0V7sH695WzzCHQV1PqxIxXZBTSjhr5vUI1+t0x EE6qcqCg==;
Received: from msx-t422.msx.ad.zih.tu-dresden.de ([172.26.35.139] helo=msx.tu-dresden.de) by mailout4.zih.tu-dresden.de with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <muhammad_usama.sardar@tu-dresden.de>) id 1v7Ycr-007Y5g-TL for tls@ietf.org; Sat, 11 Oct 2025 14:23:08 +0200
Received: from [10.12.5.228] (141.76.13.165) by msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.37; Sat, 11 Oct 2025 14:22:57 +0200
Message-ID: <16f68d04-6eb8-4ea4-9dd4-98762e0a766d@tu-dresden.de>
Date: Sat, 11 Oct 2025 14:22:56 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: tls@ietf.org
References: <20251011095218.169408.qmail@cr.yp.to>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <20251011095218.169408.qmail@cr.yp.to>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms090502070407080208010905"
X-ClientProxiedBy: MSX-T414.msx.ad.zih.tu-dresden.de (172.26.35.134) To msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139)
X-TUD-Virus-Scanned: mailout4.zih.tu-dresden.de
Message-ID-Hash: 3PVHEISTBDDOBHGZDB4FQDBWHUW4IO2R
X-Message-ID-Hash: 3PVHEISTBDDOBHGZDB4FQDBWHUW4IO2R
X-MailFrom: muhammad_usama.sardar@tu-dresden.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: [External] Re: Working Group Last Call for Post-quantum Hybrid ECDHE-MLKEM Key Agreement for TLSv1.3
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Yul6hw0gD-48n4CjCOthafKZ7Rc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

On 11.10.25 11:52, D. J. Bernstein wrote:

> Thanks---I was looking at TR-02102-1 rather than TR-02102-2.
In my understanding, TR-02102-1 is only for SRTP and MLS. The one 
applicable for TLS is only TR-02102-2.
> Content-wise, I don't see how Table 9 in TR-02102-2 supports the notion
> that SecP256r1MLKEM768 or SecP384r1MLKEM1024 is required for compliance
> with something.
In my understanding, it does not: (see response to your point (2) below)
> The claim up thread that there are "regulatory requirements" sounds
> impressive,

To me, it isn't very impressive. I believe TLS WG should be carefully 
analyzing and defining what is secure use of PQ in TLS rather than being 
forced to support potentially weak solutions by the "regulatory 
requirements". Just for clarity: it is a general statement of my view; 
in particular, I haven't analyzed PQ yet and thus currently have no 
opinion on whether pure PQ is weaker than hybrid, or whether a specific 
hybrid is weaker than some other hybrid.

Besides, a question remains: which regulations? which country/region? 
which one to prefer if the regulations of two countries/regions contradict?

> but I'd like to see a complete argument that
>
>      (1) pinpoints the "regulatory requirements" we're talking about,

Well, if we are /strictly/ talking about "regulatory requirements" then 
the English versions are not legally binding in the first place (as it 
is default in Germany). Someone has to first confirm that the 
translation is actually correct. See the note in [0]:

>  Note: The translations of these Technical Guidelines should be 
considered as courtesy translations. In principle, theGerman versions 
<https://www.bsi.bund.de/DE/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr02102/tr02102_node.html>take 
precedence.

>      (2) lays out how SecP256r1MLKEM768 and SecP384r1MLKEM1024 are
>          necessary for meeting those requirements, and

I think Sec. 3.1.3 in TR-02102-2 clarifies the situation. In my 
understanding, BSI neither recommends nor prohibits anything for PQ in 
TLS. It is just waiting for standards to be developed and matured. The 
only thing I could infer was that they /intend/ to recommend hybrid 
rather than pure PQ. Quoting the relevant text:

> Standards for the use of quantum-safe mechanisms in TLS are currently being developed and tested. The BSI intends to recommend quantum-safe mechanisms in this Technical Guideline (in hybrid use with recommended classical mechanisms) as soon as suitable standards have been adopted. 

Besides, Sec. 3.2 in TR-02102-2 clearly states that BSI is continuing to 
/recommend/ TLS 1.2, and since TLS 1.2 will not have PQ support, it 
implies to me that BSI is not even recommending moving towards PQ for TLS.

-Usama

[0] 
https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr02102/tr02102_node.html