Re: Question about pre-meeting document posting deadlines for the IESG and the community
Pete Resnick <resnick@episteme.net> Sun, 17 March 2024 02:26 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 50831C14F5F9 for <ietf@ietfa.amsl.com>; Sat, 16 Mar 2024 19:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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_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=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 lpxZQPUQBXgE for <ietf@ietfa.amsl.com>; Sat, 16 Mar 2024 19:26:00 -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 7196AC14E515 for <ietf@ietf.org>; Sat, 16 Mar 2024 19:25:59 -0700 (PDT)
Received: from [31.133.134.200] (dhcp-86c8.meeting.ietf.org [31.133.134.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.episteme.net (Postfix) with ESMTPSA id 4Ty20P4LRWzRnby; Sat, 16 Mar 2024 21:25:57 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=episteme.net; s=mail; t=1710642359; bh=eN8fpK5fKV8QPcWfvvuiduZ9mF77/XAB7xrOXksxHAw=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=MHjCZWy2uEVjS4vSZbz2wFBBIycNmIHRLcWj3sqrNfVJ0fDKrXRRuwfhd81kTHIRu s82KQGf3jQN/81leLdhs/qG+0fUudff+WUwuEvCn0bBmZxlBnqK6Yn5BIdml+9AVmW uvKPE192PBc6VC+oR3QM0TjOduoqV8wDsUQ/73io=
From: Pete Resnick <resnick@episteme.net>
To: John C Klensin <john-ietf@jck.com>
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Subject: Re: Question about pre-meeting document posting deadlines for the IESG and the community
Date: Sun, 17 Mar 2024 12:25:53 +1000
Message-ID: <85D994BF-5E89-437B-821C-12DE93C403B3@episteme.net>
In-Reply-To: <53C617FA98D84931861C1F59@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>
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, T_SCC_BODY_TEXT_LINE 0, MID_RHS_MATCH_FROM 0, FROM_HAS_DN 0, RCPT_COUNT_THREE 0, TO_DN_SOME 0, TO_MATCH_ENVRCPT_ALL 0, MIME_GOOD -0.1, __THREADED 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/-8QjLsL2uwLLiVp6vnmrzDUsH1E>
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 02:26:06 -0000
On 17 Mar 2024, at 11:41, John C Klensin wrote: > --On Saturday, March 16, 2024 19:17 -0400 Keith Moore > <moore@network-heretics.com> wrote: > >> On 3/16/24 17:20, Carsten Bormann wrote: >> >>> The current times (close 2 weeks before, open 1 day before) >>> are exactly what is needed in a good number of cases, and >>> their consistency helps people who want to do work across WGs. >> >> Nothing's perfect, but IMO the current 2 week deadlines are a >> good compromise most of the time. > > I agree. Two weeks is about right... So, as I said earlier, many things have changed, and in this case I disagree that the 2-week moratorium on posting is needed anymore. As Keith pointed, there were two reasons we set up the moratorium in the first place: (1) The secretariat had to hand-process I-Ds back in the day and was swamped before the meeting; and (2) In order to be prepared for the meeting, you wanted to have people to read the same version of the document so that everyone was on the same page. Only later, as a side effect, did we get reason (3): People act well in the face of deadlines, and this one was conveniently imposed due to other considerations. However, several things have changed. Justification (1) has completely gone away; the tools take care of things.. But even in the case of (2), I think the justification has mostly gone away. It used to be that posting a changed version would really be a problem: If some edits went in late, you would have to re-read the whole document and try to figure out what changed, and you'd had better kept the old version, because once the new version was out the old one was deleted from the server. But nowadays, we keep the old versions on the server, and we have a perfectly reasonable diff tool, where you can choose any version and get the diffs from the current version in an easy to read format. It's no longer such a big deal to read whatever version is available when you are preparing fore the meeting, and then look at the diffs just before the meeting. (And again, remember that the moratorium ends now at the beginning of the week, so it is not even effective for purpose as it stands.) That leaves the "deadlines are useful" reason. And that's a perfectly good reason, on a WG-by-WG basis, to allow chairs to close the submission for their WGs if they want to impose a deadline. But it doesn't justify shutting the queue for all WGs (some of which might not be meeting f2f) or all documents (some of which might not be associated with any WG or RG), or all chairs (some of whom might have good reasons for a late add). > and, at least last I checked, > we had procedures for ADs to make exceptions. I assume that, if > we needed exception procedures for other streams, we could > probably make them up in a hurry (if they don't already exist > without my noticing). 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. 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. (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.) > The question that started the thread is whether other mechanism > of getting documents posted --other than, e.g., mailing list > discussions-- frustrate the intent of that two week limit and, > if so whether they are reasonable. I had intended to open up, > and ask for community consideration of, the much broader set of > questions and was not asking about localized patches. Pete > clarified that point and said what I should have said more > explicitly -- that we need to look at the whole collection of > interrelated issues rather than applying isolated small patches. > I would add that we should not get distracted by possible > patches to the point of losing sight of that collection of > issues. I don't know that it is what either Keith or Carsten > intended, but a discussion of any of whether the cutoff should > be two weeks before the meetings start, what "starts" means for > that purpose, whether it should be 14 days, 20 or 10 days, one > day, some other number, or abolished entirely would be, IMO, > just the sort of distraction from the larger issues that I think > Pete and I are concerned about. Indeed, even talking in terms of a "posting cutoff" is a mistake. If mailing list discussion within the moratorium period comes to consensus (with text) on a particular issue in a document, that is just as problematic (or not) in keeping everyone on the same page preparing for f2f discussions. Does that mean that we should have an IETF-wide 2-week moratorium on mailing list discussions before f2f meetings? Of course not (I hope). But some chairs may wish to say, "On issue X, let's close discussion on the list until the f2f meeting, as I think a more interactive discussion (perhaps with people with Transport/Security/I18N/whatever expertise present) would be more helpful." And that would be fine. Again, let's discuss what we actually want to have happen, and then decide if we need some grand principle or rule imposed, at an IETF/Area/WG level, for that and what tooling (if any) we need to make it happen. > So, btw and IMO are discussions on the tools list about ways to > make Github more or less efficient for document review and > whether it is time to prohibit some I-D preparation tools or > formats. They are probably all part of the larger set of > questions but, like others of those questions, they raise > important policy questions including, again IMO, just what they > IETF means when we talk about being open, welcoming, > transparent, etc., and what we all mean when we say that > something represents IETF community consensus. Yep. See above. >> I'm less sure about opening submission to new drafts one day >> before a meeting. I might prefer that they be opened again the >> day after the meeting closes. > > Again, part of the broader problem (with interactions with other > parts), as are the questions of when WGs are expected (or > required) to firm up agendas and organize and post meeting > materials. And questions about who/what is imposing the expectation/requirement (e.g., the chair, the AD, the IETF as a whole, the tooling, etc...) 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