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

Joel Halpern <jmh@joelhalpern.com> Tue, 07 June 2022 01:53 UTC

Return-Path: <jmh@joelhalpern.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 AB74DC157B45 for <ietf@ietfa.amsl.com>; Mon, 6 Jun 2022 18:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.005
X-Spam-Level:
X-Spam-Status: No, score=-4.005 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, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, 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 (1024-bit key) header.d=joelhalpern.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 0-r-Fi10ihzf for <ietf@ietfa.amsl.com>; Mon, 6 Jun 2022 18:53:49 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 C46C8C14CF08 for <ietf@ietf.org>; Mon, 6 Jun 2022 18:53:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4LHD0s3s6dz1ntmh; Mon, 6 Jun 2022 18:53:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1654566829; bh=OA/p19yqxSx+PER5zHWlmJXucewaqjrOIUbaMMcTic8=; h=Date:Subject:To:References:From:In-Reply-To:From; b=gUIOwgMy20ehrN0Reyb+lVqTAZpvT+SSCkRP5A+XPi//KPwH8kN0KZtf+rmc8yvRa tBOS/wyJ948ZmM/mDwl7LBMTDVcN5Svg6046IEpPhJdcHHslNqvt7z/BE6U+1/gZU9 wuNbPFxsIAhhE+uT4SvQ9dWrYe4Q6eb03pxXC0AA=
X-Quarantine-ID: <4Hc6nC5AAlQa>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.23.181] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (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 mailb2.tigertech.net (Postfix) with ESMTPSA id 4LHD0r5lGbz1nsXq; Mon, 6 Jun 2022 18:53:48 -0700 (PDT)
Message-ID: <955e8c94-1c93-2f6f-c475-e28d91b8f61d@joelhalpern.com>
Date: Mon, 06 Jun 2022 21:53:47 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Subject: Re: Harassment, abuse, accountability. and IETF mailing lists
Content-Language: en-US
To: John C Klensin <john-ietf@jck.com>, 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> <b97e7721-ae59-ab49-7f27-b427e2ef7bc6@gmail.com> <3A57F3D797B85E2F0A862687@PSB> <629B4ACB.8010308@btconnect.com> <A62BB706DDC6044CA7676E0B@PSB> <629DB8E5.7070206@btconnect.com> <a0556611-dc43-9280-1ab1-1ae747b21eff@network-heretics.com> <cba4c1b9-772f-8baa-d0fc-c94701747ec0@gmail.com> <C6E2D9FD91539FC17B7AD498@PSB>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <C6E2D9FD91539FC17B7AD498@PSB>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gX4L457Drus9p5QcOb4Bctss-Rk>
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: Tue, 07 Jun 2022 01:53:53 -0000

If the document were an actual critique with examples of problems, and 
focused on the area (ART) that apparently has had problems, it would 
probably be a useful document.

Yours,

Joel

On 6/6/2022 9:51 PM, John C Klensin wrote:
>
> --On Tuesday, June 7, 2022 08:56 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>
>> On 06-Jun-22 23:56, Keith Moore wrote:
>>> On 6/6/22 04:20, tom petch wrote:
>>>
>>>> I saw an apology for the use of '...considered harmful'
>>>> recently and was suprised that that phrase was .. well
>>>> considered harmful
>>> This makes me wonder: how is making a reference to a letter
>>> that's rather famous in Computer Science history any
>>> different that referring to any established technical term or
>>> concept? Granted not absolutely everyone will have heard of
>>> that letter, but is it really hostile to newcomers to use
>>> well-established language of the subject domain that we work
>>> in when that language isn't, say, sexist or racist?   Is
>> it hostile
>>> to newcomers to refer to the end-to-end principle?
>> I suspect that, as always, context is everything. If somebody
>> had written
>> a draft "6to4 considered harmful" some years ago, I don't
>> think that
>> Keith or I would have been upset. (If you don't get that, see
>> RFC 3056.)
>> But if they had written a draft "Carpenter and Moore
>> considered harmful"
>> we would have been quite angry. Somewhere in between is
>> "Carpenter and Moore's
>> work considered harmful" - I'm really not sure how I would
>> have reacted to that.
>>
>> As a matter of fact that work was subject to a lot of
>> criticism, as was its
>> extension by RFC 3068, but I don't recall a single ad hominem
>> comment.
>>
>> We can be critical without being rude.
> Brian,
>
> I think the problems arise when almost any attempt to be
> critical is interpreted as being at least disrespectful even if
> not actually rude.
>
>     john
>
>
>