IETF Logo Mail Archive

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

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Wed, 26 November 2025 21:17 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 40EA3915B23C; Wed, 26 Nov 2025 13:17:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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_MED=-2.3, 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=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 f6HmlQ4K0h0H; Wed, 26 Nov 2025 13:17:11 -0800 (PST)
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 A18D2915B1AA; Wed, 26 Nov 2025 13:17:05 -0800 (PST)
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=VU4fHYWCG7MaDYnL2j5Tivkqz71KsUMUQ/CwXNGWb9k=; b=ssAXRuPFqtxMUbY4KqYPgZCPrE doUwV/32rbS9hEpNvxxBpTp0hKDMIC6MjNq9GMn+QDrlV1xNgQHeyn/j9PvxPFai23AHWCjPcQ/fD jhju3tFkjxALeH4FZKeoJCONqYY8dYu6D2W42+vOZd6P5i8qlMAjiqhXi0bFd2/6oILKIUIc+3et9 97+HLsr13saMtZbDEqsS2Hw+Wz3LTPgHlyX1UBQClvHLi2kfqS/Mov3juVZp3IRU3ha7mwl6eLCFS xwXzNFSQmi9+tI5dqVQaKGN7j5vLnZw4kRqLxz+5ows3ZOahjmIL2HDE+9UGqffoNOy11ps1Si/69 AgQUkNxw==;
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 1vOMsq-001Id5-NK; Wed, 26 Nov 2025 22:17:04 +0100
Received: from [10.12.5.228] (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.29; Wed, 26 Nov 2025 22:17:00 +0100
Message-ID: <91f28ee1-5408-417e-868d-bd5af47bd773@tu-dresden.de>
Date: Wed, 26 Nov 2025 22:16:59 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Eric Rescorla <ekr@rtfm.com>
References: <20251126185919.362611.qmail@cr.yp.to> <9ce12b8e-9982-4194-987d-d2ca3a41ea48@tu-dresden.de> <CABcZeBOffkV9eUtpdPp8eWB_eMA1c6-GOMHoZcDs93cGm1kwfw@mail.gmail.com> <10352a8e-c3d5-457e-854d-e72e31fca2d2@tu-dresden.de> <CABcZeBPzabtzCs=zLncyjFy=JHWXzpPb6haN5iFA6=3orXTU2Q@mail.gmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <CABcZeBPzabtzCs=zLncyjFy=JHWXzpPb6haN5iFA6=3orXTU2Q@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms060701070007070406090408"
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: mailout3.zih.tu-dresden.de
Message-ID-Hash: P5W4GUO7ZTV7HTM26RGJFSGATHMSEB3S
X-Message-ID-Hash: P5W4GUO7ZTV7HTM26RGJFSGATHMSEB3S
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: draft-ietf-tls-mlkem@ietf.org, tls-chairs@ietf.org, tls@ietf.org
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/H9SIqq7Scp1w0O5duET__U20voQ>
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 26.11.25 21:44, Eric Rescorla wrote:

> Right, though it's important to be clear on what that means:
>
> - You have to support key_share, but you don't necessarily need to 
> send it (e.g., if you're doing pure PSK without any DH).

cool, thanks very much. That resolves the apparent mismatch between 
section 9.1 and Figure 1 in my head.

> - The requirement for key_share doesn't require you to do ECC, just to 
> support the extension generally. You'd be in compliance with this 
> particular MUST if you supported pure MLKEM, though of course not with 
> the MUST to support P-256.

I think the draft should have a statement somewhere stating that it is 
no longer compliant with the base TLS specs, with pointer to section 9.1 
of RFC 8446bis.

-Usama

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