Re: [Mtgvenue] New Version Notification for draft-daley-gendispatch-venue-requirements-02.txt

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 04 March 2024 00:35 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 37905C14F60B for <mtgvenue@ietfa.amsl.com>; Sun, 3 Mar 2024 16:35:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.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_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_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 Ob0xoi0qHHGG for <mtgvenue@ietfa.amsl.com>; Sun, 3 Mar 2024 16:35:25 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 1BCF2C14F5F5 for <mtgvenue@ietf.org>; Sun, 3 Mar 2024 16:35:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 8CA6A3898B; Sun, 3 Mar 2024 19:35:22 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Cn1g7_rCGCfw; Sun, 3 Mar 2024 19:35:20 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A30D138988; Sun, 3 Mar 2024 19:35:20 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1709512520; bh=MfqeEUyo8ufNoi0cPjXkvyxPv74GAXYdjGUogW/k978=; h=From:To:Subject:In-Reply-To:References:Date:From; b=V5VUqCBoqBtjney0iUTKS2Oiaz9qh+h+7ZXiLkJ2QRj6a/4j5cxlKjGR2OShlPrXd 2wg2yYVHWd5z4ELnz0BLx6yW9sZ2cQYxuANfwmKmafBd+GkqbEFtNUSS+oa3m9BPoi xUVib9Hmci5pN9+XHxl5MsZrJ7BRP5orIjzWV7N1AzuLqM5AcDizS7sh8KrznyBOjQ 2VRQvrwLZNvxvFpoQWWtvi+MC97o6setCo83/xv0KgUwyBIja8lK7uZwtRYmXBY0bB ccSXULH1nzVDemxeFT+Ycvv4OQyqRpEnfYnCB0tXDd560WmpQKJ3jnPNBolqtq90sH 0rY20vq6OD2cQ==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9D9BA12F5; Sun, 3 Mar 2024 19:35:20 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, mtgvenue@ietf.org
In-Reply-To: <01e32f42-1c1f-189e-6440-f8559a35bb48@gmail.com>
References: <20240229190603.4E224842AE6E@ary.qy> <73C7B5D1-22CD-4CFA-8A6F-D1A75EE120D3@mnot.net> <8140ac05-63dc-1701-209f-6de9d45cb759@taugh.com> <2EBD8C64-E02F-4520-B45B-CFCE7805539E@mnot.net> <CABcZeBMA_b6pu4+rQC8nsXwOX8WX+9eaPnej778-=QhMxOwC9Q@mail.gmail.com> <fac34d30-5c82-9033-9450-e446e200e54c@emailplus.org> <01e32f42-1c1f-189e-6440-f8559a35bb48@gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sun, 03 Mar 2024 19:35:20 -0500
Message-ID: <3990.1709512520@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/VHFxpyv9SheohV_UxTlSjZCKtj0>
Subject: Re: [Mtgvenue] New Version Notification for draft-daley-gendispatch-venue-requirements-02.txt
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: Mon, 04 Mar 2024 00:35:29 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > How is a criterion based on time zones equitable? It isn't effective as
    > far as travel times go. I'm only one time zone away from the Kamchatka

And it wasn't as if the IESG chose to go with the actual time-zones of the
cities that we "missed" during the pandemic, deciding to start things at
"local" noon, instead.

    > More seriously, time zones have no particular relationship to regions
    > where we have concentrations of active or potential participants. From
    > the point of view of effective meetings that are reasonably convenient
    > for participants, economic and geographical groupings are much more
    > important.

    > Time zones *are* relevant for remote participation, but that's a
    > problem we face anyway, even if we meet in Antarctica.

For me, I think that our adherance to 1-1-1-* (by "continent") has been
sufficiently loose over time that an adherance to something by time zone is
likely to be no better for physical travel, but it might help with remote
attendee pain.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide