Re: [Mtgvenue] Updated potential meeting location list
John C Klensin <john-ietf@jck.com> Fri, 21 February 2020 22:15 UTC
Return-Path: <john-ietf@jck.com>
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 49F6E12008A; Fri, 21 Feb 2020 14:15:59 -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, SPF_HELO_NONE=0.001, SPF_NONE=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 Lm4zzSiG96yj; Fri, 21 Feb 2020 14:15:57 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 117731200C1; Fri, 21 Feb 2020 14:15:57 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1j5GaR-0001E9-Sc; Fri, 21 Feb 2020 17:15:55 -0500
Date: Fri, 21 Feb 2020 17:15:48 -0500
From: John C Klensin <john-ietf@jck.com>
To: Jay Daley <jay@ietf.org>, mtgvenue@ietf.org
Message-ID: <885793B70B14415B88EAE798@PSB>
In-Reply-To: <5288EF99-20B1-4EED-AD07-5DF8CAE7134F@ietf.org>
References: <13820272-7189-4803-A842-EA86FE051C10@live555.com> <9B420C95-9E85-4969-ADCA-8F3AAE026396@ietf.org> <CA+k3eCQz4qK-1KxYFSA=o3oX4oxG=n4t_YazW4aR2cnX9t=GxA@mail.gmail.com> <F9CC625E-477F-45B5-964F-BAD1D47AFC97@ietf.org> <815DF738991D44E1E197E78C@PSB> <CAA=duU1Qcv+Ha1kLMdnePZT=u9uFfRoNJQfqTqeaZCzW3QY04Q@mail.gmail.com> <614D74EECFB580BEF4729544@PSB> <7EE02B7E-7590-423C-8641-13B366084D79@gmail.com> <EA514464DD5E6D4FE939F2E3@PSB> <5288EF99-20B1-4EED-AD07-5DF8CAE7134F@ietf.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/TVI18jcxoCQRlWEZ0RiaPoFWvxk>
Subject: Re: [Mtgvenue] Updated potential meeting location list
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for email discussion of the IAOC 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: Fri, 21 Feb 2020 22:15:59 -0000
Jay, I see your response below as very encouraging. I agree with you about striving for objective measurements as well, but hope we can avoid the common trap of confusing "hard to measure" with "unimportant". Let me give threeexamples from recent discussions. (1) Jordi's passionate argument against meeting in Barcelona because of potential serious disruption (and the parallels it might have in Hong Kong) are not easily reduced to objective and quantitative measures and I'm sure we could find people on the other side of either position who would be equally passionate. Both are not only hard to quantify or scale objectively but they require judging risks that cannot be known exactly unless one can accurately predict the future (one could say the same thing about the odds of getting snowed in during a given week in Minneapolis (or Chicago, or Calgary, or Stockholm or Helsinki)). However, that does not diminish the importance of those issues. (2) There are several cities on the list that have extensive international and intercontinental direct air connections --something that, as you point out, can be evaluated objectively -- but only if one includes carriers that a significant number of people may find problematic and/or that some companies have on "do not use" lists. The latter is going to be much harder to get good, objective, data about about, but it can be almost as real an issue in deterring travel as places that require itineraries with multiple connections for many participants. (3) Travel or other departments push back aggressively on what they see as "tourist destinations", at least requiring extra justification. I'd guess we pretty much know what those destinations are (although we might quibble about edge cases) but I can't think of a way to either make that categorization objective or to quantify the number of people who would be effected (especially if we ignore whatever historical information we have because things change). Again, that does not make the issues less important. In any even, the general strategy seems sound. Good luck with it. And, with this note, I'm going to stop posting to this thread in the hope that it will help you get on with it. regards, john --On Saturday, February 22, 2020 10:44 +1300 Jay Daley <jay@ietf.org> wrote: > Replying to a whole bunch of emails: > > I have no idea how cities originally got onto this list, or > why some cities are not there or why some cities we have been > too are no longer there. I'm also not sure what is assessed > at what stage (which I will go away and find out). The > current state is that I've inherited an opaque, historical > process where the secretariat had done their job some time ago > but the list had not been updated and the community not > informed, and so I corrected that. > > My future focus is on defining an overall assessment pipeline > which implements the consensus policy. My initial thoughts > about that are that this definition should include: > > - how things enter the pipeline. I expect this will have > multiple entry points depending on who is asking and probably > different requirements for each, such as: — sponsors, who > offer to pay for specific cities/regions and who will probably > have the lowest burden of all — venues who send us bids with > special pricing who will probably have the highest burden and > be asked to do substantial work if they want their bid > considered — local community members, who will probably be > expected to do some initial research — community members who > have preferred cities for an endless set of reasons - what > stages there are in the assessment and what is assessed at > each stage - what community engagement takes place and when > > The detailed assessment process is already in place and ably > managed by the secretariat so this will be more an exercise in > clear definitions than changing the underlying details. > > One exception to that and something you are going to see from > me a lot, is that I prefer to use independent empirical data > for complex decisions instead of human judgement. So when it > comes to airport links I will be looking to see if there is a > public index of airport connectivity that we can refer to. > Similarly, comments have been made about some cities being > unsuitable due to air-pollution and I will be looking at the > standard air-quality indices to guide us there. Obviously > there are nuances and ranges for which human judgement must be > used, but the index should be the starting point not an email > thread about the number of flights in/out. > > Finally, there are actually two cities listed as unsuitable - > Nassau and Macau - for the reasons given in my announcement. > > Jay
- Re: [Mtgvenue] Updated potential meeting location… John C Klensin
- Re: [Mtgvenue] Updated potential meeting location… Andrew G. Malis
- Re: [Mtgvenue] Updated potential meeting location… John C Klensin
- Re: [Mtgvenue] Updated potential meeting location… Bob Hinden
- Re: [Mtgvenue] Updated potential meeting location… Victor Kuarsingh
- Re: [Mtgvenue] Updated potential meeting location… Mary Barnes
- Re: [Mtgvenue] Updated potential meeting location… Mary Barnes
- Re: [Mtgvenue] Updated potential meeting location… Victor Kuarsingh
- Re: [Mtgvenue] Updated potential meeting location… Ted Lemon
- Re: [Mtgvenue] Updated potential meeting location… John C Klensin
- Re: [Mtgvenue] Updated potential meeting location… Adam Roach
- Re: [Mtgvenue] Updated potential meeting location… Fred Baker
- Re: [Mtgvenue] Updated potential meeting location… Fred Baker
- Re: [Mtgvenue] Updated potential meeting location… John C Klensin
- Re: [Mtgvenue] Updated potential meeting location… John C Klensin
- Re: [Mtgvenue] Updated potential meeting location… Jay Daley
- Re: [Mtgvenue] Updated potential meeting location… John C Klensin
- Re: [Mtgvenue] Updated potential meeting location… Michael Richardson