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

Mallory Knodel <mknodel@cdt.org> Wed, 13 May 2020 17:33 UTC

Return-Path: <mknodel@cdt.org>
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 889633A0C9F for <manycouches@ietfa.amsl.com>; Wed, 13 May 2020 10:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 (1024-bit key) header.d=cdt.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 plZOWJQd1ilH for <manycouches@ietfa.amsl.com>; Wed, 13 May 2020 10:33:39 -0700 (PDT)
Received: from mail-qk1-x743.google.com (mail-qk1-x743.google.com [IPv6:2607:f8b0:4864:20::743]) (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 1771C3A0D39 for <manycouches@ietf.org>; Wed, 13 May 2020 10:33:38 -0700 (PDT)
Received: by mail-qk1-x743.google.com with SMTP id s1so32860qkf.9 for <manycouches@ietf.org>; Wed, 13 May 2020 10:33:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=7NyEdcsXHbGncjyLqwb3Wr6n7RXKDC+nEt4f9XdCvMM=; b=NOon+nad97KjC78r0J+fd3t0vMEalFLCpSljhDuErC1KmkJ++IHY9EUGXiENPnEyy9 bcHqApWCktJb+FKodw0FWyvIMDFxjlfrMHRA09t8BDILz31XnIl3ZGa+Q69rQA2I8tJ9 ia2zBpehgQcrUpx/wL2u0IB+DuScPmwjFlKRE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=7NyEdcsXHbGncjyLqwb3Wr6n7RXKDC+nEt4f9XdCvMM=; b=bTdwcspVxH5/eQSWV/T28VBnpTMdCH8wudxKfl+ttyAip458tXdpoYDc3+8PIa+BDc ydEAXf5GA64vf8RZFjc8IeIj6Y6qP1NNB9IjlTpHM+4rmvY/MnwpyYz4Oo4KGItJJh0o 7qefVZJBu9qH3RGPNqxBtwcv+s/2Yiy6ejSFzAMrCVQG/4p7l6nsAddS8pmda0IlwVrF ue/w9LvvaBcFO5tgdhe8RfxjzXaIDM24y0cFqSTYmz+Q/P/VswCHHkMWMqriIBBJiASa 2FzMdfCh7c8QtwJ+Cb0Er8aexia33S+iTwq1Ymi4Vh2XCjf+NEkH5ETm1o/ELpDOhK93 3PgA==
X-Gm-Message-State: AOAM532MqWxRmvP1o2QSIIubWcMoUr5KrAG7CCEdKZKzO7qWd9jj0WH4 jfc1q2O6sL4IwayG0RiT03B7rOzOn/8=
X-Google-Smtp-Source: ABdhPJw3ucTUSlt4e7n3KfXU/LK4DJ/S8JtIqh8mFTB50jm7qNNgNbvwu781sqTTPndjA/n+oVrvhw==
X-Received: by 2002:a37:9dc5:: with SMTP id g188mr764414qke.193.1589391216538; Wed, 13 May 2020 10:33:36 -0700 (PDT)
Received: from Mallorys-MacBook-Air.local (c-73-163-188-207.hsd1.dc.comcast.net. [73.163.188.207]) by smtp.gmail.com with ESMTPSA id 206sm391795qki.48.2020.05.13.10.33.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 13 May 2020 10:33:36 -0700 (PDT)
To: Alissa Cooper <alissa@cooperw.in>, manycouches@ietf.org
References: <E103897C-F9D9-4ED3-AB45-FD2967D7F49E@cooperw.in>
From: Mallory Knodel <mknodel@cdt.org>
Message-ID: <7c8de973-af9b-90b8-2e92-7a824ffcc15c@cdt.org>
Date: Wed, 13 May 2020 13:33:35 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <E103897C-F9D9-4ED3-AB45-FD2967D7F49E@cooperw.in>
Content-Type: multipart/alternative; boundary="------------6F18A08C035DA221D4235673"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/A70FhFT1aaFoTjyb-MPrQCRXytE>
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: Wed, 13 May 2020 17:33:46 -0000

Thanks for this Alissa,

And thanks to you three and everyone in the IETF leadership who has been 
dealing with these difficult questions since February.

I have looked through the I-D and the charter and it all sounds good and 
thorough. I only have a high level point, which is to say that a nice 
outcome of this might be that WG/RG chairs are more aware of and 
involved in planning their sessions based on interest, work items and 
availability.

As a manager I've always liked the guidance that says, decisions should 
be made closest to the problem by the people with the most information. 
In the case of the participation questions in the I-D I think WG/RG 
chairs should be asked to make these assessments and try to feed up as 
much information as they can to those making the larger decisions.

In general, what I'm trying to say, is that these are tough and 
important decisions that shouldn't have to be made alone in a community 
that is rigorous in its structure and format. WG/RG meetings should be 
scheduled and held based on need, assessed by the chairs, and no longer 
just based on the existence of a pre-planned, week-long conference.

-Mallory


On 5/13/20 1:08 PM, Alissa Cooper wrote:

> Hi all,
>
> Unsurprisingly, there has been a lot of discussion in the community 
> recently about planning for IETF meetings in times of crisis and 
> disruption. Below is a draft of a charter for a working group, Stay 
> Home Meet Online (SHMO), that could start to develop long-term 
> guidance of the sort it would have been nice to have as the IESG, IRTF 
> Chair, and IETF LLC have been faced with decisions about canceling the 
> in-person meetings for IETF 107 and 108. It is somewhat in the 
> MTGVENUE mold, as the idea is to provide high-level guidance about 
> meeting-related matters. Suresh Krishnan and Russ Housley and I have 
> been working on this together.
>
> 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.
>
> We’re sharing this here on manycouches@ietf.org 
> <mailto:manycouches@ietf.org> to start community discussion about it 
> with the hope of either proposing a BOF or perhaps going directly to 
> chartering if there seems to be support in the community for that.
>
> We have also published an individual I-D 
> <https://datatracker.ietf.org/doc/html/draft-cooper-shmo-questions-00> 
> that lists out the questions and considerations the IESG has been 
> facing when cancelling an in-person meeting, just to serve as a basis 
> for discussion and give the community an idea of the kinds of 
> questions where it would be helpful to have guidance.
>
> Thanks,
> Alissa, Suresh, and Russ
>
>
> —
>
> Stay Home Meet Online (SHMO) Working Group
> Draft Charter
>
> The COVID-19 pandemic has disrupted the IETF's typical schedule of 
> three in-person meetings per year. It has caused the IETF to have to 
> convert previously scheduled in-person meetings into fully online 
> meetings. Although it is the first time the IETF's meeting schedule 
> has been disrupted, it is possible that other crises could cause 
> similar disruptions in the future.
>
> The meeting planning activities that the IESG and the IETF LLC engage 
> in would benefit from IETF community consensus guidance concerning 
> novel aspects raised by these developments. The SHMO working group is 
> therefore chartered to provide high-level guidance to the IESG and the 
> IETF LLC concerning the following:
>
> - Criteria for determining when a previously scheduled in-person 
> meeting should be canceled and replaced with a fully online meeting. 
> Similar to how RFC 8718 establishes community guidance for the 
> selection of meeting venues, the IESG and the LLC would benefit from 
> community consensus guidelines about which factors to consider when 
> deciding to cancel or replace an in-person meeting and the relative 
> importance of those factors. This work item is expected to be 
> fulfilled with the publication of a BCP.
>
> - Meeting planning in the event that a previously scheduled in-person 
> meeting needs to be canceled and replaced with a fully online meeting. 
> Similar to how RFC 8719 establishes guidance for the regional rotation 
> of in-person meetings, the IESG and the LLC would benefit from having 
> community consensus guidelines about the time zone selection, meeting 
> length in days, and other high-level scheduling aspects when an 
> in-person meeting must be cancelled. This work item is expected to be 
> fulfilled with the publication of one or more BCPs.
>
> - Technology functionality requirements for the technologies the IETF 
> uses to support fully online meetings. This work item is expected to 
> be fulfilled with one or more informational RFCs.
>
> The work of SHMO is expected to produce high-level principles, not 
> detailed operational plans. Specifications of details concerning 
> cancellation criteria, meeting technologies, and online meeting agenda 
> formats and content are out of scope. Discussion of financial aspects 
> of IETF meetings is out of scope. The goal is to produce guidelines 
> for the IESG and the IETF LLC to operationalize while ensuring they 
> have substantial flexibility to continue to deliver and evolve the 
> IETF meeting experience to best serve IETF participants and the 
> Internet community at large.
>
> The disruptions caused by the COVID-19 pandemic may have been 
> mitigated by the time this group completes its work, but the 
> experience of handling meeting planning during the pandemic has proven 
> that having community consensus guidance at hand when dealing with 
> novel conditions in the future would be beneficial.
>
>
>
> _______________________________________________
> Manycouches mailing list
> Manycouches@ietf.org
> https://www.ietf.org/mailman/listinfo/manycouches