[TLS] Re: WG Last Call: draft-ietf-tls-mlkem-08 (Ends 2026-07-08)

Eric Rescorla <ekr@rtfm.com> Thu, 02 July 2026 22:34 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 A9F2D10D117CC for <tls@mail2.ietf.org>; Thu, 2 Jul 2026 15:34:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783031663; bh=nt4O34quHjkHe/Wk0JOy/ShuuO851JeTCrZIgdhht6U=; h=References:In-Reply-To:From:Date:Subject:To:Cc; b=JBxQwmU5hQ54Z3nqAT7ykwjfRbCxEM4eV9sOCsTOhl0zHenkgNOlUeUuWmHLOWUVR RfZwWy1ws6+QKDg3Nqx/kQsoE3tjcioiQ9NC2RGv2FBkdINFbg7iy+mLHbGMwwYEz2 FFiEDd35zjMpQ6yjX4foErvGc/9SKEP8JK4RyhLw=
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.20251104.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 nuIJBVOsBpW4 for <tls@mail2.ietf.org>; Thu, 2 Jul 2026 15:34:21 -0700 (PDT)
Received: from mail-yx1-xb136.google.com (mail-yx1-xb136.google.com [IPv6:2607:f8b0:4864:20::b136]) (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 9919810D115E0 for <tls@ietf.org>; Thu, 2 Jul 2026 15:33:09 -0700 (PDT)
Received: by mail-yx1-xb136.google.com with SMTP id 956f58d0204a3-664a09bc459so3036424d50.1 for <tls@ietf.org>; Thu, 02 Jul 2026 15:33:09 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1783031589; cv=none; d=google.com; s=arc-20260327; b=W/haG2ZybI4u8txXjYiUByq6CGsfAEgIfSRHzFlh5pSD4BrCMuxJVI8CXOb8OPJyrW DTAVOY8e95wRbcgwR5kv5s9iINj5sNJSdkWaXA8wSqvl7rEDb/TB+SzhnJS4d/KA3Prh 58Ey/FcSMnuVCVyOURYvwwUNdrl74ppcuRIvJgPFHgNrWLiPhDwiXYr8IgKFs5o2PvC0 yWxG0cQnZXqm7msaIUxaM6MDpE5ZZCDqKUahpZ9pfNLgJj44KRaRruUZV/0ngjwGL3jB xo00t3ZS9fcuy/wrdQlvuXbpuXmissc2V1tneEo0mdxsjnwS3TelMd57p1cgy/G3Mofz n0KA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=nt4O34quHjkHe/Wk0JOy/ShuuO851JeTCrZIgdhht6U=; fh=u3Pb6m2o8b7Hg9dXNUE83NHDatWGtDhtqbKh0GhAB6k=; b=e1YUOpV2JLdQKKBoXKIQu458TE6rKtGgyEkRq/xZEmkwQav3RG5+jSZPuyPZaZKhoP sSjmQd/Hf/+vdfdRzQH6vzBXhOvb+cD42qMzNko1hFfIUHkE2ynbmkKGwIoUwtu4UfFx x5WNRd7JOSmAcga7LUJPh5syFcDRSb5KydZv/ZczRnT2DjQ/A5lG41WG1Z7AzuqjIYnC 7IFzmIpaubZxW7qx5JUuuhrpfuSh+GvsHtb/ifzN/jSk4tQ6iraIrhT751wSYd1b74ZG 0MQ2B4LNVUDK4ZLYSVscagd9YCQBuaBFi1f6AtghQ1IPTmJttj5n2+M0B5AhjaFcMfES Smyg==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20251104.gappssmtp.com; s=20251104; t=1783031589; x=1783636389; 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=nt4O34quHjkHe/Wk0JOy/ShuuO851JeTCrZIgdhht6U=; b=U/jnO9nz9k42Z+q/mY0RolFxRNS7CJavtWYR6QQbu5D20ELXvdAI8onqloKmCN7SIW 1cPVvsxxoXQ0CjAsDvslq07Swd+7zAKXIFX2FWv6hC+xQe0JTx2z8+J7QBPFT+1Xcppt 61f++VF8ko+4FWGyrGZCJEVKLzYLagTZSU2v5Gh0o6rRau43PZVdOAe5klwCs1UzXRjm MZt1jnKd+wLImdn8R+7RfapKw8EU63h0Q6P2YRzeM5IUfQK4Gy7625VzEwAjtkmI1n2c TCi1wbpuYDWoNUXCdNZfGxSTt98tS0zVWcXiLTWdj4OhwovCVSoUnehsH0BspRCuaZxq BnXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1783031589; x=1783636389; 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=nt4O34quHjkHe/Wk0JOy/ShuuO851JeTCrZIgdhht6U=; b=BvRbh7y3V7sO6aZ4uILltEBKxx9i3RBCzDLAbO9RzlSZn3ng+E9SAYHmojxYDToIJU j5NqoswlZ8QW/dzsLI1c9lmvAWumkbw05dpcG3DDm39F9dw3j/9bx2n3ESFfcsa2RieS rgNaw9MePTcpvUj+Ibe+PcKYf+TqNr+23XMyaq2xAXFcNPa10zL2yzgUrbGF2VeCLDzy /FgJn/FJU8mVfEN3cRDQyTWtggZx1mLwgL7+49DD3Awug+ZleZn/9ccwLhaRkJmVxLSL oSL6xpAR+yCVgW44sBJRw6/S1CHkAwOkB2hYYsTjU5UoiNctyACw0a4SrkSW549sfJoK zjWA==
X-Forwarded-Encrypted: i=1; AHgh+RruBr0S9EOsP+hGWDRiIG05Tnh75cOJxiIueOdGaNsxJzTE9ZsbgZy7wu4uK8+/+Irtjos=@ietf.org
X-Gm-Message-State: AOJu0YybEcp7ALlib5I9CU0xJxpJvi8t0wJtmjb8H9dQaPKjg2vRtlW/ yrhs7LgvHAVdZDGtr12Pi08zlo5XgFtAsZ/QnIfS0JXeotxZDQWmSA3PQvvrMW/bi2tFqNuuqL5 rku313xXg3vQzendECaPcRWsMWlgVuAYbi+RcfaVOQg==
X-Gm-Gg: AfdE7cm7IpHet07OKjsnQqd8FxsywKTEPJWaWaXvxQ0biywONVQWWwMPerIdw/nyvWh +3BaFlIvmaIZoKIe5lSCg96LjEeFyXugepV5qX7aiC6ep6Q8MvX6K2DYULRpBUx3hfViTqdtBPM vsjdKWYOtIVzFsrdHwqRQwp1SiTx2qrB2i+jrIIHUmi7eeHaI8lDpul0U/b4DEzusHvbUudH7in Tl6sItUIkAZO6X9/M6y5Z2fTYLYH1jj1AdQdGGGJoTqoOQJIba7ZqfzF0JWyZRw8IIgBqIVjzYu /7LyTsMLrQH+np8O+fOdChuUx6lpl82NHaLYe3kkO8ERserYPTT1Z7V1cPa0uQGs3CrUMOoibvB MV9EEa7Awi9Y=
X-Received: by 2002:a05:690e:450f:20b0:664:db84:ed31 with SMTP id 956f58d0204a3-66521a2c6d2mr5798199d50.2.1783031589077; Thu, 02 Jul 2026 15:33:09 -0700 (PDT)
MIME-Version: 1.0
References: <CA+iU_q=8bDayFTsmVY03TmSK9uQjXtxcOrxgC07hXA4kyUtTaw@mail.gmail.com> <CAA+_yBZSDL8fOJ8S-6NTt3yGg-O24Dit3at-KRqoGBcmyZaqWg@mail.gmail.com> <CABcZeBNbPbZ4s0Utjo1rFUMesKEuEz0whGXzUNn3XJ9=GK+C2A@mail.gmail.com> <CAA+_yBZiNp8ip_U8hw7fYqQUGT63cpONMLQr0_cTfn9BjQoMWg@mail.gmail.com>
In-Reply-To: <CAA+_yBZiNp8ip_U8hw7fYqQUGT63cpONMLQr0_cTfn9BjQoMWg@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 02 Jul 2026 15:32:32 -0700
X-Gm-Features: AVVi8Ccjc_WOkzEm2ueXmvlMiVWp-8fo2_SR--IvhxZ4Vof7Xcun9yAjsHounAA
Message-ID: <CABcZeBOOPemsqUV74P67gPM9ijzPbmXB5A84r-Zr_Zf4174+MA@mail.gmail.com>
To: Orr Dunkelman <orrd@cs.haifa.ac.il>
Content-Type: multipart/alternative; boundary="0000000000007d95ec0655a8646d"
Message-ID-Hash: 75XAI7LFCTN5M3RFRSS6PNHANZKXYPAP
X-Message-ID-Hash: 75XAI7LFCTN5M3RFRSS6PNHANZKXYPAP
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: "Markku-Juhani O. Saarinen" <mjos.crypto@gmail.com>, tls@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: WG Last Call: draft-ietf-tls-mlkem-08 (Ends 2026-07-08)
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/ZRl6E7en9rgZnxa_wm21HJ0HODE>
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 Thu, Jul 2, 2026 at 3:06 PM Orr Dunkelman <orrd@cs.haifa.ac.il> wrote:

> I beg to disagree.
>
> Because many people don't see the difference between them (and yes, I am
> aware that this is an informational RFC, and yes, there is a code point
> registration). In many instances people just follow the standards, RFC,
> ISO, ETSI, and don't care whether they are informational, mandatory, or
> otherwise just a standard that is there. Many people view this as a seal of
> approval by some standardization body. And I believe that such seals should
> be given less promiscuously.
>

This is a reasonable position, but what your message actually *said* was
that 9189 "should not have been standardized". It was not.

Moreover, as I observed in my previous message, 9189 went though the
Independent Stream, not the IETF, which means that it had nothing to do
with the TLS WG. Even if the TLS WG declines to publish this specification,
the authors will still have the option of taking it to the Independent
Stream. In fact, Simon Josefsson suggested they do this yesterday.
[0] FWIW, I agree that the existence of non-IETF RFCs is confusing, but
nevertheless it's the situation we are in.


> I think that there is value in simplicity for security (and I think that
> the technical claim that simpler = better is a good point for the proposed
> informational RFC), yet, one cannot hold the idea that simplicity = better
> security, and not realize that outside IETF, once something is RFCized this
> is considered by many as an RFC. BTW, this just proves my point - once
> there is a code point registration, then now, we must have a way to
> "satisfy" this.
>

I do not understand what point you think this proves. I don't think I've
heard anyone argue that because there is a code point we need an RFC, and
all I'm saying is that the nonexistence of an RFC is not going to stop
people from implementing this specification.

-Ekr


[0] https://mailarchive.ietf.org/arch/msg/tls/SABh7Sw1dqdv_I04WFUeQByoVVY/

On Fri, Jul 3, 2026 at 12:50 AM Eric Rescorla <ekr@rtfm.com> wrote:
>
>>
>>
>> On Thu, Jul 2, 2026 at 2:39 PM Orr Dunkelman <orrd=
>> 40cs.haifa.ac.il@dmarc.ietf.org> wrote:
>>
>>> Well, you are right - RFC 9189 should not have been standardized.
>>>
>>
>> It was not. It's Informational and It's an Independent Submission/
>>
>>
>> I would guess that once there is an RFC that says this is the Kuznyechik
>>> block cipher (namely, RFC 7801),
>>>
>>
>> Another Independent Submission.
>>
>>
>>
>>> it is a bit harder to say to people - hey, this cipher, which appears in
>>> an RFC, cannot be used in TLS, because we found problems in the cipher.
>>> This is why whatever was in ISO _before_ the issues were discovered, was
>>> left and not removed, whereas the new stuff was not accepted.
>>>
>>
>> As a matter of policy, the TLS WG has a very permissive policy towards
>> code
>> point registrations, essentially only requiring that you have a document.
>> The
>> rationale behind this policy is that forbidding people from having code
>> points
>> for algorithms is not an effective way of restricting their use. In
>> certain cases,
>> once the WG has decided that an algorithm is insecure we will forbid their
>> use (e.g., RC4) and mark them as "Recommended=D", but we don't do that
>> as a matter of course for algorithms that are not widely used.
>>
>> I know I'm repeating myself, but this is also the situation for MLKEM;
>> there
>> is already a code point registration. All that is being discussed here is
>> whether
>> we will publish an Informational IETF RFC specifying it.
>>
>> -Ekr
>>
>>