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

S Moonesamy <sm+ietf@elandsys.com> Fri, 22 March 2024 22:05 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 398F7C14F714; Fri, 22 Mar 2024 15:05:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.704
X-Spam-Level:
X-Spam-Status: No, score=-1.704 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_NONE=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 qAv5C7IsdBTc; Fri, 22 Mar 2024 15:05:23 -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 E78B3C14F6F2; Fri, 22 Mar 2024 15:05:22 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.92.83]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 42MM4iIV029435 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Mar 2024 15:05:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1711145118; x=1711231518; i=@elandsys.com; bh=+jJFIF3rmx6s8P2il4EL1SUREHTwLjW762TX7tIm+ZM=; h=Date:To:From:Subject:In-Reply-To:References; b=CLu3AwFkucYWKxvVmXyYFpm+D4TBaEGKj8prYXxMXZBDZRzANDGaN2/AUKDK1r/9r /KlNvcjCx0JwZLbVQLLRUnU5tWMAOGhlFHvT1QMU7ht3Ieg3Tl/QDcwFSNKDRaQNE2 5/Ac/h4h8ObZMVPJ6nfC8wlTzJVWwvBFVhtszpSM=
Message-Id: <6.2.5.6.2.20240322143647.10ef96f8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 22 Mar 2024 15:02:27 -0700
To: Pete Resnick <resnick=40episteme.net@dmarc.ietf.org>, 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
In-Reply-To: <85D994BF-5E89-437B-821C-12DE93C403B3@episteme.net>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lP2NKQQCPBLlNvXyAkC2WdRSNsU>
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: Fri, 22 Mar 2024 22:05:27 -0000

Hi Pete, John,
At 07:25 PM 16-03-2024, Pete Resnick wrote:
>But this seems to me too high a burden. If a chair wants to make an 
>exception, they should be empowered to do so and not make this 
>depend on an AD OK, particularly right before a meeting where ADs 
>have lots of other things to deal with. And if a chair or an AD is 
>not directly involved, there is no reason an author shouldn't be 
>able to submit a document that has nothing to do with a WG.

The WG Chairs are allowed to make an exception.  If I remember 
correctly, the AD may have to "push a button" to release the I-D from 
the queue.

>We are using the accident of an old set of circumstances to drive 
>procedures rather that discussing what we really want out of the 
>tooling. Please let's stop doing that.

Yes.

Some of the side effects of the accident of history is that the 
two-weeks no-I-D window prevents non-WG I-D from being posted and the 
I-D flood at the beginning of the meeting week.

>(During a chat last night, Barry reminded me that when a change was 
>proposed several years ago, some chairs objected to the change 
>because they did not want the responsibility to allow exceptions and 
>instead wanted it to be an AD override so they could claim 
>powerlessness to insistent authors. I find such an argument a sign 
>of complete dysfunction.)

It's a bit politically unfriendly to take such a decision.

Regards,
S. Moonesamy