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

Mike Bishop <mbishop@evequefou.be> Thu, 14 May 2020 14:24 UTC

Return-Path: <mbishop@evequefou.be>
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 5E5DE3A0B19 for <manycouches@ietfa.amsl.com>; Thu, 14 May 2020 07:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=evequefou.onmicrosoft.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 IrVoSFqicMLh for <manycouches@ietfa.amsl.com>; Thu, 14 May 2020 07:24:49 -0700 (PDT)
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12on2117.outbound.protection.outlook.com [40.107.237.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28CA33A0B16 for <manycouches@ietf.org>; Thu, 14 May 2020 07:24:48 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hTKRKbXMMgHTJHbjSvC/Uv/37b1tyjMtcGClb/GITYnLovZeoY1iiaOX3uCWTbuni1jvbxUbyYxfU2I5ycRBa0faaY5zh0x1qpkDbM+rkp9v+iUvOfzqMJ2b11HPinT4Dn0lgkTZQEenTGvsiwzmU+QuJnyTcl8tQ5W4r7UiV0PMZoTmqI+20O8WkPj/ngAmLBQWMom5w4/HGi0saOr9o+vw6ADspump0PTFgoFnKlrZpkcBOqTMc1RPGaC6ejq1tGkMgPVeWpnWwCDcTZE9ixbzwCeZogwsdXeZf4G8VMfc/m2cVZ5OFGY2xJkWlGKlBayQdFyRb83SwJddk4acAA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rLWttZdZaEFxFqwnpOmJfKxZAI6GF6LMoqMJIhTbUxI=; b=KVD0LI6fGy9DysxscYktLgXu5UTNXF4RoVmCttGP0yQCeHXraK2Gd46o9KQnht4CQqxPl+M4X8g7EYUxqccg+O8ZCAxoAYPSW6ZOLLUEHOqVfXYRGTLbuRiRNxZ4qLNcdexwLuQ26bZp0LSNsG83sICW2fYPF9VekTv42DwPaiQm+PTnEZReR4yUb7t6Lj6tgx8bawkKM2Fzze7p5eNOX5Gy9Tw6o3mo1tZoTS2nqCmd8ki4DoSqPqE5d2t5ua8PtYDl2Hj6aidzGDTO/rjIXJRHVVwW/tt4z5ewesEiiZkNnrffYZXTPHX31BooLARYOfdHiZkVMWUo1IwpuXOv2w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=evequefou.be; dmarc=pass action=none header.from=evequefou.be; dkim=pass header.d=evequefou.be; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector2-evequefou-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rLWttZdZaEFxFqwnpOmJfKxZAI6GF6LMoqMJIhTbUxI=; b=GtAvDUQ6Zs85E1dqwT1hrfujjV1q4II/88ZkUvo8HCPniPf8G5UZM98mVTPDI7ouVmygRjVwraml2suV/hjIxCuaq6+U+JziQPnxfMSWur1l9VNNbGHbVbpftFeB2jxUZl/BVYpD6r2lvnrf/12alIHD15bAVDrv4+re5OD8CmE=
Received: from CH2PR22MB2086.namprd22.prod.outlook.com (2603:10b6:610:8c::8) by CH2PR22MB1799.namprd22.prod.outlook.com (2603:10b6:610:89::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3000.24; Thu, 14 May 2020 14:24:46 +0000
Received: from CH2PR22MB2086.namprd22.prod.outlook.com ([fe80::5d05:3b25:6510:2a3d]) by CH2PR22MB2086.namprd22.prod.outlook.com ([fe80::5d05:3b25:6510:2a3d%3]) with mapi id 15.20.3000.022; Thu, 14 May 2020 14:24:46 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, "manycouches@ietf.org" <manycouches@ietf.org>
Thread-Topic: [Manycouches] Stay Home Meet Online (SHMO) draft and proposed WG
Thread-Index: AQHWKUkYN+b4+rBsh06ke+pEDiNqvaimcHgugAABoiCAABgrgIABFypQ
Date: Thu, 14 May 2020 14:24:46 +0000
Message-ID: <CH2PR22MB20864C324652DCDDBE3DBE7ADABC0@CH2PR22MB2086.namprd22.prod.outlook.com>
References: <E103897C-F9D9-4ED3-AB45-FD2967D7F49E@cooperw.in> <72840D63-E994-454F-83CD-42D2D0924944@cooperw.in> <6C82EB0A-47D1-4E1C-8CD6-EB13351AB294@consulintel.es> <CH2PR22MB208644C0B499C748DB34F216DABF0@CH2PR22MB2086.namprd22.prod.outlook.com> <A5679DA7-4B0D-4C7F-A16C-D5F9428BC76F@consulintel.es>
In-Reply-To: <A5679DA7-4B0D-4C7F-A16C-D5F9428BC76F@consulintel.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=evequefou.be;
x-originating-ip: [2600:2b00:9309:6a01:bc29:e688:7d63:652e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3949b7d4-a296-4b82-2bbb-08d7f8128d96
x-ms-traffictypediagnostic: CH2PR22MB1799:
x-microsoft-antispam-prvs: <CH2PR22MB1799BE5A5BF57016B071A1B9DABC0@CH2PR22MB1799.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:5797;
x-forefront-prvs: 040359335D
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: zX48QmNpqUBvw7U4IHgqYxwCkidPe6SN9yXjdlmfrE6vERG8fWAXF/AOQk3313kmIW+YdaHvcSNtP5ELIbsmvXDcNWpcfKqEaeHSqPQCZ1R8lL39lxAiEwzv7JA7sbICA24BEByXoeT2GCH2c6xcWx3AaB7neDeU/vn6U2xErmoOj2xcQRN5sT1GMDQx2N6Cq0t32rH/fhOedKR2lHo3hdHHdnJztKNHC1l9OMqbxqi/li3nVaRq3AGnTcZD3BxbHGQA/D0pH4JG6t7Gne0k8hF+Zosa0AIqfzMWjZ7xcQPWXJnl03MC1e0hNFmWqo2uHoDqlwvUHHnArsdeC1GBfX7Zr7vMMhpAl2xdm4p6rHkIi1LHWp11RxW5m04/7vGjzRpuWPLGWHRAI4NktQgh6/v7G/3emW60rQ4ydQz+zY8CwDex4XLJ4CVL2KQGhYK5etct5JQA5bIKgjR5mD7rpYpzuM1GUZMBuDpWa12glBJtblUaLth9zpcaF549+aE+UHFqlIs5h8LwtMpA8AEEZw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CH2PR22MB2086.namprd22.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(136003)(396003)(376002)(346002)(366004)(39830400003)(71200400001)(86362001)(66476007)(64756008)(66446008)(66556008)(508600001)(66946007)(2906002)(55016002)(66574014)(52536014)(166002)(30864003)(966005)(7696005)(9686003)(76116006)(110136005)(8676002)(316002)(8936002)(33656002)(53546011)(6506007)(186003)(5660300002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: wJ6wOZamffqQ81wawyTLRWAdtCBU2pTJHD2h7dLc/Z0Q8LQ0OOOnneRvZavt14ivtLElYULHdLnX3N5HsXsYwkAigtqqMvWpgmoUFm47NSIXFY2PaGfNNQECyJyWSNkA4fCtTiM+w/Yh1suk0d9Uxaif7HDAa8wM7G7Aj2vT1WgV0Sbjfcvnoah9WaPAB88o5J0LLY0zxkCfsCO+Jn3A3WoSwqRZYoF3+fHz6gIzPVN+sf2Zqrz4gsC7c+TR3z6QjOiT9SvEhzeOx3Yp6Db+VFiTM/z4JvowfDLVKalqq2orJKHBpjkNUV1yJHdiNWSXDvCxQXErVN1w6BReXPhbxAJsphYs/CCiuyX2BfXAnEAZ//cybTbjdZCDX11LPfOYly49l+UWuxPnUHinpr/hoFYfdsdMZ/uNnMjnXm0B30R43i/Kigx6ad/51s30HldA2FamVjyT+ScpDOmcXICNcKn+sfhPYwvU2sIYAuJIowVSzEvorH3M+eC7J30mN7rnVHu932LWYiMIP0Mjvr0xlz8d6SCh+3XK8/x9lyLezLDQPSaCRQZERayl/BXpJnfH
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR22MB20864C324652DCDDBE3DBE7ADABC0CH2PR22MB2086namp_"
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 3949b7d4-a296-4b82-2bbb-08d7f8128d96
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 May 2020 14:24:46.2274 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: nXSoRXM8F9L0dEVQP5VeThA0MD3k3Ib66lTyhdtyjYgzWhVC77KAf3IVmK8NOeTuRCKX7iEM0SkGMwUg+2gznw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR22MB1799
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/o67ClX3jKW3BA95hER4gqdJdGFQ>
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 14:24:52 -0000

None of those scenarios are any different with these considerations.  I don’t see any technical barrier to a country criminalizing participation in the IETF, beyond hopefully that country having overriding legal principles which would make that difficult.  Nor is there any barrier to a company refusing to fund IETF participation (many do) or penalizing employees for participating on their own time and at their own expense.  The only possible counter-measure to that is the value which the IETF provides to the Internet.

Likewise, the over-representation of certain countries is a known issue in the IETF independent of this discussion.  Projects to increase participation from the rest of the world seem to be in active development, and they should continue to be.

The questions you raise about what circumstances would justify cancellation versus continuing with fewer attendees seem squarely within the proposed WG’s remit to issue guidance on, and I think wars and other disruptions to free travel probably fall within the set of circumstances that could justify a cancellation.

From: Manycouches <manycouches-bounces@ietf.org> On Behalf Of JORDI PALET MARTINEZ
Sent: Wednesday, May 13, 2020 5:35 PM
To: manycouches@ietf.org
Subject: Re: [Manycouches] Stay Home Meet Online (SHMO) draft and proposed WG

But this is a transversal problem …

This can be used as a way to blackmail IETF.

What happens if a big country decides to ban it citizens participating IETF ?

What happens if a big company disagree with something about a document and decides to ban its employees from participating IETF ?

What if that happens because that country decided to manage the pandemic (in this case, just an example), in a way which is different to the rest of the world. Should the *rest* of the participants pay for that? Will the IETF do the same if instead of a big country is a small one? Is not that a discrimination?

Should we agree that if those participants, even if they are from a big country, or a big company, can still participate remotely, the meeting should progress because the circumstances aren’t “venue selection” but “supervening reasons” ?

Is the cost of keeping the meeting even with less participants less than the cost of cancellation, not only for the IETF itself but also for the *rest of the participants*?

Is the problem that many co-chairs, IESG members, or whatever, are from the same company or country? This show us a very weak point! In many other organizations you need to share the balance among different countries or organization or a mix of that, to ensure that this will not become a problem.

I think there are many factors to consider, and I don’t think that all the venue selection criteria can be applied the same for a “supervening cancelation” (I’m not sure if this is the correct way to say in english, but probably is well understood).

Furthermore, if a big country starts a war with another country, and it last longer than our normal contactual cycle for venues, we may need to change the rules if the big country participants can’t come to the meetings, otherwise NONE of the venues will fit! It looks an irrealistic situation? Yes, right, how many people had considered that the Covid-19 situation can happen?

Do you remember when I was suggesting all this possible situations and the need for insurance, etc., in 2006 and even someone was almost calling me crazy?

https://www.ietf.org/archive/id/draft-palet-ietf-meeting-venue-selection-criteria-04.txt

Time demonstrated that I was not so wrong! I was just trying to look for the worst situations.

Regards,
Jordi
@jordipalet



El 13/5/20 23:19, "Manycouches en nombre de Mike Bishop" <manycouches-bounces@ietf.org<mailto:manycouches-bounces@ietf.org> en nombre de mbishop@evequefou.be<mailto:mbishop@evequefou.be>> escribió:

I disagree.  The overarching question is whether there exist factors which will cause a substantial fraction of otherwise-probable attendees not to attend..  If all attendees from a given country knew that international travel would require quarantine upon their return home, that affects their decision whether to attend.

Now, the feasibility of evaluating every country is questionable.  But countries from which a substantial portions of in-person attendees have come in the past seems like a tractable evaluation.

I like the proposed charter.  My main hesitation is that, just as we’ve experimented with various schedule layouts over the last several in-person IETF meetings, I suspect that online meeting schedules will also be the subject of ongoing experimentation.  I’m dubious that BCPs on those topics will remain “current” for very long or that we’ll be able to make informed decisions until we have several of these under our belt.

From: Manycouches <manycouches-bounces@ietf.org<mailto:manycouches-bounces@ietf.org>> On Behalf Of JORDI PALET MARTINEZ
Sent: Wednesday, May 13, 2020 4:01 PM
To: manycouches@ietf.org<mailto:manycouches@ietf.org>
Subject: Re: [Manycouches] Stay Home Meet Online (SHMO) draft and proposed WG

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.

Regards,
Jordi
@jordipalet



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

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

Alissa


Begin forwarded message:

From: Alissa Cooper <alissa@cooperw.in<mailto: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<mailto: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<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<mailto: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<mailto: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.