IETF Logo Mail Archive

Re: [Mtgvenue] Update of RFC8719 still not needed

John R Levine <johnl@taugh.com> Thu, 28 December 2023 18:48 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3DCFC151986 for <mtgvenue@ietfa.amsl.com>; Thu, 28 Dec 2023 10:48:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.408
X-Spam-Level:
X-Spam-Status: No, score=-4.408 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_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=iecc.com header.b="ECsK0kig"; dkim=pass (2048-bit key) header.d=taugh.com header.b="PU/f3eDA"
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 aTUi8nwLmBAW for <mtgvenue@ietfa.amsl.com>; Thu, 28 Dec 2023 10:48:11 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2B2FC151981 for <mtgvenue@ietf.org>; Thu, 28 Dec 2023 10:48:11 -0800 (PST)
Received: (qmail 172 invoked from network); 28 Dec 2023 18:48:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=aa658dc2e8.k2312; bh=hpoYD6QdHzWX5amxjoELVACqmpS/iNVEgRIRR2arhWk=; b=ECsK0kig5rMCTvxvqxUlSOw3xs+uaXhx0Y35qeICNVarzFjBCOSdfPLhOUthdfAZzeqSR8KiUrE88QHUg05350bqeHEmqaUhokoS80DC6qIuWji2xKeFTl719AQtzZuH5sbeAQhpSEXv6NsCxGzGe3CCUEPeo+gTEEgEgchdx2xBKAd2NUh+Lt9Jcx57TThaNi8+nGB55QK9zDMFxwttYJ3ZzjvI61JGmpty/OqGlgniKgZ53vlFRDi5woNuo6KoAXIA+A8H/6+2VDGUzj+I3N/d/YWIHJ5wn3TuNtyHXb3Suj1fAUqqbVSI5IbiskSQJTEKT1upzKreYB9+WWm7kg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=aa658dc2e8.k2312; bh=hpoYD6QdHzWX5amxjoELVACqmpS/iNVEgRIRR2arhWk=; b=PU/f3eDAXVUlulW861/zwt7nWMqtzIlB3tRF0z+NLdn2PA1bpa/6ae7DaxZFWdNZetnF48aIIjFe7nm/SZlkx/mfyxuiEitmzLaEXx8JQF/yRkVrVMuIsBYuT1UZM8VSOB1G2hrWhzOXahGajR4zJA8c9T5XFU4P2gofBLemLduGwlgds+BWIo8f6hkK1DO7sHuHWz/mrA92s/tjkzWJbPjHd2yboumE7s1o5YkWEAkozl4G+VhcJ4xQj0gnJIT5YZt8kEUkhi3k6QWNI3pB9fm73npodueik69MKUWW6Qnf76Q2KAAI1+Za/C9D4XPJsUPtJtFgSDLUdvQJD11szg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 28 Dec 2023 18:48:08 -0000
Received: by ary.qy (Postfix, from userid 501) id 264BF7F56AEC; Thu, 28 Dec 2023 13:48:07 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id C80AB7F56ACA; Thu, 28 Dec 2023 13:48:07 -0500 (EST)
Date: Thu, 28 Dec 2023 13:48:07 -0500
Message-ID: <aefe9c5f-e405-c185-fd7d-5a3eee60199f@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Benson Muite <benson_muite@emailplus.org>, mtgvenue@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <b2e3435e-6df3-1411-ac9d-7e2953bdceef@emailplus.org>
References: <20231228172411.910427F55FB9@ary.qy> <b2e3435e-6df3-1411-ac9d-7e2953bdceef@emailplus.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/BBY8rRsHxL2IlFHUN232sFpVf1w>
Subject: Re: [Mtgvenue] Update of RFC8719 still not needed
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for email discussion of the IETF meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Dec 2023 18:48:18 -0000

On Thu, 28 Dec 2023, Benson Muite wrote:
> The primary issue is that the current wording is exclusionary when it
> need not be so.  A secondary issue is that it is backward rather than
> forward looking - we cannot make the internet better solely by looking
> at the past.

I would find it helpful if you could explain in a few sentences why you 
think the IETF has in-person meetings, rather than only doing work on 
mailing lists and by videoconference.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email