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

John C Klensin <john-ietf@jck.com> Thu, 02 June 2022 05:40 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 3621FC14F72D for <ietf@ietfa.amsl.com>; Wed, 1 Jun 2022 22:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 02y7SNnYO37A for <ietf@ietfa.amsl.com>; Wed, 1 Jun 2022 22:40:55 -0700 (PDT)
Received: from bsa2.jck.com (ns.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 3F57DC14F725 for <ietf@ietf.org>; Wed, 1 Jun 2022 22:40:54 -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 1nwdZk-000MFY-An; Thu, 02 Jun 2022 01:40:52 -0400
Date: Thu, 02 Jun 2022 01:40:47 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: Harassment, abuse, accountability. and IETF mailing lists
Message-ID: <EFB9E95A38997AD1F6AD22A1@PSB>
In-Reply-To: <15505.1654129871@localhost>
References: <16C5EC99A155D55344E1F195@PSB> <5a53fa11-8138-2261-0e30-ae603b064cc8@network-heretics.com> <452764b0-a758-874a-2ce5-122f9d0de763@gmail.com> <15505.1654129871@localhost>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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/iEyz_-cr1x9_b-JNf5tWsB3Swko>
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:40:56 -0000


--On Wednesday, June 1, 2022 20:31 -0400 Michael Richardson
<mcr+ietf@sandelman.ca> wrote:

> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     > On 02-Jun-22 08:45, Keith Moore 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?
> 
>     > I suspect that the position is that there is, formally,
> no position.
> 
> I think that what John is saying is that the "appeal" path for
> non-WG lists is unclear to the participants.
> (I use "appeal" in quotes, because really, it's about to
> dispute, anti-harassement and code of conduct process)

That is correct.   And, as Bob Hinden more or less pointed out,
if the rules for acceptable behavior on an IETF non-WG list are
different from those for WG lists and the IETF list... well that
would be a really unfortunate situation, especially since some
of those lists are used to review concepts or documents that may
ultimately become part of the standards process.

But it is a bit more than that.  If one assumes that the
"appeal" path is to contact the person "running" the particular
list, then is the potential appellant (and the community in
general) entitled to know who that person (or people) are?

>     > So the missing link seems to be an IESG Statement that
> absent any other     > provision, the administrators of a
> non-WG list should fulfill the role     > described in RFC3934
> (part of BCP24).

That is one of two missing things.  The other, at least IMO, is
identification of those administrators to the community or at
least to list subscribers.

>     >> "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.

Agreed although, as mentioned below, I'd be a little bit
concerned if the responsible party (aka "administrator" in most
cases) for a list were not reading it regularly.  I am only
concerned about who someone goes to if they spot what appears to
be inappropriate behavior and whether those administrators (or
designees) are identified or completely hidden behind a role
address.

>     > Yes. Shouldn't anybody tagged as a list admin be doing
> that anyway?
> 
> You'd think so, but people sometimes forget which lists are
> theirs. And I've noticed that some WG lists aren't even well
> monitored by the chairs. (Yes, I complain)

See above.

>     >> enforce prejudices, with even less potential to correct
> them when they     >> run amok.
> 
>     > Which, I believe, is exactly why the backstop mechanisms
> we have in place for     > WG list abuse should apply here
> too. I think John has identified that at     > the moment, we
> have no backstop.
> 
> Yes.

Yes for me too.  And, again, I'm concerned for several reasons
about anonymous backstops.

   best,
    john