Re: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 19 April 2018 01:35 UTC

Return-Path: <ajs@anvilwalrusden.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 60BEA126C89; Wed, 18 Apr 2018 18:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=nvYmJPCk; dkim=pass (1024-bit key) header.d=yitter.info header.b=FbokB3Pp
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 KVNCNVYPAFWH; Wed, 18 Apr 2018 18:35:35 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D277127286; Wed, 18 Apr 2018 18:35:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 3E375BECAC; Thu, 19 Apr 2018 01:35:04 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524101704; bh=tiLjFayiwcj9GNLbkjlTRJoehrT5frtf5eiziBFgsjw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=nvYmJPCkoWonipGMLd7gVMLEgwRH9NQmgfDGMHP4M+OJ2KwSxQXeEWLVmC9G+i9Yy Yml+ZOWcQA13y45hi0qh4ZuPMWUCzC9g8DC1+xrNH/FoMeSF9Klb/uUtA1sghT7BfL GFqeRhq6V4DGA1dVRiakHFEKFikOQQm69BZgsdko=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hr5CnasRYrpz; Thu, 19 Apr 2018 01:35:02 +0000 (UTC)
Date: Wed, 18 Apr 2018 21:34:57 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524101702; bh=tiLjFayiwcj9GNLbkjlTRJoehrT5frtf5eiziBFgsjw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=FbokB3PpsukS4toTb4vGvZQSyBpo994CpBVL53P1HRSrQ/+mNrsmxen1tOtPXL3JO 31yCklrA32NVkHnCEImjLzTDJcNV6BGBCkodq+Li1lsO1QQIwpqGHqd0h+WgnUNtSp Yos5SWaQXf/zyii34KhKmL2oS9Uegr/dofNM71OQ=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Cc: mtgvenue@ietf.org
Message-ID: <20180419013457.fq4ruqj7p4lfwxb4@mx4.yitter.info>
References: <152295916074.25912.932711807710247299.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <152295916074.25912.932711807710247299.idtracker@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/icHqtdU3HP96LZj9I3-62SHvnFI>
Subject: Re: [Mtgvenue] Last Call: <draft-ietf-mtgvenue-meeting-policy-04.txt> (High level guidance for the meeting policy of the IETF) to Best Current Practice
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: Thu, 19 Apr 2018 01:35:37 -0000

Dear IESG,

On Thu, Apr 05, 2018 at 01:12:40PM -0700, The IESG wrote:
> 
> The IESG has received a request from the Meeting Venue WG (mtgvenue) to
> consider the following document: - 'High level guidance for the meeting
> policy of the IETF'
>   <draft-ietf-mtgvenue-meeting-policy-04.txt> as Best Current Practice

In a recent discussion, the IAOC came to realise that the documents
draft-ietf-mtgvenue-iaoc-venue-selection-process and
draft-ietf-mtgvenue-meeting-policy may be in some tension.  One of
them requires the IASA to balance meeting venues over time, and the
other has requirements that a meeting must meet.

One possible difficulty that arises from the combination is if one
region turns out to be vastly more expensive than others.  In that
case, some criteria for each venue may not be met in one region.  The
result might also be financially ruinous for the IETF in general.

The current IAOC interprets the drafts such that any of the criteria
except those in section 3.1 of
draft-ietf-mtgvenue-iaoc-venue-selection-process may be traded against
any other, over several years if need be, in order to meet the
geographic distribution policy described in
draft-ietf-mtgvenue-meeting-policy.  Assuming the documents are
published as they are currently written, we will use that
interpretation as governing IASA implementation decisions.  It is
worth noting that, among the criteria that could be traded are those
of affordability.  If that is not the interpretation of the IETF
community, then some clarification is needed to the text.

Best regards,

Andrew Sullivan
for the IAOC

-- 
Andrew Sullivan
ajs@anvilwalrusden.com