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

S Moonesamy <sm+ietf@elandsys.com> Sat, 23 March 2024 08:48 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 A9244C151073; Sat, 23 Mar 2024 01:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.707
X-Spam-Level:
X-Spam-Status: No, score=-6.707 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=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 vuAGdybFTqfM; Sat, 23 Mar 2024 01:48:02 -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 11B13C151071; Sat, 23 Mar 2024 01:48:02 -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 42N8ljLl017747 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 23 Mar 2024 01:47:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1711183678; x=1711270078; i=@elandsys.com; bh=0kOviXT26j+XffNOHqUDkVB+HfWEGNiH/6IdeKzqZKY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=PQmVkwUXhkcxjdrRuD4WLmpID+s7Lj/jBKv/Fe/QjNFugJdCuR9/7I3or7hbgqvoI FVBQQUof1HgGQGUhJdBbg8RvYDjciNTAMh9mgaPAem16j/7uCVeiv9xSrmvZUI8a4X uP0na8PJNI8QhDsd188JpIpl5XJODTRpgDyQWmZs=
Message-Id: <6.2.5.6.2.20240323004217.115aeb28@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 23 Mar 2024 01:46:39 -0700
To: John C Klensin <john-ietf@jck.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
Cc: Pete Resnick <resnick=40episteme.net@dmarc.ietf.org>
In-Reply-To: <7F1502637EB78EE7032F4384@PSB>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Cm5XhzntLp6qCni2y30Gvl1nY6Q>
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 08:48:06 -0000

Hi John,
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.   Now, I think such WGs
>are quite rare in the IETF, but I have seen a few situations
>that I have trouble interpreting in any other way.  Ideally, I'd
>like to see ADs actively monitoring such groups but the ADs have
>become sufficiently busy that they may not know what is going on
>unless someone tells them... and no one within such a WG is
>likely to tell them.   I also have what I gather has become a
>rather quaint notion that ADs should be accountable for the
>behavior of their WGs even though I see and sympathize with the
>overload problem.  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".

Let's see:

   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.

   3. The RAD overrides the decision.

Why have someone chair a meeting if he/she has to ask his/her manager 
for permission?

Why would the RAD override a decision when the people in the group 
seem happy with it?


It may be better to treat the "too homogeneous and resistant" problem 
separately.

>As far as groups not meeting at the IETF, I agree with you but
>with one caution.  Suppose there are people participating in one
>or more not-meeting groups but also actively involved with
>groups that are meeting.  I don't know whether activity in the
>not-meeting groups might distracting them from things during the
>week but we should at least be asking the question.  And, fwiw,
>another part of the larger picture is our traditional
>prohibition on interim meetings during, or right before or
>after, IETF meetings.  That is another area in which it might be
>reasonable for a chair to decide to waive the rules but where I
>think the responsible (interesting term, that) AD should at
>least be aware that the meeting is happening and that the
>chair(s) should be aware that participants in that WG might also
>be participating in others.

The RAD would probably receive a notice if the WG is going to have a meeting.

>I also see one of the main values of IETF meetings being the
>opportunity for people who are not actively part of a WG to drop
>in, find out what is going on, and maybe learn something.  Who
>knows, they might turn into active participants.    Even at this
>meeting, very remote and with some time zone disability, I
>managed to sit in on a few meetings that left me with the
>feeling that there are some issues to which I should be paying
>more attention.  As I have not been the only one to point out,
>documents and/or agendas and/or meetings materials posted very
>close to the meeting may tend to frustrate that sort of open
>participation and openness to newcomers to that WG.  If it
>happens at one IETF meeting, I think "perceived emergency" or
>"special circumstances" likely justify it.  If it happens time
>after time, then IMO someone external to the WG should be taking
>a look at the causes of such a pattern and whether something
>needs fixing.  I don't see it as an absolute but as one of many
>tradeoffs we need to make.  But, again, I see WG accountability
>to ADs and AD accountability to the community as crucial to
>avoiding abuses or even the appearance of them.  If the IETF has
>stopped caring about those things, my views are irrelevant to
>anything but the question of how long it will survive or
>deserves to do so.

I could not find any email from someone self-identified as new 
pointing out that they could not understand what was going on as the 
materials (for that meeting) were only available a day before the 
meeting.  I agree with what you wrote about open participation.

What is happening is that people having been finding ways to get 
around the two-weeks restriction and those ways are quite 
effective.  Every few years (it's actually 13 years), there is a 
discussion such as this one.

Regards,
S. Moonesamy