IETF Logo Mail Archive

[TLS] Re: Working Group Last Call for Use of ML-DSA in TLS 1.3

Falko Strenzke <falko.strenzke@mtg.de> Tue, 14 April 2026 05:50 UTC

Return-Path: <falko.strenzke@mtg.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 34722DBCA172; Mon, 13 Apr 2026 22:50:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776145819; bh=GX1QV0BEqFXbx/6s/pSgjOCbEFygarOP+o2hzxhWQSI=; h=Date:Subject:To:References:From:In-Reply-To; b=ICOQKwM5ynmXVgrZKHdRwKrD8KR1AWdCHvNxvtDnEU4P+oln8Rm5uPnYnMjFpewev G1IFSe0TUgFlMITQ7kOUp3fM33mQZt4ZeL9u0wuq5sp4iPBx4ziKKHxpJzE+0SwFge jXHG2Prr8BXPW/Rb/9Z1A+loJiZtCq0XwuNxNJF8=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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=mtg.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 KXLoro8WiVGs; Mon, 13 Apr 2026 22:50:18 -0700 (PDT)
Received: from www.mtg.de (www.mtg.de [IPv6:2a02:b98:8:2::2]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 19B46DBCA167; Mon, 13 Apr 2026 22:50:17 -0700 (PDT)
Received: from minka.mtg.de (minka [IPv6:2a02:b98:8:1:0:0:0:9]) by www.mtg.de (8.18.2/8.18.2) with ESMTPS id 63E5o34l024246 (version=TLSv1.3 cipher=TLS_CHACHA20_POLY1305_SHA256 bits=256 verify=NOT); Tue, 14 Apr 2026 07:50:03 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mtg.de; s=mail201801; t=1776145803; bh=GX1QV0BEqFXbx/6s/pSgjOCbEFygarOP+o2hzxhWQSI=; h=Date:Subject:To:References:From:In-Reply-To; b=lj8TsTlz7ssBmsaQR2jn4X8KKJfDhWykbCKzX/P84SI5XYzWZiStXjvdclkLj9/He vSPiw8bXyRCV/4SvoaFuO2XEeBsXOvBkZepfeaKv9MuvIxOTNZAK2LKJQF+YbNjV2G xjXqClPRiasU0bLtRY/bFtQGbH0pRCozKVq4C882DuujowsDztkEbJ+NlcptWgt4ch UJQhiONpDl7r+U+Fjw3HSMzTIBePrLZMWHnfm4xd1BaRTjrbSNGGBTrYLe6asIkQrl ZhjT4uSKZzo93L/3gTUOMHy/6/TkkPozmMXHy1GhXLurgbKrrTH8qYRoAuiXAHPMXO Sx/k/v8IRB3jg==
Received: from [10.8.0.100] (vpn-10-8-0-100 [10.8.0.100]) by minka.mtg.de (8.18.2/8.18.2) with ESMTPS id 63E5o2r9010483 (version=TLSv1.3 cipher=TLS_CHACHA20_POLY1305_SHA256 bits=256 verify=NOT); Tue, 14 Apr 2026 07:50:02 +0200
Message-ID: <b140e27d-02c7-41f8-b061-fdbcc0272eee@mtg.de>
Date: Tue, 14 Apr 2026 07:50:02 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Andrei Popov <Andrei.Popov=40microsoft.com@dmarc.ietf.org>, "Scott Fluhrer (sfluhrer)" <sfluhrer=40cisco.com@dmarc.ietf.org>, Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>, Kris Kwiatkowski <kris@amongbytes.com>, "tls@ietf.org" <tls@ietf.org>
References: <16CF0FDA-7263-461A-9F2B-D37DBEAF5DD9@sn3rd.com> <25c8d414-e4c8-455b-bd64-28132615ba75@cs.tcd.ie> <68f49a81-dd2c-4bea-896a-87da3e6aff68@tu-dresden.de> <CAMjbhoWwvfkfScpbf4-5PBzk__qb+6M4ZzAOba64kk9aXBba5g@mail.gmail.com> <d47a34ab-7fb9-4687-84aa-a5fa6bcf6a6c@tu-dresden.de> <2971d01a-89e3-43d3-a01d-b9c17b178763@amongbytes.com> <692bb582-ab7e-4d6b-aa75-ac5d93228bb2@tu-dresden.de> <DS4PPFA08475C7DBE27468E40C672197481C1242@DS4PPFA08475C7D.namprd11.prod.outlook.com> <LV0PR21MB6623B48B1F3A05D745F5A79D8C242@LV0PR21MB6623.namprd21.prod.outlook.com>
Content-Language: en-GB
From: Falko Strenzke <falko.strenzke@mtg.de>
Organization: MTG AG
In-Reply-To: <LV0PR21MB6623B48B1F3A05D745F5A79D8C242@LV0PR21MB6623.namprd21.prod.outlook.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms070604050409060005020100"
Message-ID-Hash: GZQJBHOO4TDFSPQM6BI3W6ZDROEQM766
X-Message-ID-Hash: GZQJBHOO4TDFSPQM6BI3W6ZDROEQM766
X-MailFrom: falko.strenzke@mtg.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: Working Group Last Call for Use of ML-DSA in TLS 1.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/41HaZ-yMVjG85_HuHrNoKXL-0v0>
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>

I also see the need for ML-DSA composite signatures in TLS and thus 
would support adoption of draft-reddy-tls-composite-mldsa. The demand 
for composite arises clearly in the European context, where – as should 
be well known – multiple national information security authorities have 
set the use of PQ/T hybrids as the standard.

Falko

Am 13.04.26 um 18:30 schrieb Andrei Popov:
>
> Just to weigh in on this: I would support adoption of 
> draft-reddy-tls-composite-mldsa. There is customer demand for 
> composite certs, and I would like to get these implemented in the 
> Windows TLS stack.
>
> Cheers,
>
> Andrei
>
> *From:*Scott Fluhrer (sfluhrer) <sfluhrer=40cisco.com@dmarc.ietf.org>
> *Sent:* Monday, April 13, 2026 12:30 AM
> *To:* Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>; 
> Kris Kwiatkowski <kris@amongbytes.com>; tls@ietf.org
> *Subject:* [EXTERNAL] [TLS] Re: Working Group Last Call for Use of 
> ML-DSA in TLS 1.3
>
> If you would prefer hybrid authentication, then I would suggest you 
> publicly endorse either draft-reddy-tls-composite-mldsa (composite 
> signatures; that is, the cert has both classical (e.g. RSA) and pq 
> public keys (e.g. ML-DSA) and both are used to sign in a single 
> logical signature operation) or draft-yusef-tls-pqt-dual-certs (the 
> server sends both a classical certificate  and a pq certificate, and 
> TLS generates two signatures using the two public keys)
>
> Both are currently individual drafts; public support would be useful 
> to make them working group items.
>
> My opinion: composite would be easier to for the working group; 
> composite signature algorithms (and composite certificates) are very 
> close to becoming an RFC (draft-ietf-lamps-pq-composite-sigs).  From 
> the TLS perspective, all that would be needed in addition are code 
> points (because it could just treat the signature algorithm in the 
> composite draft as just another signature algorithm).
>
> ------------------------------------------------------------------------
>
> *From:* Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
> *Sent:* Sunday, April 12, 2026 8:54 PM
> *To:* Kris Kwiatkowski <kris@amongbytes.com>; tls@ietf.org <tls@ietf.org>
> *Subject:* [TLS] Re: Working Group Last Call for Use of ML-DSA in TLS 1.3
>
> TL;DR: My concern has been addressed and I am happy to step back from 
> opposition to no opinion on this WGLC. I would have preferred 
> standardizing hybrids.
>
>
> _______________________________________________
> TLS mailing list --tls@ietf.org
> To unsubscribe send an email totls-leave@ietf.org
-- 

*MTG AG*
Dr. Falko Strenzke

Phone: +49 6151 8000 24
E-Mail: falko.strenzke@mtg.de
Web: mtg.de <https://www.mtg.de>

------------------------------------------------------------------------

MTG AG - Dolivostr. 11 - 64293 Darmstadt, Germany
Commercial register: HRB 8901
Register Court: Amtsgericht Darmstadt
Management Board: Jürgen Ruf (CEO), Tamer Kemeröz
Chairman of the Supervisory Board: Dr. Thomas Milde

This email may contain confidential and/or privileged information. If 
you are not the correct recipient or have received this email in error,
please inform the sender immediately and delete this email.Unauthorised 
copying or distribution of this email is not permitted.

Data protection information: Privacy policy 
<https://www.mtg.de/en/privacy-policy>

v2.40.4 | Report a Bug | By Email | System Status