Re: [Mtgvenue] Comments on -04

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 31 January 2017 19:48 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 070AB1293F9 for <mtgvenue@ietfa.amsl.com>; Tue, 31 Jan 2017 11:48:25 -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 CePkwdfARtnm for <mtgvenue@ietfa.amsl.com>; Tue, 31 Jan 2017 11:48:22 -0800 (PST)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 E1079129581 for <mtgvenue@ietf.org>; Tue, 31 Jan 2017 11:48:19 -0800 (PST)
Received: by mail-pf0-x236.google.com with SMTP id f144so110453449pfa.2 for <mtgvenue@ietf.org>; Tue, 31 Jan 2017 11:48:19 -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=M+JFJOr/NL+aI2wCe1RmRP0Y4y/fSS15+RR124dfGUY=; b=obZdiQFOnMUpBjIB6+plFfUvzECI4/07l0wu0fWGL+7xL2S68UAq9d2VQlZicmJRYB 85eOOfi8ijTUfycl+69fITmaUcCjH5PgOqymtKIzMtwU0zi+x+oEodjqpDBrRHIEkrrV DjmIolQcUrW/YMq+gwodDJccxwOq5yDylBwt7iJelRw7rBiliciGo71P8Yox5yunyLVf JleRYgxQkoReeuVIHt7iG3h3nXqPbhZc0QdYG+bt0ZkqowuqlnGOWRrzY5nJMgVW8iou 571O5TLihVQRTGsFhJGC2JbGazAuHLnRQSgRxswCnxXRMfR4Hulc8/1h91VHdNZkq1BB np2w==
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=M+JFJOr/NL+aI2wCe1RmRP0Y4y/fSS15+RR124dfGUY=; b=Rer3ilrpK33n5mBaiiwaShz2XU664M6uR08UeO6zLZ0zNUIswPPNf2WfCh0AeaVytS 5SfaiMtbuHRaMsuBx+JkaoW2T9CJN6U/+CHUCSqsqmUng/U4TnqQqLuy95uC1VVAYOpb xW7b7eFpMLtrnWQAO0514+ZGXBSxJHyJsQBcLMxazGZB+HV3OaCRijH8Yn/MPZgLSl2h x4MXp3Wn/3/jC9mfS/iXYGD+FVSw68VQ6y/SvjgKtg9oSQvkFWKYQw1dlYh7zKY7Xu7t oCfOh01fKMF4XqZqugUVr9HTHT/9cyysQJ/itbvnjrN/MwlLqNe6ugqRtZSTQgyr6gU1 gcUw==
X-Gm-Message-State: AIkVDXIJq3jJ3D4h0tlDOL4F0l+lHUCJZl3sRwukrCql0DMe8tH2H17JaRhMK9KjZwR3Bg==
X-Received: by 10.84.195.1 with SMTP id i1mr41505529pld.77.1485892099508; Tue, 31 Jan 2017 11:48:19 -0800 (PST)
Received: from [192.168.178.21] (179.218.69.111.dynamic.snap.net.nz. [111.69.218.179]) by smtp.gmail.com with ESMTPSA id c204sm43161707pfb.51.2017.01.31.11.48.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jan 2017 11:48:18 -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> <2c957e0e-999f-f8a2-3a61-3aff3606b087@dcrocker.net> <20170131152139.GC53056@mx2.yitter.info>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6841c575-faff-78cf-370c-ab4dbccd35b0@gmail.com>
Date: Wed, 01 Feb 2017 08:48:18 +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: <20170131152139.GC53056@mx2.yitter.info>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/aEmKX0vqoeJXmzJ_GgnLdi0qiA0>
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 19:48:25 -0000

On 01/02/2017 04:21, Andrew Sullivan wrote:
...
> If I understood Brian, he thinks that it'd be ok for the IAOC under
> those circumstances to say, "Well, yeah, the cost is outside the norms
> we have, but we thought about it so the criterion is satisfied."  I
> don't see how that comports with "requirement can[not] be met", but
> perhaps Brian can say more.

That's exactly the problem. The criterion itself is worded so that the
the IAOC has to make a judgment (in the case you cited, "is $X a night
affordable?"). So they think about it and decide that $500 is affordable,
because if they decided it was too much, the venue would be excluded.

Then the IETF's only recourse is the NomCom.

> In my reading, the requirement is a hard one and the IAOC must be able
> to say, "Yes, we have positive information that the conditions match
> this requirement at the time we selected the Venue."  If IAOC members
> cannot satisfy themselves of that, then "we walk away."  This is part
> of why I am very far from convinced that all of the Mandatory list
> items ought to be on that list.

Now there, I think, we agree. It isn't the criterion that's wrong. It's
that by giving it the label "mandatory" we distort the decision process,
perversely giving the IAOC an incentive to decide that $500 is affordable,
or we can't go to Timbuktu.

Obviously I chose an absurd price level to illustrate the point, but the
combination of "mandatory" and a judgment call will be tricky in any case.
We probably can't duck it in every case, but mandatory requirements that
depend on judgment calls need to be kept to a strict minimum.

    Brian