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

Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 14 May 2020 14:39 UTC

Return-Path: <sarikaya2012@gmail.com>
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 DAD213A0AC7 for <manycouches@ietfa.amsl.com>; Thu, 14 May 2020 07:39:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=gmail.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 qdBSTcuAU0Nv for <manycouches@ietfa.amsl.com>; Thu, 14 May 2020 07:39:26 -0700 (PDT)
Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (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 B44A03A0ABE for <manycouches@ietf.org>; Thu, 14 May 2020 07:39:15 -0700 (PDT)
Received: by mail-yb1-xb2e.google.com with SMTP id f5so1661414ybo.4 for <manycouches@ietf.org>; Thu, 14 May 2020 07:39:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=wIr9pkNSzRck0zvaDVZxG/Zmd9q283e1FUux1YmUUzg=; b=La/0mnMNgYAv41SIq5i/6n1cCDeghZIWThEw0OC3mjWINyvj/T0RGOV6f44vwDbCoe f0FsCkbq3FMiN4aAZPQFbdY0mPEVGfu1vAkBoBhTtGU6PvOodIyoH5JHlbqeQsjX0iT9 +NNjJEyHw+y5J5qUZn65mnaalETTJNJ4pNNBOULHkyFWh/agKjOP4FM6pSngezrbo5qg fmfprq3NO+g2B1kGtsnvVpNv+f0c3eyWOZtjddGHijwLK4Xa2J6M5Qnp4AHk7GUxrKVc Z6Ls9qVWVcggs5Yji1OBEoCHPSefqrFi11sd1r+61S0hMO9P1Gl14ptgZ+hjNh4YT0hH Lk3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=wIr9pkNSzRck0zvaDVZxG/Zmd9q283e1FUux1YmUUzg=; b=BmscpWYq3qYHy8sejDvbgsPCd5Xzp+YYnHHn/a1F2ftgvySUOrjLBcVQttfN7AU1Oe W0f8jDwu9QnmrsDum+8YGc5RW9ozjITymFXstiD6qqLZF8WHypTXF0WtGIhzHeoX/47a sa8TUcfC5scZi7QwChLtNGm+JGbTtwxmYWCmODiEPXj4xIByMHSFI7EEDYw7y135Bswb xYwx5mDVHzBuEDGm4tg2AVaLfl7kk49VFvwf/OF0IpeCo4nwlKFeAcm5LH/m4hTBR6jP f8QJ4t7OA4cb4ry6T5Mhx+Tr9vtgPlwy4RWe22FpJ0Y96oO+e+uZHA8SVslo+gEC9j9z GaSw==
X-Gm-Message-State: AOAM53007I1MPaJY0pTwDD7kqeNGo0WVp6uEhB8cOonX0cz5qYSR4uNI uYKzNvqS3bvzi4+23HXj8SLThl3Mtd59OOKR5J8=
X-Google-Smtp-Source: ABdhPJxLvzwlyRfojHRqNDtkQOnuo4/cPawPvI5nJNX+4V6wMk/8Bex0GHvMOUqw/k+2ERjEDSd6E/oSxX8Hha9bz4Q=
X-Received: by 2002:a25:6007:: with SMTP id u7mr7876118ybb.91.1589467154735; Thu, 14 May 2020 07:39:14 -0700 (PDT)
MIME-Version: 1.0
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> <3E2880B1-2712-4C8B-B7DF-FC35F192133F@consulintel.es>
In-Reply-To: <3E2880B1-2712-4C8B-B7DF-FC35F192133F@consulintel.es>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Thu, 14 May 2020 09:39:03 -0500
Message-ID: <CAC8QAcdDjet9HVBUrJvL9tZConXPCiHwbgdzFnAccZyqJjOMwQ@mail.gmail.com>
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
Cc: manycouches@ietf.org
Content-Type: multipart/alternative; boundary="00000000000023e86105a59ca953"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/Y80MBBeb98a2ON-q8Z1o2H9Jgr8>
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:39:29 -0000

yes, I read the charter.
I like especially this and support it:

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.

Regards,
Behcet

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

> 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
> <https://mailarchive.ietf.org/arch/msg/manycouches/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 <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.
>
> _______________________________________________
> Manycouches mailing list
> Manycouches@ietf.org
> https://www.ietf.org/mailman/listinfo/manycouches
>