Re: A contribution to ongoing terminology work
Keith Moore <moore@network-heretics.com> Mon, 05 April 2021 16:27 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 A1B723A1EF3 for <ietf@ietfa.amsl.com>; Mon, 5 Apr 2021 09:27:06 -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 lt93Z13Ky1vN for <ietf@ietfa.amsl.com>; Mon, 5 Apr 2021 09:27:01 -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 3EB653A1EC4 for <ietf@ietf.org>; Mon, 5 Apr 2021 09:27:01 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 9C7765C00BE for <ietf@ietf.org>; Mon, 5 Apr 2021 12:26:59 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 05 Apr 2021 12:26:59 -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=9hJnonEtjJRgIEpHfz5QASf0k3dJvtL+h+2cmRFvd 28=; b=G7H8f0mEwUD+qAdEiim9YvjB+rrRP7wo2pT21NEtSwLsW/qMEKpVUZks0 /KnIHy7jTM1/kFJ2PE6pX02beCgne9IwUJ9zErznhhXwohSTxNBjGOhga/p7yN5W hyxk9yHCMt1Td0gp0H0un7PEBEyBe2pSktUr4hEQXshjLyqLkV1WHKRPqd/HBnB/ tG7h7HmAJi2XLms/5Tq2IGWFUbwILx/xhrQwyRV/ae0P9KAzDWDEKk5kvC1vLd2b SZ6Af278lD/teQDZfM2PgN6Snvr8gfOI1AcU9Rh12kOy5wag6oKaNuj2b7noMuk/ vleE4mab8KKDRoyztihYDlcEyDlbA==
X-ME-Sender: <xms:UjprYPtXfGtSxWMNNcMGUeiCYtqDk7_aLpSaBLK41BORI1e9DgiKlA> <xme:UjprYJZ1JyqoCTiVToN6qpYXcPiYgDl12oNTUXxtymF8A0yk1Ivh6I90UJZYB09Qe GFKp8w8PsJQ0w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudejvddguddtvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ekredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepvefgvddvle egheegtefhgffgtdeujeefteejgfefgeevvdeiudefffevhedvkeelnecuffhomhgrihhn peifihhkihhpvgguihgrrdhorhhgnecukfhppeejfedruddufedrudeiledriedunecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvges nhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:UjprYEvAUX7uYHQw3ZHpqhByaOdC6X4XaFDDEmgyoUvJ4_nDvpLSVQ> <xmx:UjprYLH0SmbOWZ0gB6ewr_aYDNsl0MxEayy14u_-YDavm3lZldnGzQ> <xmx:UjprYPwsv6j7ixcxHFp_LF3GmL_b2qlReAdAzPQWfsnEK-tuc-pc1Q> <xmx:UzprYFKkCdA5hESwp_hPJakfVlhHBmS0H3lKWlOuul-UUwXB7o4CCw>
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 8926824005A for <ietf@ietf.org>; Mon, 5 Apr 2021 12:26:58 -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>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <1bfd3fae-f42e-6bd2-bb75-0d1163379540@network-heretics.com>
Date: Mon, 05 Apr 2021 12:26:58 -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: <F7448554-4B81-48DB-B084-31E39153C131@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/DW1Bp1RbYwIu1KJpeTc19058-2g>
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 16:27:11 -0000
On 4/5/21 11:02 AM, Carsten Bormann wrote: > On 2021-04-05, at 15:53, Keith Moore <moore@network-heretics.com> wrote: >> No, I'm troubled by how the IESG arbitrarily used the Guidelines for Conduct as an excuse to suppress criticism and dissenting voices in order to promote its political agenda while at the same time violating those Guidelines. > 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. > 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. 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 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 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. 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. > > (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. I would recommend that decisions to suppress speech be taken with extreme care, without undue haste, and with full transparency. And for reasons which should now be obvious, this should probably not be something that is within the purview of IESG or the IETF Chair. We need to be able to trust the IESG to evaluate participants' contributions fairly, and such arbitrary actions undermine that trust. And I would hate to think that we shouldn't allow rushed contributions. The fact that we effectively have deadlines means that many submissions are rushed. Keith
- A contribution to ongoing terminology work lloyd.wood@yahoo.co.uk
- Re: A contribution to ongoing terminology work Lars Eggert
- Re: [Terminology] A contribution to ongoing termi… Mallory Knodel
- Re: A contribution to ongoing terminology work Vittorio Bertola
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Benjamin Kaduk
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Masataka Ohta
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Nick Hilliard
- Re: A contribution to ongoing terminology work Behcet Sarikaya
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Benjamin Kaduk
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Marc Petit-Huguenin
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Brian E Carpenter
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Keith Moore
- RE: A contribution to ongoing terminology work Larry Masinter
- Re: A contribution to ongoing terminology work Brian E Carpenter
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work S Moonesamy
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Brian E Carpenter
- Re: A contribution to ongoing terminology work Sam Hartman
- RE: A contribution to ongoing terminology work Larry Masinter
- Re: A contribution to ongoing terminology work Sam Hartman
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Vittorio Bertola
- Re: A contribution to ongoing terminology work Masataka Ohta
- Re: A contribution to ongoing terminology work Masataka Ohta
- Re: A contribution to ongoing terminology work Masataka Ohta
- April 1st RFCs (was Re: A contribution to ongoing… Adam Roach
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Randy Presuhn
- Re: A contribution to ongoing terminology work Brian E Carpenter
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work lloyd.wood@yahoo.co.uk
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Nick Hilliard
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Joel M. Halpern
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work S Moonesamy
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Brian E Carpenter
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Leif Johansson
- Re: A contribution to ongoing terminology work Carsten Bormann
- Re: A contribution to ongoing terminology work Salz, Rich
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Wes Hardaker
- Re: A contribution to ongoing terminology work Viktor Dukhovni
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Phillip Hallam-Baker
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Phillip Hallam-Baker
- Re: A contribution to ongoing terminology work Keith Moore
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Phillip Hallam-Baker
- Re: A contribution to ongoing terminology work Lloyd W
- Re: A contribution to ongoing terminology work Fernando Gont
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Nico Williams
- Re: A contribution to ongoing terminology work Phillip Hallam-Baker
- Re: A contribution to ongoing terminology work Dan Harkins
- Re: A contribution to ongoing terminology work Lloyd W
- Re: A contribution to ongoing terminology work Phillip Hallam-Baker