Re: BoF's in the Age of Covids

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 18 May 2020 02:16 UTC

Return-Path: <spencerdawkins.ietf@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 854A23A07D6 for <ietf@ietfa.amsl.com>; Sun, 17 May 2020 19:16:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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=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 lKADi9rnavXZ for <ietf@ietfa.amsl.com>; Sun, 17 May 2020 19:16:35 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::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 AAFA23A07D5 for <ietf@ietf.org>; Sun, 17 May 2020 19:16:34 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id h4so8112140ljg.12 for <ietf@ietf.org>; Sun, 17 May 2020 19:16:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=t8KSo8cfDaj5GRgpF8KjBN55aq0TBJs8fGvFeHagcRc=; b=XNdJgyxzwoYsJJmD/cFJ/DFX/xRLvsJwAag8USdYMkV3LHvNHQW/JUX4f8u5qsD4nT lCtJB0XEZxwLzcDvGQ85EhGNJreQIX0t6rWENCZAUwGIWIBsGCTxIJfdQMOqihCWJKzq g+7+W9uHTCDVWIxjTofpzGQBkv4c5O676CIO3qmTxLEAzg545udTxozHF0uf8tV9Gfqu W9wAWvfex64jDW2QXdkqcKGKV0x8Fmkfm6orSmbVoOjCysIw5ddBRrQkWKW3e7jm5sc/ fmSwbmx76Q74CMXZIUCElQRyq3kHy5kZX5ZE17rW3awlPRO6ulWIOBio0JtrAgyW5Zpd Qnlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=t8KSo8cfDaj5GRgpF8KjBN55aq0TBJs8fGvFeHagcRc=; b=YZMt+c2qg+tEGSgBW0b/HoNOB7Zml0jTVUIlHvyVrZXxFFJemePKnSZHLFzIUy5nIz Kg3xc53flpWzwK2gpabOdjUgviwjZD8LYGl2zUj+6rU10J7/L3r4Bfima+6P/gm7ActU it3oy1hgwjZmRUM5hQANDM7bveUgOvJwoa5/yM7LFk113vTgZGvm+bmOUJuJrTWaZ39n BCvHN/Z7wA/MYGyHBf1aoyDhc+dykDhrefbicremUqP9YIqKXqolkTZov7gBt1Txi5IV 3wmOFW8fTWoc655Jl8OSFFkjIRwe2aXkcR+MmAn4Lh0AUboC2CvNtvchegaJZSOU6IG8 E24w==
X-Gm-Message-State: AOAM533Efmo1ZN14C+LGyoWr/QSRHW+T6eLjEWzyuIDp4+WaHk1EOL+8 D1gPFktwsfyMXckjeACcw4xBioMcYNkrhFrS07LivTbH
X-Google-Smtp-Source: ABdhPJxQ5H6959NfQT8B55Sue7FIGQNOZfxl1y7Cmm6oJlgfbjgmZLTKD6RjUD8VUUfGKxfmvaBsg45NQUOlJU2KPsA=
X-Received: by 2002:a2e:b609:: with SMTP id r9mr8772292ljn.125.1589768192815; Sun, 17 May 2020 19:16:32 -0700 (PDT)
MIME-Version: 1.0
References: <4db0288e-4910-670a-7897-fffe68d06982@mtcc.com> <19600.1589238846@localhost> <bd298cdc-1d29-2ae0-7ba7-f8a58220285c@mtcc.com> <7464.1589271343@localhost> <9a33c639-e85c-1d2e-bd24-50b392d1c07b@mtcc.com>
In-Reply-To: <9a33c639-e85c-1d2e-bd24-50b392d1c07b@mtcc.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 17 May 2020 21:16:06 -0500
Message-ID: <CAKKJt-dNsfVmtV48K-H0yatWLt1YTjEX7QzP_wQ+bwJ7Gv=UAg@mail.gmail.com>
Subject: Re: BoF's in the Age of Covids
To: Michael Thomas <mike@mtcc.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000687c3705a5e2c032"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-SJbyJoZV0Ssbq7MahoR1mzolPQ>
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: Mon, 18 May 2020 02:16:37 -0000

FWIW,

On Tue, May 12, 2020 at 10:13 AM Michael Thomas <mike@mtcc.com> wrote:

>
> On 5/12/20 1:15 AM, Michael Richardson wrote:
> > Michael Thomas <mike@mtcc.com> wrote:
> >      > On 5/11/20 4:14 PM, Michael Richardson wrote:
> >      >> Michael Thomas <mike@mtcc.com> wrote: > It's been my impression
> that a
> >      >> substantial amount of the work for > putting together BoF's, etc
> has
> >      >> been done loosely and informally > usually in the setting of a
> meeting
> >      >> and drinking beers with others (aka > bar BoF). Since we seem to
> be
> >      >> doing neither neither these days, from > what I can tell this
> list is
> >      >> the closest to that in purpose. Yet since > it's ietf-wide it
> includes
> >      >> lots of different areas and interests it's > easy to see how the
> >      >> signal to noise ratio might get bad in a
> >      >>
> >      >> I agree that ietf@ietf.org is a good starting point, but I
> think one
> >      >> needs to take a bit of a shotgun to a half-dozen other MLs to let
> >      >> people know you are thinking of something.  ietf@ietf.org is not
> >      >> universally read, alas.  Also making use of Any-of-Other-Business
> >      >> section of other virtual interims to talk briefly about things.
> I
> >      >> wouldn't be afraid of babbling about such things in the jabber,
> DURING
> >      >> (virtual) meetings, but also in hallway@
> >
> >      > You mean wg ml's? Often that is the *last* place I'd want to bring
> >      > something new up and from my experience the feeling is mutual :)
> >
> > I'm not suggesting trying to have the conversation there, but rather,
> that
> > it's an important place to find interested parties.  To be clear: it's
> for
> > the announcement.
>
>
> Yeah, that smells suspiciously of spam to my taste. You're trying to get
> the attention of the usual suspects, but the problem has little if
> anything to do with the wg's. The bulletin board in the lobby is a much
> more neutral place since it is passively rather than actively alerting.
> Maybe a per-area bar-bof-alert mailing list? nicer would be to be able
> to send out the idea and create a chat room for it which was reaped if
> it goes unused for some period of time.
>

In meat-space, this was what we intended the HotRFC sessions on Sunday
nights of IETF week to be.

We didn't have HotRFC for IETF 107, and no one complained because we were
thrilled we could actually get all the BOFs, area sessions, and first-time
working groups scheduled, but if we're not going to have a face-to-face
session in 2020 (does anyone think we are?), it may be worth asking the
Aaron Falks of the world to think about what they need to run HotRFC
virtually, really, and whether that could be done more frequently than
three times per year.

I note that "how important is HotRFC for IETF 108?" was on the meeting
survey a couple of weeks ago - perhaps we got some helpful thoughts there,
too.

Best,

Spencer


>
> The long and short of this is that for an org so bolted at the hip to
> e-conversations, it's going to be interesting to find all of the places
> that we're dependent to meat-space.
>
> Mike
>
>