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

Benjamin Kaduk <kaduk@mit.edu> Fri, 03 June 2022 05:27 UTC

Return-Path: <kaduk@mit.edu>
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 18AC0C15AAD4; Thu, 2 Jun 2022 22:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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=mit.edu
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 pI0gWqD8enfh; Thu, 2 Jun 2022 22:27:21 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49FE3C1594AF; Thu, 2 Jun 2022 22:27:20 -0700 (PDT)
Received: from kduck.mit.edu (c-73-169-244-254.hsd1.wa.comcast.net [73.169.244.254]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 2535R3db018940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 3 Jun 2022 01:27:10 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1654234032; bh=GAu4vR0VfEsurgQBnfm4X74auO5LOTZ6pCwd7rymLnQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=Q284slDPuMUM7PmppvECYzzxnDhM3jcaC5/Z+zGMSA+TotCaEGYK+Lg6BEOywvaIq J8tGvnlyOZnyUY+oME7DvVaY4+W852I4SoLR5P37nks9rHQxBGKS1Byqz3/LmOGzl+ toZrnhJIBFRigRnCKqab8d8I1n7BuqIu/XHMq1eeLVuKt2ZHsrvh+Uia4sZNrixNBu Hw4vwTZ7Kbkg5/woTZn+Mzr04lfkdeKwE9mwawZN6vPyEo4Ood0jKBvBN09EANqpyA QuoC9q9ysqQXZaBPu8cHuqbl9YDlwS/0NDY9E2jJzPJSamUtDpH7Ru3vZW6+8Uvye8 h/gxwQKpjNbRA==
Date: Thu, 02 Jun 2022 22:27:02 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: John C Klensin <john-ietf@jck.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Pete Resnick <resnick@episteme.net>, tom petch <daedulus@btconnect.com>, IETF discussion list <ietf@ietf.org>, art-ads@ietf.org
Subject: Re: Harassment, abuse, accountability. and IETF mailing lists
Message-ID: <20220603052702.GX28238@kduck.mit.edu>
References: <16C5EC99A155D55344E1F195@PSB> <5a53fa11-8138-2261-0e30-ae603b064cc8@network-heretics.com> <452764b0-a758-874a-2ce5-122f9d0de763@gmail.com> <4520B31984B329BF6936113D@PSB> <6298831D.8030605@btconnect.com> <941D4EB9-8EDF-4612-AD55-251C381C09FB@episteme.net> <e1d5ba16-8c12-cd30-ea4c-762b9225cee4@gmail.com> <10863445C94B1C12A5973429@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <10863445C94B1C12A5973429@PSB>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Gcier1E_e2PJYqDIrurw-7dhkPg>
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: Fri, 03 Jun 2022 05:27:24 -0000

Hi John,

Trimming judiciously, as I am not prepared to comment on all the points you
raise.

On Thu, Jun 02, 2022 at 11:26:32PM -0400, John C Klensin wrote:
> 
> (1) If someone is feeling abused or harassed in conjunction with
> an IETF mailing list, they should have readily-available
> information about who to discuss that with.  That person, or
> choice of people, should have clear responsibility for
> responding to such queries and should be identified by name and
> contact information.   Non-transparent role addresses with
> neither hints about who might receive them nor a clear
> indication that they should be used for such purposes are not
> good enough.  For the (hopefully rare) cases in which action is
> required, those contact people should have either the authority
> needed to enforce our behavior rules or quick access to someone
> with the authority and should be accountable to someone if they
> do not respond in a timely and useful way.

This is not exactly an answer to your question as written, but I believe
that it is always okay to approach an arbitrary AD with concerns of this
nature, and the AD should be able to help locate the appropriate authority
figure.  An arbitrary AD can be selected so as to be uninvolved from any
particular controversy, known to be particularly conscientious, etc.

> 
> Now, let's look at those very important pages from which, among
> other things, one ought to be able to find out who is on said
> hook and, btw, what the list is about.
> 
> * For a typical WG one, the Chairs and AD are listed, but
> without contact information (just a pointer/link to a
> datatracker profile page that does not have that information).
> I believe that is a change although I don't have any idea how
> long ago it was made.   If the observer knows enough to click on

I'm really confused.
Are you talking about the WG lists as listed at
https://datatracker.ietf.org/wg/?  I see links to profile pages, yes, which
includes a table of role/group/email entries, with the email addresses
right there -- I am not sure why you say "does not have that information"
(perhaps you are looking at a different page than I am?).

Interestingly, the list of WGs does include direct mailto: links (the
envelope icon after the name) to the responsible AD, but does not have
those for the chairs.  Perhaps that's the change you're thinking of?

-Ben