[TLS] Re: WG Adoption Call for Post-Quantum Hybrid ECDHE-MLKEM Key Agreement for TLSv1.3

"D. J. Bernstein" <djb@cr.yp.to> Fri, 28 February 2025 21:02 UTC

Return-Path: <djb-dsn2-1406711340.7506@cr.yp.to>
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 0D3FE41952F for <tls@mail2.ietf.org>; Fri, 28 Feb 2025 13:02:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Level:
X-Spam-Status: No, score=-3.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PP_MIME_FAKE_ASCII_TEXT=0.238, 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, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 L94ghCE-ViDP for <tls@mail2.ietf.org>; Fri, 28 Feb 2025 13:01:59 -0800 (PST)
Received: from salsa.cs.uic.edu (salsa.cs.uic.edu [131.193.32.108]) by mail2.ietf.org (Postfix) with SMTP id 3082C41952A for <tls@ietf.org>; Fri, 28 Feb 2025 13:01:58 -0800 (PST)
Received: (qmail 23134 invoked by uid 1010); 28 Feb 2025 21:01:58 -0000
Received: from unknown (unknown) by unknown with QMTP; 28 Feb 2025 21:01:58 -0000
Received: (qmail 745614 invoked by uid 1000); 28 Feb 2025 21:01:47 -0000
Date: Fri, 28 Feb 2025 21:01:47 -0000
Message-ID: <20250228210147.745612.qmail@cr.yp.to>
From: "D. J. Bernstein" <djb@cr.yp.to>
To: tls@ietf.org
Mail-Followup-To: tls@ietf.org, sob@harvard.edu
In-Reply-To: <8B632BD4-A604-4EE7-BC32-DEE8F7472338@sn3rd.com>
Message-ID-Hash: JXC5U7TVZSMOILPUV6LPBJ5WPBNDKTJG
X-Message-ID-Hash: JXC5U7TVZSMOILPUV6LPBJ5WPBNDKTJG
X-MailFrom: djb-dsn2-1406711340.7506@cr.yp.to
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: sob@harvard.edu
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: WG Adoption Call for Post-Quantum Hybrid ECDHE-MLKEM Key Agreement for TLSv1.3
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/8CVGtTGOJ2QXkCc5ghk4-8LiceA>
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>

Sean Turner writes:
> BCP 79 makes this important point:
>   (b) The IETF, following normal processes, can decide to use
>     technology for which IPR disclosures have been made if it decides
>     that such a use is warranted.

https://cr.yp.to/2025/bcp-79-issues.html covers that argument (giving
the same quote), and also covers the following counterargument: "this is
overridden by BCP 79’s subsequent text (quoted above) imposing a more
specific requirement upon mandatory-to-implement security technology and
imposing a higher bar for exceptions".

The page also distinguishes the two separate BCP 79 requirements at
issue. What matters at adoption time is BCP 79's change-control
requirement; that requirement doesn't have the same exceptions. The
other requirement can be met after adoption, as I explained before, so I
think the TLS discussion of that can and should be deferred, especially
if people are confusing it with the change-control requirement.

Note that this differs from the situation in LAMPS, where a spec is on
the same patented algorithm but is at a different WG stage (last call),
forcing consideration of both of the BCP 79 issues (if that spec can
reach consensus otherwise, which hasn't been established at this point).

Anyway, https://cr.yp.to/2025/bcp-79-issues.html includes links for all
of these arguments and counterarguments. I believe the page covers every
point that has been raised, structured in a way that shows when point B
is in response to point A. I'd appreciate it if anyone who sees anything
missing can let me know, of course on list for transparency.

---D. J. Bernstein