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

Benson Muite <benson_muite@emailplus.org> Sun, 03 March 2024 07:50 UTC

Return-Path: <benson_muite@emailplus.org>
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 45FA3C14F694 for <mtgvenue@ietfa.amsl.com>; Sat, 2 Mar 2024 23:50:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level:
X-Spam-Status: No, score=-2.196 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.091, 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=emailplus.org header.b="GT6V/WxG"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="BbFhzpO4"
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 xabYgT0iOsi9 for <mtgvenue@ietfa.amsl.com>; Sat, 2 Mar 2024 23:50:22 -0800 (PST)
Received: from fhigh5-smtp.messagingengine.com (fhigh5-smtp.messagingengine.com [103.168.172.156]) (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 790A0C14F61D for <mtgvenue@ietf.org>; Sat, 2 Mar 2024 23:50:22 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 956CC11400B6; Sun, 3 Mar 2024 02:50:21 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Sun, 03 Mar 2024 02:50:21 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emailplus.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm1; t=1709452221; x=1709538621; bh=YiZmAhYUANvE2g46nvVqkJK7GHU1jZVh uNsPbl5149I=; b=GT6V/WxGIMQG3QuD2Olw2stBvn2ENxEectlC+r39SQlY+aEx 8xVK4CWP7ruS5FjJcKFtEYKHmZjChEAf22ymCrWfOLdxbqw2HJaQWHQlQ9Zqf+re tcEn1IFbWvvxxno7KTBDUPIfJj0eyMh+5quzyt8xoApm/whhIpH48a2LCmo2KxvV o9uIeU6ISQ+N7HjfBACPgRq7c+v807qSX/NxuquyGuK0T5WNN9MDJ05l7rKXW71D rC+2WXqfOZoLc43cawUlpYGi5Gmx6ml8ljDXJgj19i0xInBOu1+iM/EvbbltIOM7 Dt2ZAVuFFvXnbFTbCSlnHq8n8k+fkGUEbC5Usw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1709452221; x= 1709538621; bh=YiZmAhYUANvE2g46nvVqkJK7GHU1jZVhuNsPbl5149I=; b=B bFhzpO46zSmDXQDRGHQQxc7j5CU2FIRCRohON2/1z+jCdC6R1xsuKsQ24BWX3my1 hJsr1wFRl5sf3EtYfMAhs28WhVYgYoY/N4EQT9eh961bsi5HXEw66J992k3Yo/Hz bSKhRbJYcciHg98djZXDHzG0MDvXVC9pC0hEvzatkJXMu6EHoK010be4Rd6Aye1O c+BG3J5AdoQ1sy2fYe19TcVBulG68mWMG8KfUW0z3LT1LZCymnmbf7PCvuNCngkD xElWNzTXTtDSOoMVFNjlF/2SDv96hn6Tf10eVZ4uCJFvXaSZt2O8Qp59t/bbCpOz JOnM4ytPQfeeKqR8AWTtg==
X-ME-Sender: <xms:vSvkZXVbluzVjpu9RXquxrn5YeK6ZXKzv5LOSfQU4ahVI1pjU2bRhw> <xme:vSvkZfkqAuAp0TT49eY8qtMreBXG7FEiRffj9Kw9d5dPaZM6uj-jbvhT8B4mdSjqD yekRNCUpJuyPjPQ>
X-ME-Received: <xmr:vSvkZTZadNZAVFnpjR_tSRWb-0X-y7_AKhjLXjubNAWU5eu6xrf8YrJBICjtJ4URY3SO3g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrheeggdduudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfvfevfhfhufgjtgfgsehtkeertddtfeejnecuhfhrohhmpeeuvghn shhonhcuofhuihhtvgcuoegsvghnshhonhgpmhhuihhtvgesvghmrghilhhplhhushdroh hrgheqnecuggftrfgrthhtvghrnhepuddtvdegheeltdetvdeuvedvudeileeffeetiedu heekfeekudfhfeejkefgueegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomhepsggvnhhsohhnpghmuhhithgvsegvmhgrihhlphhluhhsrdhorhhg
X-ME-Proxy: <xmx:vSvkZSVZQhuFf_SK09XCXqJNSaeHehNqwsgNzK4MZzqJZbu0Lbo5ug> <xmx:vSvkZRn3trf3x6aUf2Vmes95A9IjNuP5nFvlGHeW3m45L9WlsLM9fw> <xmx:vSvkZfdH2pRUfGyzfVxzKCqZe6JcKy7NKeXkuSYeEPOeI8cmE_shzA> <xmx:vSvkZWxudkyHcQgAP_ZlVr4rSeKblnZA6qg5JEFvueEGo-Ej2Bo3_w>
Feedback-ID: ic1e8415a:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 3 Mar 2024 02:50:20 -0500 (EST)
Message-ID: <3c0820dc-60c5-c499-125c-98459af581ec@emailplus.org>
Date: Sun, 03 Mar 2024 10:50:14 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: mtgvenue@ietf.org
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>
Content-Language: en-US
From: Benson Muite <benson_muite@emailplus.org>
In-Reply-To: <01e32f42-1c1f-189e-6440-f8559a35bb48@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/QGT0S6X1w14d8eCmb0pu1EO4szo>
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: Sun, 03 Mar 2024 07:50:27 -0000

On 02/03/2024 22.49, Brian E Carpenter wrote:
> 
> Benson,
> On 02-Mar-24 18:58, Benson Muite wrote:
> ...
>>   The aim of using time zones to split the globe is to have a more
>> precise and equitable criteria for distribution of meetings than North
>> America, Europe and Asia.
> 
> 
> I've read that sentence a number of times, and I still don't
> understand its logic.
> 
> Why does precision help us? We know that however many criteria
> we have, no site will never meet all criteria precisely, so the
> precision of any individual criterion really doesn't matter.
> 
> 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 Peninsula, but I imagine it would take me at
> least two days to get there. Similarly, Buenos Aires is due
> south of Nuuk, but I'm not sure there is a convenient flight.
> 
> 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.
> 
The present criteria of Asia, Europe and North America makes meetings
outside of these exploratory, yet there are regions within Asia, Europe
and North America that should be considered exploratory. Reykjavik and
Dakar were given as examples of places that should be exploratory, but
under the current criteria, Dakar would be considered exploratory and
Reykjavik not exploratory.  By using time zones, the rotation policy can
be separated from the exploratory policy.

Economic groupings are also important.  Adding diversity in meeting
locations by economic group (or a related proxy such as bytes of data
used per day per capita) maybe helpful.
> Time zones *are* relevant for remote participation, but
> that's a problem we face anyway, even if we meet in Antarctica.
> 
>     Brian