Re: [Mtgvenue] Comments on -04

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 31 January 2017 04:33 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 3E884129D9B for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 20:33:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 1q11LhO3UuqE for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 20:33:51 -0800 (PST)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEE51129D8F for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 20:33:50 -0800 (PST)
Received: by mail-pf0-x229.google.com with SMTP id 189so98943083pfu.3 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 20:33:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=O/f6IMc6uFjcLLnlMzWoSyDCpLcpWNZe13trg/6USrQ=; b=cvMnamTIE59Q8RtMDqbV+4PFkGWsfUmTo15Qh/mseIKb8qSo7b2B95yVXipp+/+6XX UGBZRAOXo4DF78CCTIVux27QRbkfyzTacYKA08g7tqhjQqqaXdLhbpncDZ09Woyl3LZE 9oOWStllF7LffUP35v0a576k4RyQLdlsqTSAfM8w4EO6CbD03dV9iVxS80ybSoV8jZcw d+kqzGYm1AcWgJ4NLSqQKD1bTfh8FSZYnAE5nkGRgtnHQtMv8Lw9YIbAzFJmRYfA0nsN LhMiMbO6/vf1IijldQr8iqAHXmeYTrydNNrIlDQpYQNRU0KyFoHzj+5AI5VBceeOZEYs eBdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=O/f6IMc6uFjcLLnlMzWoSyDCpLcpWNZe13trg/6USrQ=; b=gllfKIeyjtf6RElqw6/YxTqekTQjmppZ3mY+iF+BwDTyjFkoTVlqWBTq/gnjryo7iB SS9tGKeLCEXTqNHimmb6tKCKH8LoosAHirQX6vWdvUbsk3+4RCTT5/8Ze3F5SlcYnkin OYCWiSLqerMHRVVGexs5NKRmc+bElv8BrOzpR5A1cvQrGhyKU0pmOIKBIxkgXs987Ez2 Rs6VKk0c/4UUVSmM+//Uo4znsKRYgh81GgV4Zq8cbb5xrUf6kdXqZSHw9TNYreiG2ku2 /RLOUqHa7F1sNcZlt93Mql3cG9qyQMOrjVuS6cgrRs1/O1pPLjrKWPG1nYqaefvq6yG0 71kw==
X-Gm-Message-State: AIkVDXLDKKex+ZssdLQDwurQ9EEcXcvGw8mhaDYn/XLLebvgUPmxaBDqYLybCZSE41Sslg==
X-Received: by 10.84.174.197 with SMTP id r63mr37180443plb.14.1485837230406; Mon, 30 Jan 2017 20:33:50 -0800 (PST)
Received: from ?IPv6:2406:e007:7505:1:28cc:dc4c:9703:6781? ([2406:e007:7505:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 75sm36213772pfp.80.2017.01.30.20.33.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jan 2017 20:33:49 -0800 (PST)
To: Andrew Sullivan <ajs@anvilwalrusden.com>, mtgvenue@ietf.org
References: <20170131010548.GL47762@mx2.yitter.info> <de401360-8827-c427-19fe-ace8d2987f40@gmail.com> <20170131040757.GM47762@mx2.yitter.info>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <06168ed5-c84c-a262-039a-b366d997a888@gmail.com>
Date: Tue, 31 Jan 2017 17:33:48 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <20170131040757.GM47762@mx2.yitter.info>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/WQo6FL4xTrxRFBqda2q_ez1lA8s>
Subject: Re: [Mtgvenue] Comments on -04
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 31 Jan 2017 04:33:52 -0000

On 31/01/2017 17:07, Andrew Sullivan wrote:
> On Tue, Jan 31, 2017 at 02:31:13PM +1300, Brian E Carpenter wrote:
>>
>> Really? That's only an issue of document organisation.
>> Personally I think it's more readable arranged the way it is,
>> by topic. YMMV.
> 
> I don't actually care about readability.  I care about utility in
> decision-making (as I noted in the preamble to my note), and this
> organization is impenetrable for that
> 
>> But that is the whole point. Most of the 'mandatory' items are
>> in fact judgment calls. So it's mandatory to make the call, but
>> it's made by the IAOC (on the recommendation of the meetings
>> committee, presumably). And yes, most of the criteria we've
>> identified are in that category. That's a good sign, IMHO,
>> because it means that we aren't wasting time on minor issues.
> 
> This is a completely absurd meaning of "mandatory" (and not the one in
> the document).  It's not that it's mandatory to make the call, but
> rather that if the criterion cannot be satisfied then the meeting is
> not to be held there.  It's perfectly clear in the text:
> 
>    Mandatory:
>       If this requirement cannot be met, a location under consideration
>       is unacceptable.  We walk away.

Yes, but since they are all judgment calls this is actually meaningless.
If the IAOC has to consider both Timbuktu and Ulaanbaatar, they can
decide that the visa rules for Timbuktu are acceptable, and those for
Ulaanbaatar are unacceptable. Or the opposite. In effect, what I said
is the case: it's making the judgment call that's the MUST. After that,
the decisions follow automatically.

   Brian

>>>    By the same token, Venue decisions
>>>    are not themselves subject to IETF consensus, and are instead
>>>    decisions taken by the IAOC.
>>
>> To me that is implicit, but it's a fine addition to avoid doubt.
> 
> Well, if that's what we mean by this, then I think the entire point of
> the associated text is lost and it should all be removed.
> 
> Best regards,
> 
> A
>