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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 01 June 2022 23:26 UTC

Return-Path: <brian.e.carpenter@gmail.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 90224C14F721 for <ietf@ietfa.amsl.com>; Wed, 1 Jun 2022 16:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.984
X-Spam-Level:
X-Spam-Status: No, score=-8.984 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_HI=-5, 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 (2048-bit key) header.d=gmail.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 wUvfxmCPDy8X for <ietf@ietfa.amsl.com>; Wed, 1 Jun 2022 16:26:31 -0700 (PDT)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (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 107A0C15948E for <ietf@ietf.org>; Wed, 1 Jun 2022 16:26:31 -0700 (PDT)
Received: by mail-pf1-x42a.google.com with SMTP id b135so3249463pfb.12 for <ietf@ietf.org>; Wed, 01 Jun 2022 16:26:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=toKgJ/PBNZQjAYKLFauf0CKrdObUhvKUQU1bVVkFq20=; b=XgLaTTUs5/Gwdl1+6Dr4bG70IdltWTdExlTENH+hz8lKbWkr2sXBMuVaX4ZuYt81FF eDljOQXO0u3ATv5iFjAK/OOuz+S8jO4CHT2MBbJ1Z7mf1/ylX+1i+I5RwBbG6H7FO3Gx OurADprv7YAWdMJQj8uhltQFetz8pgfQRh+5HnCloGVIGsN7YTmf9nNOHqtChyPAnLPb KDtBWnH+Elg1rS0Sv4lwg+6SJ53vZDNvNI54er164bUw3CKt/TCIwytLZEIiUbVqaWd/ vMBgMKRNrv/5hivVfJsc952c01UoWJgfC3lA1MDSD3tWrnd4xoJumDz/5Sn1UGhXUqWS YNUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=toKgJ/PBNZQjAYKLFauf0CKrdObUhvKUQU1bVVkFq20=; b=6xPjLo5j8xWetfQgvYhNTkU0q0jMRnx0hl7vaWSWnVwVkfkGQMSK3U62zctnHHYuXY SSJ3wGIory/WlAyLd9GZu/6xtmINhWlD0uksM0VzyByPbDw5p4UfxgaIMjN1YZoPPRGJ vWAwoRHLz0Eqx6t5bX3LiVKhDmzqJAYXUymoGWtdHXjzTyAcgYmoU6O+8d2ifd9PJn81 IZemhAXYBFj+rmsR9mui7BzQbybN2FrzOZG9oPP/UOoHNozzXnAV4OO/X3g+t8EVsvUB BDId93WTnGKpOdyRBUBgzU/K/PcO8mIChBpvfcjnmnwxCIrbl4ZmcAYjdsCfB4JXqXrm 64aA==
X-Gm-Message-State: AOAM53330ze9lHYut/kPzoK6vXJYKU6qcGmyag6MtWMekMh+n93KW5jB VAxhXF6ofPE714yd8Pfsn5oVQ9/on6CHfA==
X-Google-Smtp-Source: ABdhPJwM/cpRrMzqN7Q8Rsq6aAe0tKTAhH4yuK7ZuHML7qoe+24FJvUqHtDy2aUc62CHSVdLN2tB9w==
X-Received: by 2002:aa7:8008:0:b0:51a:cae3:7563 with SMTP id j8-20020aa78008000000b0051acae37563mr25161456pfi.16.1654125990324; Wed, 01 Jun 2022 16:26:30 -0700 (PDT)
Received: from ?IPv6:2406:e003:1005:b501:80b2:5c79:2266:e431? ([2406:e003:1005:b501:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id je18-20020a170903265200b0015e8d4eb259sm2067502plb.163.2022.06.01.16.26.28 for <ietf@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 01 Jun 2022 16:26:29 -0700 (PDT)
Subject: Re: Harassment, abuse, accountability. and IETF mailing lists
To: IETF discussion list <ietf@ietf.org>
References: <16C5EC99A155D55344E1F195@PSB> <5a53fa11-8138-2261-0e30-ae603b064cc8@network-heretics.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <452764b0-a758-874a-2ce5-122f9d0de763@gmail.com>
Date: Thu, 02 Jun 2022 11:26:25 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <5a53fa11-8138-2261-0e30-ae603b064cc8@network-heretics.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NiZH7w5JHm8JTdjy1yW3xs8nLVM>
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: Wed, 01 Jun 2022 23:26:31 -0000

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.
When I've been the mailman admin for such lists, fortunately I've
never had to deal with untoward messages, but I'd say that it would
clearly have been my job to do so. Also, there's always an AD who
authorised each list (or their predecessor did so), so there's
a chain of responsibility.

All our policies do apply to non-WG mailing lists, according to
https://www.ietf.org/how/lists/nonwglist-guidelines/ which cites
the Note Well. In particular the code of conduct and anti-harassment
BCPs apply.

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

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

Yes. Shouldn't anybody tagged as a list admin be doing that anyway?

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

Why would it be limited compared to the power a WG chair has over a
WG list? The same rules of conduct apply.
  
> 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. 

Yes, but I assume we are concerned here with cases where self-regulation
has failed.

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

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.

Regards
    Brian