[TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt> (ML-KEM Post-Quantum Key Agreement for TLS 1.3) to Informational RFC
Russ Housley <housley@vigilsec.com> Thu, 30 July 2026 21:10 UTC
Return-Path: <housley@vigilsec.com>
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 4AE9812142686; Thu, 30 Jul 2026 14:10:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785445803; bh=j1WiqYkiTSMkFOWoAMNz8ct64RCdAAmwcmU7I0BXwBc=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=Wkt5eVibOBWQQywxxuHgBuQX+949LTMM0m/bi7mIh6dqkcWhrB22UUbK15TCOuj3i ZGVTynss2JG0I9qSlymlhK6tXTEb/QI2O/E9Hx8KNkI0eOi0+etvFxdPJJTtNRlwZB Wmn/w/ETTdULfTXJ6pvcRzo7JCmJlF8kVwVPWOYU=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 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_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=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=vigilsec.com
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 8sSgbBg_nvgm; Thu, 30 Jul 2026 14:10:02 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (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 9912812142681; Thu, 30 Jul 2026 14:10:02 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 393391A0B5B; Thu, 30 Jul 2026 17:09:56 -0400 (EDT)
Received: from smtpclient.apple (pool-96-255-71-95.washdc.fios.verizon.net [96.255.71.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 201CB1A0B72; Thu, 30 Jul 2026 17:09:56 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <178544388075.1456866.1870629541321453783@dt-datatracker-d4d6ff9d9-fsx7d>
Date: Thu, 30 Jul 2026 17:09:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5BDD708-BAF1-4B03-B268-06D972174406@vigilsec.com>
References: <178544388075.1456866.1870629541321453783@dt-datatracker-d4d6ff9d9-fsx7d>
To: last-call@ietf.org
X-Mailer: Apple Mail (2.3864.600.51.1.1)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=content-type:mime-version:subject:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=pair-202402141609; bh=kYmVDvICtX9VW/i6ddALhAOywMXwDiRXqCPzINfmkfY=; b=DXO3twaX0+AUaHc/RPu1mjMmw/dVuHfe/3DBUFLx1yPIATm4QI7l20+DsL/YUMIIbGGEX/8CvCJGu7RqGDHNFgdkDhN94xlL6gWZtzStFPmfQwnmpTBzKBfoYCKI0DirRO68o2qN8cubb1K4CJ/4fdfvSPRi9OG0/GdzPRIjo55hQRYpJ6VNtRRk2FNG9vvzF2CI1IupGgRiiXxZ4yO45DZ+JPJnGEdmfvJiajdBKHlGHyIaHA8lRDWCrBMd+aQx2tSlerIrqSOCtsWOBYuIoN1KUEGyqwWYOAO7aEyM6PT1YBc/Cwm9mQ4hFCSVeJh5l/ZS3UH/WT92DZSdYetgog==
X-Scanned-By: mailmunge 3.09
Message-ID-Hash: K3VPDTMX5I2NOL3FPCUA6QUFXE2DRPAZ
X-Message-ID-Hash: K3VPDTMX5I2NOL3FPCUA6QUFXE2DRPAZ
X-MailFrom: housley@vigilsec.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; header-match-tls.ietf.org-1; header-match-tls.ietf.org-2; header-match-tls.ietf.org-3; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-tls-mlkem@ietf.org, tls-chairs@ietf.org, IETF TLS <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt> (ML-KEM Post-Quantum Key Agreement for TLS 1.3) to Informational RFC
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/e0p_FyXBtXo6UDgNa8tPBh9egOM>
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 have read this document, and I support publication as an Informational RFC. Russ > On Jul 30, 2026, at 4:38 PM, The IESG <iesg-secretary@ietf.org> wrote: > > > The IESG has received a request from the Transport Layer Security WG (tls) to > consider the following document: - 'ML-KEM Post-Quantum Key Agreement for TLS > 1.3' > <draft-ietf-tls-mlkem-09.txt> as Informational RFC > > The IESG plans to make a decision in the next few weeks, and solicits final > comments on this action. Please send substantive comments to the > last-call@ietf.org mailing lists by 2026-08-13. Exceptionally, comments may > be sent to iesg@ietf.org instead. In either case, please retain the beginning > of the Subject line to allow automated sorting. > > Abstract > > > This memo defines ML-KEM-512, ML-KEM-768, and ML-KEM-1024 as > NamedGroups and registers IANA values in the TLS Supported Groups > registry for use in TLS 1.3 to achieve post-quantum (PQ) key > establishment. > > > > > The file can be obtained via > https://datatracker.ietf.org/doc/draft-ietf-tls-mlkem/ > > > The following IPR Declarations may be related to this I-D: > > https://datatracker.ietf.org/ipr/7227/
- [TLS] Last Call: <draft-ietf-tls-mlkem-09.txt> (M… The IESG
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… Russ Housley
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… Bellebaum, Thomas
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… Nowak, Adrian
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… D. J. Bernstein
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… Erwin Hoffmann
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… David Benjamin
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… Erwin Hoffmann
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… David Benjamin
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… Sophie Schmieg
- [TLS] Re: [Last-Call] Re: Re: Last Call: <draft-i… Salz, Rich
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… D. J. Bernstein
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… D. J. Bernstein
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… D. J. Bernstein
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… D. J. Bernstein
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… D. J. Bernstein
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… Nadim Kobeissi
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… Nadim Kobeissi
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… Christian Huitema
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… Rob Sayre
- [TLS] Re: Last Call: <draft-ietf-tls-mlkem-09.txt… D. J. Bernstein