Re: [Manycouches] Stay Home Meet Online (SHMO) draft and proposed WG

Nick Doty <npdoty@ischool.berkeley.edu> Thu, 14 May 2020 17:32 UTC

Return-Path: <npdoty@berkeley.edu>
X-Original-To: manycouches@ietfa.amsl.com
Delivered-To: manycouches@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 540043A0BC6 for <manycouches@ietfa.amsl.com>; Thu, 14 May 2020 10:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=ischool-berkeley-edu.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 iLLM3sDb-SLB for <manycouches@ietfa.amsl.com>; Thu, 14 May 2020 10:32:21 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 BC87D3A0B84 for <manycouches@ietf.org>; Thu, 14 May 2020 10:32:21 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id s1so3788401qkf.9 for <manycouches@ietf.org>; Thu, 14 May 2020 10:32:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ischool-berkeley-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VGwQSqDUjdZ3vRSH2mjnSJUmfNgc9qR5bief81ET3FE=; b=cwCj9Q6jqDbdMtOtfQSz5K3AEp+Jrf3uV7easc0rZOdm926QyOvUMYYGUoUd4z48E7 QsKK7FCi0kfjsO9ikvTtpB/+s/dCH3ciKnQRI8vruUhVX11YhSd0XIi0T/DjDPzdxr6d YGrwx63cFjpJv8WIxvYy+dJ3qOEpCbFQXTIuoBHxOEEHvYavZR0tBBTBUhlzDCjyRNba 46gNK7KdyyR9XgDKt+6I2kAP8m8Q1RK/XHmm5aC6e+8HXvqUhd2X0xIsg0SUac1D3vAJ nESGwbNQFUj2p7kTdMUPZl7kckkiiZeS5EFSWDSjD9X2zG3JkQ/Fdm+oRVi+nTR9gpT/ rHAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VGwQSqDUjdZ3vRSH2mjnSJUmfNgc9qR5bief81ET3FE=; b=RD7inIkZmafAoAde7jatk9yuYPY6dYys+6xvTz7IGG22ANg86xXXfmIMepk3sG3mLh OyJSZ0OIiFID7PbrizqgNFX+DhwQkR7ta4Zsru2EKJzw1PgsmkK6sX5jowoCJitmdKr0 QMdmOOOA4KxvZkQlXzLg69kIK1BV2FHMoQ0GHG2IIjVp/GTkEfPJi37V4IEgLkLk89cr KPIutGwAOtdMxtlaoetQiVD0HszCDljSd+sb6tjrzIE/1KGpj/UNQgeMVzD3S3wDBPZi MIpJQQYvQESbup0G1qVbCfmLKELyUzch1cTBa3VwtDuWWxoDEXDXdBye872pR5oXNHLt PdHA==
X-Gm-Message-State: AOAM530TFljCJGcZrsSrb4XidmEh9MnA/cSmmWfZhY/NE7Pv4SNf/giV dS8D9cKbnbruQUS4SPEHVZe6eblQNf8=
X-Google-Smtp-Source: ABdhPJzX5KPpH3rk7L4Un0DTw82DQPzh/dDKxgtNbELlEYBuqGKegEc/faL+A2IL17oFzPFQbMIbHQ==
X-Received: by 2002:a37:8187:: with SMTP id c129mr5900497qkd.211.1589477540640; Thu, 14 May 2020 10:32:20 -0700 (PDT)
Received: from [192.168.1.2] (cpe-71-70-181-162.nc.res.rr.com. [71.70.181.162]) by smtp.gmail.com with ESMTPSA id 74sm2879660qke.71.2020.05.14.10.32.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 May 2020 10:32:19 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
From: Nick Doty <npdoty@ischool.berkeley.edu>
In-Reply-To: <ff2f4862-6e35-84fb-4a63-17b0a7dc917d@cs.tcd.ie>
Date: Thu, 14 May 2020 13:32:17 -0400
Cc: manycouches@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <842077E3-30D6-42F6-839F-ECCD9DD21567@ischool.berkeley.edu>
References: <E103897C-F9D9-4ED3-AB45-FD2967D7F49E@cooperw.in> <ff2f4862-6e35-84fb-4a63-17b0a7dc917d@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Alissa Cooper <alissa@cooperw.in>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/ElH8evGAGK-Are-kcj2-49A9r_Q>
Subject: Re: [Manycouches] Stay Home Meet Online (SHMO) draft and proposed WG
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List is a design team list to identify issues that would arise should an IETF meeting ever be held with O\(1000\) 'remote' participants." <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2020 17:32:23 -0000

On May 13, 2020, at 1:58 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> On 13/05/2020 18:08, Alissa Cooper wrote:
>> 
>> The charter is scoped narrowly to only deal with cancellation of
>> previously planned in-person meetings. There are other related topics
>> that need community guidance — the nomcom eligibility criteria that
>> is already being worked on (see elgibility-discuss@ietf.org
>> <mailto:elgibility-discuss@ietf.org>), the overall meeting cadence
>> and mix of in-person versus virtual meetings in the future, how to
>> craft the meeting experience at an in-person meeting when
>> significantly more people are remote, etc. But just the cancellation
>> topics on their own will require a bunch of work and may attract
>> different participants than those interested in other topics, so the
>> boundary is drawn there.
> FWIW, I'm supportive. I'm also ok with the charter not
> including "should we keep planning 3 f2f meetings per
> year?" but I'd be even happier if that question were
> also included as in scope, perhaps relating to a milestone
> that's scheduled to be discussed only after the initial
> work is done.

+1 that this work seems useful and it would seem even more useful to me if we also included discussion about whether we plan as many f2f meetings and what alternatives there are. Even just for cancellation of previously scheduled in-person meetings, we will at some point have a meeting that could feasibly go ahead (that is, might have enough attendees and might not be an enormous direct risk to public health) and IESG et al will have to decide how holding that in-person meeting would compare to a variety of Stay Home Meet Online alternatives. Shouldn’t we discuss those alternatives in the same Stay Home Meet Online group? And if not -- and I mean this as a genuine question -- where should that work take place instead?

Regarding scope:
> Technology functionality requirements for the technologies the IETF uses to support fully online meetings.
> 
> Specifications of details concerning cancellation criteria, meeting technologies, and online meeting agenda formats and content are out of scope.

Developing functionality requirements for meeting technologies while avoiding specifying details concerning meeting technologies seems a narrow path to walk. I’m not sure what is in or out of scope there.

Hope you and yours are well,
Nick