[TLS] Re: Scope of the IAB's appeal response

Nadim Kobeissi <nadim@symbolic.software> Tue, 14 July 2026 12:36 UTC

Return-Path: <nadim@symbolic.software>
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 2BDD51167AC74 for <tls@mail2.ietf.org>; Tue, 14 Jul 2026 05:36:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784032599; bh=bntB225QvN02oUmlB517VuwUoLxzOL4vrInR/uOBSAk=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=h5dUXgqwMQvCCxFrAao29VXmJKp/+x98Y0hNeSjPsYPCJ0xDR+x4a3PyplKxJjGEj Zk5aBtdtC/z/WzkRNGMhGsKxoKJqmZPKb8K+20cu0GnDOvolntCbNk+oaHaYxUvY8F he+ohqveqF0LDbpZcq28OgY1TaBSTEIb5sp67/98=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 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, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_LOW=-0.7, 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=symbolic.software header.b="m2toBAkc"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="h+DerrBQ"
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 F-m3WOTZA1F9 for <tls@mail2.ietf.org>; Tue, 14 Jul 2026 05:36:36 -0700 (PDT)
Received: from fout-a5-smtp.messagingengine.com (fout-a5-smtp.messagingengine.com [103.168.172.148]) (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 459A81167AC6A for <tls@ietf.org>; Tue, 14 Jul 2026 05:36:36 -0700 (PDT)
Received: from phl-compute-04.internal (phl-compute-04.internal [10.202.2.44]) by mailfout.phl.internal (Postfix) with ESMTP id 8B95BEC00C5; Tue, 14 Jul 2026 08:36:29 -0400 (EDT)
Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-04.internal (MEProxy); Tue, 14 Jul 2026 08:36:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= symbolic.software; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1784032589; x=1784118989; bh=4BbZcf15Wu +JybETHKf2IK9ZkND3UiFDdVa0Fif673U=; b=m2toBAkc0MXvRe4qroKpB2Lkb4 DFu2CCfhI8LsPsT12xfUdNSoJAIXj4m2yQNWnhA+OBTkb333LQ0MkVypvI0YLjgx QxGRACYl3ufG0hIh+sSOJ+ey+B4DINzex6azEsiNGgVzd1cJJUH2LsMeyGYnjgFS orVqSViMby90Tg/6upecLMYGkRcvc2Rwv0suuQW50Iku80RJmczKuM5zoFPrxmYm PyRkmIuOpI8jPgP2hcECIBP2Vf9PKMna5ImbpYmq5L/e+1RKPiM/psRri9GrfKqk uDPDD9fSzVkFw2Lt+uSIK6nRpBXv+aKudaLgyQKd0FvAGj/YP46rcKA22Dhw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1784032589; x= 1784118989; bh=4BbZcf15Wu+JybETHKf2IK9ZkND3UiFDdVa0Fif673U=; b=h +DerrBQFvSvoYSBU53RuOAKLnnx3bIM9t0yT+Ff7PJOiW650PQU//qYvGBranoTt lFiu8o04dbF1gHv33IVgiobz6GK/p3XEn+fzYdYDc1Ug3A/m+4JGn5RzMcuIwaQ4 kULLujC60Dqaiyn88CxSdJz8PG3w9La198QPCJKIG4FiZasgW92opyYg+PwgUeWy S/h5OdpYgjtrInf3vfZgAHVe6z8ZIujzHSSJ/u/EtmNxckXKlMde//JTCbS4JLWi S3Pzr93Ptbayh1PyqThoqcImWeJCDLcoRn+U4GG/19Y5rZ6i6EPxkKho1TEHb/Hx dX8Doly4Zxp9UrSMg+vJA==
X-ME-Sender: <xms:TS1Waos2fwSmQSCspe8LtU5eGu7MqzG_hx12FKAd1g-p2pioP2jOaA> <xme:TS1WahwI-sgFaUURI4BQX_5uvgMd_g3mLpB3wMYLe8bQGYwA6dodFh9ep0Xe8K8Mo IDz4E-anAiwpKjsa2x1BdvWkkZFzca_sXBuujsmdcCC9E-VxG_hg3Q>
X-ME-Received: <xmr:TS1WamiljQbey4X5EZC87aud2e-nk-P5xr5U9JLQ_YyJOs_xFNQ5r9DE4nG8ksYsNSM>
X-ME-Proxy-Cause: dmFkZTFwBt1qP7v2/0KU7lks2FGl3+UT3Y+9fnyvgrUTQdJVPrISyUGdPLPzgaL/l5MpHl wkc7bFPCPg7Mcv6mTaP/WKUFx8+jevW5MHbW9aCX7nVhTulUUr2P2+aiBuufrg+bSWw4/A iEauPwKVxbkuPGiJkN0YupS6c5tavDuTN0F8z38LPcfumjS42uh4BUygzwIdtB/cn3iVgl HR+CIEguZTVk2XnBy+SqEaOg9DIN9CCF5QMZBoTw9P8sOY5YUMmEpD1Z4flXspbz6gXNxN /IL5O3OywDA2e6338Pn0Onckiy5cIpzsJTRcr62J0cn0CbKj/eVbgPHxT+Tme9xE2aL0Yl Vqo+FxmxBy9hP3291rHNauQ2zATsIg7oMJQNHj3u6JvrQrjYF3T7htSk/g6AXR5cQuu2lv 191FwvkmND4qv02oKkhbuJh58NxszH2/oD6XXYHyQQHAipXj4H13mISBWjdeTBTnIiuaQ6 S5FVsjm7MDFP8FTjha84rgmcPgMMFBqS2oUcQgFqU7tzENUGW1az+ObYm+FhAnCzUWvMvc 84zhYdbtifQxNUywwf2F8ctTAKptKo2yn/StZZArOM8egzVUi6JUUF7ynZEwGSzGtQIUWx m8m9I02uLUFRnsS6xiwlVKXGa1GT2Ns1Npiec900fEc9didEvYJ1L6k+/LQw
X-ME-Proxy: <xmx:TS1WatB8XpE1X3VwKNreX1wuwFL78dyoc7r4870SGUhVics566928w> <xmx:TS1Warv6Zm05PFD6-_sHMrP0CKHQTTHXVaW0jJ5tDfk2RmXAux1ZQg> <xmx:TS1WaqYMW5ArDOyI2pNL7wQsIP4_9filp5tEdeI-1U_Z5ZdFRji3rQ> <xmx:TS1WamUE8MpsfHRDlTBrJuK24F1Llz9jYT0zFZ7rHmu2-e7DGd7yBw> <xmx:TS1Waqo79_aaYrHTszcIryC-jkZnctD7h9fBkz7wLhuozAZEaTXQWNl7>
Feedback-ID: i6d3949ed:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 14 Jul 2026 08:36:29 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-1D1D1AA4-60BB-4197-8D3B-1ED08CAFCD47"
Content-Transfer-Encoding: 7bit
From: Nadim Kobeissi <nadim@symbolic.software>
Mime-Version: 1.0 (1.0)
Date: Tue, 14 Jul 2026 15:36:27 +0300
Message-Id: <A5C05EAA-3C14-4204-B594-2CD2B73948AD@symbolic.software>
References: <CA++PRG1-LoHW4nX75opFdR3BsxVcfn7b4r7sKSa1OFvqLcrP4w@mail.gmail.com>
In-Reply-To: <CA++PRG1-LoHW4nX75opFdR3BsxVcfn7b4r7sKSa1OFvqLcrP4w@mail.gmail.com>
To: iab@iab.org
X-Mailer: iPhone Mail (23F84)
Message-ID-Hash: JX7T6O3Y34EUUGS7IR4Z2R7F5L7MJMDP
X-Message-ID-Hash: JX7T6O3Y34EUUGS7IR4Z2R7F5L7MJMDP
X-MailFrom: nadim@symbolic.software
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, iab@iab.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Scope of the IAB's appeal response
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/ORUYM6KIs8JRR9NyHMoQRHN_yus>
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>

If the determination of rough consensus of the WGLC from earlier this year is real and legitimate and not overturned or anything like that, then why was a subsequent WGLC held and concluded just last week? Why didn’t we just adopt during the one from earlier this year and settle the matter then and there?

I would appreciate an explanation and apologize in advance if I’m missing anything obvious.

Thanks,

Nadim Kobeissi
Symbolic Software • https://symbolic.software

On 14 Jul 2026, at 2:52 PM, IAB Chair <iab-chair@iab.org> wrote:



TLS WG,

The IAB notes that its https://datatracker.ietf.org/group/iab/appeals/artifact/310" target="_blank" rel="nofollow">response to Daniel J. Bernstein’s 2026-04-24 https://datatracker.ietf.org/group/iab/appeals/artifact/272" target="_blank" rel="nofollow">appeal is being cited in ongoing working group discussion. To prevent that response from being read more broadly than intended, the IAB offers the clarification below. It takes no position on any other matter now before the WG, its chairs, or the IESG.

The IAB denied the appeal. It did not find that the chairs' determination of rough consensus to adopt fell outside the discretion that RFC 2418 affords them, nor that the responsible AD and the IESG acted outside their process role in declining to overturn that determination.

The relevant observation regarding the responsible AD was narrow. The IAB noted that the initial characterization of the adoption call by the responsible AD did not accurately describe the record, and that a more precise account followed. It was offered as encouragement to chairs and ADs to take care when summarizing participant responses. The observation concerned the accuracy of that account, not the intent behind it. It was not a finding that the responsible AD acted in bad faith, engaged in misconduct, or breached the IETF’s conduct norms.

The IAB has also seen its response read as reaching conclusions it did not state. The IAB did not determine that consensus to adopt was absent, nor did it overturn any consensus call. Its response should not be read as reaching conclusions on matters beyond the appeal, including the subsequent working group last call or the fact that a different Area Director became responsible for the working group.

Dhruv Dhody,

(as IAB Chair, for the IAB)

_______________________________________________
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-leave@ietf.org