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

Dave Crocker <dhc@dcrocker.net> Wed, 05 April 2017 19:28 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 DBA48129493 for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 12:28:34 -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 OpuXgt5MJYxx for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 12:28:32 -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 B94AC129490 for <mtgvenue@ietf.org>; Wed, 5 Apr 2017 12:28: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 v35JUX0J016666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 5 Apr 2017 12:30:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1491420634; bh=eZBkBPUo9Bp9KTPIEO1SeolnhTsF2N8WYBQ2kzaTta8=; h=Subject:To:References:From:Cc:Reply-To:Date:In-Reply-To:From; b=YP4n7DnURJcJMEIYJ0l4k7IctQSZgjnxFMoAA8dhDPGnplYvuFvZT3PJwwWn0+Nz/ OtNWZ3Lgw1bdgcKXHGPrO9EhxYe+NhxEqZYJLMhwJmH/CTEINYqe7nLYkFJKjfB8OH l1rdJw+uU6lqfw2zQVHTHFdtJZ+JxfHnz9YzrptA=
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
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>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Cc: "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Reply-To: dcrocker@bbiw.net
Message-ID: <cf365ee7-f7c2-1bb7-3db8-f241dda9c64b@dcrocker.net>
Date: Wed, 05 Apr 2017 12:28:16 -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: <c57adf52-3db7-5cfc-d301-3135010e17c6@cs.tcd.ie>
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/eo91QgocTB6cX3QV-KwmpLjlkpc>
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 19:28:35 -0000

On 4/5/2017 12:18 PM, Stephen Farrell wrote:
> 
> Dave, Eliot,
> 
> Seems to me like you're using different semantics for the same
> label.
> 
> A: Eliot: ""mandatory" means "it's impossible to have a successful;
> meeting unless the criterion is met."
> 
> B: Dave: "What dropping this item does is to move it from being an
> exception requiring community review to something the IAOC can decide
> without community review. " which I think is equivalent to saying
> that "mandatory" means "MUST unless community informed and ok with
> not meeting the criterion."

Here's what Important authorizes:

       It can be traded against other Important items

My text that you quote derives from this authorizing statement.  The 
IAOC is authorized to do tradeoffs, which means it is authorized to 
choose not to satisfy one or another of these requirements.  Hence the 
very specific questions I've annotated, for each of the items proposed 
for a change in status.

As for seeking exceptions, I merely noted a reality that has been used 
more than once:  When there is a desire to hold a meeting that does not 
conform to the considerable list of community expectations -- demands, 
actually -- the community has been asked to provide comment and the IAOC 
has decided whether to make an exception.

The problem with taking 'mandatory' to be a requirement for mathematical 
perfection that does not permit exception is that, unfortunately, humans 
can sometimes tolerate exceptions where mathematical formula don't.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net