Re: A contribution to ongoing terminology work

Keith Moore <moore@network-heretics.com> Mon, 05 April 2021 17:30 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 2517D3A20D1 for <ietf@ietfa.amsl.com>; Mon, 5 Apr 2021 10:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=0.001, URIBL_BLOCKED=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 XI6abzBKpDxe for <ietf@ietfa.amsl.com>; Mon, 5 Apr 2021 10:30:39 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E0BF3A20CA for <ietf@ietf.org>; Mon, 5 Apr 2021 10:30:38 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 398975C00E6 for <ietf@ietf.org>; Mon, 5 Apr 2021 13:30:36 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 05 Apr 2021 13:30:36 -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=fm2; bh=KU2E/v4Ctr8fTE25vnTB7ah2B31A8rUkVA2iiF/qc xs=; b=MdJYrWZa/I4h/mqPdGfNWlQ3uO1+hdc8onEF8hBM/U1pNZl6AHu+cKd3p 8l19CewO19Kz/24FrFzUGehyprFL3hg+GJosVwbw+x4dQjViqxT24ygQPBXHf+Sc QizVviC43D6JMOCF9MYkofRynKRKMjfQCw+kb+MEhoGbRis+cxIiDbJIji1UTKqh XKNfYMpF/Zt2gBSsboQAPtez1lwt+yK2IJdwyDCAamXhxTCJmAFyK0rYzLS9m3jX Ymk7qIG7MFDf8x5PVbVetrKnvhp8ilNQwaUH0Zj39FG+ZFYOzZcdwS6a1owJBZcY cemE6AGpR+xOYt5sOMWO1TnLL5w4w==
X-ME-Sender: <xms:O0lrYFvc_qRU0kLuZkl9b6q8tQaCT7qiOXbzkHTnhh-AZW4Oxrrefw> <xme:O0lrYOYV17Dcj7UuQPENvCK7eYgy5f_4JXyxG2wq9BVPtE19qPmv5GKMWeBd5-Ccs fHJ4xG5tj5PEQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudejvddgudduhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ekredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepvefgvddvle egheegtefhgffgtdeujeefteejgfefgeevvdeiudefffevhedvkeelnecuffhomhgrihhn peifihhkihhpvgguihgrrdhorhhgnecukfhppeejfedruddufedrudeiledriedunecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvges nhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:O0lrYFrsbc5h8gT6a73qDY9zMFmY8tz7GNJDb3aXIL8v7XXHKlA-5w> <xmx:O0lrYD9ryVe9ePCqXfmwAlyqPlaaotzy1cMzEDot-KbY2iHi2vu9KA> <xmx:O0lrYE9NMOaCRpP7fJ9KI4m7PAy67nnQbd-ROgCJ3nR-Rfi3CuqVaQ> <xmx:PElrYPme7lBY_PAwghSsBXhP0tdnRkKXTbZcralHO89_nxm9JT_18w>
Received: from [192.168.30.202] (c-73-113-169-61.hsd1.tn.comcast.net [73.113.169.61]) by mail.messagingengine.com (Postfix) with ESMTPA id B230F24005A for <ietf@ietf.org>; Mon, 5 Apr 2021 13:30:35 -0400 (EDT)
Subject: Re: A contribution to ongoing terminology work
To: ietf@ietf.org
References: <1e4feea2-2c81-b31a-04e3-d4c9a4adbaf7@lounge.org> <20210402163230.GH79563@kduck.mit.edu> <4c82de79-1e40-2eed-909b-8a288284393d@lounge.org> <439a33c9-5791-4c90-76a3-54aab828a37d@network-heretics.com> <5C955F3B-2EE7-43DD-85BA-DA1C1CF353F1@tzi.org> <7b3ba302-ec36-eb8d-7461-861a0b6651ac@network-heretics.com> <0dca7a0d-d51e-4c67-cc96-a44de0141480@gmail.com> <9c369a34-d47c-3af0-9793-8342f5f6ec63@network-heretics.com> <c613095d-f0b4-8df7-e703-d1b3c52bffc5@gmail.com> <tslpmzctgoi.fsf@suchdamage.org> <20210404201640.GD3828@localhost> <b24abb42-2876-40d8-2130-e80c01096e7f@alumni.stanford.edu> <9cb4a281-be2f-92b2-b883-736624788e59@network-heretics.com> <F7448554-4B81-48DB-B084-31E39153C131@tzi.org> <1bfd3fae-f42e-6bd2-bb75-0d1163379540@network-heretics.com> <EA7C8D78-1839-450C-848C-F4A8B6244F0C@tzi.org>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <e8d83506-a49f-8a47-148f-6c55a89c0bd5@network-heretics.com>
Date: Mon, 05 Apr 2021 13:30:34 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <EA7C8D78-1839-450C-848C-F4A8B6244F0C@tzi.org>
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/d10CZ7BpOzQ2147b2aVfXIXT2ho>
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, 05 Apr 2021 17:30:44 -0000

On 4/5/21 1:02 PM, Carsten Bormann wrote:

> The discussion in this thread has grown completely useless because it is layer upon layer of irrelevant distraction, discussing general statements, while the specifics are rather clear.  But to play on with the game...
>
>>> https://en.wikipedia.org/wiki/Griefer
>> I don't think that's a valid accusation, or at least I don't see the similarity.   There's a huge difference between trying to illustrate a problem versus stirring up trouble just for the sake of amusement.
> The effect (of someone stirring trouble because of a failed attempt at illustrating a problem or just for amusement) is the same (and I was admonished not to do too much inference about intents already).  If the IETF makes its rules in such a way that it can’t deal with griefers because it never can be certain about the intent, we are in trouble.
I might actually agree with the latter statement.   But it's really easy 
to dismiss constructive criticism for the wrong reasons.
>>> More gravely speaking, the founding principle of the country I’m living in is that one needs to be vigilant against attempts to destroy its freedom.  I fully subscribe to this principle, even if it means that Nazis don’t get freedom of speech here.
>> Ok but there's more than one way of interpreting that principle even among those who fully subscribe to it.  One is that freedom of speech (for example) must be preserved even though it sometimes makes people uncomfortable; another is that certain groups known to cause malice have their freedom of speech curtailed. Reasonable people should be able to disagree about which approach is better.
> “Uncomfortable” is not a useful scale.  Truth is often uncomfortable.
> I’m all for shutting up malice.  Countries have to do this with extreme care, organizations not quite as much.  Checks and balances are good in either case.
If IESG are seen as arbitrary, their role in deciding community 
consensus is very much in doubt.
>> And if those Internet-Drafts have resulted in a conversation about the propriety of suppressing speech that is critical of popular ideas, I think that's a Good Thing, and probably a necessary thing, even if it makes some people uncomfortable.
> I think it is a bad thing, because it is a waste of time to discuss nuances of general principles when the point was to act, fast.
IMO the undue haste is very much an example of the problem.
>> I am continuing to press this issue because I wish to be vigilant against degradation of IETF's traditions of openness and consensus-based decision-making.
> I understand that, but the level of noise is already a (D)DoS attack.
Well, "noise" is rather subjective.   I wouldn't be bothering if I 
didn't think it was both important and fixable.
>> I am also profoundly uncomfortable with an idea that IETF participants have a duty to not "rock the boat" because I've so often seen in other contexts how that social convention protects abuse, corruption, discrimination, and/or irresponsible behavior.
> There is a spectrum between the Catholic Church of Germany and a henhouse [forgive me if I shouldn’t use that term].  I think we are rather close to the henhouse.
>
> And there is indeed a duty of members of an organization not to damage that organization.  That has to be balanced with other duties, as the Catholic Church of Germany is slowly learning now, but it is a duty.

But if the organization is already damaged, isn't there also a duty to 
try to fix it?

>> I realize that many people implicitly consider this duty part of "professional" behavior, and I explicitly reject the idea that it's desirable.   I do think that one should consider whether "rocking the boat" will make things better or worse overall, but there's no general duty to not do so.
> Duty I don’t know, but there should be a reason for actions that waste a lot of energy.
Again, "waste" is subjective.
>>> (OK, the amount of transfer effort needed to translate these principles to what’s going on in the IETF right may be high — IETF is no country, but the point is that not every dissent is noble and deserves protection.  That is not an easy line to ride, but relitigating ad nauseam every decision the IESG makes to protect the IETF is not productive.  The submitter has even made known that he now considers his contribution rushed, and has apologized!  My mother would have said: Schwamm drüber.)
>> This wasn't just any decision, it was a decision to suppress speech that was (in my interpretation) critical of potentially harmful ideas and even of IETF leadership.
> Several people here have explained why this was the right decision.
> Apart from overly general fundamental considerations, I haven’t heard anyone actually coherently argue it wasn’t.
I have made such arguments and have yet to see a convincing argument to 
the contrary.
> Of course, we need appeals processes and all that to handle abuse of power.
> We do have that!

Better to try to have a constructive discussion first, I think, before 
trying those.

Keith