IETF Logo Mail Archive

[TLS] Re: WG Last Call: draft-ietf-tls-mlkem-05 (Ends 2025-11-26)

Jan Schaumann <jschauma@netmeister.org> Tue, 25 November 2025 14:43 UTC

Return-Path: <jschauma@netmeister.org>
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 61C3D9044828; Tue, 25 Nov 2025 06:43:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_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=netmeister.org
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 CajGYQocEHbT; Tue, 25 Nov 2025 06:43:15 -0800 (PST)
Received: from panix.netmeister.org (panix.netmeister.org [166.84.7.99]) (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 E66899044823; Tue, 25 Nov 2025 06:43:15 -0800 (PST)
Received: by panix.netmeister.org (Postfix, from userid 1000) id 5C792A1093; Tue, 25 Nov 2025 09:42:39 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=netmeister.org; s=2025; t=1764081759; bh=HcnxYj2tneAQpOMTy6ViZXq2FtzG59Lw+7fAchErl7s=; h=From:To:Subject:Content-Type:From:To:Subject; b=nyQqUjTnT51ehNTz9gmagydr+s/9pCXSq4vvpTO9yTr2VL6BRZf1O+du8U/AwY6M1 MxeO1eiB6WWwCVkFi82GhmoXUEslS5ahE1PU0sk2tF/J4aW0GWSpeco3X837hlQf7+ Zph07F+DiLNozeoXaYsfsyOstTNWzaGb5MRHPGcc5VfPgxupCbTMlSrHs+7PdQhEO9 X8Xdk0nhAxKtW9qfkCaaAieU2Llw4R8XFXaPffnqgpJ8U+H9u3ZJlZ97ywg3eusW9g KWdyjicWmYlA5k/ggAX5u3nG9S3uJMXXMjX6VNB9KP4QAP7sw0FgaSaXZgXqyybzem NJENznTAdA3GA==
Date: Tue, 25 Nov 2025 09:42:39 -0500
From: Jan Schaumann <jschauma@netmeister.org>
To: draft-ietf-tls-mlkem@ietf.org, tls-chairs@ietf.org, tls@ietf.org
Message-ID: <aSXAX04evDJ7HRuP@netmeister.org>
Mail-Followup-To: draft-ietf-tls-mlkem@ietf.org, tls-chairs@ietf.org, tls@ietf.org
References: <176236867319.904123.10146982018394612684@dt-datatracker-5df8666cb-7l4w5>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <176236867319.904123.10146982018394612684@dt-datatracker-5df8666cb-7l4w5>
Message-ID-Hash: T5C2HMHRXGBFAXERW5PVOMDHEMSVRQKJ
X-Message-ID-Hash: T5C2HMHRXGBFAXERW5PVOMDHEMSVRQKJ
X-MailFrom: jschauma@netmeister.org
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 2025-11-26)
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/4AFRn-gPmwa-q9yjzIhpbReg-jA>
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>

Sean Turner via Datatracker <noreply@ietf.org> wrote:
> 
> Subject: WG Last Call: draft-ietf-tls-mlkem-05 (Ends 2025-11-26)
> 
> This message starts a 3-week WG Last Call for this document.
> 
> Abstract:
>    This memo defines ML-KEM-512, ML-KEM-768, and ML-KEM-1024 as
>    NamedGroups and and registers IANA values in the TLS Supported Groups
>    registry for use in TLS 1.3 to achieve post-quantum (PQ) key
>    establishment.

The abstract makes the intent clear; setting
RECOMMENDED=N in the registry is additionally
explicit.

With that, I support publication.

-Jan

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