IETF Logo Mail Archive

[TLS] Re: Status of ML-KEM WGLC

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Sun, 22 March 2026 21:23 UTC

Return-Path: <muhammad_usama.sardar@tu-dresden.de>
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 62C02CF9D1CD for <tls@mail2.ietf.org>; Sun, 22 Mar 2026 14:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_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=tu-dresden.de
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 MAaPbpOkQfiJ for <tls@mail2.ietf.org>; Sun, 22 Mar 2026 14:23:24 -0700 (PDT)
Received: from mailout7.zih.tu-dresden.de (mailout7.zih.tu-dresden.de [141.76.32.220]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 80134CF9D1C3 for <tls@ietf.org>; Sun, 22 Mar 2026 14:23:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tu-dresden.de; s=dkim2022; h=Content-Type:In-Reply-To:References:CC:To: Subject:From:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=TMLnHjOGrvBeIe37iqLICUFKlmH9DfD16MlBJXJmnGI=; b=w/8x7+Di2Gs3rbWW7YQeTzoRMc vsETRRuMUdlEvcetD9k8iSVlo+fw28LMC8SWnE6uVKeD1tAlJ8m9grx3mwXLTfBcTi86pZCrWZVvs oRI6Ff+jx/kFSCt0vV0J6TwDl5vVzA3IeYgI1Zb7s0tqPhjHl+rnDik5GLOSDy8PfWxLcwW+Kr30Q xnAUFI7QmM/QP3h6oRtutZv+EYvKDBluuWNLeb7Lwh1HLUdAbiIsaB4BCxJp/h99yehqTcOtHw79X KoEgqg9hF7bksAVuloGZm/TNHl0cx9ntjv4rBqRqcajVn74YNA1v2ThwhepOVv9jXfNxvHIjOUnJJ TjXIj63Q==;
Received: from msx-t422.msx.ad.zih.tu-dresden.de ([172.26.35.139] helo=msx.tu-dresden.de) by mailout7.zih.tu-dresden.de with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <muhammad_usama.sardar@tu-dresden.de>) id 1w4QGU-001VBi-29; Sun, 22 Mar 2026 22:23:23 +0100
Received: from [192.168.178.60] (141.76.13.149) by msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.37; Sun, 22 Mar 2026 22:23:17 +0100
Message-ID: <f03a0f9f-bb6c-4955-8e4b-359b3bad01cc@tu-dresden.de>
Date: Sun, 22 Mar 2026 22:23:16 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
To: Joseph Salowey <joe@salowey.net>
References: <CAOgPGoDd=qhg-mGzB8mrFOGVKHY_9uz+_EO3P_i0_e8TG6v0Mw@mail.gmail.com> <3256af6a-db98-42c7-839e-e96802cae2dd@cs.tcd.ie>
Content-Language: en-US
In-Reply-To: <3256af6a-db98-42c7-839e-e96802cae2dd@cs.tcd.ie>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms040109090301060409010307"
X-ClientProxiedBy: MSX-L420.msx.ad.zih.tu-dresden.de (172.26.34.140) To msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139)
X-TUD-Virus-Scanned: mailout7.zih.tu-dresden.de
Message-ID-Hash: IW73UGOSBEH32SPWM2ZWFDTY2NYP3ROI
X-Message-ID-Hash: IW73UGOSBEH32SPWM2ZWFDTY2NYP3ROI
X-MailFrom: muhammad_usama.sardar@tu-dresden.de
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Status of ML-KEM WGLC
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/oiVmp3PCo9H6aiugPQ8aVFztvVg>
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 Joe and Sean,

I have the same concern as Stephen. Please precisely specify the binary 
outcome of the WGLC.

Moreover, please add the following to the list:

  * Bring an attestation of ML-KEM from Crypto Review Panel [0] of CFRG
  * Improve the security considerations to thoroughly and precisely
    discuss threat model, all the risks and concerns, such as [1]
  * Recommend hybrids first (draft-usama-tls-ecdhe-mlkem-update): apples
    and oranges should not be put in the same category

On your third bullet, I believe the question should not be /whether/ to 
include motivation or not; it should be /how/ to improve the motivation. 
IEEE 802.11 liaison statement should be cited here, whenever it becomes 
available. I don't see it yet on Liaison Statements page. What if some 
other SDO sends a LS not to publish it? Which one do we prefer?

Sincerely,

-Usama

[0] https://wiki.ietf.org/group/cfrg/CryptoPanel

[1] https://mailarchive.ietf.org/arch/msg/tls/jlsYHENwqMv-4XPRvunqKsAL36k/

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