Re: SAA Do's and Don'ts

Keith Moore <moore@network-heretics.com> Tue, 03 September 2019 00:06 UTC

Return-Path: <moore@network-heretics.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 D1F96120219 for <ietf@ietfa.amsl.com>; Mon, 2 Sep 2019 17:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 tmD3b7GWZ4Iy for <ietf@ietfa.amsl.com>; Mon, 2 Sep 2019 17:06:30 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF8BE1201E0 for <ietf@ietf.org>; Mon, 2 Sep 2019 17:06:30 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E0D3D22025; Mon, 2 Sep 2019 20:06:29 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Mon, 02 Sep 2019 20:06:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=CeePp2OVDTdozjBnp5rwNJNLwA9llUNkFw+o/s+LE pU=; b=P01gA2jPLwv/osshMNyXMmdtv5ENMmkhlGeqzp6QfkrPtdijZ3fANFK9G Bcebz/V509+bIPkCjUu58m5+8BfKN8xq+c0TWwRvFXGgo/g/a5lEzdaGrlDm/JrJ sRaap2pBMh6dAOYvSqeXXsj2OFUIkARL9mEnQlXXYLYSfAwPwf2irfyihCvqZATT iz+QObZfhX2YswQshPKizvAyWIkCA7kXZa++xzwGlRguFm17tQC+Q0rtlaF8A/cz w/HhmUpSOq1CicpW+D/p6LKmttYutyoQvKuH9ChA8fIjuM0FkG+8w7n1SEVp1sVd y7ciQRGhvDaud6zsVDvFfX6A2fa5Q==
X-ME-Sender: <xms:ha5tXdq1MbSmpC0D1_N31i-Ax3kRWiaecp-nvGT3Nt7RFfyWKMZNsg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudejuddgvdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtke ertddtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucfkphepuddtkedrvddvuddrudektddrud ehnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghr vghtihgtshdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:ha5tXcTtZn7PYUA2pT6bYDfSsq6pTM4O7Kplns8tC_1GD2a5c6twsQ> <xmx:ha5tXbN-cVVsx6bbs9UbG8i77Ek7Hw0qS4ADPNllM8BFMGxNcjkwoA> <xmx:ha5tXU0Lny-x_j9mXQvFZlivOe-C4XVaroIUuedpLmujpvJ36GKTSw> <xmx:ha5tXYIkbl8ExHpFTHpnS9rXdIB2_u_Vcj5-22V1Ahtg3duLeGTc9Q>
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 2E95B80059; Mon, 2 Sep 2019 20:06:29 -0400 (EDT)
Subject: Re: SAA Do's and Don'ts
To: ietf@ietf.org
References: <964a7d97-f146-4d2e-aa3e-d39fc08f6f76@Mikes-IPhone> <20190901195210.GA27269@kduck.mit.edu> <f4a03464-9c9d-9ee5-088a-586e2bb326b1@comcast.net> <4100d3fa-3bba-41dc-3df2-bf2d3dc0f667@network-heretics.com> <151220DC34B76BF65A993557@PSB>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <953f194f-8c95-3951-a579-b80afad5ec08@network-heretics.com>
Date: Mon, 02 Sep 2019 20:06:28 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <151220DC34B76BF65A993557@PSB>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i3vfH7BLiiDBOgWDC97rdoQqqPw>
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: Tue, 03 Sep 2019 00:06:44 -0000

On 9/2/19 7:02 PM, John C Klensin wrote:

>> At the same time, I emphatically object to "tone policing" by
>> the SAA or other IETF leadership as being both arbitrary and
>> counterproductive to IETF's purpose, and consider it an abuse
>> of power when it happens.
> Here I mostly agree with Melinda.  That particular term has
> taken on special meanings (whether you are familiar with them or
> accept them or not) and is as much of a problem as the behavior
> to which you are objecting.

Let's not get hung up on the term.   If the term "tone policing" is 
ambiguous I'm fine with using a different term.   But it's a bit tricky 
though, because I've seen so many attacks on speakers with no more 
justification than "tone" cited.  What would you call it?

> If I were to comment on one of
> your suggestions by calling you are jerk (which, for the record,
> I don't think you are and wouldn't do), that is a problem
> because it is abusive behavior and a personal attack, regardless
> of what anyone thinks of my "tone" (whatever that means).   If I
> were to describe a particular proposal as the stupidest idea I
> have ever heard, I hope someone would privately explain to me
> why that sort of terminology and classification doesn't help
> move discussions forward and would do so even if I carefully
> avoided any explicit reflection on the intrinsic intelligence of
> the person who proposed it.  I don't think that is about "tone".
I don't think those examples are about tone either, and neither do I 
think they're representative of the justifications for the attacks on 
speakers' "tone" that I've seen.
> YMMD, but I don't think that trying to move in the direction of
> categories and categories and treating behavior as acceptable or
> not depending on how the categories are defined helps any of us.

IMO, we need much more precise reasons than "tone" or even "harshness" 
to justify sanctioning speakers or even to justify distracting away from 
their contributions.

As far as I can tell, attacks on speakers' "tone" are nearly always either:

(a) a way to distract from the speaker's message for political purposes 
(can't refute their technical argument - just get them frustrated then 
attack their "tone"!), and/or

(b) a way for the attackers to justify their prejudice against the speaker.

If a speaker is really behaving badly, there will be a better 
justification for sanctioning them than "tone".

So basically the attacks on tone need to stop.   They are not only 
counterproductive to IETF's work, they are a form of abuse.

Keith

p.s.  A bit more toward the definition Melinda cited - a hell of a lot 
of people in this world have had to deal with abuse.   If they see the 
world in sharp relief because of it, that's not their fault, and 
sometimes it's even to their advantage because they see things that 
other people miss.   Criticisms of others' tone has the (often 
unintentional, I hope) effect of exacerbating the abuse that others have 
suffered.    And using tone as an excuse to ignore or distract from 
their contributions is just adding insult to injury.   And people don't 
need to know whether or not a speaker has been subject to abuse - it's 
none of their business.