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

John C Klensin <john-ietf@jck.com> Thu, 02 June 2022 05:57 UTC

Return-Path: <john-ietf@jck.com>
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 EFEC4C157908 for <ietf@ietfa.amsl.com>; Wed, 1 Jun 2022 22:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham 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 y25_z3ARizxd for <ietf@ietfa.amsl.com>; Wed, 1 Jun 2022 22:57:34 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91B57C14F725 for <ietf@ietf.org>; Wed, 1 Jun 2022 22:57:33 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1nwdpq-000MGk-Nw; Thu, 02 Jun 2022 01:57:30 -0400
Date: Thu, 02 Jun 2022 01:57:25 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Subject: Re: Harassment, abuse, accountability. and IETF mailing lists
Message-ID: <12FAAA66C828BE15672DF6A9@PSB>
In-Reply-To: <5a53fa11-8138-2261-0e30-ae603b064cc8@network-heretics.com>
References: <16C5EC99A155D55344E1F195@PSB> <5a53fa11-8138-2261-0e30-ae603b064cc8@network-heretics.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jFdJyCvvbmX5rqIV4FcZVh7kIaw>
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: Thu, 02 Jun 2022 05:57:39 -0000


--On Wednesday, June 1, 2022 16:45 -0400 Keith Moore
<moore@network-heretics.com> wrote:

> On 6/1/22 16:04, John C Klensin wrote:
> 
>> Or is it the IETF's position that no one is actually
>> responsible for monitoring the appropriateness of content on
>> non-WG lists or accountable for doing, or not doing, that?
> "Monitoring the appropriateness" seems like overkill, and it
> would seem to mean that not only would there need to be a
> designated person or people for every single IETF list, but
> also that said person or people should be promptly reading
> every message in every such conversation.
> 
> I'd like to think that it's sufficient if there be a person or
> people for each list to whom complaints can be directed, and
> who has some limited power to take corrective action.

In case it was not clear from a response sent a few minutes ago,
I didn't intend "monitoring the appropriateness" the way you are
reading it.  Apologies for not being clear.  I do expect that
someone who is responsible for a list -- "owner",
"administrator" or some other label -- will be at least
reasonably familiar with what is going on and, if they notice
seriously bad behavior, will step in without awaiting a
complaint from someone else.   But the more important point is
the one you identified: there has to be some way to direct
complaints to someone who has some reasonable ability to take
corrective action and who is responsible for considering what is
necessary or appropriate on a timely basis.

I also think that person or person should be identifiable by
people reading the list, not completely hidden behind a generic
alias.

> More broadly, I still believe that IETF works better if the
> community can mostly police itself, and mostly set its own
> standards for behavior, rather than expecting that there
> should always be some parental figure to adjudicate every
> possible conflict.  I realize that there are limitations with
> community self-policing, including (quite importantly) that
> communities can harbor and enforce prejudices against certain
> kinds of individuals even without realizing that they're doing
> so.   So self-policing can never be entirely sufficient, but
> I believe it's a necessary component.   Because appointed
> individuals can also harbor and enforce prejudices, with even
> less potential to correct them when they run amok.

I completely agree.  But I see having some responsible party,
with the authority and responsibility to either enforce or
escalate as needed, as part of that community self-policing
process, especially if abusive behavior occurs and is
sufficiently intense (for lack of a better word) to cause other
readers of the relevant list to decide not to engage with the
offender lest they become the next targets.  I also think we
would be headed for trouble if those who might be called upon to
deal with such issues were not, themselves, active members of
the community.

best,
   john