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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 25 March 2024 02:40 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 197DBC14F6E2 for <ietf@ietfa.amsl.com>; Sun, 24 Mar 2024 19:40:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.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_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 (2048-bit key) header.d=sandelman.ca
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 d9piCZcKvxQb for <ietf@ietfa.amsl.com>; Sun, 24 Mar 2024 19:40:36 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4F42C14F6BB for <ietf@ietf.org>; Sun, 24 Mar 2024 19:40:35 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [111.65.32.75]) by relay.sandelman.ca (Postfix) with ESMTPS id 9DA421F448; Mon, 25 Mar 2024 02:40:33 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="ni9E2D8F"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 57DB3A1913; Mon, 25 Mar 2024 12:40:28 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711334428; bh=jz3JtFKZ+Pzy42wVxVPuUBOQ0l1xBLLKWEYK0sK1E44=; h=From:To:Subject:In-reply-to:References:Date:From; b=ni9E2D8FwsrlUPBpelrm60hhb1vmvpDLp0WFZ818/jMZkO/ycNm2Jpe4m/XZ0UWIs kd7QlcOOA3a4NtD5mQ5ZPg0EHUqH3EWyU4P0esKYzx172nVEevk+JebPrqLoUP2Gv5 S3+I1xDg28Ecf3/DymqGq2t/j7opsG30ALftw5nlr5sLd1YJHFnhane6H6SPkha7jN zUmDTt8Lu0e5xPP30NCKTblZBIF774enQOi+E6uI6zDpOdjEpDEwsF8bzCq9pCE70P WP4G4B1kNz1aXiQzyRRtIq+1X5f2Prpl3gDLw35mPngazAbMEwRMe5hjpZO77CiQK+ xAuT9IQfzJz/w==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 56122A190E; Mon, 25 Mar 2024 12:40:28 +1000 (AEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: Question about pre-meeting document posting deadlines for the IESG and the community
In-reply-to: <9734B1A4D11337C5997FBB20@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> <85D994BF-5E89-437B-821C-12DE93C403B3@episteme.net> <6.2.5.6.2.20240322143647.10ef96f8@elandnews.com> <569FBECE-E637-4B2A-86C5-4F7B7AEC333E@episteme.net> <7F1502637EB78EE7032F4384@PSB> <332944.1711248099@dyas> <9734B1A4D11337C5997FBB20@PSB>
Comments: In-reply-to John C Klensin <john-ietf@jck.com> message dated "Sun, 24 Mar 2024 12:09:54 -0400."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 25 Mar 2024 12:40:28 +1000
Message-ID: <377761.1711334428@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tBFA3Rgr-4wokaT3GytoxlDTvt0>
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: Mon, 25 Mar 2024 02:40:40 -0000

John C Klensin <john-ietf@jck.com> wrote:
    >> Quite rare, yet worth multiple long emails over many years and
    >> a lot of hand-wringing. Please name some names!  Don't be shy.
    >>
    >> At the least, please tell the ADs and/or the IETF Chair.

    > They have been told, long before this exchange.

And?
Either the AD does not think it a problem, or the WG refuses to change, or ??
yet, your complaint, which is multiple years old, persists.
Are you in the rough?  Why not share, because maybe metoo.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*