Re: Updated potential meeting location list

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 20 February 2020 03:46 UTC

Return-Path: <prvs=13198620e6=jordi.palet@consulintel.es>
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 70E8612002E for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2020 19:46:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 hmZc5MeeVbc0 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2020 19:46:33 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32CFB12001B for <ietf@ietf.org>; Wed, 19 Feb 2020 19:46:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1582170370; x=1582775170; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=S/apPabN 7R6hwnKcGBiWhcoynaXW2+1+N4ZYKfwhLfA=; b=NsuypkUO2vJhkhVHWoKPgHf9 YM3x6HMHt7hlAlXop2FudCnEzZ0obcP4Jax5BrrsoWPDg0iYxgxM0EOUboebHN59 5g19sCYt+nBK7SxMwHSJm3MJKY8sxhm+XBfEbsHJ890cBwAPgaXpWotXfaFGJDTZ RNUfYb4ud+86NHSc964=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 20 Feb 2020 04:46:10 +0100
X-Spam-Processed: mail.consulintel.es, Thu, 20 Feb 2020 04:46:10 +0100
Received: from [220.247.146.197] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000063737.msg for <ietf@ietf.org>; Thu, 20 Feb 2020 04:46:08 +0100
X-MDRemoteIP: 10.8.10.6
X-MDHelo: [220.247.146.197]
X-MDArrival-Date: Thu, 20 Feb 2020 04:46:08 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=13198620e6=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/10.22.0.200209
Date: Thu, 20 Feb 2020 14:45:51 +1100
Subject: Re: Updated potential meeting location list
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <12588269-A1C9-420B-9B32-7ED8EA923DE7@consulintel.es>
Thread-Topic: Updated potential meeting location list
References: <158216966829.17661.75511909982202631.idtracker@ietfa.amsl.com>
In-Reply-To: <158216966829.17661.75511909982202631.idtracker@ietfa.amsl.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lK4s27a0Y9QmyJvHDH3qpvh9K2c>
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:46:37 -0000

If Dublin is the same hotel as the previous time, please discard it. It is not matching the selection criteria.

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.

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.