Re: Describing which behavior is appropriate or not (was: Last Call: <draft-eggert-bcp45bis-06.txt> (IETF Discussion List Charter) to Best Current Practice)
Keith Moore <moore@network-heretics.com> Sat, 30 October 2021 22:31 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 D95573A140D for <ietf@ietfa.amsl.com>; Sat, 30 Oct 2021 15:31:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.229
X-Spam-Level:
X-Spam-Status: No, score=-5.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-3.33, RCVD_IN_MSPIKE_H2=-0.001, 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 tThzY7u6FjrQ for <ietf@ietfa.amsl.com>; Sat, 30 Oct 2021 15:31:15 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 249253A140A for <ietf@ietf.org>; Sat, 30 Oct 2021 15:31:14 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 342F13200A39; Sat, 30 Oct 2021 18:31:09 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 30 Oct 2021 18:31:09 -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=fm1; bh=tg2fM7PQq+uGRwECGvjKWOalhi4mvC1S+lIYgK2V5 r0=; b=ZDv1QIHRqz1/gO9jxcbASQnneJrfMT6PfxRu77TznO2qcs0oNOqF6o/Rp dV+J+RSsC0R/F1ViR6zb/wIsqomEm/3mVa0XSKUdN2EN/zbIHVhAyyge8bws4LKc 9Da3dSePfgbY671V7aMMQez7kvhd0X+0tK7UUESb9Dbo5u/OwhbYpdd8fhawROlJ cwjPp+8kvpt59UkWvs7jhbP/PAL2rH5ZL5bUHfdYLU53UVGo3e+P0o/3U7CBMA8k mpDhPAwdbVie7H8OLo5CXLuLjx+jzwJpQeqgJI0lP7Hs9uVEex/2PPQdfLtLYVSW LitAv3hH6RUxHchW8lTWQIu+RVoUA==
X-ME-Sender: <xms:rMd9YftFOvX2dtMyPRb49_cY0n7oYrhpTPVqsImaKJyu5nVL2T77-w> <xme:rMd9YQdqCTrPqLkfzSq9lE84DPk8YPpEKu935NqhYvp7w7f8sAfqkJdMPGOf_Iit7 mpZpoS9T8d4jA>
X-ME-Received: <xmr:rMd9YSzHGPOoaiSFSOhfslt7pcl-lXE_z40uOcY8ADDI7mbrvoZauzX_Fhsl_aABm2jutof5b7weXdmhEC7sBFRt4k1_xfZ0DKkmy4jO9A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvdegkedguddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdlqddutddmnecujfgurhepuf fvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhr vgcuoehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrf grthhtvghrnhepffetffejtefgffekteduveduledukeefieefgeetvdefieelgfffkeeg geevgedtnecuffhomhgrihhnpehushgtohhurhhtshdrghhovhenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhk qdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:rMd9YePB8c2a96OZJznGm_3bxwnJIohv0iS0Pxnp-MxqcEG602tCRQ> <xmx:rMd9Yf9DqbdLcDsiAksznb-wjcT0koUmlXJZz7bn2eLKNKgv7ksChg> <xmx:rMd9YeWpI5iAOirmbvl_FoWZ_L4aD9JHxT4OgHkGD2UBjKvu_O-Alg> <xmx:rMd9YcI22G8hhxuOv9ASimJR-cn3Ddc_2o7Ue4bp7QOj_WTueORUpg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 30 Oct 2021 18:31:08 -0400 (EDT)
Subject: Re: Describing which behavior is appropriate or not (was: Last Call: <draft-eggert-bcp45bis-06.txt> (IETF Discussion List Charter) to Best Current Practice)
To: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
References: <163465875866.13316.15860075014903480611@ietfa.amsl.com> <EA85619D-83D6-409B-AAE7-C13850B18BA0@yahoo.co.uk> <CALaySJKeHDr7EJy4hf5GyS9W0PwpQ0C05TGtS4Gc_ihEFeQtsA@mail.gmail.com> <34ec2302-edc3-e180-be00-4d7200372d5f@network-heretics.com> <6.2.5.6.2.20211030023629.075c8550@elandnews.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <47db1859-8201-9f37-0efd-aa09f4b1379b@network-heretics.com>
Date: Sat, 30 Oct 2021 18:31:07 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <6.2.5.6.2.20211030023629.075c8550@elandnews.com>
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/JuneP-xbVmKLFzaFBYc-nmh97o8>
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: Sat, 30 Oct 2021 22:31:20 -0000
On 10/30/21 7:39 AM, S Moonesamy wrote: > Hi Keith, > At 03:53 PM 20-10-2021, Keith Moore wrote: >> The aggregate effect of such efforts is to make IETF more like an >> echo chamber, in which everyone is expected to "know their place" - >> i.e. know to not express views that might conflict with the views of >> those in power, or otherwise know the unwritten "rules". This is, >> after all, often what is expected of "professionals" in their >> workplaces, which is yet another reason why "professional" is a poor >> criterion for describing which behavior is appropriate or not in IETF >> discussions. > > I read comments about the word "professional" in a RFC over the > years. Here is another comment [1] (translated with Yandex): > > "Unfortunately, this RFC feels obliged to add that it is necessary > to behave > in a professional manner as if amateurs were avinee brutes and that > it is > only in the context of work that one can be civilized." > > The sentence with that word was the "IETF Consensus" when the RFC was > approved for publication. The "know their place" was removed during > the revision of the document. There isn't anything in the RFC which > prohibits a participant from expressing his/her disagreement with an > Area Director's decision. > > One of the points which you raised is about "a system in which people > are placed in a series of levels with different importance or > status". The RFC does not establish a system with different levels of > importance or status. For me a lot of the problem is that the word "professional" has many different meanings, and is therefore ambiguous. One interpretation of "professional behavior" seems to be norms of a corporate workplace. But corporate workplaces have many restraints on speech and behavior which aren't appropriate for IETF. For example, publicly criticizing your employer, or its leadership, or its policies, or its products, can get you fired. But IETF should be open to public criticism, even by (perhaps especially by) its participants. Another interpretation of "professional" refers to a group of persons who are all make their living in the same trade. It can even carry with it the assumption that "professionals" are privileged somehow. (There's a joke: "Why don't sharks eat lawyers?" "Professional courtesy.") But IETF is open to participation by everyone, and its participants should treat each other as peers, regardless of how they earn their living or even whether they are employed. It's hard to escape the impression that some of those insisting on "professional behavior" are looking for a way to exclude those who they deem not qualified, so as to get out of the way of the Big Corporations who want IETF to do what they want it to do. Anyway, if "unprofessional behavior" is not defined, those in power can use any deviation from "normal" as an excuse to sanction participants. But I also realize that maybe this doesn't matter much, as the scope of this document is limited to the IETF list which is of decreasing relevance anyway. The IETF list used to serve as the primary forum of the community, its center, and also its conscience. This draft along with several other IMO extremely harmful measures that have been taken in recent years (including the creation of gendispatch) narrows the scope of the IETF list so much that it effectively destroys most of the utility that the IETF list used to have, and with it the organization's core values. I don't know why people think that the solution to traffic overload is to keep siloing discussions ad infinitum, and I would argue that one of IETF's core problems has long been the over-fragmentation of discussions. Or maybe the fragmentation of the IETF list was part of a deliberate effort to subvert the IETF into being a forum that only serves the Internet industry, rather than one trying to serve the broader Internet community? > > The underlying value for some participants is most likely related to > https://www.uscourts.gov/about-federal-courts/educational-resources/about-educational-outreach/activity-resources/what-does > A participant residing in another country might not have the > background information to understand those participants. It takes > many years to understand all that. These rules don't really apply to discussions like the IETF list, even in the United States. Governments within the US are forbidden from penalizing most kinds of speech. But those restrictions on government don't prevent the moderation of discussions hosted by non-governmental organizations such as IETF, or for that matter discussions on social media sites. But it may well be true that US citizens and longtime US residents, accustomed to having few government prohibitions on speech, are somewhat more outspoken than those from elsewhere. Keith
- Re: [Gendispatch] Last Call: <draft-eggert-bcp45b… Lloyd W
- Re: [Gendispatch] Last Call: <draft-eggert-bcp45b… Lars Eggert
- Re: [Gendispatch] Last Call: <draft-eggert-bcp45b… Barry Leiba
- Re: [Gendispatch] Last Call: <draft-eggert-bcp45b… Bron Gondwana
- RE: [Gendispatch] Last Call: <draft-eggert-bcp45b… STARK, BARBARA H
- Describing which behavior is appropriate or not (… S Moonesamy
- Re: Describing which behavior is appropriate or n… Marc Petit-Huguenin
- Re: Describing which behavior is appropriate or n… Keith Moore
- Re: Describing which behavior is appropriate or n… Lloyd W
- Re: Describing which behavior is appropriate or n… Lloyd W
- Re: Describing which behavior is appropriate or n… Keith Moore
- Re: Describing which behavior is appropriate or n… Sander Steffann
- Re: Describing which behavior is appropriate or n… Brian E Carpenter
- Re: Describing which behavior is appropriate or n… S Moonesamy
- Re: Describing which behavior is appropriate or n… Keith Moore
- Re: Describing which behavior is appropriate or n… Lloyd W
- Re: Describing which behavior is appropriate or n… Keith Moore
- Re: Describing which behavior is appropriate or n… Lloyd W
- Re: Describing which behavior is appropriate or n… Keith Moore
- Re: Describing which behavior is appropriate or n… Miles Fidelman
- Re: Describing which behavior is appropriate or n… S Moonesamy
- "professional" in an IETF context Keith Moore
- Re: Describing which behavior is appropriate or n… S Moonesamy
- Re: "professional" in an IETF context Brian E Carpenter
- Re: "professional" in an IETF context Keith Moore
- Re: "professional" in an IETF context Stephen Farrell
- Re: "professional" in an IETF context David Farmer
- RE: "professional" in an IETF context Andrew Campling
- Re: "professional" in an IETF context Keith Moore
- Re: Describing which behavior is appropriate or n… Jay Daley
- Re: Describing which behavior is appropriate or n… Stephen Farrell
- RE: Describing which behavior is appropriate or n… Vasilenko Eduard
- Re: "professional" in an IETF context Abdussalam Baryun
- Re: "professional" in an IETF context Masataka Ohta
- Re: "professional" in an IETF context Miles Fidelman
- Re: "professional" in an IETF context Miles Fidelman
- Re: "professional" in an IETF context Masataka Ohta
- Re: "professional" in an IETF context Joel M. Halpern
- Re: "professional" in an IETF context Masataka Ohta
- Re: "professional" in an IETF context Behcet Sarikaya
- Re: "professional" in an IETF context Stewart Bryant
- Re: "professional" in an IETF context Keith Moore
- Re: "professional" in an IETF context Keith Moore
- Re: "professional" in an IETF context Templin (US), Fred L
- Re: "professional" in an IETF context Miles Fidelman
- Re: "professional" in an IETF context Miles Fidelman
- Re: "professional" in an IETF context Miles Fidelman
- Re: "professional" in an IETF context Brian E Carpenter
- Re: "professional" in an IETF context Stewart Bryant
- It's a trap (Re: "professional" in an IETF contex… Carsten Bormann
- Relitigating history [Re: "professional" in an IE… Brian E Carpenter
- Re: "professional" in an IETF context Scott Bradner
- Re: It's a trap (Re: "professional" in an IETF co… Lloyd W
- Re: "professional" in an IETF context Abdussalam Baryun
- Re: "professional" in an IETF context Miles Fidelman
- Re: "professional" in an IETF context Masataka Ohta
- RE: "professional" in an IETF context Vasilenko Eduard
- interface ID (was Re: "professional" in an IETF c… Masataka Ohta
- Accurate history [Re: "professional" in an IETF c… Brian E Carpenter
- Re: Accurate history [Re: "professional" in an IE… Stewart Bryant
- Re: Accurate history [Re: "professional" in an IE… Stewart Bryant
- Re: Accurate history [Re: "professional" in an IE… Scott O. Bradner
- Re: Accurate history [Re: "professional" in an IE… Brian E Carpenter
- Re: Accurate history [Re: "professional" in an IE… Masataka Ohta
- Re: Describing which behavior is appropriate or n… tom petch
- RE: Accurate history [Re: "professional" in an IE… Vasilenko Eduard
- Re: Ancient history (was Accurate history was [Re… Eliot Lear
- Re: Ancient history (was Accurate history was [Re… Masataka Ohta
- Re: Describing which behavior is appropriate or n… Bron Gondwana
- RE: [EXTERNAL] Re: Ancient history (was Accurate … Templin (US), Fred L
- Re: Accurate history [Re: "professional" in an IE… Brian E Carpenter
- Re: "professional" in an IETF context Phillip Hallam-Baker
- Re: Describing which behavior is appropriate or n… Phillip Hallam-Baker
- RE: "professional" in an IETF context Vasilenko Eduard
- RE: Accurate history [Re: "professional" in an IE… Vasilenko Eduard
- Re: Describing which behavior is appropriate or n… tom petch
- Re: Describing which behavior is appropriate or n… Carsten Bormann
- Re: Describing which behavior is appropriate or n… Masataka Ohta
- Re: Describing which behavior is appropriate or n… Keith Moore
- Re: Accurate history [Re: "professional" in an IE… Masataka Ohta
- Re: Accurate history [Re: "professional" in an IE… Greg Shepherd
- Re: Accurate history [Re: "professional" in an IE… Behcet Sarikaya
- Re: Accurate history [Re: "professional" in an IE… Nick Hilliard
- RE: Accurate history [Re: "professional" in an IE… Vasilenko Eduard
- RE: Accurate history [Re: "professional" in an IE… Vasilenko Eduard
- Re: Accurate history [Re: "professional" in an IE… Keith Moore
- Re: Describing which behavior is appropriate or n… Bron Gondwana
- Re: Describing which behavior is appropriate or n… Bron Gondwana
- Re: Accurate history [Re: "professional" in an IE… Phillip Hallam-Baker
- RE: Accurate history [Re: "professional" in an IE… Vasilenko Eduard
- Re: Accurate history [Re: "professional" in an IE… Masataka Ohta
- Re: Accurate history [Re: "professional" in an IE… Masataka Ohta
- Re: Accurate history [Re: "professional" in an IE… Scott Bradner
- Re: Accurate history [Re: "professional" in an IE… otroan
- Re: Accurate history [Re: "professional" in an IE… Nick Hilliard
- RE: Accurate history [Re: "professional" in an IE… Vasilenko Eduard
- Re: Accurate history [Re: "professional" in an IE… Nick Hilliard
- Re: Accurate history [Re: "professional" in an IE… Stewart Bryant
- Why IPv6 failed [Re: Accurate history [Re: "profe… otroan
- Re: Accurate history [Re: "professional" in an IE… Masataka Ohta
- Re: Describing which behavior is appropriate or n… S Moonesamy
- Re: Describing which behavior is appropriate or n… S Moonesamy
- Re: Describing which behavior is appropriate or n… S Moonesamy
- Re: Accurate history [Re: "professional" in an IE… Geoff Huston
- Re: Accurate history [Re: "professional" in an IE… Brian E Carpenter
- Re: Accurate history [Re: "professional" in an IE… Brian E Carpenter
- Re: Accurate history [Re: "professional" in an IE… Brian E Carpenter
- RE: Accurate history [Re: "professional" in an IE… Vasilenko Eduard
- Re: Accurate history [Re: "professional" in an IE… Brian E Carpenter
- Re: Accurate history [Re: "professional" in an IE… Erik Kline
- RE: Accurate history [Re: "professional" in an IE… Vasilenko Eduard
- Re: Accurate history [Re: "professional" in an IE… Masataka Ohta
- Re: Describing which behavior is appropriate or n… Keith Moore
- Re: Describing which behavior is appropriate or n… Abdussalam Baryun
- Re: Describing which behavior is appropriate or n… ned+ietf