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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Wed, 13 May 2020 20:20 UTC

Return-Path: <prvs=1402fd4930=jordi.palet@consulintel.es>
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 6DB123A08E2 for <manycouches@ietfa.amsl.com>; Wed, 13 May 2020 13:20:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=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=consulintel.es
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 BptSKZli90vg for <manycouches@ietfa.amsl.com>; Wed, 13 May 2020 13:20:09 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id EFEF53A08E1 for <manycouches@ietf.org>; Wed, 13 May 2020 13:20:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1589401207; x=1590006007; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type; bh=25NZGF9a4KuDzrbyOuxp1w+uJ7y8roxxzk 0XITKZPl4=; b=pavrR5PgkPj14bXE+fIGgaxq1ykmE7TA7jwmSy25wANrlxV2pb Ve/64pxolBc5HmmGPqbXcRxjFIDuIBac5WrXuKOjOrxxnFjTkP5llUn5slG9mxcP ayeIpasEfCmF7H/sYK7KE9qMzgjlPGgmUujOouyM/o7qI8LjZKmwbXRrE=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Wed, 13 May 2020 22:20:07 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 13 May 2020 22:20:06 +0200
Received: from [10.10.10.130] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000160706.msg for <manycouches@ietf.org>; Wed, 13 May 2020 22:20:06 +0200
X-MDRemoteIP: 2001:470:1f09:495:64bd:6386:b554:830c
X-MDHelo: [10.10.10.130]
X-MDArrival-Date: Wed, 13 May 2020 22:20:06 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1402fd4930=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: manycouches@ietf.org
User-Agent: Microsoft-MacOutlook/16.37.20051002
Date: Wed, 13 May 2020 22:20:04 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: manycouches@ietf.org
Message-ID: <3E2880B1-2712-4C8B-B7DF-FC35F192133F@consulintel.es>
Thread-Topic: [Manycouches] Stay Home Meet Online (SHMO) draft and proposed WG
References: <E103897C-F9D9-4ED3-AB45-FD2967D7F49E@cooperw.in> <72840D63-E994-454F-83CD-42D2D0924944@cooperw.in> <6C82EB0A-47D1-4E1C-8CD6-EB13351AB294@consulintel.es> <CAC8QAce7LJr6y2VeeH1pyT0MKW4fb_Uc9sAEGAHgtdZvc5WoWA@mail.gmail.com>
In-Reply-To: <CAC8QAce7LJr6y2VeeH1pyT0MKW4fb_Uc9sAEGAHgtdZvc5WoWA@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3672253204_1498501523"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/BUb5tKP_w0j9GHzrFr3i05I5s3Q>
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 20:20:13 -0000

In the email itself … read till the end …

 

Regards,

Jordi

@jordipalet

 

 

 

El 13/5/20 22:15, "Behcet Sarikaya" <sarikaya2012@gmail.com> escribió:

 

Hi Jordi,

 

On Wed, May 13, 2020 at 3:03 PM JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:

Hi Alissa, all,

 

I’ve read the document and I agree with all the points.

 

I’ve only one comment regarding 2.2.4. I don’t think we can neither should evaluate other countries than the one hosting the meeting. Otherwise, we end up in having problems every time *any* country has issues.

 

I guess all those inputs will belong to the SHMO WG, but just in case..

 

I’ve also read the proposed charter and I agree as well.

 

 

Where is the charter? Is this the one:

67HBuoVCIJOD8cSXAXpB0Bs-SRk

 

 Regards,

Behcet

Regards,

Jordi

@jordipalet

 

 

 

El 13/5/20 19:10, "ietf en nombre de Alissa Cooper" <ietf-bounces@ietf.org en nombre de alissa@cooperw.in> escribió:

 

FYI.. If this topic interests you, please consider joining the discussion on manycouches@ietf.org.

 

Alissa

 

 

Begin forwarded message:

 

From: Alissa Cooper <alissa@cooperw.in>

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

Date: May 13, 2020 at 1:08:01 PM EDT

To: manycouches@ietf.org

 

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), 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 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

 


**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

_______________________________________________
Manycouches mailing list
Manycouches@ietf.org
https://www.ietf.org/mailman/listinfo/manycouches



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.