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

Alissa Cooper <alissa@cooperw.in> Thu, 06 April 2017 15:29 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 95DC3129437 for <mtgvenue@ietfa.amsl.com>; Thu, 6 Apr 2017 08:29:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 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, URIBL_BLOCKED=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=gsDeaYmB; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=MoKRG0vR
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 usIxVDrP2AsR for <mtgvenue@ietfa.amsl.com>; Thu, 6 Apr 2017 08:29:23 -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 11394129400 for <mtgvenue@ietf.org>; Thu, 6 Apr 2017 08:29:23 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6B7BC20D43; Thu, 6 Apr 2017 11:29:22 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Thu, 06 Apr 2017 11:29:22 -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=EKZRJcIUh+hxl5nIC1 VEgD+9+CYP/AoZUjZy/zv47C0=; b=gsDeaYmBpqB7KtESfQEMlynvTs7ViOOeW8 PwXH4EsO2vhOI1mLCqp1lH008hBTtkJ7bpb5/cFeryBPJuVOOa39GsSSwRtVFd9K krXH59mynAoBD9K7DNgBtJCLsQCehs1+2Xtgne8Mk9hBMBAvLQxLQZBTlYsuFo1X LGdzjIhAvJir/1yzQ3It4QqHekeYREBBks0XCW7fodnjtzepL8JIna/k0xPR/nEZ 5DKWpkit07nTNKJ7GlrNiW1/runUFypWVlBtY3NdKitHaHuRu8gBBdoCDa+EUZrl ciIcgsjOFGPzncFluJ7jTimHPCpMagBUOIpnBDOBpnScxlQTrArw==
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=EKZRJcIUh+hxl5nIC1VEgD+9+CYP/AoZUjZy/zv47C0=; b=MoKRG0vR 1i+suoYitDizC9EuRYhF+fQA5V/Hea5Scyv2x0krwrsJy6VziXcHWegHypKfYUlh Mk6CoIBU5XY+Kxk/XByGScuGixjbbDcVyh4dAHVG616wTdPhDx6cppIBJ+aExaj1 Sf/f7zwyyz+6vIwjubMA4VTi+1VZCF7iLWoLsh/LlCRIIT+RdHpKmk2im24IoxCi l3pY5L3I2W92medhYeNuQJHUEYKsrxlRLT9U0CenlM4C+w0b3GU8AKeDFP9mTQWB ZUk+TNQGci+g9ihjJV2A7kS5+CgUmxsUHPJT5mr6aBsMtamijNJ/UPbqKE7kurOu W//vovLg6JHAUA==
X-ME-Sender: <xms:0l7mWCRnClBO3NDrV5vrqAOfJz0-9VlIHMcVKQKK3GtJI-tYD3KeNA>
X-Sasl-enc: eGYvYXopE6Zbv9b3Kyr4PUcLjaK02gRHsJpOfb3PX2+B 1491492562
Received: from [10.150.9.170] (unknown [173.38.117.67]) by mail.messagingengine.com (Postfix) with ESMTPA id F3F587E669; Thu, 6 Apr 2017 11:29:21 -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: <7c0589e7-e68e-481a-e625-aa744e5fbf64@cisco.com>
Date: Thu, 06 Apr 2017 11:29:23 -0400
Cc: Dave Crocker <dcrocker@bbiw.net>, Ted Hardie <ted.ietf@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <456B095C-17A0-4982-90FE-55283676B6D4@cooperw.in>
References: <37de22dc-04a4-f868-698e-cf03cd791957@cisco.com> <7add7c4a-032f-6b78-5b5f-861835a64f9a@dcrocker.net> <006325a5-83e7-9295-71a1-67c0125aa7cb@cisco.com> <c57adf52-3db7-5cfc-d301-3135010e17c6@cs.tcd.ie> <CA+9kkMA7iQrMg2y6g5=i96HL3-_8X04BsQjZEhzWe++uZzJvmQ@mail.gmail.com> <86de8a9c-3de3-dc35-b4e3-42553b91a53a@dcrocker.net> <7c0589e7-e68e-481a-e625-aa744e5fbf64@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/1et5q1lsJTWHQ6DI7NoVIkLc9GQ>
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: Thu, 06 Apr 2017 15:29:26 -0000

> On Apr 5, 2017, at 4:51 PM, Eliot Lear <lear@cisco.com> wrote:
> 
> Dave's right, and this is where Alissa chimed in during the meeting.  As
> a first priority she would like us to focus on before the contract is
> signed.

Correct. Out of a desire to see progress towards consensus, my suggestion is for folks to focus on the set of criteria needed to initially select a venue for an upcoming meeting which has no venue contracted already. If the WG can get consensus around those criteria and how to organize them, I think that it will have achieved a meaningful milestone.

At that point, the WG may want to consider how the set of criteria might apply at later stages in the process between the time of initial venue selection and the time of a meeting itself, or it may not want to consider this. That does not need to be decided now, so I think energy would be better channeled towards finding the consensus described above.

My motivation for suggesting this sequencing of the work is that decisions about breaking a contract and moving or canceling a meeting inherently have additional considerations associated with them that initial venue selections do not have — e.g., the specific circumstances leading to consideration of moving or canceling, cancellation costs, costs to our relationships with particular venues or venue chains, etc. So I think it will be easier to settle on criteria for initial venue selection before adding these additional factors into the discussion.

Thanks,
Alissa

> 
> 
> On 4/5/17 10:24 PM, Dave Crocker wrote:
>> On 4/5/2017 1:12 PM, Ted Hardie wrote:
>>> move or cancel the meeting.
>> 
>> 
>> BTW, folk seem to have mostly missed that the title of the draft
>> refers to 'selection', which is a particular step in the overall
>> process. And the wg charter concerns "specification of the venue
>> selection process."
>> 
>> All sorts of things happen after a venue is 'selected'.  These things
>> are quite distinct form 'selection'.
>> 
>> Contracting is one of those steps.  Another is monitoring and
>> re-evaluating if conditions change.  Those are, of course, essential.
>> 
>> They are also outside the formal scope of this effort, though everyone
>> seems to prefer to conflate them, which is having the predictable
>> effect of making discussion and wording considerably more complicated.
>> 
>> d/
>> 
> 
> 
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue