Re: [Mtgvenue] Priority order:

Dave Crocker <dhc@dcrocker.net> Mon, 30 January 2017 16:43 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 31E2712945C for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 08:43:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] 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 tdL8pVESMxa3 for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 08:43:37 -0800 (PST)
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 059EF129474 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 08:43:37 -0800 (PST)
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 v0UGj7pH031133 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 30 Jan 2017 08:45:07 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1485794708; bh=9v9/qZLQ9CeDiNGqdc2dWyGGnrSiRV0odpD8/nUQqF0=; h=Subject:To:References:Reply-To:From:Date:In-Reply-To:From; b=N3NQSuQGTAEknm2B8ZvRa6i3aeK3vyD6z+22oe3BuEGMsTurbuKdJsKUNEvFp8O15 yITYF2qZw2D7VSHTKRnAnaMWBNxYwv10c3PqINiwBPZPloJz5n2e9+sHINs/FNX5qA U0DbKi7YOP73j+Y9K+sm/nl7XhwSZbX8mc7fWii4=
To: Eliot Lear <lear@cisco.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, mtgvenue@ietf.org
References: <9139334c-9c5e-814d-4299-c6f5950039b8@cs.tcd.ie> <2dcdf5d1-4e93-7476-79ba-0369e41af1c0@cisco.com> <8cfa8a35-b805-a9f3-6570-a8c71a44c5d3@dcrocker.net> <cc1f5181-5106-c866-61e4-8c455dc54cf2@cisco.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <76ed751f-ced1-f420-d270-d125c409e343@dcrocker.net>
Date: Mon, 30 Jan 2017 08:43:20 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <cc1f5181-5106-c866-61e4-8c455dc54cf2@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/jgEEQC-vspkffSdeC9QFnFw_kVI>
Subject: Re: [Mtgvenue] Priority order:
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Mon, 30 Jan 2017 16:43:38 -0000

On 1/30/2017 8:16 AM, Eliot Lear wrote:
> It makes clear what's most important at a gross level.  I was actually
> surprised this wasn't the case and had initially presumed this was due
> to going back and forth on some of the criteria.


Eliot,

The requirements labels already make that clear.  And in the tabular 
form in the recent versions, it's quite easy to see those labels.

Having a claim that thinks are rank-ordered by priority carries the 
message that decision processes will treat entries differently, based on 
the ordering.  But that won't happen.

Again, this is the sort of thing that is entirely naturally to want to 
do, but in fact is either useless or misleading.  As such, it will 
mostly serve to confuse things, either within the decision process or 
when interacting with the community.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net