IETF Logo Mail Archive

[TLS] Re: WG Last Call: draft-ietf-tls-mlkem-05 (Ends 2026-02-27)

Thom Wiggers <thom@thomwiggers.nl> Fri, 20 February 2026 07:58 UTC

Return-Path: <thom@thomwiggers.nl>
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 711A4BA4C948 for <tls@mail2.ietf.org>; Thu, 19 Feb 2026 23:58:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=thomwiggers.nl
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 5MH62xCcNRdd for <tls@mail2.ietf.org>; Thu, 19 Feb 2026 23:58:48 -0800 (PST)
Received: from mail-ej1-x644.google.com (mail-ej1-x644.google.com [IPv6:2a00:1450:4864:20::644]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D8EBFBA4C943 for <tls@ietf.org>; Thu, 19 Feb 2026 23:58:48 -0800 (PST)
Received: by mail-ej1-x644.google.com with SMTP id a640c23a62f3a-b8fa449e618so294202366b.0 for <tls@ietf.org>; Thu, 19 Feb 2026 23:58:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thomwiggers.nl; s=google; t=1771574321; x=1772179121; darn=ietf.org; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=A0NEeVs4o+9eOybjlYsfqBMXe4x9OkhrJ8JYmlarMJY=; b=E9GRYo7j3BbEOyJZ9z9vNGOzl2O0UD5pHotCRXYhFMM3xzyBj048ozrddjenhM0nXJ 7TL6MKTOXxi/VplT1GU+U5guBtzp7QbtXYAlnLbrYk4vOy/mPJlfnxFnlwJ73ZXqhg7P gmucf8xmXsU8eY/4LSwplPrOxgbnIOvqiiCnk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1771574321; x=1772179121; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:x-gm-gg:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=A0NEeVs4o+9eOybjlYsfqBMXe4x9OkhrJ8JYmlarMJY=; b=B7D7ZcNvFDHyABDWEqmHa278QMDpIjONbFu5xlg1fER8iXNXhgv4q7U6zlUfOe8B8i O9NJRGqr+H99HtWJzgmPaek+q4FL2G8/2oqSABMP4mK2mBoRba2E2S2FA+zKp1xsa37x nhRQIPlc4lq52ODBVvGGl1BAAcw7ZyeSey1Q6a1cCfMU39hpE6vuM3cU4TnSUlqzKdil hUBL8kRFilYNc6sDl0uYy03W0eYGMcOhDcWDRtJ23ilDGhFMvSBxlzHIWJBmNQDMXe5a dTxO+Zok62PurqBgOCUXX5eq5W1GpQg1LlnPQdCnzghedY/xXTKcQWXtujCLzZvm42IE qFqw==
X-Gm-Message-State: AOJu0YygJDO9fq5sNj7aiGg6R6s4aNBPOVNMxAm/9VWhsVSGrii2ds3i yyLB14Sdz+Yp6jwFUzA+wp9hrtUCYmnT0JZjQOI3UIOZFjKb9IBmV5+LLWEL78JnhjgkjRfnpCl 6/Uz4IRhYLoNb
X-Gm-Gg: AZuq6aI4Z9zAdgE1oq9JR+wsdbs4H8PWG2QggpwFX4IrASJsiAvya5spTqIpAYNBmRS jcRJJxmYSSRNAKFBTUOla0Hw2b1B9IXh84uGPsc4dSH1ucYCOCrf2MCe41O4J2DQGpOdV2qctpI 5fGH4Izl0uI52BxRBYudjGDFAd7MQpC9HSqgPIhTy8yNonkSG3AdN6WPVVcZpzYs6DXuKIuIcz+ L42alwI3QSM1ua1/tT5tzvICMvUKVSI1Rdm4IBLQjDtFZRWObYIecE9rP1bm3o4/uWTKWyWR5AM xQMKYBUOX6W71Pv/DcoFTY/fK8AQ6FvKSO3FLK50UI8O9Ainee2cHZSUAsQluQAPnuDidjKQwRp vWMIZ82bubC1Kk6bfQ8gCM+tjug0J0kRi3rgkWTxyzPy5jVA19AdtomDlVv5639knmGa+JXL6PK SqfWa5z90XLPnda7UoBBwdUBYn+e8Hv+vi/ATZFmwiGilm/cywn1zgta1Ikpr1WrgbE5JglMQkc ztolva2
X-Received: by 2002:a17:907:705:b0:b73:572d:3b07 with SMTP id a640c23a62f3a-b9072f25410mr55041466b.28.1771574320678; Thu, 19 Feb 2026 23:58:40 -0800 (PST)
Received: from smtpclient.apple (63-164-187-31.ftth.glasoperator.nl. [31.187.164.63]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-b8fc766554bsm657618966b.46.2026.02.19.23.58.40 for <tls@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Feb 2026 23:58:40 -0800 (PST)
From: Thom Wiggers <thom@thomwiggers.nl>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
Date: Fri, 20 Feb 2026 08:58:29 +0100
References: <20260218194044.1135896.qmail@cr.yp.to> <7C9C99AA-42B0-4BC7-8F41-39F35754F1C4@vigilsec.com> <MN2PR17MB40310F0A2891942D76C43E60CD6BA@MN2PR17MB4031.namprd17.prod.outlook.com> <2caab265-00ba-4078-b6d0-3a178dabaa61@tu-dresden.de> <CAEEbLAbkV4YxN7cgggckpEp24MLtRZpzs6M4KemBatpzCCcs0A@mail.gmail.com> <MEAPR01MB3654415F735DE96CEE239C78EE68A@MEAPR01MB3654.ausprd01.prod.outlook.com> <aZfbhrFDBp7a0xHL@chardros.imrryr.org>
To: "<tls@ietf.org>" <tls@ietf.org>
In-Reply-To: <aZfbhrFDBp7a0xHL@chardros.imrryr.org>
Message-Id: <EB48AB24-A1A2-47C8-9C2C-47C93B9320E7@thomwiggers.nl>
X-Mailer: Apple Mail (2.3864.400.21)
Message-ID-Hash: SL4WBRUWHTW45PVJQU7J2MAEC6KSM4HO
X-Message-ID-Hash: SL4WBRUWHTW45PVJQU7J2MAEC6KSM4HO
X-MailFrom: thom@thomwiggers.nl
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: WG Last Call: draft-ietf-tls-mlkem-05 (Ends 2026-02-27)
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/ikO_b_9z7jZBingjNqqv1-L-f6g>
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>

Hi all,

I support the publication of this draft.

Cheers,

Thom 

> Op 20 feb 2026, om 04:56 heeft Viktor Dukhovni <ietf-dane@dukhovni.org> het volgende geschreven:
> 
> On Fri, Feb 20, 2026 at 01:18:52AM +0000, Peter Gutmann wrote:
> 
>> Unless it's PQC, in which case the minute it's in the spec, in fact long
>> before there's even a spec for it, everyone will be clamouring for it to
>> appear.  Not arguing against publication, just pointing out that when it comes
>> to post-magic crypto the only choices you have are "support it" or "support
>> it".
> 
> OpenSSL 3.5 and later do indeed provide an implementation, but FWIW, the
> non-hybrid ML-KEM groups are not enabled by default, both client and
> server have to choose to enable them explicitly in their configurations.
> 
> Only X25519MLKEM768 is enabled by default, and in 4.0 we'll shortly add
> a default fallback to the SecP256r1MLKEM768 hybrid (but without a
> predicted client keyshare, so used only after a server HRR, if the
> server for some reason supports the P-256, but not the X25519 hybrid).
> 
> Once a VIC-20, an abacus or a dog[1] can no longer beat demonstrated
> implementations of Shor's algorithm, perhaps the pure ML-KEM variants
> would also make sense to enable by default.
> 
> Before I take CRQCs as a credible looming issue, a milestone I'd want to
> see crossed would be an honest Shor's algorithm factorisation of a
> 32-bit RSA modulus[2], but perhaps I should first have asked for a
> 16-bit RSA moduls instead, as that too appears to be currently well out
> of reach.
> 
> -- 
>    Viktor.  🇺🇦 Слава Україні!
> 
> [1] https://eprint.iacr.org/2025/1237.pdf
> [2] https://scottaaronson.blog/?p=9564#comment-2025810
> 
> _______________________________________________
> TLS mailing list -- tls@ietf.org
> To unsubscribe send an email to tls-leave@ietf.org

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