IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 24 March 2024 02:23 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 38745C14F683 for <ietf@ietfa.amsl.com>; Sat, 23 Mar 2024 19:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_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=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 ixOA5Dr2rYaS for <ietf@ietfa.amsl.com>; Sat, 23 Mar 2024 19:23:30 -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 121E8C14F682 for <ietf@ietf.org>; Sat, 23 Mar 2024 19:23:29 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [111.65.56.232]) by relay.sandelman.ca (Postfix) with ESMTPS id 0189A1F4A8 for <ietf@ietf.org>; Sun, 24 Mar 2024 02:23:26 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="Zw7IkT6G"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 63601A1913; Sun, 24 Mar 2024 12:23:01 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711246981; bh=8N9TfN5Sna3DP1KsNOG5zV8Jw7KXa8ARu7cK3xgBYkQ=; h=From:To:Subject:In-reply-to:References:Date:From; b=Zw7IkT6GdVxH6osNBhx1BoIffmoyWWZFZV4WXSSYxtiYzSZM1ZmGQtRMX/gFI1pYd kRkQhXACJLLbzn+XQrhKmvp2btKPi/aEFi1lpgLoCWoAIw8KjRnEOAwh9MsbHmKLxF WPnGL0hUJKq92VNZy7JruIS3fVw/IW6htt1TyU41tqsHVTWkyA1R+7IuaZOjtQZtTo Cfhs4ZikXrFjXWtpuJtLa1ZRFAJNpPCk3NS7qqAwS28aEFWZj0n+kZD2sls/zT+bZj 4oVLQ1VmcopN823dQcEwZ+0cEeUIX4DsI4h70q4Rng7kfu1XJO4eSBynlYZLkskdSa ixb7mZ/lbenng==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 60D7EA0A82 for <ietf@ietf.org>; Sun, 24 Mar 2024 12:23:01 +1000 (AEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: Question about pre-meeting document posting deadlines for the IESG and the community
In-reply-to: <569FBECE-E637-4B2A-86C5-4F7B7AEC333E@episteme.net>
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>
Comments: In-reply-to Pete Resnick <resnick=40episteme.net@dmarc.ietf.org> message dated "Fri, 22 Mar 2024 19:48:39 -0700."
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: Sun, 24 Mar 2024 12:23:01 +1000
Message-ID: <330958.1711246981@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B4WXG16jEt2F--llEFzvNHPeRlI>
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 02:23:34 -0000

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.

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

v2.23.0 | Report a Bug | By Email