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

Jay Daley <exec-director@ietf.org> Fri, 22 March 2024 01:27 UTC

Return-Path: <jay@staff.ietf.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 9982BC14F680 for <wgchairs@ietfa.amsl.com>; Thu, 21 Mar 2024 18:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20230601.gappssmtp.com
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 CtUZYmM2NiGE for <wgchairs@ietfa.amsl.com>; Thu, 21 Mar 2024 18:27:00 -0700 (PDT)
Received: from mail-oa1-x43.google.com (mail-oa1-x43.google.com [IPv6:2001:4860:4864:20::43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70F2AC14F5F8 for <wgchairs@ietf.org>; Thu, 21 Mar 2024 18:27:00 -0700 (PDT)
Received: by mail-oa1-x43.google.com with SMTP id 586e51a60fabf-2218da9620cso916485fac.3 for <wgchairs@ietf.org>; Thu, 21 Mar 2024 18:27:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1711070819; x=1711675619; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=xsEKMMm9MOKQ2g9NDT+JFALPVUhAiY3MA87CWM21PXY=; b=k6KJJjIK+lvKzmzWtACY3be6dfE/g1Y3NHgFuyDX2lrrxYFc7XKbPhDiMm0VmmL1Ow NtH9ghcQAx3odde6MXGq0MCxvNDiOI3yWIjKXSKRg2IMgrZRw4p5w1uhSMPFWGRwlyjX 0TR7XzFgzhJ1fZdO24DfQM7pehAehKCZXtFVCekjwYj7fEDxeH0VbaJT2kg3dcWLazFP XHTqHdQ5RpCX27zJyaRtXXLFW5LdEIY7OO0GCEuOkxmxBK66VbOkNPjjp4v3XqHVrR15 6QQzl/odtz59TfAjAOnTbF0x2yL6ch7g3eRU9fCjXPw4qU6iiZxTQfMBcm8tBDV5/Y7y cHgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711070819; x=1711675619; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=xsEKMMm9MOKQ2g9NDT+JFALPVUhAiY3MA87CWM21PXY=; b=gw1OYWUn1/RAbcp4IPMYsM9/fVtPpKcDOAO5aK195AsQJPtodhQ9mcIh2YfNPz8xT4 /0N6J441a2vhy0SleJfWwhNil6i7BG4IzCP2a4ASoTiNxLdn08xipbPGbvGFF8M3oR5h bHj6Rm5pSvEARtHWC559JKI5uc+Q5AOXS7ml3/3PccFnJsZONnmzP/DW3Qu99K6JVRsz NvAPFxwVz5pexnPa2GONHIQTsqu9a4u/fDa24DWq8sM60IX/Xr3ZzDV704VClHx2AAKd LK0guF96kq5kwIqeiiN2aihksxCWZuoa7Xppfa6CK1Bsz0nDptmToVnrejYXMfeIr6yD cNNQ==
X-Forwarded-Encrypted: i=1; AJvYcCUNBJwHUbx4jRTk7xbrOtoRGzXAx7V+Y2a9bcx5fuFLh8r1xm8z4EWCmu8QjgJAR1qmejy32vCZejYOxEs9/jMeEQ==
X-Gm-Message-State: AOJu0YwpRosn340+DOdCdNRAfFtLzI13q+1GG1OAyuZNNgcVSAkTUe0x mleHZUaezkNRKseDn7cuWKg6MsvN498jYrauVOk8pJ7TaDgJon2xSG7SIebllX1kx3LCukMWq+3 Pf9ReS7HrSBQ=
X-Google-Smtp-Source: AGHT+IFzx17TRBfv3qSTxIq3tTrWhcnSGmwoyB/ygGw0Jqc9wb3PSCPkw63vpJRqDdnSW4bJLfOMog==
X-Received: by 2002:a05:6870:c0d1:b0:221:cb1b:c572 with SMTP id e17-20020a056870c0d100b00221cb1bc572mr984988oad.25.1711070818867; Thu, 21 Mar 2024 18:26:58 -0700 (PDT)
Received: from smtpclient.apple (dhcp-81c9.meeting.ietf.org. [31.133.129.201]) by smtp.gmail.com with ESMTPSA id h1-20020a631201000000b005dc85821c80sm504840pgl.12.2024.03.21.18.26.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Mar 2024 18:26:58 -0700 (PDT)
From: Jay Daley <exec-director@ietf.org>
Message-Id: <F88C80CE-CC06-4424-AF51-67F42760954B@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_88F1F27A-1CE2-44F4-A1C1-AE234236D3E0"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Subject: Re: [Team] Follow up on disruptive person during IETF 119
Date: Fri, 22 Mar 2024 11:26:44 +1000
In-Reply-To: <A9C2DAD5-7552-4ABC-825C-9D6E2C5B9108@kuehlewind.net>
Cc: David Schinazi <dschinazi.ietf@gmail.com>, IETF WG Chairs <wgchairs@ietf.org>, Alessandro Amirante <alex@meetecho.com>, team@meetecho.com, Laura Nugent <lnugent@amsl.com>, Robert Sparks <rjsparks@nostrum.com>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
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>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/pq1hscLopIpLuZmhcXAUWvEguBg>
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 01:27:05 -0000

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> 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> 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
>>> 80122 Napoli, Italy
>>> 
>>> Mobile: +39 329 6178743
>>> E-mail: alex@meetecho.com <mailto:alex@meetecho.com>
>>> 
> 

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org