[TLS] Re: Improving the quality of the discussion on the TLS email list

Orr Dunkelman <orrd@cs.haifa.ac.il> Fri, 31 July 2026 17:10 UTC

Return-Path: <orrd@cs.haifa.ac.il>
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 13F67121C2CE3 for <tls@mail2.ietf.org>; Fri, 31 Jul 2026 10:10:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785517823; bh=b5TxUcGpKPpenpp/vq3QtjFS708tHK3RoSko3OsUUeQ=; h=References:In-Reply-To:From:Date:Subject:To:Cc; b=h5l59fyV+6ujT4rtUAnCzcamTMCw8VBoum/6teWzC6895f+Q1ANch1fh7vhCoz/QJ mZXhD1LhnGS0sXwjxk8/x4EUy5GA6uAkyvmW3RxTM7ISwD5mTAUYf5T7wPcRgkaHqM WygOKlYi9ivS4e5tOulvv1LoDem3BsaiawC1qir4=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 (1024-bit key) header.d=cs.haifa.ac.il
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 4J3k5RDbKpFc for <tls@mail2.ietf.org>; Fri, 31 Jul 2026 10:10:21 -0700 (PDT)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 CED2B121C2CD3 for <tls@ietf.org>; Fri, 31 Jul 2026 10:10:21 -0700 (PDT)
Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-c15d111ca99so136747766b.0 for <tls@ietf.org>; Fri, 31 Jul 2026 10:10:21 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1785517821; cv=none; d=google.com; s=arc-20260327; b=GofzIqbrwKyToCDzVmQGfL95PRDRCvvwVecd3wpngqWC512Yqdqx2IIe6g/Gtsf/Pk /Pvg5sPqzlh2q16VcEmQZgKcRFo1k3xwepoWAU2UF7rjaboO1JU9u9ioruqdyTDSQ2sm 3NvdflQq5h2lxvy1nIJeygFpDz8HOJ0sZ93LAF40IUiov8gsfxq2ALOX7JtEsC6jFPtl pL5as3q74wQz34NVcfUPS2F/mMygiIOiHORupLCPnLVisEUTglZwB3keaPG9tsONhlLW 2GQfKzgUR+zvgq6GVw7H9owXu956CHTXnSDghjPCXn9Mg+e2DH5U4BUNOlb49OyiKxoN +TdQ==
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=h4asaDjTpGva8NZzAQ4keEaEFzFAuA50OQGclr5lj40=; fh=dtcubjZ8hdZg72sp2YBbzmxsqVuuGOCvr+QNaSEocNA=; b=IZ7ts4nlhUcGdJAS0CURIYTo+shVrcNtzK7TIEVtFfHUD+882+4w+BrtfWIM1Zk+g2 iZdsrNe6Aov/f1M6fy1R2oqA/BJJaqSG4+3OFD89wH1uqQL8a8AfLqr49alAI9xa+agm /ql71V1SOM+3fczoy8+7K+n9KBZbneSOkTIBePTXjc3CmUyDzSjp7FhApEytBiUKA9ZA yddyXdn6MisaEbVZJ3y2EUBvgmx9Qh/rH+pTmaJwHAxKb0x1oIMCw7lDo/7pm1r1VZ5t hhMLB9yJdTfkUAhqzaBOVhn4F5S6+QunWxpFo1xcrfkYX2rh75y+t9sSocq0pMPQCh+S Pe5A==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.haifa.ac.il; s=google; t=1785517821; x=1786122621; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=h4asaDjTpGva8NZzAQ4keEaEFzFAuA50OQGclr5lj40=; b=hssCYe2JeUk6JLQMLxjlbpN1S/Q0378rsJSTZ6C7Hq/FE2aY+4xzSY0WfJ2uHq3nJO DAKvbJV6zYOqNLzfP9qaJjq8TB7mFN/m81nWO1l56lr5YBslo7SfWX1Zyz8dxeHZLGQq y5kPM0heEWeErYpf2N/LjH01VnIRx1jVhZPG0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1785517821; x=1786122621; h=content-type: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:content-type; bh=h4asaDjTpGva8NZzAQ4keEaEFzFAuA50OQGclr5lj40=; b=F9vK2krrEnYrxOiKbUsyIS8Z4PXerFL+YMXY8Jas7kfcZgqhryZF8hKuDs67s0d6Rn IicUOwI/MFrHMA+RwJ6uvvJfHq5M7wE9/cAulvQ9fb80TY+9RnjUf+5MK9sP721ZYAuY jsmtIxozNpXDzZGNS7NHy1L45BUPxE0RkxSps0d+M3maH1est2iXiYYCRWZnspEwNWwa PWQoUu53ua2iEUzxHsMm4QJbUoUdijJKwm2trRt/3m1THR6fbeAJQ35+OzfM3a+04xOC AriXTczlyMu9aUhTWLWPAsnm3QXl1dOsrcKE7RgrAUNTxi8Zd0Wo5wXDgZSVEQbN0FK3 +8cQ==
X-Gm-Message-State: AOJu0YzKlepBfzeQZNDSgfAoX2HGrd69wCRQu//xCwTUIyRe7J3lQYmE jOkir28egK5MajZoLCm86qTTNAm05U/FFZnjKlumIlDUcd+tDVr8yFAL9Uq3JDAvbLQN/G8DOzK NTstSMVJQ13VP32yhmuxPV1ZCTH8tqzk09hkJj+9C7h5S0FOZnot6
X-Gm-Gg: AR+sD12lOZekWTbooTiGKsZ0nqQvJCgFcB9yYbfcAqZd0Mz8WQL3HxQnR+dvx42XT2T E3Qzfo2Q9hGjBfDiJDRuZAMKSHuXIcWqfSHk/E3NU8A3Ci+Xe4plyxAv6Y+QMgh5fzmlxe/am4a j2kMtMSaA37Zm6s1QM7J2EXXKoyBXMa88qe9oqMuykDOIZesS8G7dLBum3eBrz8k1pzHbmWYc4I ZZwsGxUESiJM1ZS8/CB5fSGiY7wzpQmTyxn00oSSp7yVxcDkoMj4wJhyFxeK9jqRH6gnheaxGzp LOTU9BIAe1GvqwZHE+4VA1w8nkPRAC450NboXD/Sz/Adcaz5sGcQbnikFdz4xZMqx9vOuuc+2gQ nbja6UoNDUayb5bznS3BzCmNnG/Wo8EjlQ17niQNfh6OuNIscov4rRR/CwB0Lo7AZedaGwnYW9M KYygGYHShKywr5QMOYkGMEY1fTGA==
X-Received: by 2002:a17:907:fdc1:b0:c1f:9b99:971 with SMTP id a640c23a62f3a-c1fe82bc39emr32728666b.48.1785517820620; Fri, 31 Jul 2026 10:10:20 -0700 (PDT)
MIME-Version: 1.0
References: <CAEzBKQ4fymnSeo8tgqMLOfKopvMGk4xnDq=SQJKf-RBL4-uh6g@mail.gmail.com> <CAEEbLAbhZUpempA9Rvjhm1qrLfBWXa_2ntdfpO20cqDu0h5fbQ@mail.gmail.com> <CAEzBKQ6NOzQc66T+SEdSvLa2gxjtO77DYUUWuTfr99zV_a-Ofg@mail.gmail.com> <c8a74833-35cd-44a0-8992-e5463a82aa8f@dennis-jackson.uk> <F95592F7-6E60-4835-B21C-B5B1954084F7@kenkubota.de> <b3321e23-5f9b-4f8a-8bd9-d2cca2800d67@lear.ch> <amypaHNTh0Ya7XF+@ein.win.tue.nl> <538b6162-6cbb-4051-9810-601b29f880fe@app.fastmail.com>
In-Reply-To: <538b6162-6cbb-4051-9810-601b29f880fe@app.fastmail.com>
From: Orr Dunkelman <orrd@cs.haifa.ac.il>
Date: Fri, 31 Jul 2026 20:10:09 +0300
X-Gm-Features: AUfX_myDoXhU59g5hvSAff1Qq7gEg3jddpp8MpSzCtge4gyYoEHXR7QMHEBxBms
Message-ID: <CAA+_yBYWP_3MOcTM8FH8wjiif_L_WLOPVHKnp8nVmGJzFiCCpQ@mail.gmail.com>
To: Filippo Valsorda <filippo@ml.filippo.io>
Content-Type: multipart/alternative; boundary="000000000000705ac60657eb4307"
Message-ID-Hash: IJ2GSUYZK4DY66NRCKRJ2FZKZRACNQPQ
X-Message-ID-Hash: IJ2GSUYZK4DY66NRCKRJ2FZKZRACNQPQ
X-MailFrom: orrd@cs.haifa.ac.il
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; header-match-tls.ietf.org-1; header-match-tls.ietf.org-2; header-match-tls.ietf.org-3; 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: Improving the quality of the discussion on the TLS email list
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/3pMbxvdca-lpwpEoJMHBdfE_uG8>
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>

As the ADs did not publicly release the criteria relevant to what is
considered "prior involvement" (would participation in one discussion
before the ML-KEM sufficient to be considered in this set of voices?) nor
what are the "experienced people" they deemed to be worthy of being heard
(i.e., newcomers who are experienced), it is a bit impossible to make the
statistics you have asked Tanja to make. Actually, even putting aside
mailing issues, moderation problems, and assuming that indeed all the votes
were indeed public, no one but the ADs can make these statistics. This is
exactly what reasonable people asked for in this mailing list (including
people from academia, industry and government) - to get these criteria
publicly available. Hence, contacting IESG, IAB, the UN, or even the local
fire brigade, is useless until the ADs supply this information.

Furthermore, during the discussion I've pointed out that one of the
co-designers of MLKEM found the idea of standardizing only MLKEM to be
premature. I am sure that when assigning weights to participants, one of
the guys inventing the thing (and especially as this particular individual
has years of experience in industry, so this is not just a theoretical
computer scientist with no understanding of the real world), should
probably get a somewhat higher weight than even people who participated in
past TLS discussions. As the ADs did not report counting this specific
individual's "vote" (that says that the entire idea is bad) it is unclear
whether it was taken into account. Actually, I hope to ask all the relevant
co-designers when I meet them in future conferences [relevant by my own
personal secret criteria].

Cheers,



On Fri, Jul 31, 2026 at 5:36 PM Filippo Valsorda <filippo@ml.filippo.io>
wrote:

> Excellent, sounds like you land at the same result as the chairs when
> tallying support by all participants. That’s promising!
>
> Then, have you tried tallying support by “pre-existing WG participants or
> people with demonstrated expertise” using your own methodology? Did you
> land at a result significantly different from “roughly 7/10”?
>
> Assuming you’re not looking a priori for something to object to, if you
> come to the same conclusion using your own methodology, I don’t see what
> good demanding an itemized list would do.
>
> If you do come to a significantly different result, you can share your
> methodology in your appeal, and let the ADs, IESG, or IAB assess it.
>
> 2026-07-31 15:55 GMT+02:00 Tanja Lange <tanja@hyperelliptic.org>:
>
> Dear Eliot, dear all,
> I can tally the emails on list, which were about even in favor and against.
> The chairs announced that by some process of discarding or weighing some
> votes
> they reach 70% in favor. To quote this verbatim
> "However, if we look at pre-existing WG
> participants or people with demonstrated expertise, roughly 7/10
> WG
> participants favor advancing the document, which shows rough
> consensus
> to move the document forward."
> The requests I've seen, starting right after the chairs announced their
> decision that there was consensus in favor of the document, are asking for
> which input was discarded or counted higher or lower. I cannot do the
> "homework" of checking this because I don't know the mechanism used.
>
> Additionally, the email asking for responses was sent with
> Reply-To: Joseph Salowey <joe@salowey.net>
> so that replies would go to Joe's address and to the list only if the
> sender
> chooses to reply to all (or edits the header manually), so there might be
> some
> emails that didn't go to the list and which therefore I cannot count when
> doing
> my homework.
>
> Finally, there are reports of messages not appearing on list despite the
> sender responding with the release code. We have seen some messages
> containing
> release codes appear on list (I hadn't seen that in any previous
> discussion).
> My understanding is that the chairs see those, and maybe that's where the
> chairs saw additional support, but I cannot count these in my homework.
>
> Hence, I would like to support the request for transparency of how the 7/10
> (quoted above) was reached.
>
> All the best
> Tanja
>
> On Fri, Jul 31, 2026 at 01:02:26PM +0200, Eliot Lear wrote:
> > Hi,
> >
> > On 31.07.2026 12:37, Ken Kubota wrote:
> >
> >     There have been repeated requests [1, 2] that the working group
> chairs release the participant chart/list/table publicly that supports the
> 70 % claim ("7/10 WG participants favor advancing the document" [3]).
> >
> > Unnecessary.  All the information used by the chairs is publicly
> available on
> > this list.  Do your own homework.  Stop making work for others.
> >
> >
>
>
>
>
>
>
> > _______________________________________________
> > TLS mailing list -- tls@ietf.org
> > To unsubscribe send an email to tls-leave@ietf.org
>
> _______________________________________________
> TLS mailing list -- tls@ietf.org
> To unsubscribe send an email to tls-leave@ietf.org
>
>
> _______________________________________________
> TLS mailing list -- tls@ietf.org
> To unsubscribe send an email to tls-leave@ietf.org
>