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

Abdussalam Baryun <abdussalambaryun@gmail.com> Sun, 12 June 2022 05:09 UTC

Return-Path: <abdussalambaryun@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 01640C1594AD for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2022 22:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ITv94cRktsCW for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2022 22:09:02 -0700 (PDT)
Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (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 2C615C14F749 for <ietf@ietf.org>; Sat, 11 Jun 2022 22:09:02 -0700 (PDT)
Received: by mail-wr1-x430.google.com with SMTP id q15so3314667wrc.11 for <ietf@ietf.org>; Sat, 11 Jun 2022 22:09:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hEwzOEw2+sg5350Oose5nprFrxD3ZodCHORlNqhPTdI=; b=oG4B1FGXNLvcrfVTWbslUB8Gxd6ejwJ8mgRWaAQ696UmI/6jaeCtFdmsBWid9c2ijj EiUEOmnFZx8lS9dKjBr4Jpf6F7L5ZL3bOoVfr2mGkBj0iK6BZzeFejCARUXOXtB5GYO6 ugxsgKRTq3PF9SjUGuE1zjiDq+kgTqEeyyaQGauzWWY21RH3i2bSd1Uy6PiDWFbWEkNM x9cT50juTbYshhSfeSUnZuysMM+QHIM6mWFmBw9YY4BRextCvhN95ctmfRGNkcdUkl3L p9cgBeTMGhVDt4cnr4nDAUl8fDbpna0Uy0sEdLbO6G1qopSRPtkwGHf8ySrUaIkynMs1 eFsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hEwzOEw2+sg5350Oose5nprFrxD3ZodCHORlNqhPTdI=; b=JXLdM7IW6ctToLpBeBoqSwrzgldZsstkJkRxuywLGEpkHQtmVc2cV7emXDOZobKdbq VXvccLlL0Qb7qN/vp2BtAsSGfcSu7f917VsPg2mymuwTLXlx6JLfO1cT5sLX+CxOLhmB L6yVZv9pOrtyOhuF2SYbJJiCL4p8TlO24rDXKVSeGjtCvDi/zNM5los4fTyu8YxICxzM cs7p1tUd8uXJj0R2ydLScLDptyRwgc5nfEZLRbFi7Fqa+HqJNKWhvMcVd1L4v9g26X0w 9YziphxO7zdpJyT7ioneIa5LsnMyHsAXs3/TPciaYeFi0YEih/7AjxZcnu4gUUuVb2X+ Xhgg==
X-Gm-Message-State: AOAM531iN65B3gXefqYK0ojlCfj4bfvy8CuGZHyyA3iuG4iI8/0dAJrU Bi7Cz5qmHap/5dGBDLhf5Okxp6A7Fhjt8wr9XtylBPJO
X-Google-Smtp-Source: ABdhPJxWsDY2Ls9dHhsMyI+DYeC0Xvd4rAoEQ4HsyNpsAFVDHi9x8LtBK0dEVKnto9ao5rQ2bqbv8hSP5V+NMolV2Jk=
X-Received: by 2002:a5d:64e7:0:b0:218:5626:7e7f with SMTP id g7-20020a5d64e7000000b0021856267e7fmr25809894wri.245.1655010539854; Sat, 11 Jun 2022 22:08:59 -0700 (PDT)
MIME-Version: 1.0
References: <16C5EC99A155D55344E1F195@PSB>
In-Reply-To: <16C5EC99A155D55344E1F195@PSB>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Sun, 12 Jun 2022 06:58:54 +0200
Message-ID: <CADnDZ88dRg2ObwULx52VFkCQVp=dVKaeZ0_yLWxZbD-b2JqFLA@mail.gmail.com>
Subject: Re: Harassment, abuse, accountability. and IETF mailing lists
To: John C Klensin <john-ietf@jck.com>
Cc: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000053deba05e1392b50"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vAJplGaSx_xfocL5fMlW2FeW4hY>
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: Sun, 12 Jun 2022 05:09:06 -0000

IMO the issue for each list/group making sure there is someone reading all
messages and analysing the details. What is the status anti-abuse-system
performance percentage of success per time?
I think there can be possibilities that IETF WG-chair/who-responsible-for
abuse-solving is not following the group-conversation on his/her list/room
to solve abuse situation on time.
Is IETF able to read all messages and analyse them quickly enough?

After I know the answer from management of the past performance, we can
think to discuss public identifications of responsible persons. I am not
sure if identification increases the system performance or decreases.

Best Wishes,
AB


On Wed, Jun 1, 2022 at 10:05 PM John C Klensin <john-ietf@jck.com> wrote:

> Hi.  I contemplated just sending this to the IESG but it may
> need broader community discussion.
>
> As I think we all know, someone occasionally posts inappropriate
> messages to an IETF-provided mailing list, sometimes attacking
> the person who posted an earlier message to the list and not
> their ideas.  Sometimes those public attacks are followed by
> private ones that might even be threatening.  Of course, that
> sort of  behavior violates at least the intent of the code of
> conduct and, under certain circumstances, the anti-harassment
> policies.
>
> It is not clear what we can do about the off list attacks, but
> we should not facilitate them and, where practical, should be
> offering assistance to mitigate them.
>
> When such transactions involve this list (the main IETF
> discussion one), there is a sergeant-at-arms team with whom
> issues can be raised.  When it is on a WG list, my understanding
> is that WG Chairs are charged with ensuring good behavior.
> However, it is not clear what should what the model is for
> non-WG lists and who is accountable if bad behavior occurs and
> is either very egregious or persists.  My recollection (maybe
> wrong) is that we used to identify the responsible parties for
> such lists.  Now, it seems that many such lists contain only a
> footer that says the equivalent of:
>
>    XXX list run by XXX-owner at ietf.org
>
> In the interest of transparency and accountability, shouldn't
> the people involved in managing such a list be identified?  If
> they post to the lists they are "running", their names and email
> addresses are exposed, so their participation and identities are
> not secret, only their responsibilities.  It is reasonable that
> correspondence about the list go to a different address than
> their ordinary one(s), but that does not require hiding their
> names either.
>
> Would it be reasonable to replace the line/ template above with
> something more like:
>
>   XXX list maintained by Jane Jones and Joe Smith, contact
> address XXX-owner@ietf.org
>
> (I object to "run" for other reasons, but don't feel strongly
> about it in this context if others prefer it.)
>
> 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?
>
> thanks,
>    john
>
>
>