[TLS] Re: ML-KEM recommended column

Bas Westerbaan <bas@cloudflare.com> Tue, 10 June 2025 08:39 UTC

Return-Path: <bas@cloudflare.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 3913C33103FA for <tls@mail2.ietf.org>; Tue, 10 Jun 2025 01:39:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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_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=cloudflare.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 0xKowayA5YZg for <tls@mail2.ietf.org>; Tue, 10 Jun 2025 01:39:27 -0700 (PDT)
Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (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 C725E33103E0 for <tls@ietf.org>; Tue, 10 Jun 2025 01:39:27 -0700 (PDT)
Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-e819aa98db9so2855664276.3 for <tls@ietf.org>; Tue, 10 Jun 2025 01:39:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google09082023; t=1749544767; x=1750149567; 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=CDyRDuQ37ruvZFBuLNPvvlNQDsiCKuJtxt2jUNRPQkQ=; b=UKRxan7+wku5txrxjI8eow0FksQOOFGOug8yllvcFeHR807LXkJiR9U1lMSPuFjdSB e33KKhLTCzBk1ZCjuQHG+Jt6Rn/WNwtj74g5fQL2NE543lMPLaYgcartrAB/m95j8+0V b3DfI+N1vOpzF3CxSiduKVLEnpdihKa1QVOm9GHUxAwTwDx5zZ+l2/yQqFOYwO1BY7yN t88RS5Bx+hf7ftN2+wE0CZp1ql4Qb7eBvH4k9hRpzf0ge4JpYpActR8gRhoYcSMOc1sU nqJuSLum3XyifUA5QYvK9VcR6T3LUzijvsFxlY8xvF1yfkag2+pOxl5hz05BGs9/4+bt Vx7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749544767; x=1750149567; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CDyRDuQ37ruvZFBuLNPvvlNQDsiCKuJtxt2jUNRPQkQ=; b=BqwFhiqRMliDgH7VOWP11lvZAO6rCgMD+lHqfurZvLh+jcQKR4twem8pvCxiIo/gLu DDlQ8sTbqUmdsPlHT6W4FhhQ1g8GhtY9/twjjovyadq4VMcSy0FDekx0Dt5DIqRZM2Cg B3Eiq3afgru5OjsXLPquV7DzzwKjVdHDobVotB3FtWrxxHDZEei31WA/pItwaHEXkfYi O2fzeAMJxhCMTc2beWpptvrYHZRMXjEuIAYi1GCgN8hbA8XeGLk3POUSKNjlRcyTT4hQ MUgI37ssXFzWryJ/R6Y1BMvLsAZejMo+4lR6g0tbnw8JL1IkutaTuxuA3xbJGGcN7qb7 rhNQ==
X-Gm-Message-State: AOJu0YzbWJeZ6es53q37XH6MbNimFLiolU5GO30M09B+zG0+2H7F52YT ZsRMeYJ1PCYS/f8VLauMmJC2J+tusFvSUiaW7r3reM3gk/jcXDd2fxer9Rb7S8YbBgrIlxNHZQu WOiF6mCwMycJzSGCqmCuNJiCTCiUu/t2r6lmlnYbmvA==
X-Gm-Gg: ASbGncux5B+p2nw10Sks6sO9DRgkLxAJqFTyC2zxxkWnBsr4LYwIr61CeWETfkgam7y r72Js8XvGSM8P8bLk9BqxkXUouEAEU7fFnFH3abgejgDA93PEe6GNUjPo3qxXkhiR7Kh/xRfG7J fRpRT3GV7pJmbsKKGdSJVRQQZx03pDnkuXJaWMmMxvvOM2aTHAxVqvJvEMlHOvSg==
X-Google-Smtp-Source: AGHT+IE6WOhW+TYMz8RvrC3jT/PHaHAqbZKivZuWL2+h4viHC4EnnT55a4G3/dPWgtgPE51Yb2MjIj55AV4zOS1LjaQ=
X-Received: by 2002:a05:6902:102a:b0:e7d:763c:a16c with SMTP id 3f1490d57ef6-e81a22aa25fmr20669756276.22.1749544767123; Tue, 10 Jun 2025 01:39:27 -0700 (PDT)
MIME-Version: 1.0
References: <3291f7396fa0dd06ab713ed59e01ccdc4f1e8ec6.camel@aisec.fraunhofer.de>
In-Reply-To: <3291f7396fa0dd06ab713ed59e01ccdc4f1e8ec6.camel@aisec.fraunhofer.de>
From: Bas Westerbaan <bas@cloudflare.com>
Date: Tue, 10 Jun 2025 10:39:16 +0200
X-Gm-Features: AX0GCFuza0QpTaVP8TqV9_PxSHvC5Ezyg-2IuBwRPz7gWyugVGBTqyq1AfC91oo
Message-ID: <CAMjbhoW5nc80yW0fnQW8f4jNfYxDLp78Qp93SHJVXb-uWJNC=g@mail.gmail.com>
To: "Bellebaum, Thomas" <thomas.bellebaum@aisec.fraunhofer.de>
Content-Type: multipart/alternative; boundary="0000000000005d6557063733a249"
Message-ID-Hash: 5VBOGIBZ3JN2JFT2HGYWRXLRP4EWD5XR
X-Message-ID-Hash: 5VBOGIBZ3JN2JFT2HGYWRXLRP4EWD5XR
X-MailFrom: bas@cloudflare.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: ML-KEM recommended column
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/ebuoHU9fYof9bFn5XV7SlC9z_Hc>
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>

I'd prefer marking non-PQ kexes as "D"; marking X25519MLKEM768 as "Y" and
leaving pure ML-KEM as "N".

On Fri, Jun 6, 2025 at 12:16 PM Bellebaum, Thomas <
thomas.bellebaum@aisec.fraunhofer.de> wrote:

> Hello together,
>
> I have just opened a pull request related to the hybrid vs. non-hybrid
> discussion, to highlight a possible compromise. For those who prefer mail,
> I have included the PR description below.
>
> Best,
>
> -- TBB
>
>
> ----- BEGIN PR -----
> This PR is an attempt to strike a balance between
>
> - those who would like to deploy ML-KEM as a non-hybrid, and
> - those who believe that a non-hybrid is not the best choice for the
> average user.
>
> In essence, it leaves the code point registrations (for interop), but
> clarifies that the choice to deploy a non-hybrid should only be taken in
> acknowledgement of the possible risks involved.
>
> This is done first and foremost by setting the recommended column in the
> IANA registration to Discouraged.
>
> According to draft-ietf-tls-rfc8447bis:
>
> > D:Indicates that the item is discouraged. This marking could be
> >   used to identify mechanisms that might result in problems if they
> >   are used, such as a weak cryptographic algorithm or a mechanism
> >   that might cause interoperability problems in deployment. When
> >   marking a registry entry as “D”, either the References or the
> >   Comments Column MUST include sufficient information to determine
> >   why the marking has been applied. Implementers and users SHOULD
> >   consult the linked references associated with the item to
> >   determine the conditions under which the item SHOULD NOT or MUST
> >   NOT be used.
>
> Perhaps taking could a bit too seriously for the original intent, the last
> sentence is exactly the mechanism this PR wishes to leverage. The security
> considerations have been extended by (the beginnings of; Please extend
> this!) a section about non-hybrids, and this section is intended to
> highlight and explain the use cases in which a non-hybrid might be a good
> fit.
>
> I have also made some changes to the motivation, to explain the D column
> early in the document.
>
> Goes without saying, but everything here is up for discussion :)
> ----- END PR -----
> _______________________________________________
> TLS mailing list -- tls@ietf.org
> To unsubscribe send an email to tls-leave@ietf.org
>