[TLS] Re: WG Adoption Call for ML-KEM Post-Quantum Key Agreement for TLS 1.3

"D. J. Bernstein" <djb@cr.yp.to> Fri, 18 April 2025 14:03 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 BE8411E19A7A for <tls@mail2.ietf.org>; Fri, 18 Apr 2025 07:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 LVXjR8wrDOIf for <tls@mail2.ietf.org>; Fri, 18 Apr 2025 07:03:08 -0700 (PDT)
Received: from salsa.cs.uic.edu (salsa.cs.uic.edu [131.193.32.108]) by mail2.ietf.org (Postfix) with SMTP id 43BA81E19A75 for <tls@ietf.org>; Fri, 18 Apr 2025 07:03:07 -0700 (PDT)
Received: (qmail 27427 invoked by uid 1010); 18 Apr 2025 14:03:07 -0000
Received: from unknown (unknown) by unknown with QMTP; 18 Apr 2025 14:03:07 -0000
Received: (qmail 430514 invoked by uid 1000); 18 Apr 2025 14:02:55 -0000
Date: Fri, 18 Apr 2025 14:02:55 -0000
Message-ID: <20250418140255.430512.qmail@cr.yp.to>
From: "D. J. Bernstein" <djb@cr.yp.to>
To: tls@ietf.org
Mail-Followup-To: tls@ietf.org
In-Reply-To: <56e646395f67e27ff11a092d5989c1c85eba2563.camel@aisec.fraunhofer.de>
Message-ID-Hash: AGG7RLMPIPOOJNA2DEURQ3XYL73J2JGJ
X-Message-ID-Hash: AGG7RLMPIPOOJNA2DEURQ3XYL73J2JGJ
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: WG Adoption Call for ML-KEM Post-Quantum Key Agreement for TLS 1.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/Y_Nk9Cw2v6fGawTftgRkiGHhyw8>
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>

Bellebaum, Thomas writes:
> I am counting 22 expressions in favor of adoption and 7 opposing
> adoption.

Thanks for doing the work to tally this, and for posting the details so
that people can check your message and post any necessary adjustments.

These numbers sound radically different from the AD's portrayal ("67
responses ... vast majority was in favour ... a few dissenting
opinions"). My own impression, from having read all messages as they
came in, was about a quarter of the people opposing, so I will be very
surprised if adjustments end up big enough to rescue the AD's portrayal.

So: Can we please now have an explanation from the chairs of how they
arrived at "It looks like we have consensus to adopt this draft as a
working group item"?

To prevent any confusion about the procedures: Based on what I've seen
(the whole discussion, not just the fragmentary information conveyed by 
numbers), I disagree with this declaration of consensus. I am therefore
invoking the "first discuss the matter with the Working Group's
chair(s)" provision of RFC 2026, Section 6.5.1. I ask for this
discussion to be on-list for transparency.

Within that, what I'm suggesting---both because I think it's the natural
way forward, and because of transparency considerations; I'm not saying
this is the only possibility under RFC 2026---is for the chairs to start
by explaining to the WG how they evaluated consensus, so that we can all
consider the explanation, rather than starting with a bunch of
conflicting guesses from the rest of us regarding how consensus might
have been evaluated.

---D. J. Bernstein