Re: Updated potential meeting location list

Jay Daley <jay@ietf.org> Thu, 20 February 2020 04:38 UTC

Return-Path: <jay@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36A24120143 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2020 20:38:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yzYeGB-_rjA2; Wed, 19 Feb 2020 20:38:20 -0800 (PST)
Received: from [100.126.75.76] (115-189-87-195.mobile.spark.co.nz [115.189.87.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 7952A1200D6; Wed, 19 Feb 2020 20:38:19 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-C26B5348-B172-4A04-852A-B06687C863F7
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Subject: Re: Updated potential meeting location list
From: Jay Daley <jay@ietf.org>
In-Reply-To: <13820272-7189-4803-A842-EA86FE051C10@live555.com>
Cc: IETF discussion list <ietf@ietf.org>
Date: Thu, 20 Feb 2020 17:38:16 +1300
Message-Id: <9B420C95-9E85-4969-ADCA-8F3AAE026396@ietf.org>
References: <13820272-7189-4803-A842-EA86FE051C10@live555.com>
To: Ross Finlayson <finlayson@live555.com>
X-Mailer: iPhone Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IRS0Xy19tFIyOyRXoOjCtGIbicw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2020 04:38:22 -0000

Hi Ross

> On 20/02/2020, at 5:12 PM, Ross Finlayson <finlayson@live555.com> wrote:
> 
> It might be useful to give the *complete* list of cities that have been “assessed as suitable”, rather than just those that “have been added to those assessed as suitable”.  For example, several cities where the IETF has met recently - e.g. Prague, Berlin, Vienna, London, Paris - were not mentioned, yet Vancouver (where we have met many times, and are about to meet again) is listed in the "have been added to those assessed as suitable” list.  So the list is a little confusing.

In my email announcement I provided a link to the complete list as a numbered reference in the text to aid readability with the URL at the bottom of the message  For reference that URL was https://ietf.org/how/meetings/admin/meeting-location-input/

> Also, FYI, “Malta” is a country, not a city.  (Presumably you mean “Valletta".)

Yes thank you for that, there were a number of city oddities on the list but I missed that one. 
> 
> It’s also a little surprising that no cities in Australia or New Zealand are listed.  (We met in Adelaide in 2000.)  I would expect to see Sydney and Melbourne considered as potential venues, as well as possibly Brisbane, Perth, and Auckland (New Zealand).

Australia and New Zealand do not count as Asia in the policy (the policy specifically states that Adelaide was not in Asia). Consequently our focus for some time has been on those venues that do count within the regional rotation. 

For the moment we are not accepting any recommendations for potential additions to the list until we have put some more transparent processes in place that help us manage the work. 

I hope that clarified things. 

Jay (who lives in New Zealand)

-- 
Jay Daley
IETF Executive Director