Re: [dispatch] dispatch - Not having a session at IETF 119

Jim Fenton <fenton@bluepopcorn.net> Fri, 26 January 2024 20:29 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 41E71C14F61E for <dispatch@ietfa.amsl.com>; Fri, 26 Jan 2024 12:29:22 -0800 (PST)
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 (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 1ejkn3-P3ZnK for <dispatch@ietfa.amsl.com>; Fri, 26 Jan 2024 12:29:17 -0800 (PST)
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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88F6AC14F5EF for <dispatch@ietf.org>; Fri, 26 Jan 2024 12:29:17 -0800 (PST)
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:References:In-Reply-To:Message-ID:Date:Subject:To:From:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=+REp72/iTX3pidGxWhLl75sNljNP/v7y4+2geKVuIUU=; b=EqenNXSWdmzS9iyzzGLMRE50up yEX2WbWPWbi6c6uCliBoK5kfCDn3d4q0CInLcUH0j97cty931xgaqNCUc0M0iH/u4dcNo+E4wGmSA RB2xqBwzECEvvdM5wnqCgTGbyDBDdqx5AFfm8DXvqvH10Rtrg1VPekB6LyWuxjccgIug=;
Received: from [12.89.238.34] (helo=[10.100.9.254]) by v2.bluepopcorn.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <fenton@bluepopcorn.net>) id 1rTSp9-0001HR-Kh for dispatch@ietf.org; Fri, 26 Jan 2024 12:29:15 -0800
From: Jim Fenton <fenton@bluepopcorn.net>
To: dispatch@ietf.org
Date: Fri, 26 Jan 2024 12:29:15 -0800
X-Mailer: MailMate (1.14r5852)
Message-ID: <C500DDE5-5B18-40A0-9411-8A8204BEA434@bluepopcorn.net>
In-Reply-To: <170630075054.44331.12812054230300327889@ietfa.amsl.com>
References: <170630075054.44331.12812054230300327889@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/kevg4rkrGbfaL8CIOa2YaeWvbqw>
Subject: Re: [dispatch] dispatch - Not having a session at IETF 119
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jan 2024 20:29:22 -0000

On 26 Jan 2024, at 12:25, IETF Meeting Session Request Tool wrote:

> Jim Fenton, a chair of the dispatch working group, indicated that the dispatch working group does not plan to hold a session at IETF 119.
>
> This message was generated and sent by the IETF Meeting Session Request Tool.

Just in case anyone is confused about this message, we will instead be having a combined cross-area ‘alldispatch’ session, so the artarea dispatch session is not being held.

-Jim