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

Fred Baker <fredbaker.ietf@gmail.com> Sun, 22 April 2018 21:21 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36CEA1200F1; Sun, 22 Apr 2018 14:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001, 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 0HVxYw7fTGUl; Sun, 22 Apr 2018 14:21:10 -0700 (PDT)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (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 9BC16124B18; Sun, 22 Apr 2018 14:21:10 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id p5-v6so8111031wre.12; Sun, 22 Apr 2018 14:21:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=4xwfMX/2PMGjDlFrQUFtl0CI8xpvDOBTu5JtOYU6lVA=; b=B2t5Poc5wKjMWA0DJfCAwaw76IibKR6ZjSq2eoBBoqeVcCru7LCnUOyvLLelURKD7V fVoFPfBK2s3QcD9gMzlU7BpB/4mlQ5Ctm8B56AHDBXq47Hq/CR5gfkdII81Qm7QoIiD1 ib9kiGWdr7V1FetiQa3KSUrhdfKmZisFgEkcDH0RgSmFGlaacFYl0Timr4l1Hg/ukBhx sjoQEN7TDRZVspFUKBep+r7a2A9wHZue+vgBGjd0XrD5wEpkE3mPqPjKSyvHEOqoYe1d 7+pWE+I05FaCL21zhsXPLpX5HcfeQCApqYlX+0Jb9Q8pNfrZ8uPKuIOTH4dZfsMOPohw Sbfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=4xwfMX/2PMGjDlFrQUFtl0CI8xpvDOBTu5JtOYU6lVA=; b=C2Ywf1VdjkdRfXxxI2ssqyMG+lGSmtFRd9M1K6xzQ2gLmboJ8K53M1lO+0VUmoLD3F 1EVAYH+0qiTt/tedIoSS1UXzr7nmS+pRnrd2kO3XK+fAZwik95qsJe9F+8wavQv+rl6F UTzOYNwNVG1lkkOdehjCdYzZGimydfQqsRQBKjdAWxBp8zPAri6d9mc6p2FEFtdv+Y1d VPqJoS9KaUiI999KE2jlN1mu2sY3NVsQvFasCXGPowYVTPkTRIq4AKIXnpKNY9ssAITz gl5Kf5grJbQQ4evWf9dzrceJ0OPup3/DOYQInn7QkvDQ0h3b7ZdjlJZCjwWFEJQEeyLC TTqQ==
X-Gm-Message-State: ALQs6tDZ9hwugZv17oyLfAjdAoIN8Quo6nIJMbhjPVyyLpjtnPA3VwoN 19/Xlbk6yydpBVbTGPawVXM=
X-Google-Smtp-Source: AIpwx4+xsHt5SHpuU6N6K+u7NrNpRV69Fpl69f21ShSL9JN/K90V9miCkCGGGVw9QP0DK07/9DtOIQ==
X-Received: by 10.80.142.9 with SMTP id 9mr25046191edw.101.1524432069081; Sun, 22 Apr 2018 14:21:09 -0700 (PDT)
Received: from ?IPv6:2601:646:c005:a10:69ae:d698:6a06:b973? ([2601:646:c005:a10:69ae:d698:6a06:b973]) by smtp.gmail.com with ESMTPSA id b36sm7250499edd.81.2018.04.22.14.21.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 22 Apr 2018 14:21:08 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <9768922C-6FE9-48BF-8E98-623B3B4960CF@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_81735F8A-E4DB-4A2C-BE94-F22FA0529E18"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
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
Date: Sun, 22 Apr 2018 14:21:09 -0700
In-Reply-To: <115F383E-49E6-4237-849D-E36B26DA977B@cisco.com>
Cc: Adam Roach <adam@nostrum.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>, IETF Crazy <ietf@ietf.org>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <152295916074.25912.932711807710247299.idtracker@ietfa.amsl.com> <20180419013457.fq4ruqj7p4lfwxb4@mx4.yitter.info> <CABcZeBPXUqe6ixF+Yx7P6E3Jt3fGjAMUrP368DTedGq-O-T61Q@mail.gmail.com> <ED191002-261F-4E3C-A359-CBFEF1812AF8@iii.ca> <531F8285-71D0-4EFD-AC2D-C96DD98E4F44@fugue.com> <23d1e398-887d-4c7c-2c9d-da9fad200415@cs.tcd.ie> <b4a8b4a7-7919-df3f-f301-1cd634f4900c@nostrum.com> <115F383E-49E6-4237-849D-E36B26DA977B@cisco.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/b5LoOJaRjXBy-uqeQJvLc6iPO80>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Apr 2018 21:21:13 -0000


On Apr 22, 2018, at 2:22 AM, Charles Eckel (eckelcu) <eckelcu@cisco.com> wrote:
>    Agreed, and I think the crux of the conversation underway is whether
>    these guidelines are aspirational or mandatory.

I (the guy who originally came up with a plan like this, back when the IETF demographics were about 1/6 European and 5/6 North American, with a few "others", and described a policy of 5-1 which I promptly added Adelaide to) have always understood them to be aspirational. Harald decided to try 1-1-1, as I recall, because he thought that if he did the demographics might change accordingly.

Speaking strictly for myself, I would be OK with a policy of 2-1-1-* given a supporting consensus. We have difficulty putting together asian locations, for reasons best described in terms of business-cultural norms in Asia. On at least one occasion, asians have told us that Honolulu and Vancouver were easy enough for asians to get to that they would consider them "honorary asian locations" when one in that pert of the world was being hard to arrange. I note that we seem to wind up in Vancouver more frequently than one might statistically expect - Vancouver is often a good location for a number of reasons. Maybe that's the right trade-off?

That said, I'm with Melinda on holding these drafts hostage to that discussion.