Re: [Mtgvenue] adoption of draft-krishnan-ietf-meeting-policy-01, question on geographic descriptions

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 14 January 2017 03:21 UTC

Return-Path: <brian.e.carpenter@gmail.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 2B225129426 for <mtgvenue@ietfa.amsl.com>; Fri, 13 Jan 2017 19:21:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 BYgfRJm4g_hT for <mtgvenue@ietfa.amsl.com>; Fri, 13 Jan 2017 19:21:48 -0800 (PST)
Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (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 6984B1293F5 for <mtgvenue@ietf.org>; Fri, 13 Jan 2017 19:21:48 -0800 (PST)
Received: by mail-pf0-x242.google.com with SMTP id e4so310299pfg.0 for <mtgvenue@ietf.org>; Fri, 13 Jan 2017 19:21:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=8VWSJKCbiijuuTJwbPYkok1ZQ+gqs//CAUQHFII39wE=; b=ZSPtqoJoOj/pFGfZf/oqhRJ8OO0pbRzre0XTnkTIQ1DivEBU6FJgBaGgBd1Osqfh0d 4d3M0YlK+m3Q/HLy5LwcwsF8zxzw8YiUK1PTfz0RNGL99cnkiauRgRMG2wfWGIiYmwg3 Wn2cb4Abl9mmerdnF4RJ4YjriCyV3PLY1tZHG51TaHbRz8/QW2cKvBgEEHc0IVJIWCmW irEXFEcI9QZ/6XCQb2pBfRw/Eysd3ThatmpxdMBhfmzWwO0tOlZH9QFhQFCxlwDSq+wY dZaJHc4osERwqep/BmjYrfAut9cLSP0TpQQav1WD9dw/rFlj2YC7pCZnbSzjhKzx4n0N ovBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=8VWSJKCbiijuuTJwbPYkok1ZQ+gqs//CAUQHFII39wE=; b=hjDl8nULn/jCUPD4SsvyrLY7FFhqVaVhixh2A8eFgeyglbDWpY3ml+iGsJIErMvdyM M14RNFGrtOJojqrPbeGKWnC2b7Ts8O5Lvb7tZEJx5FrJXzSw3R6g7N8zFoV0ZNdMdV8q 3UyaqMlFGEnXkj7n2VkxmA9wDo7wZVaCqa0a6ThLwQFQKdBDwIdSTgvgtEd63FJxiXrd yiu1jo4SKpjxpvJLNpA6rYmQQltM/51QLIMjryuogNtfoBUDternEyHmlXrPWgRsPIAQ Ncr+BGVHiRDe3VGbGblbFaGKCjiavclzPhwf/+dTCXVICCRJhtZ6DaBkQUEkl+LeX3XJ NYXw==
X-Gm-Message-State: AIkVDXKSXnd7DErEAVtLm0ywZaJLSV39+o/bnso4Yet2Q4BcQDw8mAxmbQ7rHVvMym981w==
X-Received: by 10.84.143.68 with SMTP id 62mr33992498ply.63.1484364107959; Fri, 13 Jan 2017 19:21:47 -0800 (PST)
Received: from [192.168.178.21] ([118.148.125.124]) by smtp.gmail.com with ESMTPSA id k76sm16285281pfg.42.2017.01.13.19.21.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Jan 2017 19:21:47 -0800 (PST)
To: Fred Baker <fredbaker.ietf@gmail.com>, Soininen Jonne Nokia-NET/Espoo <jonne.soininen@nokia.com>
References: <4F553B02-363B-4274-BA5D-B332174DA10F@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <f9754576-dcaf-f7c4-e89e-8bd1480f0f6d@gmail.com>
Date: Sat, 14 Jan 2017 16:21:54 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <4F553B02-363B-4274-BA5D-B332174DA10F@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/6wuVsCupVmI1l1tNWwwbSU7DoRo>
Cc: "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Subject: Re: [Mtgvenue] adoption of draft-krishnan-ietf-meeting-policy-01, question on geographic descriptions
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 14 Jan 2017 03:21:50 -0000

On 14/01/2017 11:40, Fred Baker wrote:
> On geographic regions, I am concerned with the level of armchair quarterbacking implied. There is legitimate concern over whether Mexico or the Caribbean are included in "North America", or whether "North America" means "the US and Canada". I could see an argument suggesting that Mexico and the Caribbean should be considered "Latin". I think that most of us can find Europe and Asia on a map, and question the need to nail it down more closely. If regions served by RIRs are in view, I would suggest including LACNIC and AfriNIC in the comment.

Firstly, I think that using the RIR "regions" is by far the simplest way of
avoiding endless arguments. I don't think it has major practical implications.

Secondly, and regardless of that, I am a bit hesitant about any language
that seems to treat the rest of the world as second class. Certainly mentioning
that (based on current participation statistics) travel and time zone
optimization does not lead to many meetings in the LACNIC and AfriNIC areas
is reasonable. Saying that we make exceptions is reasonable. But on balance
I don't like the term "wildcard". I think that "exploratory" might be better,
as in

   The 1-1-1-* meeting policy is a slightly modified version of the
   aforementioned 1-1-1 meeting policy that allows for additional
   flexibility in the form of an explorarory meeting denoted as a "*".  This
   exploratory meeting can be used to experiment with...

For example, "exploratory" would certainly have applied to IETF 27.

      Brian

P.S. to save digital ink, I will add that I also support adoption of the draft.