Re: Venue definition and distribution comments summary (was Re: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice)

Lloyd Wood <lloyd.wood@yahoo.co.uk> Thu, 26 April 2018 01:17 UTC

Return-Path: <lloyd.wood@yahoo.co.uk>
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 17ED912D94C for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2018 18:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.co.uk
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 UrI2B8Z5B5pP for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2018 18:17:09 -0700 (PDT)
Received: from sonic303-21.consmr.mail.ir2.yahoo.com (sonic303-21.consmr.mail.ir2.yahoo.com [77.238.178.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E05412D96C for <ietf@ietf.org>; Wed, 25 Apr 2018 18:17:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048; t=1524705426; bh=+F2t/TCMLCg9pNUNZxsc+nAB4NHPwdpuYxgz3M49u+8=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=GdPyIIhcXN1vWkPHG64wQRZGbY7pYoH6VEvMyC0/Gdi90SRh+OoO8qnwhzt8YyJiA4rIyIQ4irWmoS88mZDMrvGEwJfPg9mg8kA9B3mgTAIwBFzaIulW62z+/uwH7/nnVZ+mk67XzpEktRgpluW+l5z5r9nlOF0ZrW2OECOJ0Yxxprv6DIxiMl9pz/jUkZzOPev7LpdOgPgUDYqmCfeJVJwrjHGP+3sz+3Kbt0P/5bHAhkDBW7iShgYnH4kbgi2R/h3CHQ1Gt/cg1JB+P04eD0UDiHZe20Gkf5Xpc9s9CJXNDkFF0Luh80Y7+BpZG5GdmOGZPtrn6w54wqgg1HzKvA==
X-YMail-OSG: f2x5F1IVM1n84Kae6lmJ_PsLG72D.PUPjMhbebgYyJ5K8Ks1ulDQ0p3V0gVQzag 7zx3eWyPFAKCDdWRRcAZTZ_o8VmN243O8AMCSvrJXPevZA1vILGMvMj90jwDxlzwjBCAt5li.LQv I7K2wec9cmY0RR08J7kzmVPHy2CV05_G6l4AUI6m7H18PZ_dPqqrBpSH8LQO3N33M_dwyZCPKBvh MDutHSE28Gt2KCpnvhMysUF6zS1kIhUWGl2skabCdvo9FjsJ3o.ccP94.E8qFQKDTyTqzW61HuEB .Ep90DNNDDDqmgQ2Gc6NyFk.eRvpLLFZTMpmNYCNULHxrZ4Al1TrI8nORpV2t03KbsOQ3uxBO_OM _wARvXuBVfxZ3BJOMETA5TR6thE2JgcflwBik8HBH12NZbEB1mZqlGFd62FhfEmKkrvAeShZhvOp quGUY2NLRwszYeCNAWaMEuIufKRnQq0QOX4tNen_mC.Gu8tdDU1BBMSwqIlu3AsSM.IBb3PyJsin Zn3BdGtqYUrSwA29R9yXp6uwdK7nCYr5dmxWiO6C.fpd8GCXBlaXqHwtMobsefVHQnMD2Xmgq6E7 DJY00fjuedPaUEdJ88AlWPhrhCZwf5tzVWKg_
Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.ir2.yahoo.com with HTTP; Thu, 26 Apr 2018 01:17:06 +0000
Date: Thu, 26 Apr 2018 01:17:03 +0000
From: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Reply-To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
To: Suresh Krishnan <suresh.krishnan@gmail.com>, mtgvenue <mtgvenue@ietf.org>, IETF <ietf@ietf.org>
Message-ID: <378454279.1472022.1524705423161@mail.yahoo.com>
In-Reply-To: <A45155E8-DAA5-4CA5-BC3F-139A6A999228@gmail.com>
References: <152295916074.25912.932711807710247299.idtracker@ietfa.amsl.com> <20180419013457.fq4ruqj7p4lfwxb4@mx4.yitter.info> <CABcZeBPXUqe6ixF+Yx7P6E3Jt3fGjAMUrP368DTedGq-O-T61Q@mail.gmail.com> <ED191002-261F-4E3C-A359-CBFEF1812AF8@iii.ca> <531F8285-71D0-4EFD-AC2D-C96DD98E4F44@fugue.com> <23d1e398-887d-4c7c-2c9d-da9fad200415@cs.tcd.ie> <b4a8b4a7-7919-df3f-f301-1cd634f4900c@nostrum.com> <115F383E-49E6-4237-849D-E36B26DA977B@cisco.com> <9768922C-6FE9-48BF-8E98-623B3B4960CF@gmail.com> <8013c41b-242b-6e7e-46d5-41f49456045d@gmail.com> <6C706BC3-F36F-4FB2-B3C3-AD72F26F854B@vigilsec.com> <m2o9i97hbt.wl-randy@psg.com> <94f7064f-4c8e-b77c-9754-b2576d25380e@gmail.com> <A45155E8-DAA5-4CA5-BC3F-139A6A999228@gmail.com>
Subject: Re: Venue definition and distribution comments summary (was Re: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_1472021_662967766.1524705423158"
X-Mailer: WebService/1.1.11819 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8MTH4-Kh3MnQOhmzfkE9Tj_7PfY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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, 26 Apr 2018 01:17:12 -0000

> a) Change “Asia” to “Asia Pacific” - this seems pretty reasonable and non-controversial
depends on intent. The draft does later call out Australia as an exception, and though I'm told discussions about the possibility of holding other IETFs in Australia and in New Zealand have taken place, the events haven't materialised.
Is Australia in Asia-Pac? well, no, since it's not in Asia - it's a separate continent - nor is it in the Pacific; New Zealand and Hawaii certainly are in the Pacific, but one is more likely to hold an IETF than the other.
On reflection, I dislike the use of 'should's, even though this is BCP and that's not strictly speaking normative text. I think the draft should say something simple like 'most IETF participants are in the Northern Hemisphere, and meeting locations often reflect and follow that, favouring ease of travel', rather than getting bogged down in exact regional definitions or ratios to follow or aspire to.
(For many years, Cisco's office in Bedfont Lakes had a very very odd map of the world as a plaque in its demonstration area. I hope that's not the Asia-Pac definition being used...)
Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood 

      From: Suresh Krishnan <suresh.krishnan@gmail.com>
 To: mtgvenue <mtgvenue@ietf.org>; IETF <ietf@ietf.org> 
 Sent: Thursday, 26 April 2018, 9:27
 Subject: Venue definition and distribution comments summary (was Re: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice)
   
Hi all,
  I have seen messages from Russ Housley, Andrew Sullivan, Eric Rescorla, Richard Barnes, Cullen Jennings, Ted Lemon, Lou Berger, John Levine, Adam Roach, Brian Carpenter, Stephen Farrell, Mark Nottingham, Melinda Shore, Tom Petch, Charles Eckel, Fred Baker, Randy Bush, Jeff Tantsura and Lloyd Wood on these two topics. Thank you very much for your inputs.  Summarizing till now, I do see three major items that have come up.

a) Change “Asia” to “Asia Pacific” - this seems pretty reasonable and non-controversial

b) Better definition of the regions - I did ask the WG several times but my read of the WG opinion was that this was not considered desirable. Will look for further guidance from the WG, chairs, and AD on this regard. 

(As background information. the draft had earlier suggested defining the regions based on either the distribution of RIRs (e.g.  ARIN/RIPE/APNIC/LACNIC/AfriNIC) or the UN statistical department's classification of macro geographical regions.)

c) The 1:1:1 ratio not being representative of the participation - I am realizing now that the text in the draft might have made this sound like a rigid requirement that needs to be satisfied without weighing the factors in venue-selection-process. At least from my point of view as document editor this was not the intent and I apologize for not making this more apparent. This was intended to be something we aspire for, but difficulties in venue selection specifically for the Asia meetings have meant that in practice we are far from this distribution. As a data point, over the past 30 non-* meetings *ONLY 6* have been in Asia (13 in North America and 11 in Europe). I can propose some text to make it clear that this policy needs to be seen in the context of venue-selection-process along the lines suggested by Andrew. 

Does that sound sufficient to address the distribution ratio, or should we continue to further discuss putting in a different ratio?

Thanks
Suresh