Return-Path: 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 2B2C0116863CB for ; Tue, 14 Jul 2026 06:18:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784035099; bh=/u5q54Pk3T8dCX46ku9/x/37bLE4bI/FiE66Kyw2CZw=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=Hc5o4yGROvR10O6EM7oE+8hKrIqTQrA6hUe98vkiX+82TKJWCTVmoQ/eHuFf5ttAV HUoD8Yki2g8t9a9gm7meAw/zJA/IXAJvkZhGXFuBncGstA1le28C/jTGN7FyceBox3 k+9ZbAhD295Q1K8mDPqs679omxI1rVRVGtHDl1oY= 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=unavailable autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=symbolic.software header.b="auy1Xut0"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="lH/z01jN" 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 Ohf2vqDxqk9U for ; Tue, 14 Jul 2026 06:18:18 -0700 (PDT) Received: from fout-a7-smtp.messagingengine.com (fout-a7-smtp.messagingengine.com [103.168.172.150]) (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 04E6E116863C0 for ; Tue, 14 Jul 2026 06:18:17 -0700 (PDT) Received: from phl-compute-10.internal (phl-compute-10.internal [10.202.2.50]) by mailfout.phl.internal (Postfix) with ESMTP id 088DCEC0177; Tue, 14 Jul 2026 09:18:11 -0400 (EDT) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-10.internal (MEProxy); Tue, 14 Jul 2026 09:18:11 -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=1784035091; x=1784121491; bh=C3N9AEAVoe tELlC7g1P0c9YCw5bZEfyx390gbzs6Xdg=; b=auy1Xut0YD829tnMPwocU8nEmC G0MZHECGxjDKz5HqmkZpNQach9OhKzkA/o+nfBlPLIzB37v/8r1/yymCcPLxAa/X OUCxk6SUegbOVxEjL3LcngdVNOYImv14HXkz9pn3qg66xRfbYmO756CB/mMOM7u2 nS1Jlx4T4lwbyt5JOKRce254jWNUGJ8YfFI+KRs8iECRtKF7GLWesSRXVD+MV2E9 FqwbbicbSg6gSYSzp8Q6r4Vvj+2UV4bnPr1xrfRde6UtVrBqu2mpwXtoMLAIWKQh zXjUjM53P9NMrgeblTzsVXtWtl3zm0dDr8amdUs3pwk0yTWDAukICypht0Ug== 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=1784035091; x= 1784121491; bh=C3N9AEAVoetELlC7g1P0c9YCw5bZEfyx390gbzs6Xdg=; b=l H/z01jN5FXN3pel9tQvRZkpKJVvhqoef/8tdTPvSDtH0axohhLCiEnc0o0hSXSht OQvsVK2obfxfgRrzyV4mo4u0jepoNH/Whe2hE1ziV7mzb6NMjT4EdtdxdoWtuy2y 0AIIAdnPkeTdu76kr5mAdqsyTbl3VcnxkEo3sXj/47djPZxOlqHCtCqLUXT6rmjj Rzp9gCsxIEPa3rmHseefdB0FGCPxYp0B4KFwgfLyuhYlS0g3/Gjw8T3zSDauXeQ2 TgPseVJttRmx/HfeYYuXLI44XRoVufG7YIhKuhK/sF4PbLjMk8Vb3m/ZANhwc4+N LX0l5IGvNn8p/D1Rr4oAQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTF1SV5Auh9vGyuP+gBvlLaRGXrk8iRxG41dCwwdyKfekCs223/NKc7YUnDhiWewg0 mkO459Z84hqicOwOxVcMSOdfFi2LJh/7iXYTjZJ4IYet0W8kUu5BCIM2IAB+WLkyf/hovn JTP9mAsQCMvSTavg1oDe83qlFcOOtMeNV+qsOIxzXhC9rl5IUF12Hm4BuS2VjfNxmgVdA0 nDDXKfPVM4k7Zv+nd7i0HMyBcIxGzQYBphQMvLyo3/YssEygY3pVxLPmTNTcLzysaJFB2A Y9ANUrAviwHg0APMxa/n9LL+Iipnp6I/UGPKBDoN8yWzYLkCAY6X05eiccHU5RJZEa3WV1 uyktv0UP5o2cDOnyrBTQX/RD4XYTjb1SILSaNu8TyAu4ElWogQRTcssMKeDo8CWU2W8QJe xDx37xCAEevxbGYoefKZoy5gisyiH858IQ4RTlV6iAlNLkCt24NkxZOSSDkPfQjM0UV9yf oHRsxocgrhe71+8lJF4Se4eST1ythhUyBv1IMJrexenwObLUCKk/eMRERLCrs5C2B2Cd9y ED/eQHpEcbPqjhfmcxPVJNrI1v+JQSXMcLTPVUK4GyTAoWSAyWBuJxZ40HgtiLcSgTn35H HNHbvDsnMsuFDdxPUYvRD7vpLu4Gug7UcioCVwDBo8MiGvEODOufT7hDrJHw X-ME-Proxy: Feedback-ID: i6d3949ed:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 14 Jul 2026 09:18:07 -0400 (EDT) Content-Type: multipart/alternative; boundary=Apple-Mail-33FF40A2-619F-4DCC-A83E-21B8A1F0801F Content-Transfer-Encoding: 7bit From: Nadim Kobeissi Mime-Version: 1.0 (1.0) Date: Tue, 14 Jul 2026 16:18:06 +0300 Message-Id: <5B34ABF4-D76F-44C9-ACB1-5F1843372299@symbolic.software> References: In-Reply-To: To: iab@iab.org X-Mailer: iPhone Mail (23F84) Message-ID-Hash: XI3HOR42DOAWNP555FDXAFJUQOIOTSNM X-Message-ID-Hash: XI3HOR42DOAWNP555FDXAFJUQOIOTSNM 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: =?utf-8?q?=5BTLS=5D_Re=3A_Scope_of_the_IAB=27s_appeal_response?= List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --Apple-Mail-33FF40A2-619F-4DCC-A83E-21B8A1F0801F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi everyone,

I got an informative answer to my que= stion:

It appears that th= e appeal was about the decision to adopt draft-connolly-tls= -mlkem-key-agreement as a working-group document (which is how it becam= e draft-ietf-...). Now it's about publishing the resulting TLS WG Internet D= raft as an informational RPC.

Thanks to the person who clarified this to me. Shar= ing this here in case others find this helpful.

I apologize for my confusion on t= his subject and appreciate the clarification. It was an honest mistake.

Nadim Kobeissi
S= ymbolic Software =E2=80=A2 https://symbolic.software

On 14 Jul 2026, at 3:36=E2=80=AFPM, Nadim= Kobeissi <nadim@symbolic.software> wrote:

<= blockquote type=3D"cite">
=EF=BB=BFIf the determination of roug= h consensus of the WGLC from earlier this year is real and legitimate and no= t overturned or anything like that, then why was a subsequent WGLC held and c= oncluded just last week? Why didn=E2=80=99t we just adopt during the one fro= m earlier this year and settle the matter then and there?

I would appreciate an explanation and apologize in advance if I=E2=80=99m m= issing anything obvious.

Thanks,

Nadim Kobeissi
S= ymbolic Software =E2=80=A2 https://symbolic.software

On 14 Jul 2026, at 2:52=E2=80=AFPM, IAB C= hair <iab-chair@iab.org> wrote:

=EF=BB=BF

TLS WG,

=

The IAB notes th= at its response to Daniel J. Be= rnstein=E2=80=99s 2026-04-24 appealThe IAB denied the appeal. It did not find that the cha= irs' determination of rough consensus to adopt fell outside the discretion t= hat RFC 2418 affords them, nor that the responsible AD and the IESG acted ou= tside their process role in declining to overturn that determination.=

The r= elevant observation regarding the responsible AD was narrow. The IAB noted t= hat the initialadoption= call by the responsible AD did not accurately descri= be the record, and that a more precise account followed. It was offered as e= ncouragement to chairs and ADs to take care when summarizing participant res= ponses. The observation concerned the accuracy of that account, not the inte= nt behind it. It was not a finding that the responsible AD acted in bad fait= h, engaged in misconduct, or breached the IETF=E2=80=99s conduct norms.

The= IAB has also seen its response read as reaching conclusions it did not stat= e. The IAB did not determine that consensus to adopt was absent, nor did it o= verturn any consensus call. Its response should not be read as reaching conc= lusions 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 ma= iling list -- tls@ietf.org
To unsubscribe send an email to t= ls-leave@ietf.org
_________________= ______________________________
TLS mailing list -- tls@ietf.= org
To unsubscribe send an email to tls-leave@ietf.org
= --Apple-Mail-33FF40A2-619F-4DCC-A83E-21B8A1F0801F--