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

S Moonesamy <sm+ietf@elandsys.com> Sun, 24 March 2024 12:35 UTC

Return-Path: <sm@elandsys.com>
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 9B7F8C14F6B4 for <ietf@ietfa.amsl.com>; Sun, 24 Mar 2024 05:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.706
X-Spam-Level:
X-Spam-Status: No, score=-1.706 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, 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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 PjQchTeniLhl for <ietf@ietfa.amsl.com>; Sun, 24 Mar 2024 05:35:34 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C77BC14F6AA for <ietf@ietf.org>; Sun, 24 Mar 2024 05:35:34 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.84.248]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 42OCZHD9019572 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 24 Mar 2024 05:35:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1711283729; x=1711370129; i=@elandsys.com; bh=VLt/w9Tw21x9gJTLbtlHsOaqKMZputEnS/xbr/ysn8U=; h=Date:To:From:Subject:In-Reply-To:References; b=XUCuXghFotG6u+o7oRDejCEfG6AjQxTOwu3P0lsiGN7qgCfAC2xYeA3dVgiHmnj9j eYfcXXkBZcOOV8VUQzqBwUsxrDc2g/+rH3UatNdFjMN71yYWNLNiu3/UmimmIzNgvD D8NylE34VcIOVML3yuEutjpWN4x19unzzqr8gWdc=
Message-Id: <6.2.5.6.2.20240324031614.13b523c8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 24 Mar 2024 05:34:37 -0700
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Question about pre-meeting document posting deadlines for the IESG and the community
In-Reply-To: <897e2bce-2187-433c-af26-c8c8f3b37c1b@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> <6.2.5.6.2.20240323154539.127fbdb8@elandnews.com> <897e2bce-2187-433c-af26-c8c8f3b37c1b@network-heretics.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6CWbsINT-3CTPjpKDiijyHzkSBk>
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: Sun, 24 Mar 2024 12:35:38 -0000

Hi Keith,
At 03:05 AM 24-03-2024, Keith Moore wrote:
>I don't think it's possible to reliably establish that the people 
>showing interest in a WG's deliverables (for the present or future) 
>are okay with a particular set of practices.   Even if a WG 
>explicitly asks everyone on its mailing list for their consent to a 
>change in the rules, new participants may join at any time, and it's 
>not desirable to exclude or discourage new participants.

There is a misunderstanding of the requirement/rule.  There are 
requirements/rules which I cannot change, e.g. the Last-Call shall be 
two weeks.

Sometimes, a practice (sorry if it is not the correct word) is set by 
agreement when the WG starts its work.  I found it useful as it 
allows the WG to meet its target date for delivering the I-D to the 
AD.  For what it is worth, I have been off by six months on a target 
date.  All the RFCs which I shepherded were published in under three years.

Over the years, I only received one complaint about the exclusion of 
participants.  The person who filed the complaint had a 
point.  However, the point was something to do with IETF policy 
(which is something which I could not change).

The question which John asked for about documents to be discussed at 
a meeting.  A person, irrespective of characteristics, who comes to 
the meeting could protest if a rule was violated.

>I'm not a big fan of use of github by WGs, but at least that 
>particular subject has had extensive discussion within IETF.   I 
>don't think it should serve as a general example of why it's okay 
>for some WGs to work differently than others.

Ok.

>One of my big concerns about working groups, especially these days, 
>is that there seems to be an increasing tendency for WGs to operate 
>as closed clubs.  They can't stop new people from joining their 
>mailing lists or their publicly announced meetings, but they can 
>discourage participation from newcomers in various ways. Holding 
>"interim" meetings (whether remote or in-person) without 
>community-wide announcement in the usual means (e.g. ietf-announce) 
>is certainly one way they can do that.   Having the chair or other 
>designee object to any suggestion by an "outsider" is another 
>way.  It's absolutely NOT okay for a WG to operate in that way, even 
>if some of the core participants think it's ok.

As a comment on interim meetings, there is a decision by the IAB at: 
https://datatracker.ietf.org/group/iab/appeals/artifact/39

There are various ways to discourage participation by not-the-usual 
participants, e.g. setting an online meeting at any inconvenient time 
for a not-the-usual participant.  I attended meeting scheduled in 
far-away timezones.  It is a significant effort, and cost, to do that 
over a very long period.

There is a RFC which discussed clubs if I recall correctly.

Regards,
S. Moonesamy