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

Keith Moore <moore@network-heretics.com> Sun, 17 March 2024 05:56 UTC

Return-Path: <moore@network-heretics.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 0E493C14F69D for <ietf@ietfa.amsl.com>; Sat, 16 Mar 2024 22:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=pass (2048-bit key) header.d=messagingengine.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 UyAhCIw1W4Jk for <ietf@ietfa.amsl.com>; Sat, 16 Mar 2024 22:56:26 -0700 (PDT)
Received: from wfhigh8-smtp.messagingengine.com (wfhigh8-smtp.messagingengine.com [64.147.123.159]) (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 30B66C14CE24 for <ietf@ietf.org>; Sat, 16 Mar 2024 22:55:57 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfhigh.west.internal (Postfix) with ESMTP id EC4D41800092; Sun, 17 Mar 2024 01:55:56 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sun, 17 Mar 2024 01:55:57 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1710654956; x=1710741356; bh=LRXV9JiadbxOalG3uKFDsqK8DwD4 0H03lDuF/enFF+w=; b=nLsHrSuwgfoUFQKWiP5c3wtRv7UZcNOQufISsgXbp0Pw TGhahTaf5XdzMCFFHPjvoQ3pisOPyk1I2vJ1WgYt99RtbbcNHn25H9Nxt/ipBkE7 eDbmHcMYA6BDX/1zkmklFvhwHq77iU90aWFnVSK5Bv8bwCkaM/lamk53pFu10SEJ IoAfM5F6AxBPPIzaPDaiQ0u8b1rZUATULLePowRXMWFebQQ7eQN/7BI90J6Ry68v XWkSmxeFVIrz4MU/zwIs04t6aizhN8QVP3xGP7W3qqgYgIDXJA5GDg1XcH0c7Y49 u2Oa7yFhjtE+qf0PiUDW6JBa3sM2UcG0kckp/jVy9Q==
X-ME-Sender: <xms:7IX2ZTjUpJsV92leONTdgk72q9ASc7aj_awkuhNqce0nIJ4_gsyjXg> <xme:7IX2ZQDIbtenq_VQdaovyzb8lrJGPLHKA_o5jYwR1610Xwpr0ozd249uINeeE9xSU 7Yw0v-aZg4kaw>
X-ME-Received: <xmr:7IX2ZTGAO5letLiIZM18nea1CQzEsiAd-LNgphM0VmmzMbmdbcOpwXpK6y7n7Fs6oq6php7wHQ60smbrysh8dI6T6UMfmtJ3>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrkeefgdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtkfffgggfuffvvehfhfgjsegrtderredtvdejnecuhfhrohhmpefmvghithhh ucfoohhorhgvuceomhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhmqe enucggtffrrghtthgvrhhnpeejvdfhtdduhedugfekteeikeetfeefhefgueetgfdvhfeh vefghfeijedvtdevueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:7IX2ZQQHkaPEP36Ry7b7Kil3EumGiwrCDfBJ3TTH1pBvx1W672GdlQ> <xmx:7IX2ZQxZAR0X8k5wIsR7FqCqdxrjo1doUYOt1joRDdFG5sb4fYOuRg> <xmx:7IX2ZW5Oio8v8lCRnIwujURmbrjaCmMOD_9ootysJrErLrdy1nfJgQ> <xmx:7IX2ZVzKX4QMb4u8i_ERbIKQBJHEHpJ1oHYAfLbHxQ5HQtKg_C-syQ> <xmx:7IX2Zc_TGPVUJfR2uw1sw-CcTLpJE7grkGU41rwDpo9d1Ubo5RnsyQtWW_s>
Feedback-ID: i5d8c41f0:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 17 Mar 2024 01:55:55 -0400 (EDT)
Content-Type: multipart/alternative; boundary="------------0euy08IomPyaSFfl6wIpOOT3"
Message-ID: <56233d0c-d777-4142-abd6-e52e701b5f25@network-heretics.com>
Date: Sun, 17 Mar 2024 01:55:55 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Question about pre-meeting document posting deadlines for the IESG and the community
Content-Language: en-US
To: Pete Resnick <resnick@episteme.net>
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
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> <25ceeb23-542e-4578-9661-71f486f9bc3f@network-heretics.com> <D3180E63-C23C-4BFE-B558-B29BFB844B13@episteme.net>
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <D3180E63-C23C-4BFE-B558-B29BFB844B13@episteme.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5gGckdvjDMfY58i_tTG7DrZoHgY>
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, 17 Mar 2024 05:56:31 -0000

On 3/17/24 01:39, Pete Resnick wrote:

>> So I'd argue to keep the 2-week rule because I think it's about the 
>> minimum amount of time that it's reasonable to give people to sync / 
>> catch up, but the 2-week rule should apply to all updates.
>
> Except we have already established that the rule is consistently being 
> circumvented (see John's initial message) and is not working for the 
> purpose you describe, and more importantly nobody (the IESG, the 
> chairs) is willing to enforce it in the way that you describe. So now 
> what? Nice to say "keep the rule", but for what purpose? For the 
> artificial deadline function, we can do that without the rule. 
The purpose is always (or should be) to build consensus around 
technically sound solutions to relevant problems.   Making it more 
difficult to track such discussions seems inconsistent with that purpose.

Of course, if real consensus [*]  around text in a document already 
exists by f2f meeting time, that's less time needed for discussion of 
that item in the meeting.

Keith

[*] not, say, consensus by exhaustion, or the appearance of consensus 
because people have been blindsided by a late proposal