RE: Terminology discussion threads

Larry Masinter <LMM@acm.org> Sun, 16 August 2020 00:55 UTC

Return-Path: <masinter@gmail.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 E6D183A0B60 for <ietf@ietfa.amsl.com>; Sat, 15 Aug 2020 17:55:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.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 CmSjtVRkEGM3 for <ietf@ietfa.amsl.com>; Sat, 15 Aug 2020 17:55:00 -0700 (PDT)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36FBF3A0B2C for <ietf@ietf.org>; Sat, 15 Aug 2020 17:55:00 -0700 (PDT)
Received: by mail-pf1-x432.google.com with SMTP id m71so6383759pfd.1 for <ietf@ietf.org>; Sat, 15 Aug 2020 17:55:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=QKgTshFtC78nxEzwC6uZyT7nPXHL0IsOGYaSg+WPO6E=; b=Uiitf2oHdNFPnpUHHJgQeIUzvsnmX86BlKyXngiL7JSf3UWShebl3tVVXM28NRn+c9 zKDu654wQmzLU3M5thoH0QPAk8E8258887vXi4AtG/YG+HgfESHWQeBhgFf5+VPucgWJ X1K8mWfHEg0vUCJr4zgmjxeciug87d36VdNTNBpaVTrqTPZEblA0O1jHa4gVL4g1UhqB bGvx3xHxjlWPvKshYrC1U/JrhHhFeNXYsvZ7EZ+7Tz1cKwH6wV4tijKMEVtun1e9Ihm2 i3oxe1Yx6qNc+5V2trkk00pYbhnsFTf8i7Lb1rUhNGgCbDOsjJfrPBfyIK2jsJBMdXNp IyaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=QKgTshFtC78nxEzwC6uZyT7nPXHL0IsOGYaSg+WPO6E=; b=oqSUazGWCDualX0AVnJ+NtYvZEsQKNetOgaANj3ZXJxX5zbwtV0fAGLoD95wuy8i2i k+AWOAEZy+dgNB7OA3QO0vaQqZZTedG6bvtMMcxLZ4CiYUwSxxR7TJ/eWkdR1STQ8dPl p/5QHmHd8W+E7l5+x6HWBGum3S0kiiC86K5I+nhDhDpV+eYhvcvaGEc9L3bhzU80e5pX tfBf5T3/FfdiubRbLbXYiGTUQ2RSiuGprdsj+u3cMCH0XOQ/fwfuSpbm+sxFvqMFd8X0 iomTyNtNx5O8tCVE9qiOQNJvRNmcIpHbwUdCJJuAxlZqToV0kovPGSq7ydGIR9yIB2J4 +4Fg==
X-Gm-Message-State: AOAM5303NWgSw7ZBta9NIDm3p3uxFs9EVVHzHjRbUxCFfsVns9ZwGpae x/3KYyJb9c3wRPUrK4jBA5ZcX/gjdo0=
X-Google-Smtp-Source: ABdhPJxzRJyB48WAqx3RPn67VyjqqbuRGaYWVwU08w8K1tFwVo9NgX96bny39Dp3eE4fcKe/mfAWVw==
X-Received: by 2002:aa7:9357:: with SMTP id 23mr6710438pfn.278.1597539299284; Sat, 15 Aug 2020 17:54:59 -0700 (PDT)
Received: from TVPC (c-67-169-101-78.hsd1.ca.comcast.net. [67.169.101.78]) by smtp.gmail.com with ESMTPSA id n18sm11489660pgd.91.2020.08.15.17.54.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Aug 2020 17:54:58 -0700 (PDT)
Sender: Larry Masinter <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: 'Dan Harkins' <dharkins@lounge.org>, ietf@ietf.org
Cc: 'Eric Rescorla' <ekr@rtfm.com>, 'Paul Wouters' <paul@nohats.ca>
References: <6AA0BCBB-D95B-4036-B94D-5E79E7B94D75@ietf.org> <F15E387D-9FDC-4A76-8002-78B85F6D16BE@nohats.ca> <CABcZeBNitWbdPO4Y2WfCzjy10Z+s27px6cGT1uRHmtGHa5iX+Q@mail.gmail.com> <ed227fd5-3277-d7a9-f93d-b259944009d6@huitema.net> <7ec6f897-fd3e-8a22-cf6e-ea457d745982@lounge.org>
In-Reply-To: <7ec6f897-fd3e-8a22-cf6e-ea457d745982@lounge.org>
Subject: RE: Terminology discussion threads
Date: Sat, 15 Aug 2020 17:54:57 -0700
Message-ID: <019f01d67367$dd343420$979c9c60$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGA/aN3Qdc/Y7KDDzYlYf/IbFDwZgHZfQsXAcygnvwCVuQuPAMAfvN4qZs4QGA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PRfwc_DX-3BIPaVpMyJPbdA0HFI>
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: Sun, 16 Aug 2020 00:55:02 -0000

The IETF designs its processes in the various BCPs using the skills of protocol designers in these network-intermediated human-to-human protocols.

Meetings, virtual-meetings, emails, chat rooms, mailing lists, internet-drafts, RFCs, are all human-to-human protocols, along with nomcom and SaS.

As with most Internet protocols, we need to change how we work in response to changing conditions.  As with most Internet protocols, we have to balance the requirements of the different types of participants, and that results in some balance and sometimes friction depending on "whose ox is being gored". 

As with most Internet protocols, it is in some cases necessary to protect the systems from disruption, either by intention, or unintentional side effects of our protocol implementations.

In general, human recipients of communications (such as emails or internet drafts or published RFCs) have, as part of their input function, varying degrees of reaction "finding the language offensive", which interferes with their ability to receive the technical content of the communication.

Those who communicate with many recipients (especially through long-term archived communications such as internet-drafts and RFCs) should choose language that conveys the technical content without the "offended" reaction.
The same robustness rules apply on widely subscribed mailing lists.

Five years ago about, I left the appsarea mailing list, because I was offended, and unable to convince anyone to act further than to admonish the poster and, incredibly, me.
What heinous phrase had he used that I found so offensive?
 That I "sounded like a bulldog farting out a nest of angry wasps".
It really drove me crazy. "Why not a chihuahua? Or a Saint Bernard? 
"Why wasps and not bumblebees?"    So I unsubscribed.

My point in telling this story is that there is no clear, identifiable boundary between language that would cause participants to leave the group or choose not to engage, and language that is not. It doesn't mean there is no difference. 

The IETF is a global, apolitical technical decision-making body. Attacks on such bodies are widespread. Trolls and sock-puppets are well-known vectors for disruption, and getting us to focus on nonsense (perhaps this message? I hope not). 

In the meanwhile, try not to offend anyone, or to be easily offended.

--
https://LarryMasinter.net https://interlisp.org