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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 03 June 2022 23:08 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 EFE0AC14F73E; Fri, 3 Jun 2022 16:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.983
X-Spam-Level:
X-Spam-Status: No, score=-3.983 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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 T7nOQBO9quC8; Fri, 3 Jun 2022 16:08:32 -0700 (PDT)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 7EB26C14F72C; Fri, 3 Jun 2022 16:08:32 -0700 (PDT)
Received: by mail-pl1-x632.google.com with SMTP id b5so7778745plx.10; Fri, 03 Jun 2022 16:08:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=gqkint/8yfBrt66DWqNRWSd54wcdKtrZQwYTC7zgi24=; b=Q1Iln9zONPpjbY0uM8Xpryyh/YWpRS4iy7gddsGccyNcX5g5HYCBTHB7EQ4cwmV+wS SsyTQ3lzXVDNd2gJMofanh65mVTTgtKnNj1Cs4vr9r+dicA33OqHLtb5Wd7l0VYcvt5B dPCDg1dM6/6tqAdCnN2JUCi2vBjnKGCL0hY39WJOBe9p34NRnDnXCmi5NsectF6zVMkY lUcOp6taBWoRxWs6j0vlp9InOBw+iRSt6BNDUvY7UOWJ/hPEdN8W2QiuKHp+keBD1lpZ R1zTa6DclFHF0W02o/k12XMVsd0UF8yIMarDNnh2/9YeaKKa/9/Z0jqivNNpylDNIEqH u4ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=gqkint/8yfBrt66DWqNRWSd54wcdKtrZQwYTC7zgi24=; b=1fAUDyWLVRSH/xvCpTAht01DHkQqeGz33mOFavGSXbbY27yKPK9mfDI0sJXg0CAn9h JNBPWseceBA0Huu4XQebKafk/KNMXiDqa0vbY06nK551EXYckj8d85YxsY6HtGWiwql3 mTAu1s9M2SYkFMEnB5TcwF08tY4w4Xbdh8es0ak+TnxG3FTJUjZLPxJWyUB0UYNC/dyX LaO64/nvH4HgfpS/bq8s+VnC6XaCnElVgMhz5B5w+WYWsQb0P5TGJdTrDvozOaINsJrL T6Vg9GzHVoZaDdTBUoxDath8jIjCH/ZV6uImrrgO7HhpEVlNtqlMHvk7ab1vvovt0FEv 30/A==
X-Gm-Message-State: AOAM530OrkGH85h1wlup3HHRgAcklUCeIv0drFfwFPeUq7jE8Iu46PGR raWbRY7Dl3HlUi4KBhEgfq5k1UsHaURvOg==
X-Google-Smtp-Source: ABdhPJx+ZVaSQIK0Bpetr77FDBYTK0iZjz0HDwuSXJ5UGmrDSshtHTXys460rxw/y4pLEwSDptAFZw==
X-Received: by 2002:a17:903:11c7:b0:151:7290:ccc with SMTP id q7-20020a17090311c700b0015172900cccmr12284373plh.95.1654297711716; Fri, 03 Jun 2022 16:08:31 -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 d4-20020a621d04000000b0051b930b7bbesm5897307pfd.135.2022.06.03.16.08.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 03 Jun 2022 16:08:31 -0700 (PDT)
Subject: Re: Harassment, abuse, accountability. and IETF mailing lists
To: tom petch <daedulus@btconnect.com>, Pete Resnick <resnick=40episteme.net@dmarc.ietf.org>, Lars Eggert <lars@eggert.org>
Cc: Carsten Bormann <cabo@tzi.org>, John C Klensin <john-ietf@jck.com>, art-ads@ietf.org, IETF discussion list <ietf@ietf.org>
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> <A92F81D8-057D-4AA0-B94E-427D6F8AB53A@eggert.org> <55B5F6C1-B554-4675-BCD5-048043162D22@tzi.org> <65A1073F-8519-4BDB-B85C-72087B527498@eggert.org> <0325E09B-3B8D-47B5-83B8-ACA5A028B464@episteme.net> <629A3680.9010002@btconnect.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <b97e7721-ae59-ab49-7f27-b427e2ef7bc6@gmail.com>
Date: Sat, 04 Jun 2022 11:08: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: <629A3680.9010002@btconnect.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gJJEZn1vpbxQBPthTAHkBNay6dY>
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 23:08:33 -0000

On 04-Jun-22 04:27, tom petch wrote:
...
> 
> A new non-WG list was announced yesterday including the text 'For
> additional information, contact the list administrators' with no
> indication who they might be or anywhere where they might be identified.
> 
> Yes, administrators are elusive.

The Welcome message after you subscribe is no more helpful (and even
lies: "Normally, Mailman will remind you of your ietf.org mailing list
passwords once every month").

If it isn't possible to patch those messages because they are baked into
Mailman, that's another argument why the pages under our control such as
https://datatracker.ietf.org/list/nonwg should contain the appropriate
contact details.

     Brian