Re: Updated potential meeting location list

Jay Daley <jay@ietf.org> Thu, 20 February 2020 03:55 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 D7CFA120041; Wed, 19 Feb 2020 19:55:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 rzmSULt8Znos; Wed, 19 Feb 2020 19:55:28 -0800 (PST)
Received: from macbook-pro.localdomain (unknown [158.140.230.105]) (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 542BC12002E; Wed, 19 Feb 2020 19:55:27 -0800 (PST)
From: Jay Daley <jay@ietf.org>
Message-Id: <AE306706-4FEF-4102-8A04-DACD40A6187A@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F51933E8-BFFA-45FF-807A-6C8C79352FCE"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Subject: Re: Updated potential meeting location list
Date: Thu, 20 Feb 2020 16:55:25 +1300
In-Reply-To: <12588269-A1C9-420B-9B32-7ED8EA923DE7@consulintel.es>
Cc: ietf@ietf.org
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
References: <158216966829.17661.75511909982202631.idtracker@ietfa.amsl.com> <12588269-A1C9-420B-9B32-7ED8EA923DE7@consulintel.es>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P6NlIkENmfnR67e4TrCLGjIygwk>
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 03:55:31 -0000

Hi Jordi

> On 20/02/2020, at 4:45 PM, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:
> 
> If Dublin is the same hotel as the previous time, please discard it. It is not matching the selection criteria.

This list is for cities only, without any specific venue having been selected.

> Even if I was born in Barcelona, I'm sorry to say this: I strongly suggest not going there until the criminals that declared independency stop it definitively. Otherwise, there is a high risk of anything bad happening. Did happen already several times. Once that it is resolved, I will be happy to work on that. A further problem is the high cost of the suitable hotels/conference centers, at least compared with Madrid.

Thank you for that feedback.  We last asked for feedback on Barcelona in March 2017 and may now need to formally ask for further feedback given the changing circumstances since then.

kind regards
Jay


> 
> I continue to work in looking at other possible venues in Spain, but I don't think any others can match our selection criteria at the time being.
> 
> Regards,
> Jordi
> @jordipalet
> 
> 
> 
> ´╗┐El 20/2/20 14:34, "IETF-Announce en nombre de IETF Executive Director" <ietf-announce-bounces@ietf.org en nombre de exec-director@ietf.org> escribi├│:
> 
>    The IETF Administration LLC has updated the list of locations (cities) that have been assessed for their suitability to hold an IETF meeting [1]. This follows extensive assessment of each city including the solicitation and analysis of community feedback. This update adds 29 cities to the list of those assessed as suitable and 2 to those assessed as unsuitable while 8 are still being assessed. 
> 
>    This update is long overdue, for which we apologise, particularly to those that took the time to provide feedback and particularly as some of those cities only now listed as suitable have already been selected for IETF meetings.
> 
>    The cities that have been added to those assessed as suitable are:
> 
>    	Austin
>    	Athens
>    	Barcelona
>    	Boston
>    	Calgary
>    	Chiba
>    	Denver
>    	Dublin
>    	Edinburgh
>    	Fukuoka
>    	Glasgow
>    	Houston
>    	Kobe
>    	Kyoto
>    	Malta
>    	Nagoya
>    	New Orleans
>    	Niigata
>    	Osaka
>    	Ottawa
>    	Philadelphia
>    	San Francisco
>    	Sapporo
>    	Singapore
>    	Stockholm
>    	Tokyo
>    	Toronto
>    	Vancouver
>    	Washington DC
> 
>    The cities that have been added to those assessed as unsuitable are:
> 
>    	Nassau, due to concerns about corporate travel approval
>    	Macau, due to concerns about corporate travel approval
> 
>    The cities that are still being assessed are:
> 
>    	Busan
>    	Helsinki
>    	Hyderabad
>    	Kolkata
>    	Marrakesh
>    	New Delhi
>    	Panama City
>    	Tel Aviv
> 
> 
>    Please note the following important information on the meeting location selection process:
> 
>    * The meeting policy [2] is for an annual rotation between Asia, Europe and North America (the "1-1-1" policy).  
> 
>    * The final selection of meeting location is based on a complex set of criteria and so multiple cities are assessed and then multiple cities and venues are visited in each region before a selection is made.  This process generally takes some years to complete.
> 
>    * The cities on the list have not yet been chosen to host an IETF meeting, this is an early stage in a long process.
> 
>    * Inclusion on the list as a suitable location does not mean that an IETF meeting will be held in that location, only that it is now a location that we can explore further.
> 
>    * We are working on a mechanism for the community to recommend specific cities, which will involve much more than just nominating a city, and until then we will not be accepting any recommendations.
> 
>    Please feel free to contact me directly if you have questions or comments
> 
> 
>    [1] https://ietf.org/how/meetings/admin/meeting-location-input/
>    [2] https://datatracker.ietf.org/doc/draft-ietf-mtgvenue-meeting-policy/?include_text=1
> 
>    -- 
>    Jay Daley
>    IETF Executive Director
>    exec-director@ietf.org
> 
>    _______________________________________________
>    IETF-Announce mailing list
>    IETF-Announce@ietf.org
>    https://www.ietf.org/mailman/listinfo/ietf-announce
> 
> 
> 
> 
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
> 
> 
> 

-- 
Jay Daley
IETF Executive Director
jay@ietf.org
+64 21 678840