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

Andrew Lee <andrew@joseon.com> Sun, 28 June 2026 19:22 UTC

Return-Path: <andrew@joseon.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 1056D109544C9 for <tls@mail2.ietf.org>; Sun, 28 Jun 2026 12:22:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782674539; bh=4OKnkfMyr1z6/8G347E9RdnhdQTxkqi5PVDvoDW+CM4=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=iCq+utHfnYOCeGvBqRckgvi/2MmgkDLsipRanQw7Z4yIm8hgVrleaJl/iuK3O+pod nJhinIE2/m0zOyWkHgaq5qAkNMij6PCAzpNyV1I3a84luFBzmEf+ZzHc0H2COTysDL XO0lBQNWdpVthB/ABAPapsLHHweDcLEmokcI/5Rk=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=joseon-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 pcvZcWVvEF9u for <tls@mail2.ietf.org>; Sun, 28 Jun 2026 12:22:18 -0700 (PDT)
Received: from mail-dl1-x122b.google.com (mail-dl1-x122b.google.com [IPv6:2607:f8b0:4864:20::122b]) (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 19C6F109543B1 for <tls@ietf.org>; Sun, 28 Jun 2026 12:22:01 -0700 (PDT)
Received: by mail-dl1-x122b.google.com with SMTP id a92af1059eb24-139b5e604b9so3068180c88.0 for <tls@ietf.org>; Sun, 28 Jun 2026 12:22:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joseon-com.20251104.gappssmtp.com; s=20251104; t=1782674520; x=1783279320; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=4OKnkfMyr1z6/8G347E9RdnhdQTxkqi5PVDvoDW+CM4=; b=QONqVzdFsWVYGkfNrKWXddxBy1Td3+DUSRLfjw+4ZQV1zZyqLoDuqOFwoRl4nPAi60 n/txraJy9+gdj19KTJs+/aQTVK68ZgK1fBLq43Ktibb8NCyRBOfrHCq5GQaqooBR7D89 Sy1MinhRAJi/hJSt+oPcAl7jA+5LgvUUvmw9aM89nAAqHq5e0oYlRurxGfiobJooLq60 Y7FKiTcCkBH25XGg4HQIwGBTMJ3ZidecvX2BIBh8BULADwJQWWxAFRcwnJhJwF/IHPGP lvx6aw5wSag4XIMnoV82LC5eYgvpz6JSWayVjq4cgxU+FE1WkBFaybmip00G6pYqT/9Q xOqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1782674520; x=1783279320; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-gg:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=4OKnkfMyr1z6/8G347E9RdnhdQTxkqi5PVDvoDW+CM4=; b=PBxkgsmNVNFi8H8FH+8I3zGGSWzPRVc+gvbvxioj8bLZXy9ZfwpQXLRycq4sgcsU/X dRi6Tr64Qw7hry5b4MRpapvUzgbYYKuHT2wVv07uP6HfU4p0DXZNv/Ss/ZMqIYB6ti7r sPwVOPEiLuf/+rRNbtmrM82otAFdvIsxAyUjddu+goSJdmWxbVqUQt5pvDXSMmfYQC9d MSRUE6mhyzad6OIJ6hgLoctFParcOYspWB+gluBkOYMejXR6Cp1D+H5lxP2Pn5Icg/Zt 5j+fO8zwhdoycoCP8HRI8Ao2zyFguRkq10Nfp3mpq2LYa5ZUaAllIrdBDnB8nAfRbhuu Qhaw==
X-Gm-Message-State: AOJu0YwwpKCz9S+/2DNXGDSWBwOeGsJMs81I082duKlCeXYxchUw7X3G ek91c+QGd2uZ3HEJbySkcxHb/SufatSb90Mh76nmv+hqxJp0MUE58Y/yrSxRJrxONtkd7SG7G3s 9V9cN
X-Gm-Gg: AfdE7clLFvY5S4ljjzX+j9xSp2DckIZd741IHrDucFoyiGu2mVcw7WO/7CEL9iaXEW7 GC8yIYE4tu3ZELrqxPJG0ID3pKPDL6gd2WENzyrXYK6mnFa9iReJJsapGMOfXwACQ/LKVGU0pDy npwcdFMNMmUrO7Ghwxj9Qzlt2Ql9vha9XdTxznmX4u0wkTwemdJ8nXANRkt5n4J87jvW8djIBIV FMCTmRBoDO6SPdqlyKfpAaTzvBJr3M1/VcoMDApxXTgWPjSOJlpt7/FIe+sI3g+38f0NmtbCuPW j+cT1rwdA+m55PRMEmPepD4v6S5bzE2O9J2d27isdTokzaLBTi8JMXNXXOVw85ww2OBCJauPaS1 g5SCPH0DJTZDHIbgpqtTOffh08wpIO01IjVjLxJne9Apd8WGl9wKjNJbyogMV7zVYurq9Dz35G9 a643vV0HU54jWLubVqjb+IsOJqcxHbcAqxr/MTqNsPa3/PzOwVZhopJJw=
X-Received: by 2002:a05:693c:37c4:b0:30c:1865:d9f6 with SMTP id 5a478bee46e88-30c84b2b6dbmr14399613eec.6.1782674520033; Sun, 28 Jun 2026 12:22:00 -0700 (PDT)
Received: from smtpclient.apple ([192.69.242.2]) by smtp.gmail.com with ESMTPSA id 5a478bee46e88-30ec79d4746sm5912048eec.13.2026.06.28.12.21.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Jun 2026 12:21:59 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\))
From: Andrew Lee <andrew@joseon.com>
In-Reply-To: <490D59F1-4C6E-49C6-B20E-D6BE7A9CD81E@joseon.com>
Date: Sun, 28 Jun 2026 12:21:46 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E369E192-5A1C-4DD1-ADBD-F7239104CFD3@joseon.com>
References: <20260628130106.4149044.qmail@cr.yp.to> <1D346E3A-DBB2-481C-8E3A-C2E50B8EF05E@kamilner.ca> <63cb257a-3492-49d8-988d-bee1687f2839@app.fastmail.com> <490D59F1-4C6E-49C6-B20E-D6BE7A9CD81E@joseon.com>
To: Filippo Valsorda <filippo@ml.filippo.io>
X-Mailer: Apple Mail (2.3818.100.11.1.3)
Message-ID-Hash: 5JO6V2V6AGJ4EVT7K2Y7UYCILN36JJTV
X-Message-ID-Hash: 5JO6V2V6AGJ4EVT7K2Y7UYCILN36JJTV
X-MailFrom: andrew@joseon.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
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/fwtYE1uTA8eCKruMSxiiZpX3RJA>
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>

My apologies for my follow up e-mail that should have been included in my previous response, but I also wanted to caution that there is insufficient evidence to make the conclusions as opined by the accuser. It is a deliberate attempt to both create stratification/classes within the IETF and, further, could be construed as a form of gas lighting, or worse defamation, due to being presented as fact without evidence.

Again, when an IETF vote/consensus gathering activity skews into this level of mudslinging, consensus is unable to be declared appropriately by virtue of what rough consensus is.

I hope everyone can cool off and discuss this on an intellectual level as it relates to the identified risks of solo ML-KEM and procedural level as it relates to the IETF.

I definitely don’t want to see non-evidence backed accusations being thrown around on a large public mailing list on my Sunday morning.

Cheers,
Andrew

> On Jun 28, 2026, at 12:11 PM, Andrew Lee <andrew@joseon.com> wrote:
> 
> 
>> On Jun 28, 2026, at 11:45 AM, Filippo Valsorda <filippo@ml.filippo.io> wrote:
>> I'm not the In-Reply-To police, I was linked to what amounts to an external influence campaign, so I made sure the WG was aware of it and correlated it to the three (now five) most recent emails that are consistent with it.
>> 
>> Not sure how "the degree to which individuals have participated in the WG in the past should be part of how their opinion is weighted into calling the consensus of the WG" could be interpreted in good faith to refer only to opposing opinions.
> 
> I’ve seen these alleged “influence campaigns” both ways with the most egregious, and quite recent, being an IETF chair both influencing and launching a personal attack on a contributor. It was and is as appalling as it sounds.
> 
> Long story short, pointing fingers doesn’t amount to much and is a significantly lower standard than I’d have expected within the actions of those who dress themselves as mature IETF participants.
> 
> Frankly, given this mudslinging has already reached these depths, it’s clear that this topic still needs further debate and discussion.
> 
> Rushing the publication of this document under this environment would be careless at best, and unfortunately, quite far from IETF’s own procedures at worst (and a whole lot more).
> 
> Best,
> Andrew