Re: Updated potential meeting location list

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

Return-Path: <prvs=1319f974a5=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 5857612007A for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2020 20:05:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, 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 okbVdo18jw7z for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2020 20:05:23 -0800 (PST)
Received: from mail.consulintel.com (mail.consulintel.com [IPv6:2001:470:1f1d:275::250]) by ietfa.amsl.com (Postfix) with ESMTP id 137C812002E for <ietf@ietf.org>; Wed, 19 Feb 2020 20:05:21 -0800 (PST)
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.com, Thu, 20 Feb 2020 05:05:21 +0100
Received: from mail.consulintel.es ([2001:470:1f09:495::5]) by mail.consulintel.com ([2001:470:1f1d:275::250]) (Cipher TLSv1:AES-SHA:128) (MDaemon PRO v16.5.2) with ESMTPS id md50001034310.msg for <ietf@ietf.org>; Thu, 20 Feb 2020 05:05:20 +0100
X-Spam-Processed: mail.consulintel.com, Thu, 20 Feb 2020 05:05:20 +0100 (not processed: spam filter heuristic analysis disabled)
X-MDRemoteIP: 2001:470:1f09:495::5
X-MDHelo: mail.consulintel.es
X-MDArrival-Date: Thu, 20 Feb 2020 05:05:20 +0100
X-Return-Path: prvs=1319f974a5=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1582171495; x=1582776295; 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; bh=1mgFYir0PVXv0AOQ5TDRAn06sFFVJ7Oj80 PSjkbY6m8=; b=nWloyieYJIBBIROzoc52S9VAIO/KqvZWuNp0JOE3aHJYPJ3ozF iTMTXraAC+KyeTIsbp+TJzWl34NDsSDzk8gxGunDsXN5r02uVfHuyjj0fYUH5Htv odk9CvSliW3E6WNf/EbcmEtSKPA5T3QeDToXmdXboJ+Ojx3JnZrH75Wzg=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 20 Feb 2020 05:04:55 +0100
X-Spam-Processed: mail.consulintel.es, Thu, 20 Feb 2020 05:04:54 +0100
Received: from [220.247.146.197] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000063747.msg for <ietf@ietf.org>; Thu, 20 Feb 2020 05:04:54 +0100
User-Agent: Microsoft-MacOutlook/10.22.0.200209
Date: Thu, 20 Feb 2020 15:04:38 +1100
Subject: Re: Updated potential meeting location list
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <3BF89679-7801-46BA-B1FA-BF201B21EBD3@consulintel.es>
Thread-Topic: Updated potential meeting location list
References: <158216966829.17661.75511909982202631.idtracker@ietfa.amsl.com> <12588269-A1C9-420B-9B32-7ED8EA923DE7@consulintel.es> <AE306706-4FEF-4102-8A04-DACD40A6187A@ietf.org>
In-Reply-To: <AE306706-4FEF-4102-8A04-DACD40A6187A@ietf.org>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3665055887_803664492"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GgQevUneakwWISh-9J4iqr-oMrs>
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:05:27 -0000

Got the point about Dublin.

 

Regarding Barcelona, I don’t know what is in the international news, don’t trust them, neither local tourism bureau, they were selling us “all good” when we did the visit a few years ago, I was telling “no” and time proven I was right. Is sad to say, because I will be very happy to have a meeting in Barcelona, but this is not a resolved issue, for at least 2 more years, may be even more.

 

Furthermore, I think there in only a single conference center that match our criteria. Nothing changed in that regards. And that one is *very* expensive.

 

Regards,

Jordi

@jordipalet

 

 

 

El 20/2/20 14:55, "Jay Daley" <jay@ietf.org> escribió:

 

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






**********************************************
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.