[Gendispatch] Re: New Version Notification for draft-nottnick-ietf-decisions-00.txt

Pete Resnick <resnick@episteme.net> Tue, 11 August 2026 17:02 UTC

Return-Path: <resnick@episteme.net>
X-Original-To: gendispatch@mail2.ietf.org
Delivered-To: gendispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3FAD7127F6B66 for <gendispatch@mail2.ietf.org>; Tue, 11 Aug 2026 10:02:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1786467730; bh=eLfabzfNIGwSr8S+/OAIrUWrw+oNu9YSMKRMx3Q9mZs=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=OwyCJgPfOB/L0ocbPcrLwx03e2q53mY+fuox3M3j5MuW/Rz+trWhX5y76mOPV8M3e PpdXrkZYAU0sS/OXkHCXfUFcduigJqMdfCW4zpmT+RUm4F8q92Cj1DEZn97Wg2h2SM xwSahmvVlCD4EZcKyEjPNmF0pusuQkR+GxTGxn2M=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, 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=episteme.net
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 tGuujvfrp4Ub for <gendispatch@mail2.ietf.org>; Tue, 11 Aug 2026 10:02:08 -0700 (PDT)
Received: from mail.episteme.net (episteme.net [216.169.5.102]) (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 01475127F6B50 for <gendispatch@ietf.org>; Tue, 11 Aug 2026 10:02:07 -0700 (PDT)
Received: from [172.16.1.31] (unknown [172.16.1.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.episteme.net (Postfix) with ESMTPSA id 4hKHwV6KDGz15nM8; Tue, 11 Aug 2026 12:02:02 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=episteme.net; s=mail; t=1786467726; bh=eLfabzfNIGwSr8S+/OAIrUWrw+oNu9YSMKRMx3Q9mZs=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=lvE64uIgYuASaOFsL5i/pwRfr8Efp7gqKfiz+Wa680Zik0C665b+xz5F396ES06xj p3girGYKJVd7NBP45hK8dryd6By3WivJURdMZVCzhVIg3CiiAufUpwut/izQl7qu9g kpXqCbe/m9ZfdMHxkd7C16aL/wJT0gB5Q2Ki31H0=
From: Pete Resnick <resnick@episteme.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Tue, 11 Aug 2026 12:02:02 -0500
Message-ID: <75D59668-DB30-43B8-8B59-2DA0BA33CE77@episteme.net>
In-Reply-To: <f9f2e272-79c5-4ec9-bd2f-ef37edc45abe@gmail.com>
References: <178466333881.355481.1001762120519431735@dt-datatracker-d4d6ff9d9-fsx7d> <9D2F3344-9324-4C09-ABC2-2298FE104F60@mnot.net> <9a14d92b-cd7a-44be-ae0e-025528b29e0b@gmail.com> <1781911C-7CCA-4B9D-BDE6-BD21A5ADA1A4@mnot.net> <f9f2e272-79c5-4ec9-bd2f-ef37edc45abe@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_EE69F810-7ABA-41FE-9947-609A678835DF_="
X-MS-Reactions: disallow
X-Synology-Spam-Flag: no
X-Synology-Spam-Status: score=0.4, required 5.5, FREEMAIL_ENVRCPT 0, FROM_HAS_DN 0, FROM_EQ_ENVFROM 0, __NOT_SPOOFED 0, MIME_GOOD -0.1, MID_RHS_MATCH_FROM 0, NO_RECEIVED -0.001, RCVD_COUNT_ZERO 0, TAGGED_RCPT 0, HTML_MESSAGE 0.001, MISSING_XM_UA 0, __THREADED 0, RCPT_COUNT_THREE 0, HTML_MISSING_CTYPE 0, TO_MATCH_ENVRCPT_ALL 0, TO_DN_ALL 0, __HDRS_LCASE_KNOWN 0, FREEMAIL_TO 0, ARC_NA 0, MIME_TRACE 0, R_MISSING_CHARSET 0.5
Message-ID-Hash: YIWTYTVHI2LKTBUXC4Y5EAHEDQ33Q7RX
X-Message-ID-Hash: YIWTYTVHI2LKTBUXC4Y5EAHEDQ33Q7RX
X-MailFrom: resnick@episteme.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Mark Nottingham <mnot@mnot.net>, GENDISPATCH List <gendispatch@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Gendispatch] Re: New Version Notification for draft-nottnick-ietf-decisions-00.txt
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/Li6dnSxLcALFoigPLF5N291ivCI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>

On 10 Aug 2026, at 16:02, Brian E Carpenter wrote:

> Another point occurred to me. The IESG and IAB charters don't mention _rough_ consensus. In fact the IAB charter [BCP39] has a voting rule. The IESG charter [RFC3710] has a quite complex discussion of decision-taking and the IESG ballot procedure [1] is pretty complex too.
>
> I think the draft needs to mention the IESG and IAB decision-taking models, even if only to note that neither of them is rough consensus. Specifically, the IESG does not use rough consensus to determine whether there is IETF rough consensus on a document.
>
> [1] https://datatracker.ietf.org/doc/statement-iesg-ballot-procedures-for-documents/

Well, the "Alternate" procedure is definitely voting, but it's not clear what to call the rest of it, particularly given the discussion here:

https://datatracker.ietf.org/doc/statement-iesg-discuss-criteria-in-iesg-review-20140507/

What the IESG is doing as described here certainly doesn't sound much like voting, and may even be close to the IESG coming to rough consensus, though undoubtedly in a convoluted way.

I wrote this thing a while ago that might be also of interest:

https://wiki.ietf.org/en/group/iesg/archive/ballottheory

I'd prefer that the IESG didn't use a hard number (2/3), but I wonder the number of times that this has even been an issue: How many documents have we had that failed IESG review with > 1/3 Abstains? Any? I suspect if there were sufficient Abstains (or even one total showstopper Abstain), one or two other ADs would pickup a Discuss and things would keep going, for the sake of coming to rough consensus.

The IAB's procedure seems to be "unanimity if possible, consensus otherwise, plus a weird little add on about quorum". The only real "voting rule" has to do with getting rid of the IAB chair, AFAICT.

pr
-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best