[TLS] Re: ML-KEM security considerations
Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Fri, 10 April 2026 20:48 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 2D1ADD9FB3DC for <tls@mail2.ietf.org>; Fri, 10 Apr 2026 13:48:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1775854083; bh=wqM56suSK5yacswPEJrLtywn+cBJ/xIO/DyZUNvU2V8=; h=Date:Subject:To:CC:References:From:In-Reply-To; b=NytQ6a70gKPPWGBvvKdJv2eUE5oh+E/A7pQO/WilxMkt9Z2g5ANA7O9GRojFqi6eD Zlf7pBEH3wmKN2qcal/hDSEkEGEwaTTjlLVhqaxlZeL4w5fgFtuAmwQ9JDzW/0uQ2M aU/R1Jm5D+vwM6FlDUz6vDQbMenzZUnBTGbJB2DA=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 l6h_9tMItDBk for <tls@mail2.ietf.org>; Fri, 10 Apr 2026 13:48:02 -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 AFC12D9FB3CB for <tls@ietf.org>; Fri, 10 Apr 2026 13:48:02 -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=b4fPxKyavUUt2I25sleWXc/qT3TPd6rGxJU5yGlkyjk=; b=ufgqPstz4Bn64WbyyRnRPNVbYl uqRGED0Av3MufLEmyWQLkkBI/BQHYytsaKGcHbxt5OLX7VcTnoYQya4EQxykqTfHv4n5w//9zidhU cDCKjXeSRPeDvy6HhBzzlk3PPNdqLeiD5EEw6kSPqQKIPZoAJbw6a0oGrXP8lnPwt8Ato/LIE0E+q HbrU+vzM1/yju9WGdn3/DWcHDLGuXuPpVoRnC8BdhGIGm7+S6ptqliasrNqF20yxj2DTJl4+hqx6r wsD2vVy15rYR6AOFogHCUdj9mn39QF+V2/jaXV3TGFut9hLCtvMs9VkWOLW/hwJzjcAD6E5IZfuxl A+nWIhIA==;
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 1wBIlh-001z6D-0I; Fri, 10 Apr 2026 22:48:01 +0200
Received: from [10.12.5.228] (141.76.13.165) 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; Fri, 10 Apr 2026 22:47:56 +0200
Message-ID: <73d66638-7693-4e7f-a979-64d1ef47853c@tu-dresden.de>
Date: Fri, 10 Apr 2026 22:47:50 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Eric Rescorla <ekr@rtfm.com>
References: <MN2PR17MB4031C02ECAC48452E131D245CD592@MN2PR17MB4031.namprd17.prod.outlook.com> <CAFR824xYZYkN1NyOKn704hR42A6s3tXeSKUFYUQ16twKPTnc4g@mail.gmail.com> <CABcZeBMgu6+X6Wip=s-nP+JL7PCfE+UMAx-UMLU20EhmN_r5Gw@mail.gmail.com> <530418e4-cfe8-4e42-9820-13cccddb413f@cs.tcd.ie> <CABcZeBOc2=H2sNhRHA3OYRiguD7=DMZFvu0Hi3iZ_xcd-18nFA@mail.gmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <CABcZeBOc2=H2sNhRHA3OYRiguD7=DMZFvu0Hi3iZ_xcd-18nFA@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms090700060003010704080501"
X-ClientProxiedBy: msx-t420.msx.ad.zih.tu-dresden.de (172.26.35.137) 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: MSLSRCJZIH4UCXKKFMKMVYUPJUJARGIX
X-Message-ID-Hash: MSLSRCJZIH4UCXKKFMKMVYUPJUJARGIX
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: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, TLS List <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: ML-KEM security considerations
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/K32qeS0eEoYeoNlIR96xzXRLRZw>
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>
On 10.04.26 19:24, Eric Rescorla wrote: > On Fri, Apr 10, 2026 at 10:16 AM Stephen Farrell > <stephen.farrell@cs.tcd.ie> wrote: > > On 10/04/2026 18:04, Eric Rescorla wrote: > > As I said, my preference is for hybrids, but I think trying to > produce some > > text that will achieve consensus that says, in essence, "hybrids > are better" > > is quite challenging and probably not worth the effort. > > Disagree as to it being worthwhile. This WG has spent loads of > cycles due to the lack of consensus on the topic. > > > Which you propose to remedy by spending yet more cycles? No urgency has been demonstrated for this work. Codepoints have been assigned. I propose PARKing this draft and stop wasting more cycles on it. Best, -Usama
- [TLS] ML-KEM security considerations Salz, Rich
- [TLS] Re: ML-KEM security considerations Stephen Farrell
- [TLS] Re: ML-KEM security considerations Salz, Rich
- [TLS] Re: ML-KEM security considerations Stephen Farrell
- [TLS] Re: [EXT] Re: ML-KEM security considerations Blumenthal, Uri - 0553 - MITLL
- [TLS] Re: [EXT] Re: ML-KEM security considerations Stephen Farrell
- [TLS] Re: [EXT] Re: ML-KEM security considerations Salz, Rich
- [TLS] Re: [EXT] Re: ML-KEM security considerations Muhammad Usama Sardar
- [TLS] Re: ML-KEM security considerations Salz, Rich
- [TLS] Re: ML-KEM security considerations Stephen Farrell
- [TLS] Re: ML-KEM security considerations Deirdre Connolly
- [TLS] Re: ML-KEM security considerations Nico Williams
- [TLS] Re: ML-KEM security considerations Salz, Rich
- [TLS] Re: [EXT] Re: ML-KEM security considerations Blumenthal, Uri - 0553 - MITLL
- [TLS] Re: [EXT] Re: ML-KEM security considerations Salz, Rich
- [TLS] Re: [EXT] Re: ML-KEM security considerations Muhammad Usama Sardar
- [TLS] Re: [EXT] Re: ML-KEM security considerations Salz, Rich
- [TLS] Re: [EXT] Re: ML-KEM security considerations Muhammad Usama Sardar
- [TLS] Re: ML-KEM security considerations Eric Rescorla
- [TLS] Re: ML-KEM security considerations Stephen Farrell
- [TLS] Re: ML-KEM security considerations Eric Rescorla
- [TLS] Re: ML-KEM security considerations Stephen Farrell
- [TLS] Re: ML-KEM security considerations Muhammad Usama Sardar
- [TLS] Re: ML-KEM security considerations Nico Williams
- [TLS] Re: ML-KEM security considerations Eric Rescorla
- [TLS] Re: ML-KEM security considerations Nico Williams
- [TLS] Re: ML-KEM security considerations Eric Rescorla
- [TLS] Re: ML-KEM security considerations Nico Williams
- [TLS] Re: ML-KEM security considerations Nico Williams
- [TLS] Re: [EXT] Re: ML-KEM security considerations Blumenthal, Uri - 0553 - MITLL
- [TLS] Re: [EXT] Re: ML-KEM security considerations Nico Williams
- [TLS] Re: [EXT] Re: ML-KEM security considerations Eric Rescorla
- [TLS] Re: [EXT] Re: ML-KEM security considerations Nico Williams
- [TLS] Re: [EXT] Re: ML-KEM security considerations Eric Rescorla
- [TLS] Re: [EXT] Re: ML-KEM security considerations Nico Williams
- [TLS] Re: [EXT] Re: ML-KEM security considerations Stephen Farrell
- [TLS] Re: [EXT] Re: ML-KEM security considerations Eric Rescorla
- [TLS] Re: [EXT] Re: ML-KEM security considerations Stephen Farrell
- [TLS] Re: [EXT] Re: ML-KEM security considerations Eric Rescorla
- [TLS] Re: [EXT] Re: ML-KEM security considerations Stephen Farrell
- [TLS] Re: [EXT] Re: ML-KEM security considerations Jack Grigg
- [TLS] Re: [EXT] Re: ML-KEM security considerations Nico Williams
- [TLS] Re: ML-KEM security considerations Deirdre Connolly
- [TLS] Re: ML-KEM security considerations Tim Bray
- [TLS] Re: ML-KEM security considerations Deirdre Connolly
- [TLS] Re: ML-KEM security considerations Soatok Dreamseeker
- [TLS] Re: ML-KEM security considerations Muhammad Usama Sardar
- [TLS] Re: ML-KEM security considerations Eric Rescorla
- [TLS] Re: ML-KEM security considerations Muhammad Usama Sardar
- [TLS] Re: ML-KEM security considerations Eric Rescorla
- [TLS] Re: ML-KEM security considerations Salz, Rich
- [TLS] Re: ML-KEM security considerations Daniel Apon
- [TLS] Re: ML-KEM security considerations Eric Rescorla
- [TLS] Re: ML-KEM security considerations Daniel Apon
- [TLS] Re: ML-KEM security considerations Daniel Apon
- [TLS] Re: ML-KEM security considerations Wang Guilin
- [TLS] Re: ML-KEM security considerations Bas Westerbaan
- [TLS] Re: ML-KEM security considerations Wang Guilin
- [TLS] Re: ML-KEM security considerations Soatok Dreamseeker
- [TLS] Re: ML-KEM security considerations Muhammad Usama Sardar
- [TLS] Re: ML-KEM security considerations Muhammad Usama Sardar
- [TLS] Re: ML-KEM security considerations Deirdre Connolly
- [TLS] Re: ML-KEM security considerations Muhammad Usama Sardar
- [TLS] Re: ML-KEM security considerations Deirdre Connolly
- [TLS] Re: ML-KEM security considerations Muhammad Usama Sardar
- [TLS] Re: ML-KEM security considerations Nadim Kobeissi
- [TLS] Re: ML-KEM security considerations Loganaden Velvindron
- [TLS] Re: ML-KEM security considerations Sean Turner