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

Alia Atlas <akatlas@gmail.com> Tue, 12 April 2016 13:33 UTC

Return-Path: <akatlas@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 4F29712DC24 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level:
X-Spam-Status: No, score=-102.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 DLxqOettMs4g for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:33:13 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (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 203E612E06D for <ietf@ietf.org>; Tue, 12 Apr 2016 06:33:13 -0700 (PDT)
Received: by mail-ob0-x22e.google.com with SMTP id bg3so11379690obb.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:33:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=BiorpVctUVyI1dQwbG3Z2CluqLhSBhVyBUkPBB0BXQc=; b=mqgJeA7yWg8i2FZb3mbvXpzB993lNOEdRHM/YbBw/5sNRzGZQzsQpr3xztET6WowoA 2kS9ncvjIzyqZhKJF0x6MEa1g8+V5i7AoPPX03H0W/20BnSmPZqTMOeajAM0FXRJx7KO lIYa27tlGtIlCUMaXHeMp22jGYAGbo2+grPmwT69xXBOTjy76wXWeo3PIbmN9dKi+9nC LXUk440C3+UkFeLTjVSvYdQ+UvmPQn59La+Uecb2zi2uMR50T1wzaT2wFdrp4p5YP900 3gYGBMtFx9NHLwrFJABrYlKiVYzSETmZ4PmJsWyTSOIsOF66ICRWklD9rUmRMgK3qjLg F2Xw==
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:date :message-id:subject:from:to:cc; bh=BiorpVctUVyI1dQwbG3Z2CluqLhSBhVyBUkPBB0BXQc=; b=heWdUItLDb5KhWpagZV8NHrLtN+wtwZMyUz4bzZLXx7yr7bNX7hPVRqVU4F3B8W5Pz APYnk6vAtwBhhmEIaFe20p5RgtY6HP4EAw1470ZapmhBBhOtqzKDtQ2lkIpJ7i7lHB3j d22EGCEjMozJ2F612w/8lpoSWFSt1Q2v/N1q1A6nOD8Uga63BqcsY7mE26/qapxWq1MC COpDkiM+x9dLVCkc9zetTEFkW2cHEyGERKO2dqHhZ3GEkGND4sNFdDtxuNIJw5IMIay3 HZj9qFRALU4/2efKMJxaU6uLLZZAIVuqQL+wWoQCuR/WB80Rz+CGcpMgrpU0gq0J/Lh6 vGiA==
X-Gm-Message-State: AOPr4FVWSfBofg7uQRT8fJlpKUT6N/dO0rEyuIxpes9kEFnkpS+C0vImQj0bdhxHMtCPRGzaNXFHeiSSZOF7RQ==
MIME-Version: 1.0
X-Received: by 10.60.56.170 with SMTP id b10mr378480oeq.27.1460467992517; Tue, 12 Apr 2016 06:33:12 -0700 (PDT)
Received: by 10.60.115.168 with HTTP; Tue, 12 Apr 2016 06:33:12 -0700 (PDT)
In-Reply-To: <CAPt1N1ncty=agWKaNnYFNBXnLQnxCzZMKe8S1zTUq7hQ3SLA1w@mail.gmail.com>
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> <CAPt1N1ncty=agWKaNnYFNBXnLQnxCzZMKe8S1zTUq7hQ3SLA1w@mail.gmail.com>
Date: Tue, 12 Apr 2016 09:33:12 -0400
Message-ID: <CAG4d1rd1x=gbj3OS2t_N8njOPxnbbCeS9T+tKcFuTgShetPFZA@mail.gmail.com>
Subject: Re: Virtual IETFs (was: Re: Concerns about Singapore)
From: Alia Atlas <akatlas@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=089e013a0ec2e668e0053049b370
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/VK_HUJh72ujbxxuo_frliu7ejiY>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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:33:15 -0000

On Tue, Apr 12, 2016 at 9:22 AM, Ted Lemon <mellon@fugue.com> wrote:

> 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.
>

It clocks those working groups at a higher rate.  Many people find it
easier to prioritize IETF work when there are specific deadlines or a loss
of face if work isn't done.

While the IETF determines consensus on mailing lists, there has been a
strong tendency in the last decade to focus on the physical meetings for
the next deadline, to have necessary talks, and so on.   I personally feel
that it is important to push back on this.

Discussing an issue on the mailing list suffers from people losing state on
the issue being talked about - for instance:
     Day 1: Alice reviews a draft and posts her review with a technical
point to consider.  Bob, an author, sees the email but is
                in the midst of a day-job priority.
     Day 4: Bob reads the email, rereads the draft section, and suggests a
fix.  Alice sees email, but is focused on day-job.
     Day 8: Alice refreshes her memory and responds with a point that
wasn't handled.
etc.

A benefit of virtual interims is that folks try to be up to speed and that
conversational back and forth can happen.
We do the same thing - aspirationally - on WGLCs on the mailing lists where
a two-week period is set aside to focus on a
particular draft.

Regards,
Alia



> 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?
>>>
>>>
>>
>>
>