Re: Question about pre-meeting document posting deadlines for the IESG and the community

Pete Resnick <resnick@episteme.net> Sat, 23 March 2024 16:29 UTC

Return-Path: <resnick@episteme.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 695C2C14CEFD for <ietf@ietfa.amsl.com>; Sat, 23 Mar 2024 09:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=episteme.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ay9kqFuqN6Nh for <ietf@ietfa.amsl.com>; Sat, 23 Mar 2024 09:29:10 -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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BDF6C14F6F7 for <ietf@ietf.org>; Sat, 23 Mar 2024 09:29:09 -0700 (PDT)
Received: from [192.0.0.2] (unknown [172.58.209.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.episteme.net (Postfix) with ESMTPSA id 4V24QW5YQFzS207; Sat, 23 Mar 2024 11:29:07 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=episteme.net; s=mail; t=1711211348; bh=3uanaUd+oOV8L1FOZx3KMbUWDvi9mrMr8uT/+rxvqBQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=lAyUbXEbzgxOJ/6IyCDOlersVgJQP7IymtUDmnoeruwQ+FTlvTLmgxlAYx2Agnuqy WehExlGVCfAWejmtGssJ8TFi0vuAdk7fsefIBuWD9RmETeUPjGxJPnMwvBBVAZTId8 sr76j3aaRbYXvyl4EZLqclqpocc5jkbOmApy/92s=
From: Pete Resnick <resnick@episteme.net>
To: Keith Moore <moore@network-heretics.com>
Cc: ietf@ietf.org
Subject: Re: Question about pre-meeting document posting deadlines for the IESG and the community
Date: Sat, 23 Mar 2024 09:29:00 -0700
Message-ID: <1E012E8F-7245-4F31-8D2D-3D1C24085FB5@episteme.net>
In-Reply-To: <240d0bf6-36e8-410d-8f86-2069dfc16f52@network-heretics.com>
References: <7826C4F13FA874CD79459A4B@PSB> <65A7921B-2A05-439A-976C-226560C5E7F4@strayalpha.com> <e0702d8a-cea5-4928-b571-98442ccd4f29@petit-huguenin.org> <6d0c6b07-2fc3-496c-ba66-dc40cbf46df8@dfn.de> <69EE71C9-C42B-49A6-BC0D-508F799DB68E@tzi.org> <1d301b86-c994-4a9c-810c-9a42e12a0ad8@network-heretics.com> <53C617FA98D84931861C1F59@PSB> <85D994BF-5E89-437B-821C-12DE93C403B3@episteme.net> <6.2.5.6.2.20240322143647.10ef96f8@elandnews.com> <569FBECE-E637-4B2A-86C5-4F7B7AEC333E@episteme.net> <7F1502637EB78EE7032F4384@PSB> <6.2.5.6.2.20240323004217.115aeb28@elandnews.com> <240d0bf6-36e8-410d-8f86-2069dfc16f52@network-heretics.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_C26CF56D-FE47-463F-B5A2-3A8A74BC12DB_="
Content-Transfer-Encoding: 8bit
X-Synology-Spam-Status: score=-0.1, required 6, TO_DN_SOME 0, __THREADED 0, RCPT_COUNT_TWO 0, HTML_MESSAGE 0.001, RCVD_COUNT_ZERO 0, FROM_EQ_ENVFROM 0, MIME_TRACE 0, __NOT_SPOOFED 0, MID_RHS_MATCH_FROM 0, NO_RECEIVED -0.001, ARC_NA 0, FROM_HAS_DN 0, TO_MATCH_ENVRCPT_ALL 0, MIME_GOOD -0.1, HTML_MISSING_CTYPE 0, __HDRS_LCASE_KNOWN 0
X-Synology-Spam-Flag: no
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9SWIbjdHyQQ2koUoQ2mwE1bS3JQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Mar 2024 16:29:14 -0000

On 23 Mar 2024, at 8:48, Keith Moore wrote:

> On 3/23/24 04:46, S Moonesamy wrote:
>
>> At 09:22 PM 22-03-2024, John C Klensin wrote:
>>> I think where we disagree is that I'm at least a little more
>>> concerned about working groups that become too homogeneous and
>>> resistant to "outsider" views and input. [...]
>>> [...]  So I see "AD must approve" as a possible
>>> small way to alert an AD that someone out of the ordinary
>>> _might_ be going on.  I'd be almost as happy with "WG Chair can
>>> decide, but AD must be notified in a timely way and has the
>>> right to override the decision".
>>
>>   1. A WG Chair decides to allow an I-D to be added a day
>>      before a meeting.
>>
>>   2. There isn't any complaint about the decision.
>
> A decision made a day before a meeting doesn't allow enough time to 
> see whether there would be complaints.

Completely agree with Keith that making these decisions at the last 
minute is not acceptable.

But where I disagree with John is with the notion that these artificial 
rules and procedures address the issue in any meaningful way. Insofar as 
there are groups that are "too homogenous and resistant to 'outsider' 
views and input" (and I don't doubt there are some), that's a cultural 
problem. It's caused by chairs who are not sufficiently sensitive to the 
issue (or the ADs appointing them), or the charter not being clear about 
bringing in the right amount of well-rounded input, or chairs who are 
not pushing back on their WGs, or an IESG or IAB not paying attention 
and giving appropriate guidance, or other similar possible causes. A 
relatively arbitrary rule or procedure that throws up a road block for a 
train that's already drifting off the rails doesn't do much. At best, 
it's simply an annoyance, a barrier that folks will simply route around 
or plow through; at worst, it makes things worse by removing 
responsibility from chairs to make thoughtful decisions.

If the culture of the organization is shifting away from principles that 
many of us think are core and foundational, that stinks. Shifting back 
to those principles is hard and takes serious conversations and work. 
Quick "fixes" (that I don't think do much fixing) aren't the way.

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