AW: [Team] Follow up on disruptive person during IETF 119

N.Leymann@telekom.de Fri, 22 March 2024 02:29 UTC

Return-Path: <N.Leymann@telekom.de>
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 2180CC14F698 for <wgchairs@ietfa.amsl.com>; Thu, 21 Mar 2024 19:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.102
X-Spam-Level:
X-Spam-Status: No, score=-7.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (2048-bit key) header.d=telekom.de
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 5GFNWcun-wnF for <wgchairs@ietfa.amsl.com>; Thu, 21 Mar 2024 19:29:38 -0700 (PDT)
Received: from mailout21.telekom.de (mailout21.telekom.de [194.25.225.215]) (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 1D939C14F69B for <wgchairs@ietf.org>; Thu, 21 Mar 2024 19:29:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1711074578; x=1742610578; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Ib5Ex7YSfN8vvyY2kAcloxsMAlfzqlFmmQH39TIUCN0=; b=Lifw9EmWWJ2TuyRTsHi5cBZaHdDdYudEmgDe+Bxr452SJWKjkwBWmDqd leuKzi4m6gsdQE1hPuHfyElEiLu0W1/j8UC04jiFyRefBSxRUxNTJh3jM fdbcDkMdgaNPvjfXuHlfkGuRqWfyDGVK79bUggJUgrpnh6bfH+Dm7L4Wd bvBNpejSAWiJ9ffcoQXhfuvVPJ7pVdx9TSKXwnqI35nHGa/x95uTFHXF2 glRGyE+YdUuk6IFoV+wWPlZgNtsRwJ0/inPISoT7QfDZe1aARgAICC0ro AuWe1iUGq2WujZMm/nzv4hJ+FdN19aGOLgdgHmUYs61edGjD7sKkYSrdb A==;
Received: from qdezc2.de.t-internal.com ([10.171.255.37]) by MAILOUT21.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 22 Mar 2024 03:29:33 +0100
IronPort-SDR: 65fced0c_S7u9FSrOqlzB2TZ7ZmaSHv3wJlppc1UwBTUvPw0k1xghOn3 Khf5MYo8qV5YULM1xpY9PlT8YVHM7nRIyxQ0XlA==
X-IronPort-AV: E=Sophos;i="6.07,144,1708383600"; d="scan'208,217";a="963251332"
X-MGA-submission: MDFeTtSV4xAaNHsn9KzzRitMlOIRjLKxA1SI6XrVIAL+O8YxmxLX5Wxlpt7na/hs0vxEqIT35IBdCj/iqxOlRIfNLFTmdXRK4DxDtdB1xVZcgaU3ZmQ7sxjv3h5VX5vVWYzqQ0H6P6KJCr7Km0Jt+gm63Ligz4UMACiP8wvUQE/eWw==
Received: from he104281.emea1.cds.t-internal.com ([10.169.119.195]) by qde0ps.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 22 Mar 2024 03:29:32 +0100
Received: from HE126309.emea1.cds.t-internal.com (10.169.119.206) by HE104281.emea1.cds.t-internal.com (10.169.119.195) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Fri, 22 Mar 2024 03:29:32 +0100
Received: from HE102772.emea1.cds.t-internal.com (10.171.40.44) by HE126309.emea1.cds.t-internal.com (10.169.119.206) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28 via Frontend Transport; Fri, 22 Mar 2024 03:29:32 +0100
Received: from DEU01-FR2-obe.outbound.protection.outlook.com (104.47.11.168) by O365mail09.telekom.de (172.30.0.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Fri, 22 Mar 2024 03:29:32 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DSN6DsFytiyWlOLR+eA6vO35aaziBGH6zhxyYsCaynxEn20W0t0hKF0Zo+IGyMs/1JCyMLkRebTdRbCvJJpN/T4s9LCBSd6Rfir/ahYxvMs9/S/TRywsRYsdtS8oL3qebhpv2GohLeRsSAuGoReBtAmY/4DacdLA0MDR5q61H08t16TIOYXSZ6/9CrnNA/EeoFt+hld8/LXYvABCBX+Pf1sT4b7n+XMVvNKux1hW4dI7P1hgZs530r9DlbuqbzcHcsTeBmLrNXE5O2h9SkxxJLNofHGFimToWT+VGG2qxzrwwDBW/h6MCARjRNkU5kJhoZeETjwWKYzdc6MeJhTFrA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; 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=Ib5Ex7YSfN8vvyY2kAcloxsMAlfzqlFmmQH39TIUCN0=; b=e4uPUsj2mRIddZHjMQf5xGFX/ao2W0FOPCl7wFFMbWtpU2qZ4zpT4vTkyLaMvb/98mahS/ovBYCRRheZKxwBAVFTMIAQl3EBagYThdXrz/Vry+uYdfdVzS+6rw7/4JLoJGaD97uHStBdl37K8W/iFIoSI4N3M3z6NqXK+sBYgN/xpPYs2u6Ge2ae44JRa2t02q+GjnE7AoH4eRgO9faIwuLtUtR386CBHaM8kF3agbIVaZnDoXMhsMdjVDzR8pGyVqh11fC/XsKuUXa4g5/a7Hj+JTnVlU34txCvdcsrkwx7UyTubkrfHq1yCHm/azAhkvAkACq8uTzY26kiEjZO4g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from FRYP281MB2010.DEUP281.PROD.OUTLOOK.COM (2603:10a6:d10:47::5) by FR3P281MB2586.DEUP281.PROD.OUTLOOK.COM (2603:10a6:d10:5d::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7409.24; Fri, 22 Mar 2024 02:29:26 +0000
Received: from FRYP281MB2010.DEUP281.PROD.OUTLOOK.COM ([fe80::f9fb:f099:149b:1ffd]) by FRYP281MB2010.DEUP281.PROD.OUTLOOK.COM ([fe80::f9fb:f099:149b:1ffd%4]) with mapi id 15.20.7409.010; Fri, 22 Mar 2024 02:29:25 +0000
From: N.Leymann@telekom.de
To: c.l=40huawei.com@dmarc.ietf.org, mark@internetpolicyadvisors.com, adrian@olddog.co.uk
CC: wgchairs@ietf.org, team@meetecho.com, lnugent@amsl.com, alex@meetecho.com, rjsparks@nostrum.com
Subject: AW: [Team] Follow up on disruptive person during IETF 119
Thread-Topic: [Team] Follow up on disruptive person during IETF 119
Thread-Index: AQHae/dkdHKzFAJihEiQDT0VfUrdUbFC+BAAgAAB0QCAAAF3AIAAAn8AgAALY+A=
Date: Fri, 22 Mar 2024 02:29:25 +0000
Message-ID: <FRYP281MB2010D24D1DFDC4E5E7D48BE098312@FRYP281MB2010.DEUP281.PROD.OUTLOOK.COM>
References: <5F30A325-7A57-49C5-8FD9-B23ADE8D155B@ietf.org> <CAL02cgRRhZFDFWxUAOSOkku-+soo5bQZmx44a2fh5dXpO3F4kQ@mail.gmail.com> <03c50f14-ca6a-4c4b-b11b-dca9dd345d10@meetecho.com> <CAPDSy+4PD2=gFQf=8=mzJEhbhckeFuwUXAa-PSjFFmsBk3V+Aw@mail.gmail.com> <A9C2DAD5-7552-4ABC-825C-9D6E2C5B9108@kuehlewind.net> <F88C80CE-CC06-4424-AF51-67F42760954B@ietf.org> <080501da7bf8$eb08a890$c119f9b0$@olddog.co.uk>, <CAJMFcSd3UGFSmEGZ5yeoyqzoPn1tsrLUyO6=Hf5-mJv6vY3t9g@mail.gmail.com> E74913AC-02D1-4137-83D1-DCB0FCE6BCC7
In-Reply-To: E74913AC-02D1-4137-83D1-DCB0FCE6BCC7
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: FRYP281MB2010:EE_|FR3P281MB2586:EE_
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: TbcpmALjPifopKhIPbcnigDmmjSw1EUygC+q0VU2g1zjXRPKSYIwit42FFX6A7I0smyp5g9vvWZosHIRoBRgA6gyZyC/Lhyxun8TI0rdT9P9u2hz0D7GX2YryhURdJmJNMEMKHuZC2cyJWy4nF9sbZ7QjgG4xlgeLogLmbB7fnInoROYYZsJ3qDJYZYhZKp0x8mUVzWaYsDQ65s7oEh7DBCKuqr7n+P02bS/1UWV5oIHTlE66i7V6O1F9OIq9Ofz7mbrZu0Nv1u3qzJZE67s8vzRaSDLjW5BnjtsBkmf/Kw1g1CEvD/TnsvAArcLpSsge1tvbyLgI5YKkCcWSifqecTeVicWa23QGkO1djl/fTI9PawfLMx+8T/ZwVGmZ/v27f4GFnoNU7XCrdMyo9Y8XcnD7jVBrw6CrT8r1CNRMfrwzRF+pygFrDogXBcXY7kU8dWDk1fJYRNeEOcrCvELuRrVtWEweAUZkLtMP6NjiK3VuRYIfv4mITWrtNO3aR/pLdM4s5qfKW4i98UBOcs7vaCKUPX9QHOzoQ9xzAYM3+LzC+NadZSpZnYLHbtQh7FhyPzxGxRuWltp8qtcnF+ULjf1Eol3INZ1qAyBjfLc1Ew=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:FRYP281MB2010.DEUP281.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(13230031)(376005)(1800799015)(366007); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: qrHAjCzC8gQtM4C+iSwOBkfl4+FrZLM8+/gmtZ3ygNeKkyIFlfzUDp3bL7qhZmdvZCxzioh1+dSW4QWnzLsEAGrAbi02UMb7FBk3OqoSk5GwDN/eptCU/dRiazafUgRMitx3GEDh6ZsxNHh4EznLI+uNWldTXiw+QUsnTtYXK0oBM6sS4YQDNqB6UIX7D7VefBmlK9/+qNhNt6M1T364MvIsFhQLGuFyghcGDXldgnG/j9XmSnvXPAgkFybPzmP3wFh5SUlh/IoYGkaex8BeB+OL6VsJPYzjF5BH72WPSvii/BJADg1fM2zOLqbzo/TFjUzA1G2sqI2axbuLu0LLHDwNsK6jiJ3OTEwXqA9xQ1gLdXbcxzEEfudByDvpIzRjzIze0aHkGxb+LbJOrRPe9YN7vjJd37e4iGUTkQ1DS8P7bW5N/VKGUvsKrJrkrK6OIzsCArxsuSX0OLeLoa3mdGXOMboO7kBj2GG9FH7ZCW6MkuXzBfVMA+wanglzQxXb21wvxcXpRoimlxEAwKr1uddYyUnOwdh0ERzc2VnLsqIG2lHpwf77C//rlL1SyWNzVNsCAAcrglSLvVumJmY3MgXOXWJHNf+MPZYrpXqem/sTxIad0NKAWSCtBNqEUMe5LzI3GRm7vcYsGVNX1exAwuGV5YyDNMyK+sVhlDRBVCAz/ME6lDtWVUf8GpBRzpeZYiIBE5K4NndJRKhCVMBAfZIkyQLqwBRXsZxsf1tBbsMd9VISPyuUugv5wofgjOrPb0McTN2pDky9AJNsnzERHHkfDiktKzdr4Gfi6hlrIZ5Tesup47HrpgzYB6Zpqgegtd/v3nov41FPViqAivwSS++PgNyjg7x1UYu7pWgrfxMoW69ZfY/cyx+J+GL8Kpc4unmfJD0p2zfEI4OVNrJsbuNt2yOWCUImrMxQX6zpSzUziscYGrHYGHNP3UCbuXMZqNkfYXmSGBl9ovxVnTvjhMz6oMDp1A1xhqXErCoBzALT5Ar7Jtj2yiU/hzymu7nPwOmHSsxk3VBRHSTIzJZuOxpBBhtANY9MmuxkYhJ8nue04aDyBHtApfSOAqQnMnzJ7QT6cQn9Dec7E7m50zssxBMrEJaHIkOJI/9Xm/3wM4orepQ8/NzZFSIIWFt8dLjr6A4bczWiH0aKOQKf0+GpAiU8BgGI4DfYGl96aiPZY9eGuCSUc7Syyk9eTOVL6KfnReojJkjHYiigu1n9VBp46EUHTpa6tyvFVjqgq9r1WmWeqFKP/NtY8EH7Ffi0knI6PU0ENVzxcEncNJkrCjIblqK6tsUT/0On32Sq075p4FFvYGAylGq5i5R8UWFAEF6kuaT1Q4Frjo3UngoXchg0mPSqOWFkrjl3MZR6G7NIRf13+/B0Yr69MbTGWocO5kuljhmxFl4s5ESbASsqdTVuAqGvX5Xa4A1QFrQxo2944DIMq59eRHFC8I47kKT4WgPGB301gKgUd01LiqYSw5MFapcIzBfbqvJuyaNBQEyuxxD7RIJyygbZV5sTioXh3ILvWaS2B86bl0JFUiXToO0PxqDUbF2r0pPeFQ1/kvd51vx88z/1eYmzivWLOatPCFrO
Content-Type: multipart/alternative; boundary="_000_FRYP281MB2010D24D1DFDC4E5E7D48BE098312FRYP281MB2010DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: FRYP281MB2010.DEUP281.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 79c5a6de-20ee-40f7-7be0-08dc4a17e493
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Mar 2024 02:29:25.8933 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: TZ5yWu1Q6U+lvARqoBmdX1YqunO//ala6Pc9Wfg6FIReCmu0jWGnWoK/SWO0jY9zqihua7SHhHwX6lte2X+wBg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FR3P281MB2586
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/7_x1YthnXy2xQn_QzN9DDVGU2m8>
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: Fri, 22 Mar 2024 02:29:44 -0000

Hi,

My understanding this that the process will work only for meetings using meetecho.
For side meetings on Webex/Zoom/… you have to handle it on your own using whatever
mechanism is provided by the conferencing tool of you choice.

Regards

Nic

Von: WGChairs <wgchairs-bounces@ietf.org> Im Auftrag von Cheng Li
Gesendet: Freitag, 22. März 2024 02:47
An: Mark McFadden <mark@internetpolicyadvisors.com>; adrian <adrian@olddog.co.uk>
Cc: IETF WG Chairs <wgchairs@ietf.org>; team <team@meetecho.com>; Laura Nugent <lnugent@amsl.com>; Alessandro Amirante <alex@meetecho.com>; Robert Sparks <rjsparks@nostrum.com>
Betreff: RE: [Team] Follow up on disruptive person during IETF 119



We met a strange guy in a side meeting as well. I was struggling to ban him because I have never met this situation before. But after that, I think we should ban him for other participants. He really made the meeting very weird and distructed the attention.

Hope to make the rule clear so that we can handle the similar situations in the future.

Thanks,
Cheng

________________________________

李呈 Li Cheng
Mobile: +86-15116983550(中国电话)/+33-625833229(法国电话)
Email: c.l@huawei.com<mailto:c.l@huawei.com>
发件人:Mark McFadden <mark@internetpolicyadvisors.com<mailto:mark@internetpolicyadvisors.com>>
收件人:adrian <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
抄 送:IETF WG Chairs <wgchairs@ietf.org<mailto:wgchairs@ietf.org>>;team <team@meetecho.com<mailto:team@meetecho.com>>;Laura Nugent <lnugent@amsl.com<mailto:lnugent@amsl.com>>;Alessandro Amirante <alex@meetecho.com<mailto:alex@meetecho.com>>;Robert Sparks <rjsparks@nostrum.com<mailto:rjsparks@nostrum.com>>
时 间:2024-03-22 11:39:38
主 题:Re: [Team] Follow up on disruptive person during IETF 119

+1

Mark McFadden
CTO
internet policy advisors, llc
+1 608 504 7776<tel:+1%20608%20504%207776> | +44 2921 25 3640<tel:+44%202921%2025%203640>
mark@internetpolicyadvisors.com<mailto:mark@internetpolicyadvisors.com>


On Fri, Mar 22, 2024 at 11:33 AM Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>> wrote:
Thanks for pushing this, Jay.

To be more precise, there should never be the need to curtail someone’s ability to consume the stream, only their ability to contribute to it.

BTW, audio *and* video.

Cheers,
Adrian

From: WGChairs <wgchairs-bounces@ietf.org<mailto:wgchairs-bounces@ietf.org>> On Behalf Of Jay Daley
Sent: 22 March 2024 01:27
To: Mirja Kuehlewind (IETF) <ietf@kuehlewind.net<mailto:ietf@kuehlewind.net>>
Cc: IETF WG Chairs <wgchairs@ietf.org<mailto:wgchairs@ietf.org>>; team@meetecho.com<mailto:team@meetecho.com>; Laura Nugent <lnugent@amsl.com<mailto:lnugent@amsl.com>>; Alessandro Amirante <alex@meetecho.com<mailto:alex@meetecho.com>>; Robert Sparks <rjsparks@nostrum.com<mailto:rjsparks@nostrum.com>>
Subject: Re: [Team] Follow up on disruptive person during IETF 119

Thanks.  This seems to be a common call now so we’ll come back with more details on that way.

Jay

On 22 Mar 2024, at 11:21, Mirja Kuehlewind (IETF) <ietf@kuehlewind.net<mailto:ietf@kuehlewind.net>> wrote:

Giving chairs a button to mute audio/video of participants and even be able to keep that locked in for the whole session is a useful feature no matter what. That's just what the role of a chair/moderator is supposed to do. E.g. chairs can also set the email list in moderation.



On 22. Mar 2024, at 02:15, David Schinazi <dschinazi.ietf@gmail.com<mailto:dschinazi.ietf@gmail.com>> wrote:

I'm very glad we're looking into this, but I worry that this might not be sufficient. I'd say we were lucky that this individual was just speaking, and not streaming pornographic content, as has happened in public meetings of other organizations. This was a case of someone being confused, whereas we might need to deal with someone who is actively malicious. In order to respond to such a scenario, I would suggest allowing the chairs (and delegates, etc) to (1) ban someone for the duration of the current session, and (2) to temporarily disable audio/video for participants. You could also imagine a "moderated mode" for the plenary where you "ask to share audio/video" similar to how today we "ask to share slides". If meetecho already has such tools, please make them available to chairs.

Thanks,
David

On Fri, Mar 22, 2024 at 11:14 AM Alessandro Amirante <alex@meetecho.com<mailto:alex@meetecho.com>> wrote:
Il 22/03/24 02:10, Richard Barnes ha scritto:
> Hi Jay,
>
> Thanks for taking action on this.  I'm surprised that this is such a
> complicated thing to implement, especially the part where a WG chair has
> to contact the secretariat.  That adds a bunch of slowness during an
> IETF meeting, and is clearly not workable for interim meetings.
>
> Normal web conferencing platforms (Webex, Zoom, MS Teams, etc.) have
> tools for a meeting host to manage disruptive "Zoom bombing"
> participants.  Does MeetEcho not have such tools?

Yes, obviously Meetecho does have such tools as well.

AA

> --RLB
>
>
> On Thu, Mar 21, 2024 at 9:04 PM Jay Daley <exec-director@ietf.org<mailto:exec-director@ietf.org>
> <mailto:exec-director@ietf.org<mailto:exec-director@ietf.org>>> wrote:
>
>     IESG / WG Chairs
>
>     The background here is that we had one individual disrupt a number
>     of sessions, including the plenary, and we were required to first
>     temporarily ban them and then permanently ban them.
>
>     The meetings team (LLC, Secretariat, NOC, Meetecho, Tools) have
>     discussed this and we propose the following way forward to manage
>     similar instances in the future.
>
>     1.  Maintain a trust-based approach with an exception process,
>     rather than introduce new controls to lock/unlock a whole session.
>     We think approach both maintains the permissive culture of the IETF
>     and avoids extra complexity for WG Chairs.
>
>     2.  Add a new feature in Datatracker that allows the Secretariat to
>     remove a participant from a session and more permanently.  The
>     technical details here are that this feature will revoke their
>     registration permissions and call a Meetecho API to remove them.
>
>     3.  For single session removal this new process can be invoked by a
>     WG chair (of the session) or an AD, contacting the Secretariat.
>     Permanent removal can only be authorised by me or Roman, normally
>     after rapid consultation with the IESG.
>
>     Does this work for everyone?
>
>     Jay
>
>     --
>     Jay Daley
>     IETF Executive Director
>     exec-director@ietf.org<mailto:exec-director@ietf.org> <mailto:exec-director@ietf.org<mailto:exec-director@ietf.org>>
>

--
Ing. Alessandro Amirante, Ph.D.

Meetecho S.r.l.
www.meetecho.com<http://www.meetecho.com/>

Via Riviera di Chiaia 124<https://www.google.com/maps/search/Via+Riviera+di+Chiaia+124+80122+Napoli,+Italy?entry=gmail&source=g>
80122 Napoli, Italy<https://www.google.com/maps/search/Via+Riviera+di+Chiaia+124+80122+Napoli,+Italy?entry=gmail&source=g>

Mobile: +39 329 6178743
E-mail: alex@meetecho.com<mailto:alex@meetecho.com>


--
Jay Daley
IETF Executive Director
exec-director@ietf.org<mailto:exec-director@ietf.org>