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

Daniel Ajike Chidi <dactechng@gmail.com> Wed, 13 April 2016 05:30 UTC

Return-Path: <dactechng@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 D97B912D588 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 22:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.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] 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 O6ZypJJxb0ou for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 22:30:32 -0700 (PDT)
Received: from mail-pa0-x243.google.com (mail-pa0-x243.google.com [IPv6:2607:f8b0:400e:c03::243]) (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 D3F7912D179 for <ietf@ietf.org>; Tue, 12 Apr 2016 22:30:31 -0700 (PDT)
Received: by mail-pa0-x243.google.com with SMTP id vv3so2980928pab.0 for <ietf@ietf.org>; Tue, 12 Apr 2016 22:30:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:subject:message-id:importance:from:to:cc:mime-version; bh=DbFS9yBA18AnanhR++BimIl1nBvqxWW/PaGXaUYh6YY=; b=CjZ9Raos3E48w6Rbisnvf9xO37bdR6RaKnpUpz9WctqPi2/8oJe1GmK8Yzoiydlsy/ vkfA3DEv5/3m0HHIuFmtYuTbC2f0aJ27NFCKj+/jBA1nI8TaTLxN6WtulL6VmXmeV5+G MoE//47q2u4z6/gnYgRGEkaeeV3Jltv1PzDRi0flU3gODefu56SS6EhhwUNE7vomV4K8 +IjqV3402QOz7CpMaAM0FVCCuJLm7jvM7Jsz9zxl0n7H+/XTvv56ZI+LrWQLF4YLomBn nDMZ2VqH9yNy8zoVmoYuHLSq6rKD0C61PN4lfg3CZ3UCmYU6zR1ri/71fhXIXIX3zYRD mZTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:subject:message-id:importance:from:to:cc :mime-version; bh=DbFS9yBA18AnanhR++BimIl1nBvqxWW/PaGXaUYh6YY=; b=Evwh+Rd3GW3wZwkSNakEpyeHcxf2CByfE8MrxiBJOVYISzp1CjWJ8y2CgPbYqnqK3W uFfx50sSy7WnEqvs9+FoYgtM3W5lHHkYyejo6LJ8MVQW/AMpCt04H+L9u8zOmPS1ouJs 4Aak2rWev9z/MfrTUDkFyGQ64xZy1pF3IrGP7d8XsF3kQEzfojsVJUGpz728UH8KAG2i NYWDB7IeWB/F5C5aWiFBxaJhxwbVLNQL303hxk5pQfr23skQkirYMdHplA2klbyjbIyE b8HIPblQk1PpdBaMz7cwjxYggUlHMLLDVIAPe1y5cqudeqf2RqmIyRuDDtJNy+mi03UN aMvA==
X-Gm-Message-State: AOPr4FV+5jgIJo/CQC596s7ii57EWueFcXZgQ41uyQjjtaMKWyIN3bGbxAR/pnVovtc27g==
X-Received: by 10.66.246.165 with SMTP id xx5mr10231333pac.87.1460525431455; Tue, 12 Apr 2016 22:30:31 -0700 (PDT)
Received: from [10.0.0.164] (151-236-44-231.static.as29550.net. [151.236.44.231]) by smtp.gmail.com with ESMTPSA id v74sm47610100pfa.7.2016.04.12.22.30.27 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 22:30:30 -0700 (PDT)
Date: Wed, 13 Apr 2016 06:30:19 +0100
Subject: Re: Virtual IETFs (was: Re: Concerns about Singapore)
Message-ID: <8hmexuao0v6uj7vgeyf8e863.1460525419380@email.android.com>
Importance: normal
From: Daniel Ajike Chidi <dactechng@gmail.com>
To: Ted Lemon <mellon@fugue.com>, Tim Chown <tjc@ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_16206164285010"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_GJvl2mD4ZWsaBsrtUCgrcF8Meo>
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: Wed, 13 Apr 2016 05:30:34 -0000

Remove me from mailing list oooo


Sent from my Samsung Galaxy smartphone.-------- Original message --------From: Ted Lemon <mellon@fugue.com> Date: 12/04/2016  2:47 pm  (GMT+01:00) To: Tim Chown <tjc@ecs.soton.ac.uk> Cc: ietf <ietf@ietf.org> Subject: Re: Virtual IETFs (was: Re: Concerns about Singapore) 
When I had to miss Prague, I just time-shifted for the week.   Wouldn't work for everyone, but it seemed fine to me.
On Tue, Apr 12, 2016 at 9:42 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
On 12 Apr 2016, at 14:22, 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.
Well, there may be a number of WGs that wish to progress their work a bit more briskly, or have one or more specific topics that need prompt discussion, and use an interim meeting to achieve that. So I’m not sure it’s adding to workload, rather it may allow us to be more efficient.  But the main issue with any virtual meeting is timezones. There’s really no way to deal with that problem satisfactorily. 
Tim

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?