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

Dave Crocker <dhc@dcrocker.net> Wed, 05 April 2017 23:12 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 80C241293F9 for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 16:12:32 -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 yZWgnqxP5AEw for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 16:12:31 -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 56DF51293F5 for <mtgvenue@ietf.org>; Wed, 5 Apr 2017 16:12:31 -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 v35NEd48027246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 5 Apr 2017 16:14:40 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1491434080; bh=xX5mGvsOT217QrmSIvLc/GwST55zJrF1zW03TodzNo8=; h=Subject:To:Cc:References:From:Reply-To:Date:In-Reply-To:From; b=rEUGTqVB14sqXOgHQLd9BK6mlNzhrkVCverjIBOdnAMNNX/0hHETbUghuZZB5NVVS /ZSW4wgzV2ah9bpnBgH9EsvAmOc4Hmm6oOwogaLI5z2mGcMwDeJg2vRAvfs7Lgv6ra vTIsPQ+9gnT+ss0sFnAG2xe/0NCKXUwzaSx6ZE/k=
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> <4f7214d4-6dbb-861c-ea17-072af055c379@dcrocker.net> <3186844C-A706-4ECB-90EA-47B585DE7B61@qti.qualcomm.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
Message-ID: <97b5899a-375f-f7ed-6e68-6d05860d7c69@dcrocker.net>
Date: Wed, 05 Apr 2017 16:12:22 -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: <3186844C-A706-4ECB-90EA-47B585DE7B61@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/vjY8zk16bKkzChsEwrnortEn5nQ>
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 23:12:32 -0000

On 4/5/2017 4:02 PM, Pete Resnick wrote:
> The above text says that the WG is to discuss and agree on what goes 
> into three things: policies, selection process, and detailed criteria 
> going forward. I read those as three separate items and not solely about 
> the selection process.


So, there's no constraint on the first clause or the last one?

Since they aren't constrained to the selection process, what else bounds 
their scope?

The charter has no explicit reference except to meeting venue selection 
process -- and there are quite a few such references to exactly and only 
that, and FWIW as I recall, that was intentional -- so I must be missing 
the text that enables considering a wider range of issues.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net