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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 27 May 2020 18:22 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 909AE3A07D6 for <manycouches@ietfa.amsl.com>; Wed, 27 May 2020 11:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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 (1024-bit key) header.d=cs.tcd.ie
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 1Xs2_rKBc5pP for <manycouches@ietfa.amsl.com>; Wed, 27 May 2020 11:22:04 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A37273A00B2 for <manycouches@ietf.org>; Wed, 27 May 2020 11:22:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id AAD7ABE24; Wed, 27 May 2020 19:22:01 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ebt2TcXs77Sh; Wed, 27 May 2020 19:21:59 +0100 (IST)
Received: from [10.244.2.119] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E4525BE20; Wed, 27 May 2020 19:21:58 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1590603719; bh=tKXg2Nl+LIwsSU54qPn3cNr2VF6EqoXaq+NpPoiik1U=; h=Subject:To:References:From:Date:In-Reply-To:From; b=viWKoTkQuJ6skwUdfLDyt4qcnrW73qKcimx/FUFhm3C7gQMneZf5XF195ZsY6qUvX tuAX5ED8spzaDWxiVdmWDMMkhftWDmSA9902ZBzWIr1WsCbwk3s8HL56ndbqiaU/xj ncrBYY1vMLWnNHa6+IwOpSXQASb8SmKHH2Y5d79k=
To: Alissa Cooper <alissa@cooperw.in>, manycouches@ietf.org
References: <E103897C-F9D9-4ED3-AB45-FD2967D7F49E@cooperw.in> <53DD003D-4464-4F17-92BB-C9B1D7ACF09D@cooperw.in>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Autocrypt: addr=stephen.farrell@cs.tcd.ie; prefer-encrypt=mutual; keydata= mQINBFo9UDIBEADUH4ZPcUnX5WWRWO4kEkHea5Y5eEvZjSwe/YA+G0nrTuOU9nemCP5PMvmh 5Cg8gBTyWyN4Z2+O25p9Tja5zUb+vPMWYvOtokRrp46yhFZOmiS5b6kTq0IqYzsEv5HI58S+ QtaFq978CRa4xH9Gi9u4yzUmT03QNIGDXE37honcAM4MOEtEgvw4fVhVWJuyy3w//0F2tzKr EMjmL5VGuD/Q9+G/7abuXiYNNd9ZFjv4625AUWwy+pAh4EKzS1FE7BOZp9daMu9MUQmDqtZU bUv0Q+DnQAB/4tNncejJPz0p2z3MWCp5iSwHiQvytYgatMp34a50l6CWqa13n6vY8VcPlIqO Vz+7L+WiVfxLbeVqBwV+4uL9to9zLF9IyUvl94lCxpscR2kgRgpM6A5LylRDkR6E0oudFnJg b097ZaNyuY1ETghVB5Uir1GCYChs8NUNumTHXiOkuzk+Gs4DAHx/a78YxBolKHi+esLH8r2k 4LyM2lp5FmBKjG7cGcpBGmWavACYEa7rwAadg4uBx9SHMV5i33vDXQUZcmW0vslQ2Is02NMK 7uB7E7HlVE1IM1zNkVTYYGkKreU8DVQu8qNOtPVE/CdaCJ/pbXoYeHz2B1Nvbl9tlyWxn5Xi HzFPJleXc0ksb9SkJokAfwTSZzTxeQPER8la5lsEEPbU/cDTcwARAQABtDJTdGVwaGVuIEZh cnJlbGwgKDIwMTcpIDxzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllPokCQAQTAQgAKgIbAwUJ CZQmAAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAUCWj6jdwIZAQAKCRBasvrxexcr6o7QD/9m x9DPJetmW794RXmNTrbTJ44zc/tJbcLdRBh0KBn9OW/EaAqjDmgNJeCMyJTKr1ywaps8HGUN hLEVkc14NUpgi4/Zkrbi3DmTp25OHj6wXBS5qVMyVynTMEIjOfeFFyxG+48od+Xn7qg6LT7G rHeNf+z/r0v9+8eZ1Ip63kshQDGhhpmRMKu4Ws9ZvTW2ACXkkTFaSGYJj3yIP4R6IgwBYGMz DXFX6nS4LA1s3pcPNxOgrvCyb60AiJZTLcOk/rRrpZtXB1XQc23ZZmrlTkl2HaThL6w3YKdi Ti1NbuMeOxZqtXcUshII45sANm4HuWNTiRh93Bn5bN6ddjgsaXEZBKUBuUaPBl7gQiQJcAlS 3MmGgVS4ZoX8+VaPGpXdQVFyBMRFlOKOC5XJESt7wY0RE2C8PFm+5eywSO/P1fkl9whkMgml 3OEuIQiP2ehRt/HVLMHkoM9CPQ7t6UwdrXrvX+vBZykav8x9U9M6KTgfsXytxUl6Vx5lPMLi 2/Jrsz6Mzh/IVZa3xjhq1OLFSI/tT2ji4FkJDQbO+yYUDhcuqfakDmtWLMxecZsY6O58A/95 8Qni6Xeq+Nh7zJ7wNcQOMoDGj+24di2TX1cKLzdDMWFaWzlNP5dB5VMwS9Wqj1Z6TzKjGjru q8soqohwb2CK9B3wzFg0Bs1iBI+2RuFnxLkCDQRaPVAyARAA+g3R0HzGr/Dl34Y07XqGqzq5 SU0nXIu9u8Ynsxj7gR5qb3HgUWYEWrHW2jHOByXnvkffucf5yzwrsvw8Q8iI8CFHiTYHPpey 4yPVn6R0w/FOMcY70eTIu/k6EEFDlDbs09DtKcrsT9bmN0XoRxITlXwWTufYqUnmS+YkAuk+ TLCtUin7OdaS2uU6Ata3PLQSeM2ZsUQMmYmHPwB9rmf+q2I005AJ9Q1SPQ2KNg/8xOGxo13S VuaSqYRQdpV93RuCOzg4vuXtR+gP0KQrus/P2ZCEPvU9cXF/2MIhXgOz207lv3iE2zGyNXld /n8spvWk+0bH5Zqd9Wcba/rGcBhmX9NKKDARZqjkv/zVEP1X97w1HsNYeUFNcg2lk9zQKb4v l1jx/Uz8ukzH2QNhU4R39dbF/4AwWuSVkGW6bTxHJqGs6YimbfdQqxTzmqFwz3JP0OtXX5q/ 6D4pHwcmJwEiDNzsBLl6skPSQ0Xyq3pua/qAP8MVm+YxCxJQITqZ8qjDLzoe7s9X6FLLC/DA L9kxl5saVSfDbuI3usH/emdtn0NA9/M7nfgih92zD92sl1yQXHT6BDa8xW1j+RU4P+E0wyd7 zgB2UeYgrp2IIcfG+xX2uFG5MJQ/nYfBoiALb0+dQHNHDtFnNGY3Oe8z1M9c5aDG3/s29QbJ +w7hEKKo9YMAEQEAAYkCJQQYAQgADwUCWj1QMgIbDAUJCZQmAAAKCRBasvrxexcr6qwvD/9b Rek3kfN8Q+jGrKl8qwY8HC5s4mhdDJZI/JP2FImf5J2+d5/e8UJ4fcsT79E0/FqX3Z9wZr6h sofPqLh1/YzDsYkZDHTYSGrlWGP/I5kXwUmFnBZHzM3WGrL3S7ZmCYMdudhykxXXjq7M6Do1 oxM8JofrXGtwBTLv5wfvvygJouVCVe87Ge7mCeY5vey1eUi4zSSF1zPpR6gg64w2g4TXM5qt SwkZVOv1g475LsGlYWRuJV8TA67yp1zJI7HkNqCo8KyHX0DPOh9c+Sd9ZX4aqKfqH9HIpnCL AYEgj7vofeix7gM3kQQmwynqq32bQGQBrKJEYp2vfeO30VsVx4dzuuiC5lyjUccVmw5D72J0 FlGrfEm0kw6D1qwyBg0SAMqamKN6XDdjhNAtXIaoA2UMZK/vZGGUKbqTgDdk0fnzOyb2zvXK CiPFKqIPAqKaDHg0JHdGI3KpQdRNLLzgx083EqEc6IAwWA6jSz+6lZDV6XDgF0lYqAYIkg3+ 6OUXUv6plMlwSHquiOc/MQXHfgUP5//Ra5JuiuyCj954FD+MBKIj8eWROfnzyEnBplVHGSDI ZLzL3pvV14dcsoajdeIH45i8DxnVm64BvEFHtLNlnliMrLOrk4shfmWyUqNlzilXN2BTFVFH 4MrnagFdcFnWYp1JPh96ZKjiqBwMv/H0kw==
Message-ID: <e2d19641-1f8a-7416-6df0-a9bea37b5234@cs.tcd.ie>
Date: Wed, 27 May 2020 19:21:58 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <53DD003D-4464-4F17-92BB-C9B1D7ACF09D@cooperw.in>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="sHMY453LlwW7hccVQRILhTYx7rIxAX7wq"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/86e2tBMfuTBpZsvw_DB-WpWl6Fg>
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, 27 May 2020 18:22:07 -0000


On 27/05/2020 19:02, Alissa Cooper wrote:
> In reviewing this thread it seems like there are two key questions
> that were raised that bear on the charter text:
> 
> 1. Whether the charter should cover broader changes to the cadence of
> in-person meetings outside the context of cancellations. When
> developing this charter I had written up some text about this but was
> on the fence about including it as it does broaden the scope. I think
> including this as a work item but gating it on the completion of the
> other work items could be a nice compromise. This was the text I had
> to describe the work item:
> 
> - The cadence of meeting scheduling and the mix of in-person versus
> fully online meetings going forward once the disruptions caused by
> the pandemic have subsided. The working group is expected to document
> the expected future meeting cadence as a BCP if consensus emerges to
> depart from the existing cadence of three in-person meetings per
> year. Notably, any such guidance will not become actionable until 3-4
> years after it achieves consensus, given the length of the IETF
> meeting planning cycle.

I think that's plenty good enough.

S.

> 
> 2. How to be clearer about the level of specificity expected in the
> guidance to be provided. I’m not sure how to tackle this one.
> Regarding technology, my hope was that by saying “technology
> functionality” this would be sufficiently clear — e.g., recommending
> that two-way audio and video are available is in scope, whereas
> recommending that we always use H.264 is not. For the meeting
> planning work item I’m not sure what more can be said aside from
> using the term “high-level guidance.”
> 
> Thoughts?
> 
> Thanks, Alissa
> 
> 
>> On May 13, 2020, at 1:08 PM, Alissa Cooper <alissa@cooperw.in>
>> 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
>> <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
> 
> 
> 
> _______________________________________________ Manycouches mailing
> list Manycouches@ietf.org 
> https://www.ietf.org/mailman/listinfo/manycouches
>