Re: Question about pre-meeting document posting deadlines for the IESG and the community
Pete Resnick <resnick@episteme.net> Sat, 23 March 2024 02:49 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 7DB8CC14F6E8 for <ietf@ietfa.amsl.com>; Fri, 22 Mar 2024 19:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, 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 yC529bv8bZzI for <ietf@ietfa.amsl.com>; Fri, 22 Mar 2024 19:49:07 -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 3FB89C14F5F4 for <ietf@ietf.org>; Fri, 22 Mar 2024 19:49:06 -0700 (PDT)
From: Pete Resnick <resnick@episteme.net>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=episteme.net; s=mail; t=1711162144; bh=KTRWKpZb1c9Gb+vIpIvw2oiFY37SfKK6Z9bdqzTchWE=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=XEV86IRDLXApCLnv+6iirXuqjrtqzr/GBtyfYELKDj2795RRnPbORvFbf6TvXKjiJ jEGIfDlVehXxz/Ddegv7wLLD/OSPMcsamwe29dVjdt5/U4khqvnPs3TRnRk9JWjOlx mLApx74q0kaWOlfC04Q+8mJn/2fhXL++7xgbNM40=
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: ietf@ietf.org
Subject: Re: Question about pre-meeting document posting deadlines for the IESG and the community
Date: Fri, 22 Mar 2024 19:48:39 -0700
Message-ID: <569FBECE-E637-4B2A-86C5-4F7B7AEC333E@episteme.net>
In-Reply-To: <6.2.5.6.2.20240322143647.10ef96f8@elandnews.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>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; markup="markdown"
X-Synology-Spam-Flag: no
X-Synology-Spam-Status: score=-0.101, required 6, ARC_NA 0, MID_RHS_MATCH_FROM 0, FROM_HAS_DN 0, TO_DN_SOME 0, TO_MATCH_ENVRCPT_ALL 0, MIME_GOOD -0.1, __THREADED 0, RCPT_COUNT_TWO 0, RCVD_COUNT_ZERO 0, FROM_EQ_ENVFROM 0, MIME_TRACE 0, __NOT_SPOOFED 0, __BODY_URI_ONLY 0, __HDRS_LCASE_KNOWN 0, NO_RECEIVED -0.001
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yJrnWn4cKouyikgQVHvgRD8RErs>
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 02:49:11 -0000
On 22 Mar 2024, at 15:02, S Moonesamy wrote: > 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. As far as I know, the WG Chairs still have to ask permission of the AD, and then the AD must manually ask the secretariat to process the document; there is no button to push. One part of this is the tool, and I should probably "put my money where mouth is" and help at the Code Sprint to write the tooling to make this possible. But the other part of it is policy, which I think should be made more flexible. >> 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. Yep. And the fixed two weeks means that there is a flood two weeks before, where some WG chairs might be OK with one week, or require three weeks, or be OK with two days before. The accident of history should not constrain us. >> (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. Yes, that's why they "pay us the big bucks". Chairs sometimes have to make unpopular decisions and say no to pushy authors. I promise to be supportive. pr -- Pete Resnick https://www.episteme.net/ All connections to the world are tenuous at best
- Question about pre-meeting document posting deadl… John C Klensin
- Re: Question about pre-meeting document posting d… touch@strayalpha.com
- Re: Question about pre-meeting document posting d… Marc Petit-Huguenin
- Re: Question about pre-meeting document posting d… Pete Resnick
- Re: Question about pre-meeting document posting d… John C Klensin
- Re: Question about pre-meeting document posting d… Brian E Carpenter
- Re: Question about pre-meeting document posting d… Benoit Claise
- Re: Question about pre-meeting document posting d… Carsten Bormann
- Re: Question about pre-meeting document posting d… Salz, Rich
- Re: Question about pre-meeting document posting d… Pete Resnick
- Re: Question about pre-meeting document posting d… George Michaelson
- Re: Question about pre-meeting document posting d… Jan-Frederik Rieckers
- Re: Question about pre-meeting document posting d… touch@strayalpha.com
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… Carsten Bormann
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… Michael Richardson
- Re: Question about pre-meeting document posting d… John C Klensin
- Re: Question about pre-meeting document posting d… Carsten Bormann
- Re: Question about pre-meeting document posting d… Pete Resnick
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… Pete Resnick
- Re: Question about pre-meeting document posting d… Abdussalam Baryun
- Re: Question about pre-meeting document posting d… John C Klensin
- Re: Question about pre-meeting document posting d… John C Klensin
- Re: Question about pre-meeting document posting d… Murray S. Kucherawy
- Re: Question about pre-meeting document posting d… John C Klensin
- Re: Question about pre-meeting document posting d… Brian E Carpenter
- Re: Question about pre-meeting document posting d… Carsten Bormann
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… Martin J. Dürst
- Rule of removing adopted work (was Re: Question a… Abdussalam Baryun
- RE: Rule of removing adopted work (was Re: Questi… Adrian Farrel
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Rule of removing adopted work (was Re: Questi… Keith Moore
- Re: Rule of removing adopted work (was Re: Questi… Brian E Carpenter
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… S Moonesamy
- Re: Question about pre-meeting document posting d… Michael Richardson
- Re: Question about pre-meeting document posting d… Pete Resnick
- Re: Question about pre-meeting document posting d… John C Klensin
- Re: Question about pre-meeting document posting d… S Moonesamy
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… Pete Resnick
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… S Moonesamy
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… Abdussalam Baryun
- Re: Question about pre-meeting document posting d… Lloyd W
- Re: Question about pre-meeting document posting d… John C Klensin
- Re: Question about pre-meeting document posting d… S Moonesamy
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… John C Klensin
- Re: Question about pre-meeting document posting d… Michael Richardson
- Re: Question about pre-meeting document posting d… Michael Richardson
- Re: Question about pre-meeting document posting d… John C Klensin
- Re: Question about pre-meeting document posting d… Michael Richardson
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… Murray S. Kucherawy
- Re: Question about pre-meeting document posting d… Carsten Bormann
- Re: Question about pre-meeting document posting d… Murray S. Kucherawy
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… Salz, Rich
- Re: Question about pre-meeting document posting d… Benson Muite
- Re: Question about pre-meeting document posting d… Salz, Rich
- Re: Question about pre-meeting document posting d… touch@strayalpha.com
- Re: Question about pre-meeting document posting d… touch@strayalpha.com
- Re: Question about pre-meeting document posting d… Murray S. Kucherawy
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… Carsten Bormann
- Re: Question about pre-meeting document posting d… Michael Richardson
- Re: Question about pre-meeting document posting d… Eliot Lear
- Re: Question about pre-meeting document posting d… Rob Wilton (rwilton)
- Re: Question about pre-meeting document posting d… John C Klensin
- Re: Question about pre-meeting document posting d… Michael Richardson
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… John C Klensin
- Re: Question about pre-meeting document posting d… Keith Moore
- Re: Question about pre-meeting document posting d… S Moonesamy