IETF Logo Mail Archive

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:39 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 B02F1C14F6E2 for <ietf@ietfa.amsl.com>; Sun, 24 Mar 2024 19:39:11 -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 (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 KpXd1rr6mZvj for <ietf@ietfa.amsl.com>; Sun, 24 Mar 2024 19:39:06 -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 9F8BEC14F6E1 for <ietf@ietf.org>; Sun, 24 Mar 2024 19:39:06 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [111.65.32.75]) by relay.sandelman.ca (Postfix) with ESMTPS id F1E821F448; Mon, 25 Mar 2024 02:39:03 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="IUXdwHU5"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 6FB10A1913; Mon, 25 Mar 2024 12:38:56 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711334336; bh=8wm7OrZFgF6dQHUr/fym89XhhAI+2iaD3rgCSjFNOhQ=; h=From:To:Subject:In-reply-to:References:Date:From; b=IUXdwHU50wJkCGbKL4DKpfW4ibvloXkKCBfmRBrlwLnQTbe8IbcyXakLuKpj4ctZU m1TXIleGgCPcQiHsUdqnwP44IGDIc0THXybOjllVlzQTgkSLk35+NNbIHML888YJeH rGghRGQ60SIsgqrNn4TiZezrK29jO5R9xxgw7uYMsEHSrR/Ni0pok56bUL5iFOedwv W2FQDQ7d62U5HfuH4bUraV9c3J7GfEreiosS6pukLJi9cUHCawqmF091pi0VrzqvS1 iA2lVQOfJxebh2d2MNCPHr5mGxgwnRPWkdz8mwyI6+nUiv6g2wnO01ZEqij51Y2ax0 iY07CxCe/HnDw==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 6C694A190E; Mon, 25 Mar 2024 12:38:56 +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: <0FE963BE36AFC49E57D062A1@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> <330958.1711246981@dyas> <0FE963BE36AFC49E57D062A1@PSB>
Comments: In-reply-to John C Klensin <john-ietf@jck.com> message dated "Sun, 24 Mar 2024 12:20:07 -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:38:56 +1000
Message-ID: <377701.1711334336@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g57pbKWksAHHbDEi0cl8hdtvwb4>
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:39:12 -0000

John C Klensin <john-ietf@jck.com> wrote:
    > 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

The participants do not have travel budget. It's a small (8-10) group.
They are open source developers, largely unfunded, or funded through consulting.
We could have a meeting during plenary week, but all that would do is make
those of us who do participate in multiple WG experience more meeting
conflicts.

We move our March meeting to the first week of April, the November meeting to
the beginning of December (with no end-of-December meeting), and we cancel
the July meeting entirely.
See: https://datatracker.ietf.org/wg/cellar/meetings/

The majority of our work is done on ML and github issue/pull-request.

We would welcome more participation from "the rest of the IETF", but it is
indeed very specialized.

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

v2.23.0 | Report a Bug | By Email