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

Cullen Jennings <fluffy@iii.ca> Sat, 21 April 2018 15:57 UTC

Return-Path: <fluffy@iii.ca>
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 3F70912D7F9 for <ietf@ietfa.amsl.com>; Sat, 21 Apr 2018 08:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 WA9bBiivB9SF for <ietf@ietfa.amsl.com>; Sat, 21 Apr 2018 08:57:08 -0700 (PDT)
Received: from smtp86.ord1c.emailsrvr.com (smtp86.ord1c.emailsrvr.com [108.166.43.86]) (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 3CDFA1277BB for <ietf@ietf.org>; Sat, 21 Apr 2018 08:57:08 -0700 (PDT)
Received: from smtp27.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp27.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id A72894024C; Sat, 21 Apr 2018 11:56:57 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp27.relay.ord1c.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 0C7A74024B; Sat, 21 Apr 2018 11:56:56 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.24.57.70] ([UNAVAILABLE]. [128.107.241.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.12); Sat, 21 Apr 2018 11:56:57 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_44EAD4FB-7418-4610-AF68-72CF40540804"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
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
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CABcZeBPXUqe6ixF+Yx7P6E3Jt3fGjAMUrP368DTedGq-O-T61Q@mail.gmail.com>
Date: Sat, 21 Apr 2018 08:56:55 -0700
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, mtgvenue@ietf.org, IETF Crazy <ietf@ietf.org>
Message-Id: <ED191002-261F-4E3C-A359-CBFEF1812AF8@iii.ca>
References: <152295916074.25912.932711807710247299.idtracker@ietfa.amsl.com> <20180419013457.fq4ruqj7p4lfwxb4@mx4.yitter.info> <CABcZeBPXUqe6ixF+Yx7P6E3Jt3fGjAMUrP368DTedGq-O-T61Q@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1Oaf_Pez2sOqnqzo_J2k7kG0qJ4>
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: Sat, 21 Apr 2018 15:57:11 -0000

When we went to a 1-1-1 policy, we agreed the locations should roughly match participants location to be fair. The argument was made that if we had more meetings outside north america, the participation would come to match approximately 1/3 , 1/3 , 1/3. That has clearly not happened so I think we need set the rotation of where we do meeting to something we agree is fair to our participants. 

I do not support the 1-1-1 policy as it is based on a false premise that this mirrors our participation. 


> On Apr 19, 2018, at 5:36 PM, Eric Rescorla <ekr@rtfm.com> wrote:
> 
> Andrew,
> 
> Thanks for raising this.
> 
> While the stated rationale in S 2. is to spread travel pain around,
> I don't really think this gets us to 1-1-1-*.
> 
> First, if you look at historical demographics, over the past 12 IETFs,
> we have 23% Asia, 26% Europe, and 42% NA). Put another way, the last
> time we had > 1/3 Asian attendance was IETF 94 in Yokohama, and the
> last time we had less than 1/3 NA attendance was IETF 79 in Beijing.
> So, a policy that was designed to match per-continent attendance would
> be more like 2-1-1-*.
> 
> Second, continent is not a very good proxy for travel pain, both
> because Asia is so large (for instance, the shortest Tokyo to
> Singapore route is 7:25 out and 7:10 back (on JAL) and the shortest
> Tokyo - Honolulu route (ANA) is 7:20/8:10, so not really much
> different at all) and because flight connections are such a big
> contributor ( for instance, SFO-BKK is almost 20 hours, whereas
> SFO-NRT is 11).
> 
> Bottom line, if this is supposed to be real requirements rather
> than just aspirations, I think it needs a rethink.
> 
> -Ekr
> 
> 
> On Wed, Apr 18, 2018 at 6:34 PM, Andrew Sullivan <ajs@anvilwalrusden.com <mailto:ajs@anvilwalrusden.com>> wrote:
> 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 <mailto:ajs@anvilwalrusden.com>
> 
> 
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue