Re: [Mtgvenue] [IAOC] testing draft-ietf-mtgvenue-iaoc-venue-selection-process against the venue change that just occurred

Alissa Cooper <alissa@cooperw.in> Tue, 18 July 2017 13:17 UTC

Return-Path: <alissa@cooperw.in>
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 73EFF13167D; Tue, 18 Jul 2017 06:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=pPk7sRTN; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=P3cpJ2kN
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 dIsunp8LOvSO; Tue, 18 Jul 2017 06:17:00 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 095D1131B4B; Tue, 18 Jul 2017 06:17:00 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 78AF320A49; Tue, 18 Jul 2017 09:16:59 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Tue, 18 Jul 2017 09:16:59 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=edZoFN0RB5SchpETp7 ml6Aqo5b7/eJEjdChFSHeM2nw=; b=pPk7sRTNskR+hcUiy4t0uzRUl5BgVzYIRX QJ3VYqesFqrzUp39vrtrV+oGSV6LS81ArM1grPbZIuBlwjdECmZ9FZWSDfq2C7Y1 AOHODgcdFGbtGCwjHiTIaz6km9QmwSHeNNFquZsQw4mgqllKOLwcgfgzZ3FMlNqO p9BBJ5c2EayF3s6H9UdCKhRhC1Q/hIE8gaN7fjSPwYj+n8WU2+8VNP+5ha2BLWTw dQgC+SWwz7WSIRwVnLUJ4QAIFvSjU6XvlfHtY886mE+jYT1ZWEKX6igu6yTUrHpT Q/VswkYVvzpL8ly0XmRQsX1jICHIVJATc0pnrMxajkgD77MeXw9w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=edZoFN0RB5SchpETp7ml6Aqo5b7/eJEjdChFSHeM2nw=; b=P3cpJ2kN xcqSw9f/9R1UQQXszYBrGCRwptcp/i+ZviO+BqCBy74QZOfp0DCS1Jc68oHY7uE3 KQZfBp/OJ2x5wFus7RAUxmF8mi5dvW4VkNxlB+qXrf4Uqm4tJMVPBYxkZAVuc8SS Ok/DGUXu2XL0uz+BzKl5O6T85hH4XGNTD4nOvipPpnhMITiNpa8zAjAUiHXccujQ KGieG0RIXb2Eyy7Rl2Br2YnszX8lDAtn5VP7yqXW+xk2OWCope/o213Qfv9hQk0v 99HeqTaAhLkHre381pEvyZaVPN63Pdd5iJ0OqHNwU4hdPPYYmNIWvwFZH6OZEz2d CZfE6Qd+zGJ5ng==
X-ME-Sender: <xms:SwpuWTZ02EcKq58RUOynfFZZ9alp7ROoA1UJwOvHyeqOjtdj9_QZNg>
X-Sasl-enc: gSCOUCqP8mEi0krjyWfN8quq7am0ZFqAeDZNF7wRbxCG 1500383819
Received: from sjc-alcoop-8816.cisco.com (unknown [128.107.241.174]) by mail.messagingengine.com (Postfix) with ESMTPA id 65EE77E17C; Tue, 18 Jul 2017 09:16:58 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <764472f5-29d6-5c1c-3fd6-35d9db81f32e@nostrum.com>
Date: Tue, 18 Jul 2017 09:16:56 -0400
Cc: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>, Eliot Lear <lear@cisco.com>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>, IAOC <iaoc@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <50DF5C58-7D7E-40F3-A58C-4017CC061F6F@cooperw.in>
References: <27b1a6a1-5dfc-6403-1d24-3171f7dba74a@cisco.com> <20170718094546.pcu4mx6ezxdo3k7c@mx4.yitter.info> <E4BE06F7-1886-4734-846A-7F95D874D315@tik.ee.ethz.ch> <764472f5-29d6-5c1c-3fd6-35d9db81f32e@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/9XtBWwQPt6Jx0Tjifiib8esjUH4>
Subject: Re: [Mtgvenue] [IAOC] testing draft-ietf-mtgvenue-iaoc-venue-selection-process against the venue change that just occurred
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: Tue, 18 Jul 2017 13:17:06 -0000

> On Jul 18, 2017, at 6:43 AM, Adam Roach <adam@nostrum.com> wrote:
> 
> On 7/18/17 11:59, Mirja Kühlewind wrote:
>> So my understanding is actually that the venue was chanced because of the uncertainty we currently have about the travel restrictions that may occur in future. So I actually think it does not match the bulletpoint on travel restrictions that is cited below.
>> 
>> Also how do we know that 60 people or more will be effected (despite the fact that we are taking about potential further changes that may happen in future but did not happen yet).
> 
> My understanding is that this was based on the 15% number that Leslie cited in her recent announcement:
> 
>> 15% of those living outside the US who responded to the survey said they were so concerned about US travel restrictions that they decided not to attend IETF 98 in Chicago.
> 
> Prediction is hard business; however, it's been pointed out to me that "tomorrow will be the same as today" is frequently as good a predictor for weather as an actual, well-sourced forecast.

15% of people who responded to the survey is not the same as 15% of expected attendees. The survey gave us an indication of concerns in the portion of the community who chose to respond to it.

Also, this is a minor detail, but at the time when we may need to make a venue change decision, we may not have an expected attendee number for the relevant meeting. For example, we don’t presently have the expected attendee number for IETF 102 because those numbers get established as part of the 2018 budgeting process, which starts next month. The estimates have been somewhat stable in consecutive years, but that could change. So if people are wanting to be real strict about this (e.g., thinking that 60 is different from 55), it might involve having to generate the expected attendee number further in advance than usual, or using a number from a previous year or something.

Alissa  

> 
> /a
>