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

Keith Moore <moore@network-heretics.com> Sat, 16 March 2024 20:31 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 24763C14F5FF for <ietf@ietfa.amsl.com>; Sat, 16 Mar 2024 13:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.903
X-Spam-Level:
X-Spam-Status: No, score=-6.903 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_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 (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 E1marj7Wr88I for <ietf@ietfa.amsl.com>; Sat, 16 Mar 2024 13:31:35 -0700 (PDT)
Received: from fout3-smtp.messagingengine.com (fout3-smtp.messagingengine.com [103.168.172.146]) (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 E5CBAC14F5F9 for <ietf@ietf.org>; Sat, 16 Mar 2024 13:31:34 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfout.nyi.internal (Postfix) with ESMTP id 940F713800C0 for <ietf@ietf.org>; Sat, 16 Mar 2024 16:31:33 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Sat, 16 Mar 2024 16:31:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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= fm1; t=1710621093; x=1710707493; bh=TvABOCUbVDuVHLZL9Nw7CgSZj/bC Yee/itGk0fhrpig=; b=LDCX+xjyv3CyaU9sXk4wPUA3vo76BXnR7qP/tQb9c0d8 tyH9ryHXVwStEPafTcybfutxzT6yIgq2ENemHNXsf/tslreR5+QgLyxI9EPbe8iU z8d7+jctqUSTnifaJT+SN12Hoax6j+dJ4oOJf5b6MNCuYPng3kgkVscSwdwE/nPG 9BgWEuRKzqlJjMLcs+RK1rxpKpZ0GjeKaKTGSyD9uv9I2tbgUUV2beaDIjdu7e2n 0CedIbuQ8nOnrTFeUTT84MAv3LIIo9+prbUFGvJgfMZtx16VPkY9QGhdmaZI29IX XZCH/LVQYMk9rOP0qiAkTpUZ0MgTVVJXuYkONS0EvA==
X-ME-Sender: <xms:pQH2ZZKzd36uE-rOzioctE-QguMainzgc_bQB8625LCp_DaPfYiN9g> <xme:pQH2ZVK92tIu2oWBKIIEEIlsQ0SL667ghOJ8qmKAmx4ukKGq96hW8y956a8E9NiwY hWCnYWGP2WsXw>
X-ME-Received: <xmr:pQH2ZRugMugVpXjKJH2yT2RClz9pUxfiDXKhlQRGG1PyXjcHiLvjzf3vy_oZRKf9ln3m5SR-m5JJnRq7CSqirnhNLF2EsuIl>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrkedvgdduudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtkfffgggfuffvfhfhjgesrgdtre ertddvjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepheefgeektdelie ehleejheegfeehvdfhieeiheefjefgtddvfedtveehtdektddunecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkh dqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:pQH2ZabZLaGFuQWTevYXhz2bP3bJV7P1ZKG_ZszoSfL6zvHmanPh_g> <xmx:pQH2ZQaUXKd-T2DoVkt89FZo8DNblQAkJWLxZKKrjKgp50EN6EHMxg> <xmx:pQH2ZeAG15nTEAYW1rbmJPD-DsnWwjcl9gXRiimdLIKzqE1dStMkTQ> <xmx:pQH2Zea-2Ln_VkHJpSGtDBHUyCN47e_xW0_nIWLrjGZ7ac_NAIfVSA> <xmx:pQH2ZbwzbOvf7ROkj8hS2GuttjxhtQUKq1DKUiGdVVL9Qxlkt1waeA>
Feedback-ID: i5d8c41f0:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <ietf@ietf.org>; Sat, 16 Mar 2024 16:31:33 -0400 (EDT)
Content-Type: multipart/alternative; boundary="------------01ordU7pC8fepze7hpBjCzAJ"
Message-ID: <f330c14b-5281-45c5-9ec4-0a2337e3df2c@network-heretics.com>
Date: Sat, 16 Mar 2024 16:31:32 -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: ietf@ietf.org
References: <7826C4F13FA874CD79459A4B@PSB> <65A7921B-2A05-439A-976C-226560C5E7F4@strayalpha.com> <e0702d8a-cea5-4928-b571-98442ccd4f29@petit-huguenin.org> <63B37D76-6744-4A3E-BE64-B181013B33CE@episteme.net> <2780ea4c-6041-901c-bb58-ef5e2b1e8a00@gmail.com>
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <2780ea4c-6041-901c-bb58-ef5e2b1e8a00@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lXVtixvI_lIbkqQnW56baPWfFMg>
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, 16 Mar 2024 20:31:39 -0000

On 3/15/24 18:49, Brian E Carpenter wrote:

>> Can we have a go at why we want these mechanisms in the first place
>> instead of making arbitrary changes?
>
> As far as I recall, it was originally intended to ensure that in the
> face-to-face meeting of each WG, people had all read the same version
> of each I-D.

I seem to recall (from sometime back in ancient history, probably the 
early 1990s) that in the days before web submission (and indeed, before 
the web existed) and before xml2rfc and automatic document checkers, the 
secretariat staff once had to do a fair amount of manual processing for 
each submitted internet-draft (including manually extracting them from 
received email, and sometimes corresponding with the authors/submitters) 
and they were pulling all-nighters before face-to-face meetings trying 
to get the late-submitted drafts processed in time.   And I think the 
two-week deadlines were originally instituted in that timeframe, partly 
to reduce the load on the secretariat (but probably also on IESG and 
chairs and maybe other participants also).

I also remember from the days before the 2-week deadline, as an author, 
pulling some all-nighters trying to get drafts submitted before 
traveling to the meeting.

One more data point: I remember when some WGs would request two meeting 
slots during the week, one early in the week and one on Thursday or 
Friday.  The WG would discuss the draft at the first meeting, discuss 
problems and potential resolutions during that first meeting.   Authors 
and major collaborators would then meet privately during  the week  to 
revise and resubmit the draft if they felt they could make progress that 
would win rough consensus.  The Thursday or Friday meeting used to close 
the loop and discuss the changes made during week.

That way, in theory, we could revise a draft twice in a four-month 
period rather than just once.   And often (not always) this actually worked.

Keith