IETF Logo Mail Archive

[TLS] Re: Status of ML-KEM WGLC

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Mon, 23 March 2026 21:31 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 1E524D04325A for <tls@mail2.ietf.org>; Mon, 23 Mar 2026 14:31:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.795
X-Spam-Level:
X-Spam-Status: No, score=-2.795 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_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=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 b07xLHDcHWVl for <tls@mail2.ietf.org>; Mon, 23 Mar 2026 14:31:58 -0700 (PDT)
Received: from mailout3.zih.tu-dresden.de (mailout3.zih.tu-dresden.de [141.30.67.74]) (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 23873D04320B for <tls@ietf.org>; Mon, 23 Mar 2026 14:31:58 -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:From:References:CC:To :Subject: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=8n8rZG+GWd9RLNMprRzRLI/Aqcwjqc1YcyxIUSLaN+c=; b=Y6B7aF/IoZKa4q/TSXpJaEIiqS IDw15wnCiramyUA9s/E0DToOdp/N2b3UWyO6W3KUtlfvTexuqJWK9D1AyDV1RN5lMKhvuZwqQ5SEt l4/AtD4ObKLc1827bwWq9h4pPSu19vh5y1uNEaSG/4Mfdbw35LbRaHFXthetPvFc2h8K4y4QFSYX3 CWQh2Nly2KClkDbVTheSz1RDyfiMO5G6yBybAA7gMqpZbJw82ATpLBhR2pJExOSqdLLVayzn9Hd2m sSyFsgOLz802PL3EYlbbvKhPyclG0jlRPrQu5//THVeApZErDeE5TCvu/y6LHr5L3fyS71aLd10bX 9XiQp6rw==;
Received: from msx-t422.msx.ad.zih.tu-dresden.de ([172.26.35.139] helo=msx.tu-dresden.de) by mailout3.zih.tu-dresden.de with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <muhammad_usama.sardar@tu-dresden.de>) id 1w4msO-0075WT-Oi; Mon, 23 Mar 2026 22:31:57 +0100
Received: from [192.168.20.20] (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; Mon, 23 Mar 2026 22:31:53 +0100
Message-ID: <27a23f34-9deb-48cd-b890-a8f69c46e01f@tu-dresden.de>
Date: Mon, 23 Mar 2026 22:31:51 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
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> <CAOgPGoCMAXmJodSsQcg9ve2TmHd1nfOpek9nmh=BcDOpN1fvTQ@mail.gmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <CAOgPGoCMAXmJodSsQcg9ve2TmHd1nfOpek9nmh=BcDOpN1fvTQ@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms070800080804090201050209"
X-ClientProxiedBy: MSX-L416.msx.ad.zih.tu-dresden.de (172.26.34.136) To msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139)
X-TUD-Virus-Scanned: mailout3.zih.tu-dresden.de
Message-ID-Hash: RIODKCV3WK7CE7TUDAAHTY2X6IXNF56X
X-Message-ID-Hash: RIODKCV3WK7CE7TUDAAHTY2X6IXNF56X
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/LUCOxxmL-8CmcHr-GvCr4q4Wps8>
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>

Dear Joe and Sean,

On 23.03.26 16:51, Joseph Salowey wrote:
> [Joe] The chairs have determined that there is no rough consensus, but 
> people have requested changes.  The chairs have asked the author to 
> see if changes to the draft make a difference.

Thank you for the update. I apologize I am still a little bit lost. May 
I ask for a clarification? To be on the same page regarding the process, 
I am trying to unpack what that means to me:

 1. WGLC did not succeed.
 2. The draft will move back from WGLC to WG document state.
 3. Chairs are collecting the issues to be addressed ("We are working
    through issues ..." upstream implies to me chairs are not done yet)
    and then share that on the list.
 4. Author will update the draft addressing the issues.
 5. A new WGLC will then be launched.

If my understanding of any of those five is wrong, please correct that 
as the chairs intended it. Many thanks.

Best regards,

-Usama

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