Re: Virtual IETFs (was: Re: Concerns about Singapore)

Ted Lemon <mellon@fugue.com> Tue, 12 April 2016 13:23 UTC

Return-Path: <mellon@fugue.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 2794D12EE63 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:23:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 OytqKrPmh79t for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:23:37 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 AF28612EE54 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:23:36 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id g184so24876048lfb.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:23:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bqnmIO6t1xbAy5LbfSq9EU8RFye/r+Ba3YF5d5AVDUc=; b=dOBJqx2UNosGhkUTK1huNE8GVDZMBXzPtsS/29SVr3Uc/VSB3zuUKzovopAtpZeiTM V5YkYO9guWe1/BmiTuwLDrCgkd717ve5t+hocT2NbWIBFbd6jnweMnM45NjmWfWHvhXb UvXysMWYiuqc0Czps/41gE2c1FGhhWV/yXQQimHEWZ+95P/WEjC6VE9yQpkXhccz3Ek5 xZqrGd4Xtg32iMLMcbS+9UgXpCUDw7/ZDFm9uSDaqVoIkTf2TQK8rE0Z4xsdYuLpPcwN 8NET7y+DPn5PrU9PtlW9Hi3kSbZgFeui+Pjc3wgxehJF1iKIPyy1etGDWmAbvBYRCaBj EFzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bqnmIO6t1xbAy5LbfSq9EU8RFye/r+Ba3YF5d5AVDUc=; b=DWYx2MHS6rQhhcXzHVJ/LQgijJkpJRWTk8K9QVTDOagSe+qvPY5cxxrpYMSROGPIaa uIs8yN5Q9fS7W8ZaVsUh3y+Su53+qHiK9uEDTOiyV0kEKOVDDajyPHD9m0JRJaqTAKzj kwc6RBmZ0TRYX0GtwIL2aaDb3huAgXeHJgL3VXmE92ciQnEJGpfilUMLfbd/KoUFuZob m17LoK6ACYUMORdWF5OKrBd4WnKN15qMFYXiBlY0bn3YKLfDQIwxukX1+kJJH4i0j4Yc F8xWCKW8v4HVyJHwWLrXJtYFw2V+EnhPC5F6eocFjcZ8n4EBVB6gnDs9nArF7G9x1CEz 3epw==
X-Gm-Message-State: AOPr4FUVDAg1C9MJJlAzRaiGjD5dm6GiT0M3kDtToZzDcZZBKqEYX/2Q6s11shT3/iice5JMtOFaLNt39bFV9A==
X-Received: by 10.112.143.40 with SMTP id sb8mr1352376lbb.83.1460467414773; Tue, 12 Apr 2016 06:23:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 06:22:54 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <EMEW3|bbf82c39a7afc0305d21ff1c5582540bs3BDUh03tjc|ecs.soton.ac.uk|22CF4C02-B728-4148-A86A-B42080728FE6@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> <DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <EMEW3|9aaa87920b361e2e71efe9c7005e927cs3BChQ03tjc|ecs.soton.ac.uk|DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk> <CAPt1N1nucCAg99gVDWOHVE2up=2xK0Qm2Ud81hUhp4ryHRmwPA@mail.gmail.com> <EMEW3|bbf82c39a7afc0305d21ff1c5582540bs3BDUh03tjc|ecs.soton.ac.uk|22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 09:22:54 -0400
Message-ID: <CAPt1N1ncty=agWKaNnYFNBXnLQnxCzZMKe8S1zTUq7hQ3SLA1w@mail.gmail.com>
Subject: Re: Virtual IETFs (was: Re: Concerns about Singapore)
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=089e011832ba76c4d80530499151
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fTnhDf9CV0J9KubzC__V376vYH8>
Cc: ietf <ietf@ietf.org>
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 13:23:39 -0000

The problem with a larger virtual interim is that it doesn't replace an
IETF, and so you're adding workload but not subtracting any workload.   I
don't see the point in that.

On Tue, Apr 12, 2016 at 8:30 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> On 12 Apr 2016, at 12:49, Ted Lemon <mellon@fugue.com> wrote:
>
> Agree about Buenos Aires.   We already do excellent virtual interims--I
> think if your standard for whether we can do a virtual IETF is that virtual
> interims work, we are already there.
>
> I think that if we want to test this idea, what we need to do is designate
> some future IETF virtual _now_, and then start preparing, rather than say
> "oh, we should do a virtual" and then dither about when we might be ready.
>   We will never be so ready that a virtual IETF feels identical to an
> in-person IETF, so let's just abandon that idea and get started on making a
> virtual IETF that, while different, is still a success.
>
>
> Sounds interesting, if something of a big leap to attempt. Is a larger
> wholly virtual, multiple WG interim meeting a next step then?
>
> Btw where do we get the virtual T-shirt? ;)
>
> Tim
>
>
> On Tue, Apr 12, 2016 at 7:43 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>
>> 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?
>>
>>
>
>