Re: [Mtgvenue] Where we are, post #2

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 30 January 2017 22:30 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 621D612964B for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 14:30:12 -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 U3vt10WZWU4i for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 14:30:11 -0800 (PST)
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (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 533B212963D for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 14:30:11 -0800 (PST)
Received: by mail-pf0-x241.google.com with SMTP id 19so24391974pfo.3 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 14:30:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=AGqrXd1RpAhRMoJmc3nqgoup7bYOiQG0XnTrK3UiKho=; b=RWmcf88UjZv3cVTfmaQeBckh64NCKUlgDbO7Mxx1OM0/mEq9dVO2LI2YYTzICloQyF a9P83Srw7ZCBvj5BqoXAxh1rUCWbdCiibrZgzaIIJod1TrP6xIWp7+xKXmU+8LKsHKqJ DHJim4BkVB4zzooQn45jL7f+PLmUwiSaeknx8lPsbvyk690JsDrhiyAaQh0E+zAej8b6 uNWVD+NZ4UaLH1XjbtgY4VCI6o3QM+p5Ds6eusfrB3ipc+G6QE7yNe9jwm7LkHmyC1rF NSpNa8DfKCBy10WpuE0B15C7F0tltmnZ0/0APgDfaI4mQb//2zwO1KhWIm/n9RxUFrzZ NEeg==
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:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=AGqrXd1RpAhRMoJmc3nqgoup7bYOiQG0XnTrK3UiKho=; b=SvA7MTipmFMSdlNvCHpTwRdQET+4IyhXTv8mrRKv1koAhjMm8T80WLkEyFFlsFHC2f QKLVNyaphdGXqo8Z5FacykfeufsXUifI6d8TJT3h9N7gaDYyVWyQl9ZisOt19+lA7K8N 1cZoz+oD8YEeBQyzWAIvR6t6E+rWFkmAtmngycMk3eFiYYR/txbuC9EN74I0OnRaTvsa LJFu2OjOorOWojYoM5JT8Y5oHRALV1w44APYijKhlVailjRbvQNk8LOcIMTUcRONLcu6 myaU9wwZDZoR/FdAZCRscwHGqLcpBG/7MYvgHzTCap5lYJjbGfup8Wnwm7g3HNxQ8BAQ DxiQ==
X-Gm-Message-State: AIkVDXKUpYFvMe1qacvec/pVEgq2tkncX8tk5AmG6EMVUIokin6thpZzkiceWd32JAe6Mg==
X-Received: by 10.84.136.75 with SMTP id 69mr35405376plk.172.1485815410741; Mon, 30 Jan 2017 14:30:10 -0800 (PST)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by smtp.gmail.com with ESMTPSA id c74sm35078434pfc.1.2017.01.30.14.30.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jan 2017 14:30:10 -0800 (PST)
To: Melinda Shore <melinda.shore@nomountain.net>, mtgvenue@ietf.org
References: <056312a7-741c-77af-8759-657aedb24f43@nomountain.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <8e501210-5db5-c8db-5aa0-0f58a0a90d59@gmail.com>
Date: Tue, 31 Jan 2017 11:30:08 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <056312a7-741c-77af-8759-657aedb24f43@nomountain.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/08uU1QFZBgBl6pT7FEAB2g1sy7s>
Subject: Re: [Mtgvenue] Where we are, post #2
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: Mon, 30 Jan 2017 22:30:12 -0000

Hi Melinda,

Thanks for the attempt to bring clarity.
On 31/01/2017 10:47, Melinda Shore wrote:
> Hi, all:
> 
> This post will try to identify questions under discussion
> in which there is no agreement.
> 
> 1) Stephen raised questions about temporal aspects of the policy -
> that a venue's acceptability may change.  After some disagreement,
> he further clarified that he thinks that section 5 should contain
> a substantive statement that the IAOC would publish how they're
> diverging from the processes laid out in this document and then
> get community feedback.  Dave asked if there's some reason
> that this should be treated differently from how other documents
> change and Stephen answered that he thinks that processes will
> change more often than the document will be revised.
> 
> So, we need to bring this to closure.

I think his point has some merit. Perhaps it can be met by a
small addition in

>> 5.2.  Consultation
...
>>    d.  On a public web page, the IAOC lists all candidate cities, when
>>        community input was solicited, and if a city is to be considered
>>        as a potential meeting location.

Add to this:

 If the IAOC has decided to waive any requirements for a
 particular location, or to consider additional requirements,
 this will also be noted on the web page.

That is both transparent and future-proof.

> 2) There was disagreement about the use of the phrase "business
> travel" in section 3.2.  Brian proposed "typical business travel"
> in its place.  I don't think I've seen any comments on this, and
> it should be an easy one to close out.
> 
> 3) The food discussion is, as usual, somewhat contentious.
> Stephen has proposed that accommodating chosen dietary restrictions
> should not be mandatory.  My understanding from his messages is
> that the scope of "chosen" includes religious and ethical
> dietary restrictions.  At this point I'd be interested in hearing
> from anyone who agrees with that, as he appears to be alone on
> that one.

I disagree. Further, I suggest that we duck the question by simply
deleting the words "health-related and religion-related". It's
not our business why people have dietary restrictions.

   Brian