IETF Logo Mail Archive

Re: DISPATCH Virtual Meeting

Ben Campbell <ben@nostrum.com> Wed, 25 March 2020 01:08 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 858C43A0986; Tue, 24 Mar 2020 18:08:27 -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_TEMPERROR=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 zjwBmCjwoUtN; Tue, 24 Mar 2020 18:08:17 -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 C824C3A0989; Tue, 24 Mar 2020 18:08:10 -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 02P18218079996 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 24 Mar 2020 20:08:04 -0500 (CDT) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1585098485; bh=K6I50yAXHSQIRsQYlEzKOCMoy6ScSC4GMnIqwiRa2XM=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=To31hsIvx4T7enkBg4GF54DDQnGqsRuJVEoY+NN24qDcmCOwTztkKDYCofEo7OddS /luBrMT7TmUlukRCgMDCFICEqT9ocvlwdsemR+CqdeQbQFEM0tgfvT+cU8bLWmddI4 yyCzT4ZykK2yL6dUWWAc3vEQZ2iwz/Gm+Upx31pc=
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: <F026A8A5-D6DB-4639-815F-AB2E96D42AE2@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4216A129-FF2B-4DDB-994F-647F8060FF78"; 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 20:07:54 -0500
In-Reply-To: <26960.1585088537@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> <FE35AEFC-F92F-48ED-B517-883EE8BD2944@nostrum.com> <26960.1585088537@localhost>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/57f8_mk57ABKA3YlRzqxtLhLVrI>
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: Wed, 25 Mar 2020 01:08:46 -0000


> On Mar 24, 2020, at 5:22 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Ben Campbell <ben@nostrum.com> wrote:
>>> The chair/host role can mute people.
> 
>> The chairs were not the WebEx host. The secretariat can and did mute people.
> 
> Why weren't the chairs the webex host?
> I guess there can only be one host?

That’s the way it was set up for us. I have no idea if there can be multiple hosts. I’m pretty sure a host can transfer the host role to someone else. But the chairs had enough on their hands chairing the meeting, without having to deal with the technical aspects of keeping the conference going. I think having the secretariat, or someone else, managing the bridge is the right way to do it; much like we have the MeetEcho staff manage remote participation for f2f meetings.

> 
>>> 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.
> 
> I think that everyone should use the webrtc version if they can.

I know the local client usually works from my house. I have not found the WebRTC client as reliable. As chairs, our first concern was to try to make the meeting run smoothly.


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

v2.23.0 | Report a Bug | By Email