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

"John Levine" <johnl@taugh.com> Sun, 22 April 2018 21:16 UTC

Return-Path: <johnl@iecc.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 2EF6E126B72 for <ietf@ietfa.amsl.com>; Sun, 22 Apr 2018 14:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=lQLRiAUz; dkim=pass (1536-bit key) header.d=taugh.com header.b=O8/MiNbg
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 TveoGYbojwr3 for <ietf@ietfa.amsl.com>; Sun, 22 Apr 2018 14:16:15 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39ABB124B18 for <ietf@ietf.org>; Sun, 22 Apr 2018 14:16:15 -0700 (PDT)
Received: (qmail 16542 invoked from network); 22 Apr 2018 21:16:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=409c.5adcfb9d.k1804; bh=UMQb/xBvbk4+60ucTEsKm2Xgbf7LqJtp5y0vmWbi00k=; b=lQLRiAUzxmHxAP447H0f1NjOYv/BOX9RaWOOOgNOirsot0fX7NEIr4DTl3gn89SRLQoIPUMUFHQv0wQpFfUlTsZojKlpFvd1kutCZda/zADqvi22KXzcYJocy2IRZDVDJ+1BaATbtj/i+Oj0IPocsmbDTJE0pMfNhfTkqCwM57tICRdFXf/HqE5VToe3vHVng/aLAZ6ui0guLB0JUnu7xfQyjQJyAFfqsGf65BlBhNf/00mul443BS8Wk37SNHZF
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=409c.5adcfb9d.k1804; bh=UMQb/xBvbk4+60ucTEsKm2Xgbf7LqJtp5y0vmWbi00k=; b=O8/MiNbgTRTHUO5Bmq2+u0gLaAH8Lf7eexXbsm98Q0i0yOtoYDcTPqdrHP9xkXP5/07Qgp/fXywWOWaQYliQtjPQmBG2tjXWTjBKA1R3AJLh+rIXDGpwO6tAM7LGrN3Mf+KsjFjvh+Zd0wd8iRtckq5mf+2SJBxHCMsqICExUcx8lgngsVt8Iswt2kkTaLiji+SjUcMMQsjY7OKr8WICCx5ioa8hURZh9e7OZT0ygblw/sL3Tqy6fwLasBcYbmni
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 22 Apr 2018 21:16:13 -0000
Received: by ary.qy (Postfix, from userid 501) id 66FC0255FD7A; Sun, 22 Apr 2018 17:16:12 -0400 (EDT)
Date: Sun, 22 Apr 2018 17:16:12 -0400
Message-Id: <20180422211613.66FC0255FD7A@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
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
In-Reply-To: <23d1e398-887d-4c7c-2c9d-da9fad200415@cs.tcd.ie>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OmoY5LaT7BLvOw1bsGmzJMRzFjc>
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:16:17 -0000

In article <23d1e398-887d-4c7c-2c9d-da9fad200415@cs.tcd.ie> you write:
>I don't see evidence sufficient to warrant a change to
>something else right now. In saying that I regard the
>1-1-1 scheme as being somewhat aspirational in practice,
>and that's ok.

At this point, we need to think about how to figure out what the
rotation should be, maybe 1-1-1, maybe something else.  That will
require a combination of data we have and a lot of data we haven't.

It would be really nice if there were some way to find people who
didn't come to a meeting but would have if it were somewhere else, but
I don't know how to do it.  Perhaps some sort of polling of past
meeting attendee lists might provide useful data.

There's the related issue that meetings in some places are a lot more
expensive than in others.  For example, there are places that look
like they'd be great except that the circuits we need for the
conference network we want would cost vastly more than they do
elsewhere.

R's,
John