Re: [Mtgvenue] issue #3: Too many mandatory

Dave Crocker <dhc@dcrocker.net> Wed, 05 April 2017 17:42 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 0BC93126C26 for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 10:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 XpXhAIuRCHzK for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 10:42:11 -0700 (PDT)
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 47E5C129407 for <mtgvenue@ietf.org>; Wed, 5 Apr 2017 10:42:11 -0700 (PDT)
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 v35HiJGw011913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mtgvenue@ietf.org>; Wed, 5 Apr 2017 10:44:19 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1491414260; bh=4t/QG68VPHdxvJmGIxu+9mew7ZvkTfVUWIKrOTG8k04=; h=From:Subject:To:References:Reply-To:Date:In-Reply-To:From; b=M9USzPYUXvTa0KF2JcQ/h9RmWkObQ/C+UE7kDO+Eq5N1iXJP9F9wGK1Ji//grz1ty KKaB9RGQvyyvWMS+8KC0YWmdOmkpfH5BjP31j6wvnTmI8yMr675LvfXXkC65zn2bVV +taGgawDjvrY/ayiAK25A2vOTMk/E8L6wufxlubo=
From: Dave Crocker <dhc@dcrocker.net>
To: "mtgvenue@ietf.org" <mtgvenue@ietf.org>
References: <37de22dc-04a4-f868-698e-cf03cd791957@cisco.com>
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
Message-ID: <7add7c4a-032f-6b78-5b5f-861835a64f9a@dcrocker.net>
Date: Wed, 05 Apr 2017 10:42:02 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <37de22dc-04a4-f868-698e-cf03cd791957@cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/xTAB6WKBPBaekbT7W-6-hNpEY7I>
Subject: Re: [Mtgvenue] issue #3: Too many mandatory
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 05 Apr 2017 17:42:13 -0000

On 4/5/2017 6:40 AM, Eliot Lear wrote:
> As mentioned by the chair, I am downgrading requirements based on 
> working group discussion, mostly from Mandatory to Important.  As a 
> reminder, the words are intended to be used consistent with their plain 
> meaning.  That is- just because something is now Important specifically 
> does not mean that it is UNimportant.

While it's understandable to wish for a shorter list, the realities of 
what this community keeps insisting on is what produced the current set.

For each item that folk propose to drop, we should carefully discuss the 
history that produced it and the likely community reaction if the 
requirement is not met, going forward.


>  From Mandatory to Important:

So this means that any of these items can be traded-off against some 
other item.  That means that for each one, it can be acceptable not to 
satisfy the 'requirement'.

Note that there is always the ability to seek exceptions to any 
requirement.  What dropping this item does is to move it from being an 
exception requiring community review to something the IAOC can decide 
without community review.


Consider...


>   * Travel to venue is acceptable based on cost...

So, it's tolerable to have the travel costs, time and/or effort be 
prohibitively high and/or difficult?


>   * The venue is assessed as favorable for obtaining...

The challenge in downgrading this has already been noted.


>   * Travel barriers and visa requirements...

So, it's tolerable to have travel barriers and visa requirements be 
UNacceptable?


>   * Economic, safety, health...

So, going to dangerous, horribly expensive environments, rife with 
outbreaks of pandemics is tolerable?


>   * Facility support technology and services...

How, exactly, are we doing to have a successful meeting if this is not a 
mandatory requirement?


>   * Facility directly provides or permits...

Same question.


>   * The IETF Hotel(s) directly provide, or else permit...

Same question.


>   * The guest rooms at the IETF Hotel(s) are sufficient...

Same question.


>   * The Venue environs, which includes both onsite, as...

Sam question.


>   * A range of attendee's health-related and religion...

So we are back to deciding that it's acceptable to have folk with 
special dietary requirements have to bring a week's worth of food with 
them to the meeting (or to have to travel long distances from the venue, 
in order to eat)?


>   * Overflow Hotels can be placed under contract...

It will be tolerable to have no overflow hotels under contract or to 
have them be a long way away from the meeting venue?


>   * The Venue environs include budget hotels within...

The goal of inclusivity will not be significantly damaged if there are 
not budget hotels or they are distant from the venue (meaning long and 
maybe expensive transit both ways)?


>   * There are sufficient places (e.g., a mix of hallways, bars, meeting
>     rooms, and restaurants) for people to hold ad hoc conversations and
>     group discussions.
>     (This last one is split out from a Mandatory)

Given how often and vigorously complains when this is not satisfied, 
what will make it tolerable, going forward?



d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net