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 23:25 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 5389691DAD02 for <tls@mail2.ietf.org>; Thu, 27 Nov 2025 15:25:39 -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 iazmKLIaUEAE for <tls@mail2.ietf.org>; Thu, 27 Nov 2025 15:25:38 -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 6D9D191DACF8 for <tls@ietf.org>; Thu, 27 Nov 2025 15:25:38 -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=LM6yjeCr00nToONmrUeYbOFGeKRG6yKz2iFSXFfz5fc=; b=iX6tmpzqnWJolzFrEVWKyRSZCg g1sHzNppsjEfE67mstXnl7MoUZGzlAC6BWg207KlQnRjYlIpFO2io1/nhx2Mv3n887k/bj5119qyq pwlsE+DZc/DqQ0VtDW47WvzAKt5isSx31faPdeZsywdpG8HUTmLM8/ArUSaAJwdixJs37tYdoQzOP eK4015PEcv242fHk4ubiG4u9HHvzAGcqgzKFK4ZOQh4GRuZD9i4TLDLa4I1D3bFjI+oukPY2hk03A IeOmU/a9LNasrzXtwHOlnyxIPC4x88NUhgfNuofre4z1S9phXeOOj8ncxeWgEysjf0IcQuNvhNReb SgyeYrDA==;
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 1vOlMn-002A09-Jq; Fri, 28 Nov 2025 00:25:37 +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; Fri, 28 Nov 2025 00:25:36 +0100
Message-ID: <18fd549c-0e8b-43dc-b79f-4ecbcbb9e417@tu-dresden.de>
Date: Fri, 28 Nov 2025 00:25:35 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Eric Rescorla <ekr@rtfm.com>
References: <9c237f425c0b1ebccf099c47a8badfcf41eb2ef0.camel@aisec.fraunhofer.de> <20251127194517.439400.qmail@cr.yp.to> <CABcZeBNNsGEKSMcAyfnTyxCZLXxsBZT-u0adtn+5KyPMKm8wNw@mail.gmail.com> <4e3283a6-b4c1-43d1-b956-7905783db82b@tu-dresden.de> <CABcZeBO_HkFkN2UNOYV=WcAo9W3Co__Oyx3_vsFe=rh_qz6FQg@mail.gmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <CABcZeBO_HkFkN2UNOYV=WcAo9W3Co__Oyx3_vsFe=rh_qz6FQg@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms070906090400090908040201"
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: CY6H3CSUHWIBRZD24RZSH65JYG6RMXQT
X-Message-ID-Hash: CY6H3CSUHWIBRZD24RZSH65JYG6RMXQT
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: 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/r9ATK2FRJhYdZTwPuOiThoqpaDY>
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 23:37, Eric Rescorla wrote:

> On Thu, Nov 27, 2025 at 2:14 PM Muhammad Usama Sardar 
> <muhammad_usama.sardar@tu-dresden.de> wrote:
>
>     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?
>
> TBH, I think this is an undecided question. [...]
Thanks.
>
>      1. Does it necessarily have to be standard track document?
>
> I think the term "standard" here strongly suggests that the document
> has to be Standards Track.

makes sense; I just got confused by CNSA 1 and 2, which were presented 
as examples in the thread.

-Usama

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