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

Bob Hinden <bob.hinden@gmail.com> Thu, 02 June 2022 03:57 UTC

Return-Path: <bob.hinden@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 9E4BDC14CF17 for <ietf@ietfa.amsl.com>; Wed, 1 Jun 2022 20:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 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, RCVD_IN_DNSWL_HI=-5, 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] 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 bUVFYd1cQEnV for <ietf@ietfa.amsl.com>; Wed, 1 Jun 2022 20:57:52 -0700 (PDT)
Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (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 DC7EAC14F72D for <ietf@ietf.org>; Wed, 1 Jun 2022 20:57:52 -0700 (PDT)
Received: by mail-wr1-x433.google.com with SMTP id e25so4744705wra.11 for <ietf@ietf.org>; Wed, 01 Jun 2022 20:57:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=ROFlD7A+My22XCgv95V/ZAgWx49hRQn3rzufasqSIJk=; b=Li3YELvTffBPET4sHDYIskuPbgUK3wcKlk/c/5oydF/MFXxEY2af8bHXOQbtoT9Gx3 NOT4VpigFB2y7RSSH/G0pH66cmHBcrIgQT1KQIxWwcXhwggXDJRAkN4EiinRt2GrLZI1 SlwSyPqRS1Oecxogon63uD0xcOECjOnluXelC6NJ3lSsjepPLjPd/ne+QsBrQN6ji6+S 716GW5P3T5rcvKKN62KXfOtXu+ZRAcAOgD+8L9Jp9K8jbzEo98Oocdg2bg4vsbVNgnGU 1FzmUG4H+9InH2BDkxzur12LlIUPaqaw/oMB1fcOXMJjnDr2g7zRnS6k7aL5YmChTNMb EQMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=ROFlD7A+My22XCgv95V/ZAgWx49hRQn3rzufasqSIJk=; b=n+PIEr7sT8NjAN1zg+QSBeSs1v0hgCgBXFFt8HvKscJf6p3E3cjEpBTzj71l3t3smT xWLSjkdWfPLHy44NlO2icL8JVgqGcQmeJfi9gsoHtWoPEz63ByRORwF262wcitfe2l5j yLeeqCgsCRxMTSbyg/kvXg4mu+zoP3lkhcnP+YIjgUyqosKi4py/I8WLp0UWYx8lk1fv EFDJsvJDmnZ0L0xdAti7bu5R1NQkyLyXdNLUnzxWYjM7pZY/6m6NbTb028PVHV/mimzT G90L7QblIt2T5WQwjHorI/yW5FeMHbt5ZNC0Z5OeA+aqM2JxtP6zA8no10pUSCe2lE5P FHWQ==
X-Gm-Message-State: AOAM530MeqEKzZSA6tsRo9iuGV9NF17x35P+z8drqEz2OLJ7nzV/fHro a4KJk7o0R0TD+93OXQAsF3EJh0HuuTZV2w==
X-Google-Smtp-Source: ABdhPJx2hydBEcxSHOTfjlM4L9/7anuT8InWFDyzoqFhbNyGE/Kn0ZhrqzdOpXsnTF8v1uuO69uFkA==
X-Received: by 2002:adf:f704:0:b0:211:7eed:4412 with SMTP id r4-20020adff704000000b002117eed4412mr1872612wrp.165.1654142270832; Wed, 01 Jun 2022 20:57:50 -0700 (PDT)
Received: from smtpclient.apple ([2600:1700:4383:c05f:c113:c60c:85e0:93b6]) by smtp.gmail.com with ESMTPSA id v13-20020adfe28d000000b00212a83b93f3sm989391wri.88.2022.06.01.20.57.49 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Jun 2022 20:57:50 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_9D4C3B19-AACF-4BBF-8968-E89B562488FB"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
Subject: Re: Harassment, abuse, accountability. and IETF mailing lists
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <16C5EC99A155D55344E1F195@PSB>
Date: Wed, 01 Jun 2022 20:57:46 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, John C Klensin <john-ietf@jck.com>
Message-Id: <9BFF0439-CE43-42AC-A26B-389EC7EF467B@gmail.com>
References: <16C5EC99A155D55344E1F195@PSB>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Nc539x-xIMKxHvRNnxWn3KeD3WI>
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 03:57:56 -0000

Hi,

My take on this is that lists hosted by the IETF should have the same expectations about conduct.   The difference between w.g. and non-w.g. lists are impossible to detect externally from the list name.

If someone wants to create an IETF hosted list, then they should be willing to abide by a set of IETF rules about conduct (for example, the anti-harassment policies).   If someone wants to have a list that isn’t covered by the IETFs rules, there are a very large number of other places to have it hosted.

Bob




> On Jun 1, 2022, at 1:04 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
> 
>