[Mtgvenue] issue #3: Too many mandatory

Eliot Lear <lear@cisco.com> Wed, 05 April 2017 13:40 UTC

Return-Path: <lear@cisco.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 BDE3F129447 for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 06:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 uMJzbUtXBbL1 for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 06:40:53 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF7B3128DF6 for <mtgvenue@ietf.org>; Wed, 5 Apr 2017 06:40:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7361; q=dns/txt; s=iport; t=1491399652; x=1492609252; h=to:from:subject:message-id:date:mime-version; bh=VFNBUepkmW/ANcJqW/B4ABY6ziO303uAwXgQZD2eka8=; b=GHKBQJS6USQpW3x4lq/11aLmp7UFsG7w+cXwe+FuRjKtD+er2w6NVzhn 1zzS2yyzY2AqGTUNZdXYliYfUNW1k/A+qojTRPQxk38mTGTmf3jL6sg9j pn1PPkO0DvUwGRKMKKEBqrcHjlL6A31vG3RsQZC+Ld3XPkIUulkiqliaV g=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ApAgCV8+RY/4cNJK1cGwEBAQMBAQEJAQEBg1SFT4oSoVyFNIIOiW8/GAECAQEBAQEBAWsdC4U/UmECXw0IAQEQiXqbLJAHgiYrij4BAQgBAQEBFQ+IU4pHgl8FiweRaYN8gg2MSYphhluTdh84gQUlFggYFYccPol+AQEB
X-IronPort-AV: E=Sophos;i="5.36,278,1486425600"; d="asc'?scan'208,217";a="232763428"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Apr 2017 13:40:51 +0000
Received: from [10.86.241.121] (che-vpn-cluster-1-376.cisco.com [10.86.241.121]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v35DeoMO017961 for <mtgvenue@ietf.org>; Wed, 5 Apr 2017 13:40:51 GMT
To: "mtgvenue@ietf.org" <mtgvenue@ietf.org>
From: Eliot Lear <lear@cisco.com>
Message-ID: <37de22dc-04a4-f868-698e-cf03cd791957@cisco.com>
Date: Wed, 05 Apr 2017 15:40:48 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="lwXoGWda2RJ0NbJPWd4tXX4nB0RBxWS98"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/LMbIXMThlvWJCrft7LUlYn8ssQE>
Subject: [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 13:40:55 -0000

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. 

From Mandatory to Important:

  * Travel to venue is acceptable based on cost...
  * The venue is assessed as favorable for obtaining...
  * Travel barriers and visa requirements...
  * Economic, safety, health...
  * Facility support technology and services...
  * Facility directly provides or permits...
  * The IETF Hotel(s) directly provide, or else permit...
  * The guest rooms at the IETF Hotel(s) are sufficient...
  * The Venue environs, which includes both onsite, as...
  * A range of attendee's health-related and religion...
  * Overflow Hotels can be placed under contract...
  * The Venue environs include budget hotels within...
  * 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)

Several requirements are removed based on the discussion.  They include
the following:

  * Available travel issue assessments -- such as...
    This requirement is to be moved into Section 5.
  * The economics of the Venue allow the meeting to be...

This leaves but three mandatory requirements as follows:

  * Consultation with the IETF Community has not produced concerns
    sufficient to disqualify the Venue.
    This requirement should probably turn into normative text in Section 5.
  * The Facility is assessed to be able to provide sufficient space in
    an appropriate layout to accommodate the expected number of people
    to attend that meeting. (reworded to be clear as to what is mandatory)
  * The Facility permits easy wheelchair access.
    Based on discussion in the room.

Eliot