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

[Mark McFadden <[e-mail]>]

+1

Mark McFadden
CTO
internet policy advisors, llc
[phone] <+1%20608%20504%207776> | [phone]
<+44%202921%2025%203640>
[e-mail]


On Fri, Mar 22, 2024 at 11:33 AM Adrian Farrel <[e-mail]> 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 <[e-mail]> *On Behalf Of *Jay Daley
> *Sent:* 22 March 2024 01:27
> *To:* Mirja Kuehlewind (IETF) <[e-mail]>
> *Cc:* IETF WG Chairs <[e-mail]>; [e-mail]; Laura Nugent
> <[e-mail]>; Alessandro Amirante <[e-mail]>; Robert
> Sparks <[e-mail]>
> *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) <[e-mail]>
> 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 <[e-mail]>
> 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 <[e-mail]>
> 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 <[e-mail]
> > <mailto:[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] <mailto:[e-mail]>
> >
>
> --
> Ing. Alessandro Amirante, Ph.D.
>
> Meetecho S.r.l.
> 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: [phone]
> E-mail: [e-mail]
>
>
>
>
>
> --
> Jay Daley
> IETF Executive Director
>
> [e-mail]
>
>
>