[dispatch] Alldispatch at IETF 121
Jim Fenton <fenton@bluepopcorn.net> Fri, 04 October 2024 21:44 UTC
Return-Path: <fenton@bluepopcorn.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61524C1D52EF; Fri, 4 Oct 2024 14:44:34 -0700 (PDT)
X-Quarantine-ID: <CU2XnCciK0p7>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...T_ADDRESS@@ for details. Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, 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=bluepopcorn.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 CU2XnCciK0p7; Fri, 4 Oct 2024 14:44:30 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04AD5C1840F7; Fri, 4 Oct 2024 14:44:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:Date:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=OjRPQC/CQVT2qh74IoZjr2G5lmJ/4Vcrsj1Mzue9pAA=; b=eS7mojMylCVWGhb7Cd4ZQp5qzq eIAYPRK+9X60Y7VKa6mdsdarCZVinu6GOR2+ulSlzVFEGsVoxJC7V3q1Fnx689o9nF4+jXZR/+aIo +jVlsztippVAqJ1o1LaKwsiXtveuGtpsWcUN+hcrknUw7MFCKuT0fGHGv/qIxJgvguss=;
Received: from [2601:647:6801:6430:e19b:ce94:26f3:8453] (helo=[10.10.20.169]) by v2.bluepopcorn.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <fenton@bluepopcorn.net>) id 1swq68-007A6p-1Y; Fri, 04 Oct 2024 14:44:28 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
To: alldispatch@ietf.org
Date: Fri, 04 Oct 2024 14:44:27 -0700
X-Mailer: MailMate (1.14r5852)
Message-ID: <034BC6D3-395F-42E2-AA66-7B33A449D7AF@bluepopcorn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; markup="markdown"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: MO5NM4MLXF7FPTR2ONCPWLQ3LUI4DTR7
X-Message-ID-Hash: MO5NM4MLXF7FPTR2ONCPWLQ3LUI4DTR7
X-MailFrom: fenton@bluepopcorn.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dispatch.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: dispatch@ietf.org
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [dispatch] Alldispatch at IETF 121
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/VMqBZcGCxDgTT1RD4QWEuyMm_hg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Owner: <mailto:dispatch-owner@ietf.org>
List-Post: <mailto:dispatch@ietf.org>
List-Subscribe: <mailto:dispatch-join@ietf.org>
List-Unsubscribe: <mailto:dispatch-leave@ietf.org>
As you may have already seen, the preliminary agenda for IETF 121 has come out and Alldispatch will be Monday from 15:30 to 17:00 (subject to change, of course) rather than the first thing Monday morning. Note that this is also a shorter timeslot than at previous alldispatch sessions. If anyone has a topic to be dispatched that the alldispatch chairs haven’t already gotten, please send them to alldispatch-chairs@ietf.org ASAP. We already have a quite full agenda that we will be publishing in the near future. Alldispatch will be conducted as described at https://wiki.ietf.org/en/group/alldispatch. If you are contemplating proposing a topic to be dispatched, please note the requirement to have an internet-draft submitted by the cutoff date (21 October). -Jim (for the alldispatch chairs)
- [dispatch] Alldispatch at IETF 121 Jim Fenton