[Mtgvenue] Food (was: Re: comments on draft-ietf-mtgvenue-iaoc-venue-selection-process-04)

Dave Crocker <dhc@dcrocker.net> Mon, 30 January 2017 19:28 UTC

Return-Path: <dhc@dcrocker.net>
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 9BC96129575 for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 11:28:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-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=dcrocker.net
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 qzVR37VTnxhy for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 11:28:25 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B70FB129576 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 11:28:25 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v0UJU0CB006485 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 11:30:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1485804600; bh=9tNCHQss+IkCdenbAbKHLKTyMetfBqzukwLyiCQ8h0s=; h=Subject:References:To:From:Reply-To:Date:In-Reply-To:From; b=X0302SKg/81BooerN7rqOblsgTQ/Q/pB9szyjdXSeoHmcElwF7LQeJGavcsseO02I xuPTBN0MZrSKHu3tXbTYo464tENUUj/IW6i0LQ5K++8LsGKTUbd4yS9bEQoDvYU36T QW6A3KeAh6w/hlQdEBCzxy03UxC4wikMcn2sCSvk=
References: <9139334c-9c5e-814d-4299-c6f5950039b8@cs.tcd.ie> <CAHBDyN5K93_HXBM3427KHcMtGq+3g82zKudm6eNB2FMOGrTZ3g@mail.gmail.com> <ace8262c-a863-9140-ebfd-3c1e8d6f8363@cs.tcd.ie>
To: mtgvenue@ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <2dc96522-35e5-d323-7ed3-7ab93ac3e1bc@dcrocker.net>
Date: Mon, 30 Jan 2017 11:28:16 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <ace8262c-a863-9140-ebfd-3c1e8d6f8363@cs.tcd.ie>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/ODgAOlJNn5L-JVUxg75c_4NAxi8>
Subject: [Mtgvenue] Food (was: Re: comments on draft-ietf-mtgvenue-iaoc-venue-selection-process-04)
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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 19:28:26 -0000

On 1/30/2017 11:05 AM, Stephen Farrell wrote:
> So I've no problem with medical issues (as in your case)
> being mandatory or treated at the same level as
> accessibility or whatever is correct.
>
> I don't however think the same applies to cases where the
> dietary restriction is a choice. That's not because I
> want to make anyone's life harder, it's just that I think
> there's a slippery slope there of choices that people
> could make.


Taken to its logical extreme, this might mean choosing a venue that has 
no acceptable choices for vegetarians.  Or for those who don't eat pork. 
  Or...

It is not reasonable to ignore the matter entirely, nor is it possible 
to accommodate all possible needs and preferences with detailed 
requirements.  Hence we have to find a balance between these extremes.

The current text was developed rather carefully and was the result of 
quite a number and variety of discussions seeking to strike a pragmatic 
balance.

If someone proposes changes to these bits of text, I strongly urge them 
to offer specific alternative text and very clear explanation for what 
makes it superior.

In particular the explanation should consider what benefits accrue and 
-- perhaps more importantly -- why the detriments are acceptable.

By way of example -- and I stress this is meant only as an example -- 
agreeing to Stephen's suggestion that Section 3.5 be made Important 
rather than Mandatory means that we could wind up at a venue that only 
serves pork and has no alternate sources of protein.  Silly?  In the 
particular, perhaps, but in terms of making attendance largely 
impossible for people with serious dietary restrictions? Not really.

The implicit view that these are matters of choice and, therefore, 
should be treated as secondary, misses both the fact that they are not 
at all a matter of choice for many folk, and that for many others, the 
choice is an integral part of their life.

Again, we cannot accommodate every detail for everyone.  So the text 
seeks to make things reasonably comfortable for a useful range, and 
reasonably tolerable for others.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net