IETF Logo Mail Archive

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

Dave Crocker <dhc@dcrocker.net> Wed, 05 April 2017 20:25 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 39DAD1293F2 for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 13:25:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level:
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 wajNJi2aqWVC for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 13:25:01 -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 1317A127A90 for <mtgvenue@ietf.org>; Wed, 5 Apr 2017 13:25:01 -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 v35KR3bR019352 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 5 Apr 2017 13:27:04 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1491424024; bh=RNgCQkj8IjSKBJbVZE58bqwGqXhcn4l5LWWHViXEyuk=; h=Subject:To:Cc:References:Reply-To:From:Date:In-Reply-To:From; b=W+MgBcpf4ovI7YcsBlYOS1H6K+GAR6fdknw4KI4qQlCdsNwVr1GTvjfMVA/G6miId riwrkz48VAkckmqeOjmiddBIksA/ex9WlbPO8UOukgmD7DlCHfymi+95fTY6i1/jiD LCkPulWJZ6qs8p5AZqf0J/q1xrK1Pxni/3MMvrWg=
To: Ted Hardie <ted.ietf@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: "mtgvenue@ietf.org" <mtgvenue@ietf.org>, Eliot Lear <lear@cisco.com>
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>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <86de8a9c-3de3-dc35-b4e3-42553b91a53a@dcrocker.net>
Date: Wed, 05 Apr 2017 13:24:46 -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: <CA+9kkMA7iQrMg2y6g5=i96HL3-_8X04BsQjZEhzWe++uZzJvmQ@mail.gmail.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/sXaGTTVV3bmo-sX3eTdPaLk-V9Q>
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 20:25:02 -0000

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/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email