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

John C Klensin <john-ietf@jck.com> Sun, 24 March 2024 16:20 UTC

Return-Path: <john-ietf@jck.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 DA5B3C14F5EB for <ietf@ietfa.amsl.com>; Sun, 24 Mar 2024 09:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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] autolearn=ham autolearn_force=no
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 eQM7iylWGQIR for <ietf@ietfa.amsl.com>; Sun, 24 Mar 2024 09:20:15 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74FF2C14F5E5 for <ietf@ietf.org>; Sun, 24 Mar 2024 09:20:15 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1roQZw-00083R-On; Sun, 24 Mar 2024 12:20:12 -0400
Date: Sun, 24 Mar 2024 12:20:07 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
Subject: Re: Question about pre-meeting document posting deadlines for the IESG and the community
Message-ID: <0FE963BE36AFC49E57D062A1@PSB>
In-Reply-To: <330958.1711246981@dyas>
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> <569FBECE-E637-4B2A-86C5-4F7B7AEC333E@episteme.net> <330958.1711246981@dyas>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/upT9_Z_qPkjfCp1xxQUk6NCQQAU>
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, 24 Mar 2024 16:20:20 -0000


--On Sunday, March 24, 2024 12:23 +1000 Michael Richardson
<mcr+ietf@sandelman.ca> wrote:

> As the wg chair of a WG which has never met at an IETF, and
> thus the two week freeze serves no purpose for this *WG*, I am
> in favour of the two week freeze.  Why? Because many of us
> participate in more than one WG. Given that the queue now
> (since a few years) opens on Saturday morning rather than
> Monday morning, it provides a useful and reasonable deadline
> which authors can work with.  (I'm agnostic about an earlier
> deadline for -00)
> 
> In one or two cases, the freeze has been annoying to a document
> which was at the IESG, but the AD override worked fine for
> that, and the AD was in fact completely in the loop.

FWIW, Michael, the "participate in more than one WG" point is a
large portion of the point I've been trying to make.

The other question I would ask is why that WG has never met at
an IETF meeting?  Would you and the participants not find value
in possible participation from those are are not heavily
involved or at least already on your mailing list?  Do you not
see that possible exposure of your work to more of the community
as worth the trouble?  That your work is so specialized that
other IETF participants are unlikely to be interested?  Or
something else?

    john


    john