Re: [irsg] Follow up on disruptive person during IETF 119
Toerless Eckert <tte@cs.fau.de> Fri, 22 March 2024 03:17 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.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 AE784C14F685; Thu, 21 Mar 2024 20:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.66
X-Spam-Level:
X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
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 v1dnaUs856dB; Thu, 21 Mar 2024 20:17:05 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 357EDC14F60D; Thu, 21 Mar 2024 20:17:03 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4V16v01XpKznkSd; Fri, 22 Mar 2024 04:17:00 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4V16v00JFyzkn9k; Fri, 22 Mar 2024 04:17:00 +0100 (CET)
Date: Fri, 22 Mar 2024 04:17:00 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Reese Enghardt <ietf@tenghardt.net>
Cc: Francesca Palombini <francesca.palombini=40ericsson.com@dmarc.ietf.org>, Jay Daley <exec-director@ietf.org>, The IESG <iesg@ietf.org>, IETF WG Chairs <wgchairs@ietf.org>, Robert Sparks <rjsparks@nostrum.com>, Laura Nugent <lnugent@amsl.com>, "team@meetecho.com" <team@meetecho.com>
Subject: Re: [irsg] Follow up on disruptive person during IETF 119
Message-ID: <Zfz4LLqXK_4kgqyL@faui48e.informatik.uni-erlangen.de>
References: <5F30A325-7A57-49C5-8FD9-B23ADE8D155B@ietf.org> <PAXPR07MB7838B22552B3EAE3840E954398312@PAXPR07MB7838.eurprd07.prod.outlook.com> <8006de20-277e-b940-b57d-f1ea1dc7a3a2@tenghardt.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <8006de20-277e-b940-b57d-f1ea1dc7a3a2@tenghardt.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/8lQrHBOIz2VVpNvBBECk9RZkAyg>
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 03:17:09 -0000
I would like to repeat what Adrian said, especially for the tools that we should be able to control well ourselves: We should as much as possible NOT constrain a person to consume our content based on behavior. Only to contributing to it. And yes, even in meetecho this may involve a bit more steps than simply not admitting a person. Disallow to send video disallow to send audio, maybe disallow to even show the users name/metadata (not sure if this could be abused for e.g.: obscene names or the like). And also +1 to Lou's comment on the notes tool and some way to exclude contributions to a page by specific dattracker accounts. Not sure how to best do this, as there i usually no identified notes page owner. Cheers toerless On Fri, Mar 22, 2024 at 11:35:37AM +1000, Reese Enghardt wrote: > Hi, > > On 3/22/24 11:19, Francesca Palombini wrote: > > > > I appreciate that we would keep a “trust-based approach”, but I do think > > that WG chairs or at least ADs need to be able to not necessarily remove > > disruptive participant from a session, but definitely block a > > participant from sending audio/video for a longer amount of time, say a > > session (that is not switch their audio/video off) without necessarily > > going through the secretariat. > > > > I also think we need to think about the same for chats, even if it was > > not a problem this time. > > > I agree with Francesca here. > > The individual in question was in one of the sessions I chaired. > > I worked with Meetecho in the chat, and they said they're able to boot the > participant if needed. This was fine for me, if stressful. > > It'd be better if we as chairs had an easier way to do this, and definitely > please don't make it harder. Having to contact the Secretariat while also > chairing is definitely harder than just contacting Meetecho, we chat them > for general audio/video issues anyways.. > > I noticed that in my next session as chair, I saw new controls to revoke > audio/video from a participant (once, then they could start staring > audio/video again). This feature is a good start, and it was sufficient to > address the individual in question. Is this feature temporary or will it > stay? > > Also, big shout-out to the Meetecho folks for their great support in this > matter! > > Best, > Reese -- --- tte@cs.fau.de
- Follow up on disruptive person during IETF 119 Jay Daley
- Re: Follow up on disruptive person during IETF 119 Michael Richardson
- Re: Follow up on disruptive person during IETF 119 Richard Barnes
- Re: [Team] Re: Follow up on disruptive person dur… Alessandro Amirante
- Re: [Team] Re: Follow up on disruptive person dur… David Schinazi
- Re: [Team] Follow up on disruptive person during … Mirja Kuehlewind (IETF)
- Re: Follow up on disruptive person during IETF 119 Jeffrey Haas
- Re: [Team] Follow up on disruptive person during … Jay Daley
- Re: [Ext] [Team] Follow up on disruptive person d… Paul Hoffman
- RE: [Team] Follow up on disruptive person during … Adrian Farrel
- Re: [irsg] Follow up on disruptive person during … Yoav Nir
- RE: [Team] Follow up on disruptive person during … Lou Berger
- Re: [Team] Follow up on disruptive person during … Mark McFadden
- Re: [Team] Follow up on disruptive person during … Lucas Pardue
- RE: [Team] Follow up on disruptive person during … Cheng Li
- Re: [Team] Re: Follow up on disruptive person dur… Richard Barnes
- AW: [Team] Follow up on disruptive person during … N.Leymann
- AW: [Team] Follow up on disruptive person during … N.Leymann
- Re: Follow up on disruptive person during IETF 119 Jay Daley
- Re: Follow up on disruptive person during IETF 119 Mark Nottingham
- Re: [irsg] Follow up on disruptive person during … Toerless Eckert
- Re: Follow up on disruptive person during IETF 119 Yoav Nir
- Re: [irsg] Follow up on disruptive person during … Michael Richardson
- Re: [irsg] Follow up on disruptive person during … Melinda Shore
- Re: [irsg] Follow up on disruptive person during … Michael Richardson
- Re: [irsg] Follow up on disruptive person during … Melinda Shore
- Re: Follow up on disruptive person during IETF 119 Bron Gondwana
- Re: [irsg] Follow up on disruptive person during … Melinda Shore
- Re: [irsg] Follow up on disruptive person during … Stephen Farrell
- Re: [irsg] Follow up on disruptive person during … Bron Gondwana
- Re: Follow up on disruptive person during IETF 119 Francesca Palombini
- Re: [irsg] Follow up on disruptive person during … Reese Enghardt