Re: mic lines not working as well as they used to...

Chris Inacio <inacio@cert.org> Wed, 23 November 2022 15:32 UTC

Return-Path: <inacio@cert.org>
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 C028BC14F73A for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 07:32:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d2asoWziYG2I for <wgchairs@ietfa.amsl.com>; Wed, 23 Nov 2022 07:32:38 -0800 (PST)
Received: from USG02-CY1-obe.outbound.protection.office365.us (mail-cy1usg02on0711.outbound.protection.office365.us [IPv6:2001:489a:2202:d::711]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54AE5C14CEE3 for <wgchairs@ietf.org>; Wed, 23 Nov 2022 07:32:38 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector5401; d=microsoft.com; cv=none; b=eD1s5m4gezqc41if8+60o7kujmL9umKJgLNUd9vvTCtcy5U0WlY8ZaaO7c1o/eycEeDiwJQj0BwL7RS2hz8n6VNc+t+raBbemhPwZrJ9hvAS8Nf93uJpU/oybeiAIIyJROTpOTe1+L7bKRzmAA09E2jWqrdvOfEGcc88a83NSEiOGE7BASf+SGG+YAPj0SdnpyW7pTAetf6hBJFWCx5kulUK43/1ob1lbe5QS3b4xSGvQjObsLJvzskgklldSGKNhSv34VBC5S5nzj7svgGEf9nYpgbihOePo1RLGpy/xlN+OdsdbNzya8NqqOghrnnl5CeaH0sG9TU56OcmTN6npg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector5401; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=5qiuhycKoBmVc5k0in51qabL0kdztVfFqBIqdRRo600=; b=RasmOWg/rwstZLTjwrfI6+0PDuNhecrJRGXl8NQTA2N2B4ALrktdJ1lRlYYEt6d4rs0a0bGk3A9ELGzaVfoOAq0JZn8fa71WP8y+k3MqPX1BxBo9h6/Ar4hA9+uc5SK6ocTSsqNJUUOSFDMY/y1VHNIOPOnD74S0Kuaw+GwWr4BLVgnZv1/ZpujznlZSmmecPK9oi4jGApuvsb9SbA6I5NGGKx5cU9hSISzP/UiBZ+WDiEStAOk2IvSIkGzr7zgaXma04XHg6blh0aIlJPw6ES5OU5f+qF5DU/Ld6ER9F4qi8iZUKcxbSBFa4+j3vYcakc0gdNGo63oqghGLL9STxw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cert.org; dmarc=pass action=none header.from=cert.org; dkim=pass header.d=cert.org; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5qiuhycKoBmVc5k0in51qabL0kdztVfFqBIqdRRo600=; b=X33ns/hVvB3xrs6fKA9Mut61amRXMKICBuGATXxS3y10FJLtY8I+aDLIINpKod7i8BqT7tXx0N/7+FiSSk2WImm0Rqn20D3gxYyQSlWro/5pvcFzzw5T4QD/l8CHcwk3xThCTEnuRKwhJX5PbzDQ5nDgr140iBXMd3SdJZhG2NA=
Received: from SA1P110MB1373.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:192::12) by SA1P110MB1502.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:196::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5834.15; Wed, 23 Nov 2022 15:32:34 +0000
Received: from SA1P110MB1373.NAMP110.PROD.OUTLOOK.COM ([fe80::b03d:b825:30a2:4a7a]) by SA1P110MB1373.NAMP110.PROD.OUTLOOK.COM ([fe80::b03d:b825:30a2:4a7a%5]) with mapi id 15.20.5834.015; Wed, 23 Nov 2022 15:32:34 +0000
From: Chris Inacio <inacio@cert.org>
To: Aaron Parecki <aaron=40parecki.com@dmarc.ietf.org>, Working Group Chairs <wgchairs@ietf.org>
Subject: Re: mic lines not working as well as they used to...
Thread-Topic: mic lines not working as well as they used to...
Thread-Index: AQHY/0ysxBMotMYfPkSp7fTFY06UaK5MnDSAgAADoACAAADOeQ==
Date: Wed, 23 Nov 2022 15:32:34 +0000
Message-ID: <SA1P110MB1373E7BA1874ACDFFF6772C6AD0C9@SA1P110MB1373.NAMP110.PROD.OUTLOOK.COM>
References: <9cb6c587-f964-966e-a47d-f97a2aff474a@cs.tcd.ie> <bea920d0-feba-2007-67b3-6af1b485d322@joelhalpern.com> <CAGBSGjo9460n9_VXRtzcdrb6Yx_N5e3GZCuPOwjygpYtbozzHw@mail.gmail.com>
In-Reply-To: <CAGBSGjo9460n9_VXRtzcdrb6Yx_N5e3GZCuPOwjygpYtbozzHw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=cert.org;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: SA1P110MB1373:EE_|SA1P110MB1502:EE_
x-ms-office365-filtering-correlation-id: e0a70c0a-b823-4fce-6408-08dacd67f16c
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: amDKAH52MFI4dzee/WdXLPIpndwTAGWCWk3fs8pi4Yu3hgkwdbzp0GKN25WHBBk5/3vb9TPDW5QgxQxgFyDqSuuQiLAqvbgqCjxy1HTIWRFM/Y8dMHRo1151dF+BqcCfSt/kESjhnEW1vIVS3u7xEymaHOuwB9hns/iK6bQItu0P24d4eAOBcnIwo6/wsSDEq5qebPCDr7b2aJguns3wJ5O/o/bMHtqCyBkis4jMy2+R/Aiwc0I9S9jjX4h4y4F/bg2tqCKFfv9yYyD/0zEWmxF2ZFHjq79juebEVoiQ3bNKQ4McNULeSAx+QgIv38YL/k11udr2F5HT3/hH8cmiWSLmVSJUAlsYNQ287ziQv/wUnYBdKw69OWISQsMQ7aVEEP376PLKTLpUW51IIDFtfSICpMToSelfy8DpZY7uyBw9HF6SChCeUoT1Bg1sljbRupDKJkgn6IyQAPW7UqI/9qhUj/TApyDgie2CPkxJ2JG7AVl1NnkU1CAV6Id/9Hh9TPfJLqq7uHqf2l/bfNiMZPfzXJ6honPxvUlyRD5Mqp6kx7G1uckT+lfaUZkU6k7+
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:SA1P110MB1373.NAMP110.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(13230022)(366004)(136003)(396003)(39830400003)(451199015)(33656002)(7696005)(5660300002)(186003)(9686003)(6506007)(110136005)(76116006)(66556008)(53546011)(8676002)(64756008)(66476007)(66946007)(41300700001)(8936002)(52536014)(99936003)(122000001)(38070700005)(82960400001)(83380400001)(2906002)(55016003)(66446008)(86362001)(38100700002)(41320700001)(508600001)(71200400001)(579004); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: Tz0ORZw7VQDtN/mvZsDmaBhf6fIBWT8BPy7+QHOYaq3v0QZgKMC5RVBX8ThHQsdEguTp3kcSnCtvUYr7nH0fkOwksd2zOX6yhg5ucusVSf4MiaTZxLXs3mx1NeHkFUO4YLRXypYaJSvTV/fK4QJIWibWhxZp31UNuuqVvgdcwu7Y8rQEWIBd2AolANgquZTAYFbFVqj/3RgXm6aEPs3bdtKERLV9kGiSC7W2ckqmIoAWR3G1uc1z/yBGceuOIYSX6lvu4HHUJlas40utHACmav6MHuro8Oe+IUy+c8HWndzp+utIz0k1/9ClIn4nJ5Vrj3eqTEF2E+8UnXzeKJ3c3dix73LysJfIRQDl6icny4LgDKWGjDgnjA3DhDpwCDYLvTQdzqR/UqgGUWFU4BxTYxHGg5QtVzkZEuA9ore3vDu7XUhcJjaTsdd+TcAziNPjYs/gV4fgy/OHA5rri/GqkV6MUX8mFFdaX+EI/Ml2THE=
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha256"; boundary="_20C5C456-01DE-4043-8789-D5206AAA8F46_"
MIME-Version: 1.0
X-OriginatorOrg: cert.org
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SA1P110MB1373.NAMP110.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: e0a70c0a-b823-4fce-6408-08dacd67f16c
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Nov 2022 15:32:34.1928 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 95a9dce2-04f2-4043-995d-1ec3861911c6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SA1P110MB1502
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/XUsDnGZoBpw40o_khu7vdFvGszU>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.39
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, 23 Nov 2022 15:32:42 -0000

I don’t have anything constructive for Stephen’s first point (fewer mic participants), but on his second point:
 
My experience is that WGs that bend the rules a bit work best – but this is to the detriment of remote participants, IMO.  When the chair allowed back and forth to happen between the presenter and possibly multiple parties at the mic, I thought the best discussion happened – but this disadvantaged the remote participants slightly.  After a back-and-forth, normal orderly meet echo queueing was followed.  What I haven’t seen work as well (although I have seen it work some) is back-and-forth with a remote participant involved.  (But maybe Barnes was a chair but participating as an individual contributor in that interaction…)
 
Stephen, what I understood you to express was that discussion of a topic/issue/idea is stunted because the lack of organic back-and-forth at the mic.  (Your second point.) If you meant something different or more, please correct my understanding.
 
Chris
 
From: WGChairs <wgchairs-bounces@ietf.org> on behalf of Aaron Parecki <aaron=40parecki.com@dmarc.ietf.org>
Date: Wednesday, November 23, 2022 at 10:21 AM
To: Working Group Chairs <wgchairs@ietf.org>
Subject: Re: mic lines not working as well as they used to...

As an in-person participant, I found it quite straightforward to add myself to the queue with meetecho lite, and I appreciate the unified in-room and virtual queue. I would not want to change that. I also appreciated being able to remain seated until I was called up.

 

As a new chair, I appreciated having participants' names visible so that I can more quickly learn names of people in the group.

 

If anything, what's missing is a way to highlight on the screen the name of the person speaking at the microphone, similar to how you can always see the name of the remote person speaking. (In practice, I noticed a mix of people/chairs removing the person from the queue when they got to the mic, so their name was no longer visible while speaking.)

 

Aaron

 


 

 
On Wed, Nov 23, 2022 at 7:08 AM Joel Halpern <jmh@joelhalpern.com> wrote:


I don't think we can stop requiring the use of the queue, as otherwise 
including remote participants becomes very difficult.

Having said that, maybe there are other changes that can be made to 
address the important issue that we do want discussion of topics at the 
mike.  That is generally why we are having the meeting sessions.

At one point, the plenary used a dual-queue approach where comments on 
the current topic could come forward before folks who wanted to raise 
another issue.  I don't know quite how to represent that with the 
tooling, or how to make it timely enough to be effective, but I wonder 
if something like that could be helpful?

Yours,

Joel

On 11/23/2022 10:02 AM, Stephen Farrell wrote:
>
> Hiya,
>
> I think we're making a bit of a mistake in requiring people
> who are in the room at meetings to join the meetecho queue
> before they join the physical mic line. It's not an end of
> the world thing, but I think it is a bit damaging.
>
> The results of what we've done this year seem to me to be
> that:
>
> - fewer people join mic lines overall
> - there's almost no real discussion of topics raised
>   at the mic as there used be
>
> I realise that being fair to remote participants needs to
> be a hard requirement, but I think we've gone a bit too far
> and ought back off some, e.g. to where we encourage but
> don't require people (whether remote or in-person) to join
> the meetecho queue. I think we ought also encourage more
> discussion at the mic (for both remote and in-person folks)
> and not be so fixated on the order in which people appeared
> in the meetecho queue. That requires a bit more chairing
> but that's why we're supposedly at the front of the room.
>
> But, maybe others like the current rigid setup or haven't
> found the lack of mic-line discussion a problem?
>
> Cheers,
> S.