IETF Logo Mail Archive

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

Larry Masinter <LMM@acm.org> Wed, 03 June 2020 17:08 UTC

Return-Path: <masinter@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 144D03A0B21 for <manycouches@ietfa.amsl.com>; Wed, 3 Jun 2020 10:08:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level:
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 Iezc3Sog1P8j for <manycouches@ietfa.amsl.com>; Wed, 3 Jun 2020 10:08:44 -0700 (PDT)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (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 D61483A0B1C for <manycouches@ietf.org>; Wed, 3 Jun 2020 10:08:44 -0700 (PDT)
Received: by mail-pg1-x529.google.com with SMTP id r10so2155781pgv.8 for <manycouches@ietf.org>; Wed, 03 Jun 2020 10:08:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:content-language :thread-index; bh=xd7kWMdYWOvhK8/pZUpFI/ankF0EBJxkOOVozRkp8eE=; b=tz5Hr82vT9h9zaxwcqlfHzciMmHjHp3wdFyBVUhnJjIbjYCTrnClNl6chicSeIchR/ j9pGrkWgZ3ECE1r2lh4iWNP1Xy1gXYBEdI6ybQmwAM9uBhIzXKj+925ha1gWBEQAYaEg BStRgcHNOt61mNdXbuigOVKoULYqDnQvJYoxZRMbOJyLjIvvoBFp40jkV79zI2ZRGY6j o/yjdEyVrApkGuDDfRKoi1iTgvFuRwxIVyfRFhUYyT5uk165fgxQXY1pipNOB8x11UJd D4vziOpOoAw6wNxU3gHRSW5aSujWue2N4IxWY9G91hE2cAuT381/mvWzWB5OOOjRxcX9 HVxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding :content-language:thread-index; bh=xd7kWMdYWOvhK8/pZUpFI/ankF0EBJxkOOVozRkp8eE=; b=j47D54MUg2NSxUQ5Xq4OT9IEav2Vyc4FbFTwk0Ilql1zzqE2Amaz0e4IU2WOctbCam 7YObA8Qe1GIC7Bj38ndKY0PzeSmIFlmD4u7OGS7HvP9dQ0qcJavZzkRItHtLkw6ussDe l8dSO/3jnqd779QpkjmA5qfU/pRKQ/I3oCeDeXRiCU41qaGVOSfQ/5czEQy+u8wRpZPy 5vY3dsmw3BOVMx3iZcLm3jGtMzn5VHouy4EXYKxp+nEGpExNkSdEb92VwBfLa6H/5qto Pi+oB2rx5h+xvaI54iWRYoE4ixUTJbfYTwdgCE0fYQv+eC3W+ebxaWPBrRvUTSO0gIeg 5k2Q==
X-Gm-Message-State: AOAM53189Ps5IvmQMpgEuhizIJkGehbpdGKC2sjNIeZjErbhoTKXEJD9 ifqe8wf0MICF5/gHW7bJ3LNuOT3T
X-Google-Smtp-Source: ABdhPJxSeUVdfkgiIOU1Zx7BZ8xZO5UOGhsCJv/MfxHb5ZOAp0z9S7d2E1xOPwBLKeYN9d0HZ5h3eQ==
X-Received: by 2002:a17:90a:8a98:: with SMTP id x24mr858666pjn.103.1591204124119; Wed, 03 Jun 2020 10:08:44 -0700 (PDT)
Received: from TVPC (c-67-169-101-78.hsd1.ca.comcast.net. [67.169.101.78]) by smtp.gmail.com with ESMTPSA id m20sm2543262pfk.52.2020.06.03.10.08.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jun 2020 10:08:43 -0700 (PDT)
Sender: Larry Masinter <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: 'Alissa Cooper' <alissa@cooperw.in>, 'Michael Richardson' <mcr+ietf@sandelman.ca>
Cc: manycouches@ietf.org
References: <E103897C-F9D9-4ED3-AB45-FD2967D7F49E@cooperw.in> <53DD003D-4464-4F17-92BB-C9B1D7ACF09D@cooperw.in> <82259599-7678-4C5F-A6B4-3E2187645301@cooperw.in> <2251.1591146507@localhost> <4D474B9A-EBC2-409C-8155-455C9016274A@cooperw.in>
In-Reply-To: <4D474B9A-EBC2-409C-8155-455C9016274A@cooperw.in>
Date: Wed, 03 Jun 2020 10:08:41 -0700
Message-ID: <00f301d639c9$a28ede10$e7ac9a30$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQKez4DGdc63EdhFzVUjnSprTVSA8AGSH2/qAfcqm+8B714PkgJAcZYLpvgMzOA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/9KAw3oafPHIcfh7VgO4ZLaFej3E>
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, 03 Jun 2020 17:08:46 -0000

Some thoughts on the SHMO charter

I'd like to see the working group consider

   https://www.w3.org/Guide/meetings/continuity.html

which addresses many of the issues, and
https://www.w3.org/blog/2020/05/virtual-advisory-committee-meeting-and-may-2020-w3c-strategic-highlights/

which described some things that might be useful for plenary sessions, which included
pre-recorded presentations (including transcripts, captions, and translations into 3 languages)
and two virtual Q&A sessions with live captioning and simultaneous translation.

Some of these ideas might increase the cost but also justify the benefits of paying to participate.

>From their participants feedback, or making this a best practice:

    “I suggest W3C management exchange opinions with other standard bodies to make a best practice about big virtual meetings.”

I suggest that SHMO consider the possibility of establishing a BCP (perhaps jointly 
with W3C, who seem to be ahead of the IETF curve on some issues).

v2.23.0 | Report a Bug | By Email