[TLS] Re: WG Last Call: draft-ietf-tls-mlkem-08 (Ends 2026-07-08)

Paul Wouters <paul@nohats.ca> Mon, 13 July 2026 13:03 UTC

Return-Path: <paul@nohats.ca>
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 E782D115C9322 for <tls@mail2.ietf.org>; Mon, 13 Jul 2026 06:03:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783947826; bh=MFhr/NKekqE3Dlf6/v6OpL5U/JQ99yRIgRyROHl87RY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=I+B155zYkC+j2iJzPYIta6svtS9tXYKxW7xK6EbJXTPl9vWKvYXZ2/AJpHo5oB+4B /H2ur9AROGVacg9X0Rkrh1I5d+YfOpneOb6dOjwUvH9l+yXn4iPsR38Wg6W8gspCm6 ijwmsW1n17Mk5Sxrcom1sQTGUpvfMMgboeeQYxWs=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 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_MED=-2.3, 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=nohats.ca
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 GsDFy58dtPVg for <tls@mail2.ietf.org>; Mon, 13 Jul 2026 06:03:46 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::85]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 23526115C9314 for <tls@ietf.org>; Mon, 13 Jul 2026 06:03:46 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4gzN0n6QVkzpK; Mon, 13 Jul 2026 15:03:37 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1783947817; bh=MFhr/NKekqE3Dlf6/v6OpL5U/JQ99yRIgRyROHl87RY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=gN99mu34hMU1Tg4Bv6h+eoB6eR1OpFHLTcooahuc4n+vZ0KLSLaD4m8+CXqevQaGH Xk9/xTGXn32Nlp5nr236aCfA4q4jnPFJRYNrrjK0s12DyWq6ViRZ9a8oEQ8EAV2ndZ 4h2vYWnpcGhO52AdSlcrQKROnluJhdXkPs7wurh0=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id fO96cu4Ku6dQ; Mon, 13 Jul 2026 15:03:36 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 13 Jul 2026 15:03:36 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 3BF0719229AD; Mon, 13 Jul 2026 09:03:35 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 379F019229AC; Mon, 13 Jul 2026 09:03:35 -0400 (EDT)
Date: Mon, 13 Jul 2026 09:03:35 -0400
From: Paul Wouters <paul@nohats.ca>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
In-Reply-To: <7ee02219-d3b2-428d-a9ad-02fed9cc5187@cs.tcd.ie>
Message-ID: <68b15dc6-d024-72b8-f0ce-1ee0a6a7af59@nohats.ca>
References: <76f613e9-e952-40fb-a6e0-745392575b91@appelbaum.net> <ak3ochQmnlYhKt6h@chardros.imrryr.org> <ak55dB3pb2etyFoj@ubby> <CAOjisRw2HMHbv30QGe9JkPYXbgpCj1GiwSeAQ6tO4MfewxJ-_w@mail.gmail.com> <CAOjisRyi9h3im5YuL_sXYcUZWDkRt5d24uEB5FD01HwsD45rYw@mail.gmail.com> <ak6tr7pD2B281iXG@ein.win.tue.nl> <ak6yTqUFo2WJ7Q-m@akamai.com> <ak89AMLg_ZVnvJ8Y@ein.win.tue.nl> <751a6f2b-0c8f-477e-b711-23921a2ad8f7@streamsec.se> <ak9XauPVYm7OA65k@ein.win.tue.nl> <92e0e621-8efa-4e8d-a7ea-4183981616b9@streamsec.se> <0e91ce21-028a-438d-9ea8-a416d3d393ee@appelbaum.net> <78945c98-373b-4041-84fc-79689d4b67f1@streamsec.se> <70756c21-7ecc-4f83-89ee-db9a69331a0f@appelbaum.net> <655d7b49-e099-40a5-a04c-546a54d6ce57@streamsec.se> <6d3bb45c-4bf0-43b9-a9e8-7e4632eebe94@appelbaum.net> <CA+iU_qn0XUYY8MEgyEOZuNt=bsHoBd1kKOjyNuFAjVOYG8FoPw@mail.gmail.com> <AS4PR07MB8825C6262BD443833F31A2D089FB2@AS4PR07MB8825.eurprd07.prod.outlook.com> <7ee02219-d3b2-428d-a9ad-02fed9cc5187@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-ID-Hash: HDO2674C5DJNUZRWKMU4OACN6QLYO53T
X-Message-ID-Hash: HDO2674C5DJNUZRWKMU4OACN6QLYO53T
X-MailFrom: paul@nohats.ca
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
CC: "tls@ietf.org" <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: WG Last Call: draft-ietf-tls-mlkem-08 (Ends 2026-07-08)
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/PfELgM3ZvsDErwWRKY-xINEkRiI>
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 Sun, 12 Jul 2026, Stephen Farrell wrote:

> The above seems sensible. IIRC 4086 was AD sponsored, which'd have
> been my initial take on how to process a successor, but it's quite
> arguable that a WG could be better now, esp since we have new fancy
> crypto here and there (e.g. ppm) where some new issues might arise.
> A WG is probably more likely to result in such issues being thought
> through.

A year (or two?) ago, the SEC ADs looked at having some people create a
4086bis, as we kept running into drafts that would reference 4086 but it
was so outdated it was better not to reference that but instead say "use
your OS secure random source". Only the SSHM WG purposefully did not
include a reference to it (and I believe they wrote a few lines of text
in their RFCs basically saying "just use your OS RNG, these are better
that your homegrown stuff". The SEC ADs at the time didn't feel we got a
good segment of volunteers with modern OS knowledge together for them to
write a 4086bis, so yes perhaps a WG would be a better approach.

That said, a 4086bis would mostly target people who are not very
familiar with cryptographic requirements. I feel any algorithm document
specification would be implemented by people who should know enough on
cryptographically strong random sources to not need such sentences, and
I'm perfectly fine not adding anything to either mlkem drafts.

I do think this discussion is more a red herring against pure mlkem than a
real argument for text being really needed into these drafts. But provided
both drafts get equal treatment getting the same sentence(s) added on
randomness to avoid conspiracy theories and bad faith citations of the
differences, I think this is okay to do. Which does means we would have
to do this quickly as the hybrid mlkem is now in the RFC Editor queue.

Paul