IETF Logo Mail Archive

Re: [Terminology] We should avoid childish acronyms as well

reynolds@cogitage.pairsite.com Tue, 11 January 2022 17:43 UTC

Return-Path: <reynolds@cogitage.pairsite.com>
X-Original-To: terminology@ietfa.amsl.com
Delivered-To: terminology@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ADD13A0C0A for <terminology@ietfa.amsl.com>; Tue, 11 Jan 2022 09:43:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.496
X-Spam-Level:
X-Spam-Status: No, score=-0.496 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 MTaUvIg20USf for <terminology@ietfa.amsl.com>; Tue, 11 Jan 2022 09:43:31 -0800 (PST)
Received: from www1.webmail.pair.com (www1.webmail.pair.com [209.68.6.94]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6932B3A0C07 for <terminology@ietf.org>; Tue, 11 Jan 2022 09:43:31 -0800 (PST)
Received: from rc.webmail.pair.com (localhost [127.0.0.1]) by www1.webmail.pair.com (Postfix) with ESMTP id ADDAB1A1062; Tue, 11 Jan 2022 12:43:29 -0500 (EST)
MIME-Version: 1.0
Date: Tue, 11 Jan 2022 12:43:29 -0500
From: reynolds@cogitage.pairsite.com
To: Dan Harkins <dharkins@lounge.org>
Cc: terminology@ietf.org
In-Reply-To: <538e446e-1624-f517-fba0-c8ca4674d522@lounge.org>
References: <CAMm+LwgpVzCVkEuv4NMfLJ9KhnAyUoD0sCqKj8WaAfoScuBnMA@mail.gmail.com> <11986BE7-1C65-49F8-8615-2A622C6B311E@kuehlewind.net> <MN2PR06MB6559A862E85C2910969F7646F8509@MN2PR06MB6559.namprd06.prod.outlook.com> <389f5791-14b8-1a91-77fc-1a86048ab5cf@lounge.org> <CAMm+LwhWqmyZrFsc=xbBHUDnjBoNvxeh18OiocDsZm521uM3xA@mail.gmail.com> <538e446e-1624-f517-fba0-c8ca4674d522@lounge.org>
Message-ID: <e60d3cb783ad1bd280a5bd4d02a879e4@cogitage.pairsite.com>
X-Sender: reynolds@cogitage.pairsite.com
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/EqdvJPKGYAREFO2Gy9Hv3XTjmqU>
Subject: Re: [Terminology] We should avoid childish acronyms as well
X-BeenThere: terminology@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Effective Terminology in IETF Documents <terminology.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/terminology>, <mailto:terminology-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/terminology/>
List-Post: <mailto:terminology@ietf.org>
List-Help: <mailto:terminology-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/terminology>, <mailto:terminology-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2022 17:43:34 -0000

On 2022-01-10 17:20, Dan Harkins wrote:
> Divining for offense is a popular pastime these days so the fact
> that someone somewhere was offended by an IETF backronym should 
> surprise
> absolutely no one. This really took off when the definition of offense
> changed from intention of the speaker to how the recipient felt about
> it and being offended started to be used as a cudgel. It's basically a
> power-grab-- I take offense at your words and you must now grovel to
> my satisfaction.
. . .

"Sticks and stones may break my bones, but names will never hurt me." 
used
to be a long-established cultural tool available in cases like these at
issue.  Useful to help all sides of an issue maintain calmness and 
rationaliy,
but I have not seen it being used lately.

Tom

v2.23.0 | Report a Bug | By Email