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> Thu, 27 November 2025 22:14 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 E130D91D691E for <tls@mail2.ietf.org>; Thu, 27 Nov 2025 14:14:44 -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 GgVEcdOS6l_y for <tls@mail2.ietf.org>; Thu, 27 Nov 2025 14:14:44 -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 E0AF891D6914 for <tls@ietf.org>; Thu, 27 Nov 2025 14:14:43 -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:To: Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc: 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=xrdQrUhSzPaZ+iORLE+ytUrJimgiDJjV6pjI6qwaD7A=; b=ahVk2OvG9VreDdmXloXiXnIGZj 85ODUcVq2cLLrERsrvhWrtQfURhMDNzl1u7fEFVglfPrDfhWVmMpaxa2PnkgJ9cfgkvOu7dylIjRB B4GR+43kfcaChln8k2i4UpmjEgbdRfGCqZpW64vf14ySRU3c5VmhbI5aUoXenT27IcdaHZp9LmKXA SHUFWp2RIqYjeah+EfyC/aOLoxU1HGtQIkasy1EmSF+IyhaDis3enJgn4Uw5q2j9OzUJY0hrcnLmt 2BCWkyJssETvcuLkl8BlGmIfMc97g8fZX9ztp/58hNJbsjbQVoqS/PoyjB5S+A2fzHPWZEeNRQcDF WPlaQAwA==;
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 1vOkGA-00FC1d-Qs; Thu, 27 Nov 2025 23:14:43 +0100
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.29; Thu, 27 Nov 2025 23:14:25 +0100
Message-ID: <4e3283a6-b4c1-43d1-b956-7905783db82b@tu-dresden.de>
Date: Thu, 27 Nov 2025 23:14:24 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Eric Rescorla <ekr@rtfm.com>, tls@ietf.org
References: <9c237f425c0b1ebccf099c47a8badfcf41eb2ef0.camel@aisec.fraunhofer.de> <20251127194517.439400.qmail@cr.yp.to> <CABcZeBNNsGEKSMcAyfnTyxCZLXxsBZT-u0adtn+5KyPMKm8wNw@mail.gmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <CABcZeBNNsGEKSMcAyfnTyxCZLXxsBZT-u0adtn+5KyPMKm8wNw@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms040909090905090404080206"
X-ClientProxiedBy: MSX-L422.msx.ad.zih.tu-dresden.de (172.26.34.142) 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: RJOMVGMFZFDM2E2QADDZGK3RQLZ7WLED
X-Message-ID-Hash: RJOMVGMFZFDM2E2QADDZGK3RQLZ7WLED
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
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/9NCFnXuFNVCVbwgKzx8-yGc8UHE>
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 27.11.25 22:29, Eric Rescorla wrote:

> In this context I generally agree that "application profile" refers to
> an IETF standards track document describing the use of TLS with some
> other protocol.

Thanks for stating in more understandable way but I am still lost. RFC 
9151 (CNSA TLS profile) [0] is informational. Intended status (as of 
now) of CNSA2 TLS profile [1] is also informational. Am I missing 
something here?

John mentioned 3GPP; I couldn't find any draft on that defining a TLS 
profile. Did I miss something?

Anyway, my question mainly originated from this statement:

 > Constrained devices, for example, often support only one of secp256r1 
or X25519.

I don't see how this is connecting to any standard track document. If 
device vendors start issuing their own profiles (my perception of what 
this sentence means; John may correct me if I am wrong) and still claim 
to be compatible with RFC 8446 since they have a "profile", then how 
does this MTI bring in any benefit?

Two concrete questions:

 1. (trying to phrase my /authority/ question more precisely) Is IETF
    the /only/ body to define "application profile standard"? or do
    other SDOs count as "application profile standard" as well?
 2. Does it necessarily have to be standard track document?

-Usama

[0] https://datatracker.ietf.org/doc/rfc9151/

[1] https://datatracker.ietf.org/doc/draft-becker-cnsa2-tls-profile/

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