Re: Registration details for IETF 108

Colin Perkins <csp@csperkins.org> Thu, 11 June 2020 12:20 UTC

Return-Path: <csp@csperkins.org>
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 C14353A0795 for <ietf@ietfa.amsl.com>; Thu, 11 Jun 2020 05:20:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=csperkins.org
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 Zyxbh3QHNdvy for <ietf@ietfa.amsl.com>; Thu, 11 Jun 2020 05:20:09 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (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 3B9843A0771 for <ietf@ietf.org>; Thu, 11 Jun 2020 05:20:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=To:Date:From:Subject; bh=JesQFcVpcE7Y5q/3BPY5SUSUEXOfcVw2NW6RRRn/Kv0=; b=Lr3+IIpb3f3GJZQ0QTCwePBrdq 57I3pCv71EF64jbJI3v5QeVntylZsrS83bLUGKLG/Ji9I3z+2jv4SjR+ngrE0ItfSANWRJwmf/55Z hrrNfsXY4P/WW3p9ioe5vM/kqD98+N4TEaYv/RBnWrjrte14a/pJBqWBqOgR6KOZscZtSs8zfldwG Sj62SAx5Yj/hyQLiuCAzcYqla4SGKmiFZj0z3nDXmTClRXBSA0lUV8YJm0EmAPc2RJtKcySOzUcMO N66yn2vAg8B390S1i0RK+tY19a1vQWrkuH+IFYnK02LilRz3GOl13vmpEkQRwEKLyRVm3Cmr8dplY /fIMEIuA==;
Received: from [81.187.2.149] (port=44542 helo=[192.168.0.80]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1jjMBi-000314-Lq; Thu, 11 Jun 2020 13:20:06 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Subject: Re: Registration details for IETF 108
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <m2ftb1reu1.wl-randy@psg.com>
Date: Thu, 11 Jun 2020 13:20:03 +0100
Cc: Tim Chown <tjc.ietf@gmail.com>, IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2E2893AA-2BCC-4EA1-AF31-0B4BA437C46F@csperkins.org>
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <9F71F116-D7B2-4ECE-9000-957A0C497404@ietf.org> <01d701d638ca$c096b5e0$41c421a0$@gmail.com> <CABcZeBOLAw_9s-gobFYB=5THu_Q70UmDLn_ZhVXhNRHN_nu_0w@mail.gmail.com> <607b7682-0a75-62b6-fd0e-5e2e1171a68b@cs.tcd.ie> <CA+9kkMBEqhn115ToB0SwOGavmXze4DdJdL941J4LeVMRrPngpQ@mail.gmail.com> <e1b804ae-4c2e-fdf3-8804-47820d35facf@cs.tcd.ie> <CA+9kkMC8ZWHaCBg=WzwtriVf-3bq=egupVgAH-J7dSqspwLoFw@mail.gmail.com> <a19c3066-bfa7-ded2-d98f-b5e367645451@cs.tcd.ie> <E8BE49F8-6FE8-4470-9314-21F8BFE9768A@gmail.com> <1UWAyqDxFn.1IOJoXgqe8i@pc8xp> <m2tuzpz0eg.wl-randy@psg.com> <94fdbedd-358b-7fae-c784-9550311d8aea@gmail.com> <m2h7voztz5.wl-randy@psg.com> <6F3828AD-FFE3-4331-8E76-E212F1357919@gmail.com> <m2ftb1reu1.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3445.104.14)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CwCeTbIfcBqKgEW4asArU_lsjio>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 11 Jun 2020 12:20:13 -0000

> On 11 Jun 2020, at 13:01, Randy Bush <randy@psg.com> wrote:
>>> let me see if i can push you just a little bit out of the box.  a
>>> small step.
>>> 
>>> there are two time slots in the day which work for what i call three
>>> continent calls, apac, emea/africa, noam/alyc.  each day a different
>>> wg meets in one of those two slots of *their* choice.  thus the ietf
>>> 'meeting' is smeared over three months.
>> 
>> Keep pushing.
>> 
>> And this would win us a schedule free of WG meeting clashes, and
>> avoidance of several hundred drafts being published in 24 hours with
>> very little hope of reading the ones that interest you before the WG
>> meeting.
>> 
>> Many WGs are already embracing more frequent online interims, so
>> “smearing” the work is already happening.  The question is whether
>> some structure like the above is preferred, or ad-hoc meetings as and
>> when each WG wants them.
> 
> an example
> 
> https://ooni.org/post/2020-internet-measurement-village/#schedule
> 
> TMA2020, which i am attending as i type, is a more classic format,
> mixing zoom and slack, and is time skewed somewhat to try to have a
> timezone footprint which is not too onerous for asia and the americas.
> but they tried to innovate in the discussions, per-paper slack channels,
> interactive q&a, etc.
> 
> maybe the hardest part is what our community refers to as 'the hallway.'
> i am looking for communities trying to innovate in this space.  imiho,
> this is really important.  i can read your paper/draft/...  and zoom +q
> interaction is about as good as the mic line.  but hanging out,
> discussing, gossiping, ...  is more important to us funny monkeys the
> tools seem to support.


I’ve seen a couple of conferences using gather.town – there’s a video from PLDI at https://www.youtube.com/watch?v=Y0xZLJVhzPc that talks about their plans.

We’ve had some discussion of trying it with IETF, although it’s not clear it’ll work at the scale we need.

Colin