Re: Follow up on disruptive person during IETF 119

[Richard Barnes <[e-mail]>]

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?

--RLB


On Thu, Mar 21, 2024 at 9:04 PM Jay Daley <[e-mail]> 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
> [e-mail]
>
>