Re: [Terminology] [Gendispatch] WG Review: Effective Terminology in IETF Documents (term)

Keith Moore <moore@network-heretics.com> Fri, 30 April 2021 14:48 UTC

Return-Path: <moore@network-heretics.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 D4F3D3A1B2C for <terminology@ietfa.amsl.com>; Fri, 30 Apr 2021 07:48:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 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_DNSWL_LOW=-0.7, 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 Bncc5TjE6cDf for <terminology@ietfa.amsl.com>; Fri, 30 Apr 2021 07:48:37 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 403B93A1B2D for <terminology@ietf.org>; Fri, 30 Apr 2021 07:48:37 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 9BBBD5C0160; Fri, 30 Apr 2021 10:48:35 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 30 Apr 2021 10:48:35 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=0pdzbIDsYrMesU3zEBsOpoCKMqu6v8NNDnySZkgeM dw=; b=GDwuodU14brVDBDz8iYL3y2Uie3oZWCxICvTjMSAZ76Gwkee6G2HUl1+4 jj28Iv/lwC373RkPXzU4qNkone7A8hCqRQTB7vvSGybiu92dX/6uhsN1l6e+1/j+ BuCETPZtYSI4EqT0uv8PJcZx2Ne/t4XPDfUKXOnF41cvpOjgUD6cbfgOxjW4zz6U FdSwpqft9xN/+vbPlccs37Gh/Fo6viUuKOn5YFsbXTQwoDTD972WnZZ6F1qOMl6k RJtKEduM8EulkNflLMQk40Qej5+gy+KLyyRJK+zEU+yKg7Kf8F1pKlkgAafdqQ52 HMODD7QrDS96NMqF6tAmVu+Z1Ty0g==
X-ME-Sender: <xms:wxiMYHhg33NCJipmLDGPtMgrD0H3SKwFEqnalQcm2KPvLFYktNH6rg> <xme:wxiMYED_XU1-SaNqyzzMAk3FrR6GqLd9Ed17UguaF3VeHi3XWToWKLFzc6UgzNPJx spnlaZpVQBWiA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddviedgkeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomhepmfgvihht hhcuofhoohhrvgcuoehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh eqnecuggftrfgrthhtvghrnhephefhuedtheefgfefgffhkeehgfeugfeiudeugeejkeef leelueeiffetfeeuudeunecukfhppedvfedruddvgedruddtrddujedtnecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:wxiMYHGGuSqdhVZ8765k_BLYO5YyI-lnbQtRwTVeRhxHUShy7dYECA> <xmx:wxiMYEQw1xJZStsjpBq9ib42vTBN0v58dnpVSE7ihn7VqH5GMlTXig> <xmx:wxiMYExp8A00JaJvbhlmkEDt0qJaoPFwoKLDc6JaU-r8GbI_7Wi6WQ> <xmx:wxiMYD9iXrLT7dPUI-PUNgoJ4TY8rlWwzea1mr0TC1iON8sgv7nEJg>
Received: from [192.168.1.121] (23-124-10-170.lightspeed.knvltn.sbcglobal.net [23.124.10.170]) by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 30 Apr 2021 10:48:34 -0400 (EDT)
To: "Salz, Rich" <rsalz@akamai.com>
Cc: "terminology@ietf.org" <terminology@ietf.org>
References: <6A5DA6CC-573E-4ABA-AAEB-EDEB28D2C9F1@akamai.com> <6AFB15EC-A4AE-4CF9-9A29-797208A6EE63@network-heretics.com> <35FBCD5D-2956-474B-AF81-063CB47F5EB5@akamai.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <18c7a12d-1d8f-c78f-63d7-f32d52df0801@network-heretics.com>
Date: Fri, 30 Apr 2021 10:48:33 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <35FBCD5D-2956-474B-AF81-063CB47F5EB5@akamai.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/terminology/hXT1mfyUVgSIzZCKLsR3SdJxMTM>
Subject: Re: [Terminology] [Gendispatch] WG Review: Effective Terminology in IETF Documents (term)
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: Fri, 30 Apr 2021 14:48:42 -0000

On 4/30/21 10:17 AM, Salz, Rich wrote:

>>     Either we find common cause or getting consensus is hopeless.
> rough consensus not complete agreement.

The way I see it, if you can define a problem in a way that pretty much 
everyone will agree on the problem statement, you have a much easier 
time getting some kind of consensus, than if you try to define the 
problem in a way that is controversial.  The solutions in the two cases 
might be the same or very similar, except that you might never reach a 
solution in the latter case and you might create a lot of unnecessary 
bitterness in the process.

Keith