Re: DISPATCH Virtual Meeting

Ben Campbell <ben@nostrum.com> Tue, 24 March 2020 18:22 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 855BB3A0D59; Tue, 24 Mar 2020 11:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.404
X-Spam-Level:
X-Spam-Status: No, score=-1.404 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.274, MAY_BE_FORGED=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 y6t1ITXS3mlG; Tue, 24 Mar 2020 11:22:03 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 87BBE3A0CC5; Tue, 24 Mar 2020 11:22:03 -0700 (PDT)
Received: from [192.168.127.239] (mta-70-120-123-175.stx.rr.com [70.120.123.175] (may be forged)) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 02OILxEX007365 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 24 Mar 2020 13:22:01 -0500 (CDT) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1585074121; bh=UgGwFKeY2T0aDm+Q/BHjn1eLwRwpGbeanzipgXL1WVI=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=nSmw5M2ao836I7Vt46w5UHcXGfb0XpwgYVdOm/nwZKhqHlW+NjQhdgGO+X7wYTt3q 3Bf0XKJGQVbdVCfubEvZraoWkNXy6IdR8mSbucIMJrqsUtyHSRGEjVx5WbxlIrcInD eb9YhA8lQn/CQ1Q4pKcKQpnh5M+GtugkgB+SV7kQ=
X-Authentication-Warning: raven.nostrum.com: Host mta-70-120-123-175.stx.rr.com [70.120.123.175] (may be forged) claimed to be [192.168.127.239]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <FE35AEFC-F92F-48ED-B517-883EE8BD2944@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_91266DCD-590A-479E-ADD2-562F4A99962D"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Subject: Re: DISPATCH Virtual Meeting
Date: Tue, 24 Mar 2020 13:21:52 -0500
In-Reply-To: <31012.1585073861@localhost>
Cc: wgchairs@ietf.org, Patrick McManus <patrick.ducksong@gmail.com>, manycouches@ietf.org
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <6CF30D21-30B8-41B2-9DBD-12276A7349B4@nostrum.com> <31012.1585073861@localhost>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/UZwJQOJSUG6oM-yaHHscw2uJ4eA>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Mar 2020 18:22:06 -0000


> On Mar 24, 2020, at 1:17 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Ben Campbell <ben@nostrum.com> wrote:
>> There was a lot of interesting side-discussion in the jabber chat—to
>> the point that I wonder if we can encourage more of it to make it into
>> the webex. I know that gets logged, and people can review it, but I
>> doubt it will be captured in institutional memory as well as the
>> minuted stuff.
> 
> txauth restricted *webex* chat to mic line.
> So it would be better if we could be consistent across WGs in how we use it.
> And the webex chat is really hard to use, has no memory after you reconnect,
> and jumps around everytime someone writes to it.

Sorry, I did not mean the webex chat. I meant “take it to the mike” :-)


> 
>> We did get the occasional problem when a person forgot to mute. Overall
>> it wasn’t bad. We got an occasional side coversation, but the worst was
>> when someone has the session running on multiple devices with live
>> mikes. (The feedback from that is very…distinctive).
> 
> The chair/host role can mute people.

The chairs were not the WebEx host. The secretariat can and did mute people.

> 
> I'm surprised you had the enter/exit stuff turned on.
> I wouldn't have done that for any big group, or any situation where people
> might have to reconnect.

… again, not a chair decision.

> 
> Did you rely on the webrtc version?

No, I used the MacOS local client.

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