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

Eliot Lear <lear@cisco.com> Tue, 06 April 2021 05:02 UTC

Return-Path: <lear@cisco.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 037BB3A13EF; Mon, 5 Apr 2021 22:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level:
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 ihVMx47obh9F; Mon, 5 Apr 2021 22:01:58 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ED463A13ED; Mon, 5 Apr 2021 22:01:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9316; q=dns/txt; s=iport; t=1617685317; x=1618894917; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=DO0gTwZO2yasy+NwGngRUM105ZL4vyk7pgxlxp6Ct/E=; b=LKkYyRJQEGzCsyqeI15XvQCTrdp28MjI+rWyl1kqU+XpDABJJyrTCira Q1hNEaWWwJ0S0DjEPrS1RSfDF/seaWRnqN3efTzao6jh7YM5i9MqE8Ry2 tVXfujpeCt9HE/FoTsYn5UxRzW4qqxrTOF8Y4Ys3+fI+jXGxZs1xUampv U=;
X-Files: signature.asc : 488
X-IPAS-Result: A0ALAQAl6mtglxbLJq1QChwBAQEBAQEHAQESAQEEBAEBghKDIlYBJxIxhEKJBIhOA5RChjeBaAQHAQEBCgMBAR0BCgwEAQGEDEQCgX0mOBMCAwEBAQMCAwEBAQEBBQEBAQIBBgQUAQEBAQEBAQFohVANhkQBAQEBAgEBASFLBgUFCwkCDgoqAgInMAYTgnEBgmYhD49Bmw53gTKBAYRYhHgKBoE5gVOFKgGGTkOCC4E6HIJfPoJgAQGBMRODMTWCCSIEgVVxZQZQWyAdRQwpjD6RaYshkWGDFIM6gUWLfYVJhjEDH5QqkESzWWCEAQIEBgUCFoFrIYFbMxoIGxU7KgGCPj4SGQ6OOIhrhUc/Ay84AgYBCQEBAwmMD14BAQ
IronPort-HdrOrdr: A9a23:1Cv1a6v0Ofgzeo2ZdYWo+5KA7skD9NV00zAX/kB9WHVpW+aT/v re/8gz/xnylToXRTUcicmNUZPtfVrw/YN4iLNxAZ6MRw/j0VHDEKhD6s/YzyTkC2nC8IdmtZ tIV6RlEtX/ARxbgK/BjTWQN9YlzJ25/LuzheHYpk0DcShQZ6tt7xh0B2+geyUceCB8CZU0D5 aa7MZczgDQHEg/VNixBXUOQoH4yeHjqZSOW29lOzcXrC2HjTal89fBYnyl9yZbdS9TyrE/9m WAtAr16syYwpeG4y6Z8XPP5JJLn9ak8P9/PYinj8gYLSiEsHfOWLhc
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.81,308,1610409600"; d="asc'?scan'208,217";a="34723449"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 Apr 2021 05:01:55 +0000
Received: from [10.61.144.71] ([10.61.144.71]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 13651sj8024092 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 6 Apr 2021 05:01:54 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <90270CD1-23BA-455D-A5E4-BB15577D1276@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_48FA9636-C3E6-41C2-BD02-BEECA076B77B"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Tue, 06 Apr 2021 07:01:53 +0200
In-Reply-To: <bbdc6b67-ed0a-0ee5-1606-263c7bdec485@cdt.org>
Cc: Carsten Bormann <cabo@tzi.org>, "terminology@ietf.org" <terminology@ietf.org>, The IESG <iesg@ietf.org>
To: Mallory Knodel <mknodel@cdt.org>
References: <161677836041.26846.148884814967107510@ietfa.amsl.com> <0b747dd8-f4f5-23a1-d09d-91ea30f525a7@cdt.org> <3E83A93B-2AD3-497B-B40E-EC2E0C4E2711@eggert.org> <CAGVFjMJaYjroPLL5-Ns50CeyAB33thH5HpLgh0EXxPmxob4CEg@mail.gmail.com> <4C9BFF1C-5BC3-4980-B1D7-92812086C976@tzi.org> <bbdc6b67-ed0a-0ee5-1606-263c7bdec485@cdt.org>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-Outbound-SMTP-Client: 10.61.144.71, [10.61.144.71]
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/fGRO_YnhV2QyVBGF1NMlEXc7ahE>
Subject: Re: [Terminology] 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: Tue, 06 Apr 2021 05:02:03 -0000

The whole point of that text, as far as I am concerned, was to keep engineers from trying to get into language games, for which not one of us is equipped to properly answer.  If anything, to me the original text isn’t restrictive enough, because almost nobody else in the industry is properly equipped to answer the question being asked.  The compromise is that we have one, and not multiple, arguments about which list to use.  Perhaps we can even find one or two people who know what they are talking about when they create such a thing.

Eliot

> On 5 Apr 2021, at 16:34, Mallory Knodel <mknodel@cdt.org> wrote:
> 
> I removed restrictions to the text. Your point about IETF creativity on these terms may be right 99% of the time, and suggest that this be a major consideration whenever recommendations are made. But to restrict the charter at this stage seems like it would be unhelpful possibly in the future.
> 
> -Mallory
> 
> On 4/5/21 10:26 AM, Carsten Bormann wrote:
>> Sorry I didn’t pay attention to this discussion yet.
>> I don’t think the IETF should become creative in what terminology it wants to shun.
>> The proposed charter text was exactly right as it was.
>> 
>> Grüße, Carsten
>> 
>> 
>> 
>>> On 2021-03-30, at 22:55, Mallory Knodel <mknodel@cdt.org> wrote:
>>> 
>>> Sure, change this sentence:
>>> 
>>> The WG will identify and recommend an external, independently-updated resource containing examples of potentially problematic terms and potential alternatives to IETF participants, in order to align its efforts with broader activities by the technology industry.
>>> 
>>> To:
>>> 
>>> The WG will identify and recommend language resources on inclusive terminology and potential alternatives to problematic terms to IETF participants, in order to align its efforts with broader activities by the technology industry.
>>> 
>>> Best,
>>> -Mallory
>>> 
>>> On Monday, March 29, 2021, Lars Eggert <lars@eggert.org> wrote:
>>> Hi Mallory,
>>> 
>>> thanks for the feedback!
>>> 
>>> On 2021-3-26, at 19:11, Mallory Knodel <mknodel@cdt.org> wrote:
>>>> 2) Acknowledge that in some cases it will make sense for the IETF to be the authority on certain terminology as it relates to the IETF mandate, whereas others will need to be external given the mandates of other bodies. In other words, I don't think the IETF should abdicate all of its responsibility for setting standards with the best terminology, as it sees fit.
>>> Could you make a suggestion for what text changes you'd like to see to address this?
>>> 
>>> Thanks,
>>> Lars
>>> 
>>> 
>>> 
>>> --
>>> Mallory Knodel
>>> CTO, Center for Democracy and Technology
>>> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
>>> 
>>> 
> --
> Mallory Knodel
> CTO, Center for Democracy and Technology
> gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
> 
> --
> Terminology mailing list
> Terminology@ietf.org
> https://www.ietf.org/mailman/listinfo/terminology