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

Eric Rescorla <ekr@rtfm.com> Sun, 30 November 2025 19:54 UTC

Return-Path: <ekr@rtfm.com>
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 6B16C92C727E for <tls@mail2.ietf.org>; Sun, 30 Nov 2025 11:54:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20230601.gappssmtp.com
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 wXstEI3Lfiev for <tls@mail2.ietf.org>; Sun, 30 Nov 2025 11:54:13 -0800 (PST)
Received: from mail-yw1-x112c.google.com (mail-yw1-x112c.google.com [IPv6:2607:f8b0:4864:20::112c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id AEFD692C7277 for <tls@ietf.org>; Sun, 30 Nov 2025 11:54:13 -0800 (PST)
Received: by mail-yw1-x112c.google.com with SMTP id 00721157ae682-78a835353e4so34958357b3.2 for <tls@ietf.org>; Sun, 30 Nov 2025 11:54:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20230601.gappssmtp.com; s=20230601; t=1764532447; x=1765137247; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lmdgTMIDzhWQaAv2BCK9Zq7SWeKud5jMu8bE9kv4lY0=; b=z5BlZdKX6MARV7DhqmVFpoTvsE7uN9/ftzWld28HsN+mGi9VuG9E4uHQCkY0i9ZaAy Uia3MDxCQJuZG3pYSSVQ0MRnCalbjYTUEMtpkbqO0+V2XYx63R90v4EDH5O5uKBuN3dm iCmtnqGC2snQQEnqweAsG6mgeROByOLaPtge0zxv3aI0FUeYgEewcBjfkbzUvzSoOzgB HZcfung8r0UIKtR45sDC8L6tdkO64B/Ka+L/1A9pVKUcD+ozVHFe6SCM6KOZ3FKbUVNZ iWGPOqfdlUNeI06z2GpSnb1O8O4Y82YKinMXNEOp9MV7wsfFdVDTml9sIDEHuAXvV5e6 ZGqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764532447; x=1765137247; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=lmdgTMIDzhWQaAv2BCK9Zq7SWeKud5jMu8bE9kv4lY0=; b=Q/p+LQ9W3HLrgqNOHCEhCFJ9C56OREd2m0gHlK54lUfgqJ881HpDN9cQZ7WcmLbK2O PG0kJ7kZfF+xIRR2tZ9aaYLrGD3VAeg/OqlHHLo+U20VcQl5Xrgvfy3TqgADWsH+/SJg yyCUltCLhLA3zVwXC//Qt6BvcWGv6T3lMHdMNdp5OkGKWEolYsyXWPnjr5IjZROaSuL3 vXVt0OWBC/dT+z5iT/1kUu592XOp/1YiTRrv09azaN2TePrXtDD648sFxfBDKIKsIPMl NuuwzU3kSyJVOwaUNDCMMcp/W/C8sqSsc6xsgJ56VdStoPA975aWGg+hxpErsd+fNw7U URxA==
X-Forwarded-Encrypted: i=1; AJvYcCUpX7sb6BkqArS5doy/JZmtays3H4mNcuFX92WowHqW729aSammuWT8YfjDxgPysLGrtXo=@ietf.org
X-Gm-Message-State: AOJu0YymghbmsyzsxS3U5b3KsEb51NC69kl4VuDreO148KXrCkLgpsRV hpfYvyj7nO3ma8y9sJydE4UEudGqhbt+Qt4tv/VbX5d2fj4Mf22TkdIHQ8/U+b4gjWx+571ivDc gZ5pmT74oxZ6I61rbhdZnF48WWqGDz1VOVJ0VoaikjQ==
X-Gm-Gg: ASbGncstUWOFGJAa3JhcRafkMyVyjd8KNLgSFe9zadkV+e7cvsgiOlWU6+0qBpzKU3E RO5bk/adNv/2LtbnSyy8n9ugPpCv9DP6M/A6opJ2Kw2ixqxZXokklywr8O+ViwknJ/CEBmqRksZ IB0f6v4HWKgFxY+jdNnxqmfpbP7yIJRD7VflgWEua1Oqz56QXmrHT2HkwegxPvicvb6JATi1uvK OijSUmBquzEFESV6FL7qdWOVl+gez3d/GMN1gUXFTOWPlOmb71CbTp9Pz10RWGjfRsjP+vl1hwO 2i8U2cAqi3R8cQjFkefSdZbh7Xt0r4jAfJDA4dM88AhAU462RnNR8kBxRcDfZPAmULRuWlqvMY0 MerisCewmPVc1zHrVFoZ6
X-Google-Smtp-Source: AGHT+IEESDcNhen7SmQiE7zLrJO/pR2hoC4BKWO5gdO24F1KbsFfuJg/cPJNBL2ZztAkLwpCXI4YMtzjSBs2l0GBXAc=
X-Received: by 2002:a05:690c:6282:b0:787:f72d:2a5d with SMTP id 00721157ae682-78a8b478e4bmr283776217b3.2.1764532447496; Sun, 30 Nov 2025 11:54:07 -0800 (PST)
MIME-Version: 1.0
References: <CABcZeBNNsGEKSMcAyfnTyxCZLXxsBZT-u0adtn+5KyPMKm8wNw@mail.gmail.com> <20251128045939.466639.qmail@cr.yp.to> <CABcZeBO=JVUgHNph=yrv9ocTPn6Xd5xME=v=VAy-GiOaLgsihA@mail.gmail.com> <c3511e79-7fdc-4006-a6a5-f0b74645590f@tu-dresden.de> <GVXPR07MB9678CCCA73654597036A618F89DDA@GVXPR07MB9678.eurprd07.prod.outlook.com> <GVXPR07MB9678B6A380F89573725AF14789DAA@GVXPR07MB9678.eurprd07.prod.outlook.com> <8bd35743-8b7a-4f0d-8205-4a48e91d794d@tu-dresden.de>
In-Reply-To: <8bd35743-8b7a-4f0d-8205-4a48e91d794d@tu-dresden.de>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 30 Nov 2025 11:53:31 -0800
X-Gm-Features: AWmQ_bkCnGtzpdPSAgWcPKZ9RoGxnYuNjbvub1eo8nqsgQI78wp-RfTyCFyQZXg
Message-ID: <CABcZeBOBOjL1w7nsC0t9Rc6NjrPimhm2myfwFqzD-bRqFox5Fw@mail.gmail.com>
To: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
Content-Type: multipart/alternative; boundary="000000000000ba5a170644d53912"
Message-ID-Hash: OFNXVBFPWAIRMSUW4Z5AL2ZMN4Y3VFVH
X-Message-ID-Hash: OFNXVBFPWAIRMSUW4Z5AL2ZMN4Y3VFVH
X-MailFrom: ekr@rtfm.com
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" <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/gAtjxvOfY2MMb0fEriD7KI27C6E>
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 Sun, Nov 30, 2025 at 5:08 AM Muhammad Usama Sardar <
muhammad_usama.sardar@tu-dresden.de> wrote:

> Super naive question: how critical is this "application profile standard"
> discussion for MLKEM draft? IMHO, if it is orthogonal enough, maybe we can
> move it over to a separate thread?
>
As best I can tell, not at all.

-Ekr


> On 30.11.25 09:57, John Mattsson wrote:
>
> If you interpret the word “standard” as defined in United Nations
> A-HRC-53-42,
>
> "The term “standard” refers to an agreed norm defining a way of doing
> something in a repeatable manner."
>
> Is this how most people in the IETF interpret this term? I don't think so
> and the argument of mixing and matching definitions from outside applies
> here as well. IMHO, we should attempt for complete definitions of our own,
> rather than letting people import their desired definitions or
> interpretations from outside.
>
> Besides, in my naive understanding (sincere apologies again if I am
> missing/misunderstanding something), D. J. Bernstein's concern seems to be
> on the word "profile", rather than "standard".
>
> In general, I think we agree that there is an ambiguity in "application
> profile standard", and things are left over to interpretation, which is
> leading to misunderstandings.
>
> IMHO, a collaborative way to solve this is to perhaps write a
> clarification document addressing D. J. Bernstein's concerns. I would
> assume that would need some lengthy debates. Perhaps that is too late to
> make RFC8446bis wait for it to resolve? Hence, a proposal for a small new
> draft.
>
> -Usama
>
> PS: While I am mostly in agreement with Ekr and John (except for the above
> UN interpretation), having seen the notice of moderation of D. J.
> Bernstein's posts and to be fair with him, personally I will not post on
> this topic any further until one of his posts land in the mailing list to
> give him equal opportunity to clarify/defend his perspective/position.
>
> PPS: I am not super invested in this topic in the long term. This is
> probably not something I can formally prove to be correct or wrong. It is
> most likely just a matter of definition: one can define it one way or the
> other, leading to very different results. Nevertheless, I do believe it's
> important to resolve for us to peacefully work towards the shared goal of
> securing TLS rather than having to deal with appeals. So if that helps, I
> am volunteering to initiate a draft to try to resolve any misunderstandings
> and at some point in time, shift the draft over to one of you to move it
> forward.
>