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

Dave Crocker <dhc@dcrocker.net> Wed, 05 April 2017 22: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 AF728126DFB for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 15:25:15 -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 O-RIyLRd3szM for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 15:25:14 -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 1B748124C27 for <mtgvenue@ietf.org>; Wed, 5 Apr 2017 15:25:14 -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 v35MRMCw024879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 5 Apr 2017 15:27:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1491431242; bh=Je4AVY+eDVmN/iu1hLKvOwPboUnWnHygCQ4zYqHWHhE=; h=Subject:To:Cc:References:From:Reply-To:Date:In-Reply-To:From; b=WgPNnpLyCaIabbcibmsemvMJSWWPwg/YKz551myOcf1EUwylJ1VeM8lhkJS6u8J5w k1xa/fvKRJXMRP2fVBbC4eOiAGC8Dya8y9fed0QEv5LoF5Y4akCP2EjvakWoC3kizX YgYE0DT6k4BuwFEOsMDXnLYwzgMeD1MTq01OSQJo=
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: "mtgvenue@ietf.org" <mtgvenue@ietf.org>
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> <CA+9kkMDgwgHd0-THd_eENrCf0GfLjQaMSivx3phX5Bkgyb=fiA@mail.gmail.com> <b706e895-0e7c-8883-7188-9e1c6891780e@dcrocker.net> <19C30E48-363A-4BF4-B21E-FB72C5182949@qti.qualcomm.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
Message-ID: <4f7214d4-6dbb-861c-ea17-072af055c379@dcrocker.net>
Date: Wed, 05 Apr 2017 15:25:05 -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: <19C30E48-363A-4BF4-B21E-FB72C5182949@qti.qualcomm.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/-_8n3npUyaMxiWz_Wx8P-QJQhYc>
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 22:25:16 -0000

On 4/5/2017 3:02 PM, Pete Resnick wrote:
> On 5 Apr 2017, at 16:02, Dave Crocker wrote:
> 
>> "move or cancel" is language that only has meaning /after/ selection. 
>> It is therefore formally out of scope.
> 
> Whoa there! Dave, it is not your call that this (or anything) is 
> formally out of scope.

That's a style of objection that we do frequently in the IETF and misses 
the distinction between authority and ability.  Any of us can raise the 
question.  I'm raising it.


> As I said at the f2f meeting, the charter is not crystal clear on this 
> point:
> 
>> The MTGVENUE working group is the forum where the IETF community can
>> discuss and agree on what should go into the policies, the selection
>> process, and the detailed criteria going forward. All criteria and all
>> other aspects of the process are open for discussion.

Again, all of the language is about the selection process.  It says 
nothing about contracting or canceling or any other part of the venue 
process as being within scope.

> 
> As Alissa said at the meeting, the charter is flexible enough to allow 
> the WG to write a document that can be applied only at the beginning of 
> the process, or might be applied at multiple points. 

Where is this sort of flexibility justified in the charter?

d/

ps. Again, the ultimate issue is that going beyond the specifics of 
/selection/ conflates things in a way that is already adding significant 
complexity to the discussion.

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net