Re: Concerns about Singapore

Tim Chown <tjc@ecs.soton.ac.uk> Tue, 12 April 2016 11:43 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
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 60ACF12EB69 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.517
X-Spam-Level:
X-Spam-Status: No, score=-4.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 AfkeRi48hAKp for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:43:29 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C53C012EB2D for <ietf@ietf.org>; Tue, 12 Apr 2016 04:43:28 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CBhQSg014369 for <ietf@ietf.org>; Tue, 12 Apr 2016 12:43:26 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u3CBhQSg014369
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1460461406; bh=VUay0I+sy3Hwyr4HYqwJQSv+6sE=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=zhjjid5Yp8ymEBcM6UVuTxC6AmAL0jmPBRxjp5LqdbeADWC30dxzdrGj3syxZIh2f O1m20+wIduU2qAk8eg5VbUz2J9VnQ9g4LtvBIMWbvRCVuU0KL8VslH+rxQY2ToO+se SZqyB4hhdNTUA99Fo9/G3fBkbrMqh+aZ6+1o1wDw=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s3BChQ3219206321GJ ret-id none; Tue, 12 Apr 2016 12:43:26 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:a93e:5914:9e35:ffe3] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CBhNA9029840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 12 Apr 2016 12:43:23 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Concerns about Singapore
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com>
Date: Tue, 12 Apr 2016 12:43:22 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|9aaa87920b361e2e71efe9c7005e927cs3BChQ03tjc|ecs.soton.ac.uk|DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk>
To: ietf <ietf@ietf.org>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s3BChQ321920632100; tid=s3BChQ3219206321GJ; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u3CBhQSg014369
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/q9LMYCxfy3SQUl4D86WB2y0WFmw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 12 Apr 2016 11:43:30 -0000

Hi,

To minimise the chances of a ‘Singapore’ happening again it would seem prudent to

a) re-use previous successful meeting venues for the bulk of our meetings (say, every 5 in 6 meetings); this is one criteria for meeting selection as it stands anyway; that list might include venues like Prague, Berlin, Vancouver, etc.; we’d need to be clear in what ‘successful’ means - the meeting feedback forms provide one such mechanism;

b) be transparent at an early stage about where new venues might be, whether by country or city, so there is a fair chance for people to give feedback; of course, how such feedback is weighed is an open question, but at least it would be there, and the IAOC can then make a decision ‘eyes wide open’.

In such a system, Buenos Aires would have been a ‘1 in 6’ venue. In that light, I’d note that many people have said how much they enjoyed Buenos Aires as a meeting place. And while the IAOC probably feel rather down over the comments about Singapore, they should be praised for going out on something of a limb in making the Buenos Aires selection. (And I’d add that the enthusiasm and helpfulness of the LACNIC hosts was also fantastic.)

In terms of virtual meetings, I’d suggest we try to hold more interim WG meetings, some completely virtually, and learn how to make those better. If we can regularly hold good quality wholly virtual interim meetings, then we can consider whether the same technology might be used for a larger meeting.

Tim

> On 12 Apr 2016, at 00:54, Ted Lemon <mellon@fugue.com> wrote:
> 
> While I do not think it's true that we can entirely get away without doing in-person meetings, I do agree with you that we can do better at doing remote meetings.   Perhaps we should let this unfortunate event drive us to make the attempt.
> 
> If we were to attempt such a thing, how do you think it would work?