IETF Logo Mail Archive

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

Stephan Verbücheln <stephan@verbuecheln.ch> Mon, 06 July 2026 21:08 UTC

Return-Path: <stephan@verbuecheln.ch>
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 47A5F11110D6A for <tls@mail2.ietf.org>; Mon, 6 Jul 2026 14:08:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783372128; bh=657/Stvvae38ltQgDdjwUZ4/0Mu37l3s0UbAwOD5ftY=; h=Subject:From:To:Date:In-Reply-To:References; b=ctGN1AVSPLtXtPYhyU6SfngM/Oc65nYj+mlTXEg/xopi2c9s6ILFCF1+XZIZZIY+I 3lJZ5d0QkXK+KQvJ7FLjbZGVHpt6uv/jTZQfxbL5u7lcdiY93SNSV5b6xARU1SLaIX vFR1B2E9gWAP8U9JFHnmmvaHgujWiloRRAoITmoE=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.306
X-Spam-Level:
X-Spam-Status: No, score=-1.306 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_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=verbuecheln.ch
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 zpfUA9teD42n for <tls@mail2.ietf.org>; Mon, 6 Jul 2026 14:08:47 -0700 (PDT)
Received: from verbuecheln.ch (unknown [213.55.213.228]) (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 AAC8D11109103 for <tls@ietf.org>; Mon, 6 Jul 2026 13:55:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verbuecheln.ch; s=default; t=1783371307; bh=657/Stvvae38ltQgDdjwUZ4/0Mu37l3s0UbAwOD5ftY=; h=Subject:From:To:Date:In-Reply-To:References:From; b=RaFr7jvMJnYZcz5wbKTroVU0jkcetbiNlM+f0rpfLTjPgsR0EqeB+GCTXSJ0URT+C S8QG7EHjhigEM0GiPyb4Mq6HE5PVVgNUCbwJjUHPTU9nzPqpR4BR5veQA5IixHRB6x hTFhbmYrJ3ZB570OQ/nquMjsNfRzKDaF1hYOK9N10DOtBexIBbLz34FE+ImWpdolLI mDCu9N8036jOqpuXTqXchGwXOxTb6EbllqPKdAu0z/weDYCfQ5bhxH5EYCsR6q6qg6 HWIVA/noJdNXDZuTNNNj1SArjcqeLUzNzMeoDcq/C1EJtJket9UC95lAY30l2Hlkk7 vcBvFR5BK5UyA==
Received: from [IPv6:2a04:ee41:4:4001:749b:468c:5262:8882] (unknown [IPv6:2a04:ee41:4:4001:749b:468c:5262:8882]) by verbuecheln.ch (Postfix) with ESMTPSA id 7A93A8D for <tls@ietf.org>; Mon, 06 Jul 2026 22:55:07 +0200 (CEST)
Message-ID: <9e676757770ba20b4f57fdebd210114bfb3d1230.camel@verbuecheln.ch>
From: Stephan Verbücheln <stephan@verbuecheln.ch>
To: tls@ietf.org
Date: Mon, 06 Jul 2026 22:55:06 +0200
In-Reply-To: <492f2df5-0e44-4140-8d72-9046a5a8e3b5@zhaw.ch>
References: <492f2df5-0e44-4140-8d72-9046a5a8e3b5@zhaw.ch>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-NEJEOuPZMgFZQcTGnwl3"
User-Agent: Evolution 3.56.2-0+deb13u1
MIME-Version: 1.0
Message-ID-Hash: SSNEY66EFWXQFFUZ22RWEMP3B63BQRQT
X-Message-ID-Hash: SSNEY66EFWXQFFUZ22RWEMP3B63BQRQT
X-MailFrom: stephan@verbuecheln.ch
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-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/UMLwDiNUf0lNNW1PIA6B01BxpoQ>
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 do not support publication of solo ML-KEM in TLS.

Since I feel that everything has already been said in this discussion
multiple times, I have nothing to add.

Regards

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