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

Joel Halpern <jmh@joelhalpern.com> Sat, 11 June 2022 23:22 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 8FFAAC14CF09 for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2022 16:22:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.006
X-Spam-Level:
X-Spam-Status: No, score=-4.006 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_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 fRFbg168ChvR for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2022 16:22:30 -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 05E48C14F727 for <ietf@ietf.org>; Sat, 11 Jun 2022 16:22:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4LLDPx403Nz1ntwp; Sat, 11 Jun 2022 16:22:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1654989749; bh=eKvYAlqLATqi27tgBuap84PYEBvBGFdtdEt4ZY5DGPo=; h=Date:Subject:To:References:From:In-Reply-To:From; b=XeQGwsVH2LWAcCdo/mPrvmTQKpS0iuYN8Saky63CH56ND/KZGr7KPPPqeY6ELmM1Q JK238ESDD5zlfzrQAcV1ESeOr0ikCiCIETPe2p/YgXLuy3GRM80vrx6feDukevsZd4 tzkJ9VZvnjFTMEkOW+Px+KqMpSjU0RB9UY49DR1s=
X-Quarantine-ID: <ZsGJ4HMNHzFf>
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)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4LLDPw73F8z1ntR6; Sat, 11 Jun 2022 16:22:28 -0700 (PDT)
Message-ID: <a6a336a2-5501-22e0-3842-9b6c1c4f8a84@joelhalpern.com>
Date: Sat, 11 Jun 2022 19:22:28 -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: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
References: <16C5EC99A155D55344E1F195@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> <8CD09EF0-A825-4539-9B3F-38B881BA4F2D@ietf.org> <6410e897-4a1a-35d7-9564-fe1b9445b2c5@network-heretics.com> <82ACFD06-E4C4-4DB5-A3DE-6543E41F8CB3@ietf.org> <2b247525-b651-1292-940e-fc98c2df84d0@network-heretics.com> <28b0e3d6-8f17-11f6-6d7a-f701adee0833@network-heretics.com> <5fd805da-1247-4b5c-dd0a-b7d577776ba4@joelhalpern.com> <8d6d5e69-560b-f351-a4e1-2b22995d952a@network-heretics.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <8d6d5e69-560b-f351-a4e1-2b22995d952a@network-heretics.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z9_evOKaJw69UhXrv_QjI6qiXKk>
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: Sat, 11 Jun 2022 23:22:34 -0000

Yes, we use "rude" in email.  Yes, the documents use "professional
  or "unprofessional" to which you have objected.  So proposed better 
wording.  Just saying "do not limit things that way" does not help us 
get to a state that works better for the community.

Yours,

Joel

PS: I recognize that there have been some (we can debate how often) 
abuses of these rules to suppress dissent.  I agree that is also very 
bad for the community.

On 6/11/2022 7:03 PM, Keith Moore wrote:
> On 6/11/22 18:12, Joel Halpern wrote:
>
>> If I am reading your email correctly, most of your concern is about 
>> the vague definition and vague applicaiton of "rude".
>>
>> As far as I know, the terms of reference use terms like "personal 
>> attack" and other descriptions which are much less vague.  We tend to 
>> use "rude" as the shorthand for the discussions of the topic rather 
>> than reciting the defintions and descriptions in the RFCs.
>>
>> Do you see the RFCs referring to "rude"?
>>
> I'm mostly responding to Jay here.   But the RFCs use derivatives of 
> "[un]professional" which are equally problematic.
>
> Keith
>
>