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

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 03 June 2020 17:32 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 AA06D3A0C5C for <manycouches@ietfa.amsl.com>; Wed, 3 Jun 2020 10:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 3SY01J40Qo_G for <manycouches@ietfa.amsl.com>; Wed, 3 Jun 2020 10:32:27 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E9153A0C55 for <manycouches@ietf.org>; Wed, 3 Jun 2020 10:32:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 64A5238A32; Wed, 3 Jun 2020 13:30:02 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 7yBM9QMmJ93J; Wed, 3 Jun 2020 13:30:01 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 52144389F6; Wed, 3 Jun 2020 13:30:01 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 40D613F; Wed, 3 Jun 2020 13:32:24 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Larry Masinter <LMM@acm.org>, manycouches@ietf.org
In-Reply-To: <00f301d639c9$a28ede10$e7ac9a30$@acm.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> <00f301d639c9$a28ede10$e7ac9a30$@acm.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 03 Jun 2020 13:32:24 -0400
Message-ID: <6999.1591205544@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/bXKrcnnKttUD5Nj1I9SGGbz0Yxg>
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:32:31 -0000

Larry Masinter <LMM@acm.org> wrote:
    > 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).

I think that working with W3C/coordinating with W3C is a good thing.

Are these two resources actual W3C working groups, or are they just
advice/wiki-best-practice-guidelines?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-