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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 05 April 2017 19:40 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 3B78A129477 for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 12:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-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=cs.tcd.ie
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 afqjyjTV8Od6 for <mtgvenue@ietfa.amsl.com>; Wed, 5 Apr 2017 12:40:49 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C74A912941D for <mtgvenue@ietf.org>; Wed, 5 Apr 2017 12:40:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 52EA8BE74; Wed, 5 Apr 2017 20:40:47 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Taa7AQc1FKyW; Wed, 5 Apr 2017 20:40:46 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id BFC1DBE2C; Wed, 5 Apr 2017 20:40:45 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1491421246; bh=EZMlMPsQraIGfIx+E6A/vx5iTq1KCTaLzG26l66VUSM=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=fUY3D5vW4kfbXolTNh62WznOiiCZDUMOQbyrQ0tTPWdZbkOmKQRXaMGISksfzwVWt SJqXVyFJdkqx3abFyrodlO0h/w0MR5Kggtc6sNx6EZASOZVcMbUViLvDFF4l6+Mk9G PNIinIB5tW+RY45R6GRvS4gh9jzRYEMmd7big/uQ=
To: dcrocker@bbiw.net
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> <cf365ee7-f7c2-1bb7-3db8-f241dda9c64b@dcrocker.net>
Cc: "mtgvenue@ietf.org" <mtgvenue@ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <e545c0b9-57e4-353b-587e-e2e6227d78a0@cs.tcd.ie>
Date: Wed, 05 Apr 2017 20:40:45 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <cf365ee7-f7c2-1bb7-3db8-f241dda9c64b@dcrocker.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="vtrLp79PJ9F09tObJbTQ9TLmQXuhup86m"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/Ug05vfbtIoXahiTVZhO3zZ30GXc>
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:40:52 -0000


On 05/04/17 20:28, Dave Crocker wrote:
> 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.

Nah, the difference between A and B is neither a mathematical
nicety nor a subtle human frailty - they're just different concepts
that ought be labelled differently. I reckon that A is not very
useful here but that B could well be quite a useful distinction
for this document. I'd encourage the editor to ponder whether
re-casting the requirements in terms of (some label for) B might
make the whole thing more clear. (And even maybe avoid a future
kerfuffle or two:-)

Cheers,
S.



> 
> 
> d/
>