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

Dennis Jackson <ietf@dennis-jackson.uk> Fri, 31 July 2026 14:22 UTC

Return-Path: <ietf@dennis-jackson.uk>
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 A8ECC121A8A08 for <tls@mail2.ietf.org>; Fri, 31 Jul 2026 07:22:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785507755; bh=N+/RMxQDH92aXKySXS6HScFBBKUnWgVhXa4c20blD4Q=; h=Date:Subject:To:References:From:In-Reply-To; b=hiMEarxV2MXkt3QAy0mKquR8DU2IYFD1Jun84Abbly59E/PHcIXhPuZp06oxnd5iG NP+0tV7n5M6K1Ng8RqWySBhWpyjZ+JrKpPMEXTDLyZFo8Wxiqodrkwx52kj9KvMCBu kHhQGeSnXThdNZ+WK8LwE4iWju/kvHGBddou4I9s=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=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=dennis-jackson.uk
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 GU2o9_5g1yb3 for <tls@mail2.ietf.org>; Fri, 31 Jul 2026 07:22:34 -0700 (PDT)
Received: from mout-p-202.mailbox.org (mout-p-202.mailbox.org [80.241.56.172]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8D72F121A89E0 for <tls@ietf.org>; Fri, 31 Jul 2026 07:22:10 -0700 (PDT)
Received: from smtp1.mailbox.org (smtp1.mailbox.org [10.196.197.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-202.mailbox.org (Postfix) with ESMTPS id 4hBStw5mlBzMlHs for <tls@ietf.org>; Fri, 31 Jul 2026 16:22:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dennis-jackson.uk; s=MBO0001; t=1785507720; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PUUGIxu7RzErIXAoM6ciqw+fS7stiNNC6HSZPH+k/II=; b=cLoSRGYeW4QtnMrHdrsrOV+1poyZDJ5Cca1uEnEuxal8sUFpo8WCkOfmjoGXOYuXjKdwO8 v4TbqPeMWeXPVj5PCsvvVewC7j87bQtlZhMDPtiQJH6SO6rf4yuvSD3TBThSz7Qfz268dd 8f8kkMDg+Y+f3Uashwsf63BcAvczTtUL1vR/3wlmNoClCMqnuQNB+BbHs1px/TC/f5i22Z 0wcYDS7y/9T2pqOiSV21LP7zplyE8KruwBA/LBNYY1E9n61+qFAEy0bfNNvypsb7IbA5FL QibYsui4ad2zkunUrEn+c35fXl30sZTSBQnywWqkcMMwi3jF9O0AXK6EkBlNpg==
Message-ID: <d38b83e2-8b57-4544-baa0-b10b9360e950@dennis-jackson.uk>
Date: Fri, 31 Jul 2026 15:21:58 +0100
MIME-Version: 1.0
To: tls@ietf.org
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>
Content-Language: en-US
From: Dennis Jackson <ietf@dennis-jackson.uk>
In-Reply-To: <amypaHNTh0Ya7XF+@ein.win.tue.nl>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: W52FLWRHCDMKBJOU4HKHIMC5Q32M4XB5
X-Message-ID-Hash: W52FLWRHCDMKBJOU4HKHIMC5Q32M4XB5
X-MailFrom: ietf@dennis-jackson.uk
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
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/_-xsdwX4Pae20P7pLD_MqWJ-Pvk>
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>

The data is public. Do your own analysis. If you disagree with the 
outcome, the process for appealing a chair's decision is well documented.

On 31/07/2026 14:55, Tanja Lange wrote:
> 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