Re: Harassment, abuse, accountability. and IETF mailing lists

Pete Resnick <resnick@episteme.net> Fri, 03 June 2022 14:24 UTC

Return-Path: <resnick@episteme.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A50DC15AACE; Fri, 3 Jun 2022 07:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=episteme.net
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 AGJtmZpUDU5V; Fri, 3 Jun 2022 07:24:20 -0700 (PDT)
Received: from helm.helm.episteme.net (helm.helm.episteme.net [209.51.32.195]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BD3DC157B50; Fri, 3 Jun 2022 07:24:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=episteme.net; s=mail; t=1654266258; bh=3s+yehazCiPIEeTF03xdDATKrJxPqLBPYW9NzerVrU8=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=ByTFLHMzhIqyY3vsh0DyZzF0YtQLkQFqiRm1pXo58vixWzQr1jjIbYdETsL7p4rgZ tiWomyyHo+R6+DQj2zFVL16o2gctM+FUfH+yIKbHtPSqC4S22dWl8VpIAsXJZan2v8 AtYzZi2OkeNWaQTM2c9PKDolEi27Ful//18PtMMs=
From: Pete Resnick <resnick@episteme.net>
To: Lars Eggert <lars@eggert.org>
Cc: Carsten Bormann <cabo@tzi.org>, John C Klensin <john-ietf@jck.com>, art-ads@ietf.org, IETF discussion list <ietf@ietf.org>
Subject: Re: Harassment, abuse, accountability. and IETF mailing lists
Date: Fri, 03 Jun 2022 09:24:16 -0500
X-Mailer: MailMate (1.14r5898)
Message-ID: <0325E09B-3B8D-47B5-83B8-ACA5A028B464@episteme.net>
In-Reply-To: <65A1073F-8519-4BDB-B85C-72087B527498@eggert.org>
References: <16C5EC99A155D55344E1F195@PSB> <5a53fa11-8138-2261-0e30-ae603b064cc8@network-heretics.com> <452764b0-a758-874a-2ce5-122f9d0de763@gmail.com> <4520B31984B329BF6936113D@PSB> <6298831D.8030605@btconnect.com> <941D4EB9-8EDF-4612-AD55-251C381C09FB@episteme.net> <e1d5ba16-8c12-cd30-ea4c-762b9225cee4@gmail.com> <10863445C94B1C12A5973429@PSB> <A92F81D8-057D-4AA0-B94E-427D6F8AB53A@eggert.org> <55B5F6C1-B554-4675-BCD5-048043162D22@tzi.org> <65A1073F-8519-4BDB-B85C-72087B527498@eggert.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8-W18FuizLudioXyssSmwey2MCo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2022 14:24:25 -0000

On 3 Jun 2022, at 6:30, Lars Eggert wrote:

> On 2022-6-3, at 13:38, Carsten Bormann <cabo@tzi.org> wrote:
>> On 2022-06-03, at 09:19, Lars Eggert <lars@eggert.org> wrote:
>>>
>>> They can always contact any AD, the IESG as a whole, or the IETF 
>>> Chair.
>>
>> (One problem with such a broad recommendation is that a newcomer will 
>> have no way to know who in the IETF organization colludes with whom.  
>> We may think it is a job requirement for an AD to be able to act like 
>> an ombudsman, but how does the newcomer know that.)
>
> which is why there is an ombudsteam?

(Speaking without hats)

Let's be clear about the division of labor here: RFC 7776 anticipates 
that common disruptive behavior on a WG mailing list is handled by the 
chair of the WG, and then escalated to the AD, IESG, etc. as needed. The 
ombudsteam process is normally reserved for the kinds of harassment that 
can't be dealt with that way. While the ombudsteam has been completely 
open to advising people (both participants and chairs) on cases of 
straightforward misbehavior (and in fact recently was asked to speak at 
a WG meeting in order to deal with such behavior), I would personally 
not be too keen on the default position for every concern to be brought 
to the ombudsteam; that's a recipe for the ombudsteam to become the 
good-behavior-enforcement-body in the IETF, which IMO would be a very 
bad thing (let alone against what RFC 7776 says). The default should 
always be to bring it to the person(s) leading the discussion, which in 
the case of WGs is the chair(s).

For non-WG mailing lists, there is an IESG statement: 
https://www.ietf.org/about/groups/iesg/statements/disruptive-posting/. 
It's pretty clear that for non-WG lists, the administrator deals with 
disruptive posters. But I just happen to know about that IESG statement 
because Iwas on the IAB when an appeal caused that statement to be 
written. A newcomer probably would not know that non-WG list 
administrators are expected to deal with disruptions. More importantly, 
as John and others have said, finding the identify the list 
administrator is not trivial. Somewhere, in an easy to find spot, anyone 
should be able to discover the procedures for dealing with disruptive 
behavior and the names of the humans who handle it.

pr
-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best