Re: tone policing

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 09 September 2019 22:43 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 78018120026 for <ietf@ietfa.amsl.com>; Mon, 9 Sep 2019 15:43:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XkUElD5hsbfr for <ietf@ietfa.amsl.com>; Mon, 9 Sep 2019 15:43:18 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 C3B23120020 for <ietf@ietf.org>; Mon, 9 Sep 2019 15:43:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 46S3925GFDznTcL; Mon, 9 Sep 2019 15:43:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1568068998; bh=RJ5H7c8PbTFqaZzwPhMsAi+NEIVw7sOWPbJbOW4XuUM=; h=Subject:To:References:From:Date:In-Reply-To:From; b=W11r4D6QEiuG0mtKk9cXr52mUrD+aMl/RbYoFaxswV/Fn9uVMH1g7woEkNAfwQ9rX soVl/Tj/ewJOqD0I6sSM47ZTKLWO7ViAjJ4/IP/LTk6BH+asZugWVQxtzB7uK3Q11j zWinu9TWEky5smgVkgc+ukhyiDHwxCyayXj0VkAI=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [172.20.7.244] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 46S3921j7bznTcG; Mon, 9 Sep 2019 15:43:17 -0700 (PDT)
Subject: Re: tone policing
To: Dan Harkins <dharkins@lounge.org>, ietf@ietf.org
References: <F2D6FBAB-7DED-41AE-9560-4D0D13B15107@ericsson.com> <1BF349D9-8ABB-4844-965A-A43964E18A41@fugue.com> <29c10b3d-8f48-8888-68c9-7390b1e4df5d@network-heretics.com> <ae8353f1-adf9-c615-a721-9fba85b40d5c@foobar.org> <059707fd-afea-e4b4-fa77-967e38206c52@network-heretics.com> <737e066d-4646-7021-3466-6a66f8f0a28e@lounge.org> <259BC9E3-EE7B-4152-8BDD-3900D2D75775@network-heretics.com> <B13131F3-BFB5-4C97-B5A4-E96C34CDAB7C@akamai.com> <4cc1dcb9-ae84-2cef-6439-247a5ccd41af@network-heretics.com> <A166D628-8356-4E72-A302-4E45988C1BDB@akamai.com> <daa6c925-8306-cb91-b5a0-bb8c7450eafc@lounge.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <a7a9f058-0acf-fa3b-c96e-c2504caf497e@joelhalpern.com>
Date: Mon, 09 Sep 2019 18:43:15 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <daa6c925-8306-cb91-b5a0-bb8c7450eafc@lounge.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NxAIA-tpOk1R5K4VYYfgpx6AK9A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 09 Sep 2019 22:43:21 -0000

Dan, you asked for specific examples of speech whose acceptability has 
changed.

A clear and simple example is personal attacks.  It is no longer 
acceptable (or at least, we try to make it impossible) to respond to an 
argument by saying "you do not know what you are talking about, so we 
should ignore your input."  Other even more extreme and personal 
comments were once accepted in this community.   they are not accepted 
any longer.

This debate seems to be about how do we handle cases which are not 
simple and obvious personal insults, but can be taken as such.  (Part of 
the complexity lies in who could reasonably take it as an insult and 
when.)   Given what has been acceptable in at least some working groups 
in the recent past, I personally hope we can improve the situation. 
Having said that, I do recognize that we need to avoid going overboard 
and losing the free technical discussion that is the core of our work.

Yours,
Joel

On 9/9/2019 6:27 PM, Dan Harkins wrote:
> 
>    Hi Rich,
> 
> On 9/9/19 1:42 PM, Salz, Rich wrote:
>>      > The world has evolved, and what used to be acceptable is now 
>> commonly seen as less so, and as a worthwhile trade-off for more 
>> inclusivity.  You seem opposed to the IETF doing this, or do I 
>> misunderstand you?
>>>     You misunderstand me.    I do not object to trying to be more 
>>> inclusive,
>>      but I strongly object to imposing arbitrary, poorly-defined 
>> constraints
>>      on IETF contributions.
>> I am sorry if I was not clear.  I am saying "we are choosing to do A 
>> in order to get B"  You are saying "I want B without A"
>>
>> So, like Paul asked: how do you propose to get B without A?
> 
>    You are assuming that if you do A you'll get B.
> 
>    What is this evolution of which you speak? Can you give me specific 
> examples of things
> that used to be acceptable at the IETF but now are commonly seen as less 
> so?
> 
>    I'm pretty sure B in your example is "more inclusive" but I'm not 
> sure what A is.
> 
>    If A is more mentoring then great. If A is more Sunday classes for 
> newcomers then great.
> If A is prohibition on speech that is based on the recipient deeming it 
> "toxic" or "harsh" or
> "hurtful" or some vague word then not great at all.
> 
>    regards,
> 
>    Dan.
> 
> 
>