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

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 03 June 2022 18:00 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 015E5C14F74E for <ietf@ietfa.amsl.com>; Fri, 3 Jun 2022 11:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.708
X-Spam-Level:
X-Spam-Status: No, score=-1.708 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=sandelman.ca
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 ZcjdtfIj-6gk for <ietf@ietfa.amsl.com>; Fri, 3 Jun 2022 11:00:44 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 DC929C14F736 for <ietf@ietf.org>; Fri, 3 Jun 2022 11:00:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 6DAD039A4B; Fri, 3 Jun 2022 14:15:44 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gxNjp3WcjZpc; Fri, 3 Jun 2022 14:15:43 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4FA2E39A35; Fri, 3 Jun 2022 14:15:43 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1654280143; bh=fp0Cjw2RkEt5QNNJ4f7zDrqZrLbys3P29YO5pJZa0Jw=; h=From:To:Subject:In-Reply-To:References:Date:From; b=Z1JB2n3IJMD/hQBLPfcinCkRM2sbpuHCjwdoACa3Z56/Wu9JmoXHXjYXoR9j0X00V HJGbymoILmVtofHgCy1bgPJp5b7paqoqq0I5+x9fXC3eUDoKp2LUHROJIoa+kT9XYv yB2oEfNj+x1cZpMfmMKTQWgVgsVZqiAy4Ls3KrYE+5+dLM07n6gJc6Ij6dZg3NNiBG bCHOC7Rih01wjpHuebG58oWL+rZqq2r24sEjYedMAUyfQQ6drOIjkOWM7Y5Sppe2U4 5ZpkXh/pC4hv1ft08cD9ojY750DAaBq26k4A+bMBeDk96++D3orlIwhAlTltfBiKNh JTrqaE0t3PhMQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 66E11683; Fri, 3 Jun 2022 14:00:42 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Pete Resnick <resnick=40episteme.net@dmarc.ietf.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: Harassment, abuse, accountability. and IETF mailing lists
In-Reply-To: <941D4EB9-8EDF-4612-AD55-251C381C09FB@episteme.net>
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>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 03 Jun 2022 14:00:42 -0400
Message-ID: <28986.1654279242@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1iGxsMLcT087WGHNIIE_vHQJ2mk>
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 18:00:49 -0000

Pete Resnick <resnick=40episteme.net@dmarc.ietf.org> wrote:
    > On 2 Jun 2022, at 4:30, tom petch wrote:

    >> How about
    >>
    >> <list-name>-owner
    >>
    >> making it clear in future to those who take on that responsibility that
    >> that is part of their responsibility?

    > Yes, but the email address and/or name of the human(s) on the other end of
    > <list-name>-owner needs to be easily and publicly available.

And the expansion of <list-name>-owner alias will need to be DMARC safe too.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide