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

Eliot Lear <lear@cisco.com> Tue, 06 April 2021 14:13 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 5F0183A22BB; Tue, 6 Apr 2021 07:13:02 -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 pT1iWzX5WTtx; Tue, 6 Apr 2021 07:12:57 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5A803A22B9; Tue, 6 Apr 2021 07:12:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12216; q=dns/txt; s=iport; t=1617718377; x=1618927977; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=swNCTNj4jAkW7Uq7De76qMMs9I1oautwOw2dWV0KJo8=; b=FS1I3c0VzC9YSY0aCdv95xTGCAuQU00am0MnbngKuoujG8GAgxpKYuJQ dmypk829EB4gA4+osSmijX/m60eC6YhmRfCe/cn0ghEwbORxbWMn7B9wl Byc48YpBP+MaqNSIu2I1BkDn5lRl05/zu2/NB/IMAlNJiwcPN9cKb94JZ 4=;
X-Files: signature.asc : 488
X-IPAS-Result: A0BoAQBaa2xglxbLJq1aHQEBAQEJARIBBQUBghKDIlYBJxIxhEKJBIhPA5REhjiBaAQHAQEBCgMBASQQBAEBhFACgXcmOBMCAwEBAQMCAwEBAQEBBQEBAQIBBgQUAQEBAQEBAQFohVANhkQBAQEDASNICQUFCwsOCicDAgJGEQYTgnEBgmYhD6ptd4EygQGEWIRyCgaBOYFThSoBhk9DgguBEyccgV+BAD6CYAKBKBxQgmE1ggkiBIFaZmsDAx8QIXsdQQQ1YotdhRuLLIElnQKDFYM+gUWEYIxohjEEH4NNiniFZooqhhyebIITkl5ghAECBAYFAhaBayEtgS4zGggbFTsqAYI+PhIZDo4rDQmDTopbPwMvOAIGAQkBAQMJjGZeAQE
IronPort-HdrOrdr: A9a23:/3WXRa+4FN/mJeYZBMxuk+BaI+orLtY04lQ7vn1ZYxY9SL36q+ mFmvMH2RjozAsAQX1Io7y9EYSJXH+0z/9IyKYLO7PKZmPbkUuuaLpv9I7zhwDnchefysd42b 17e6ZzTP38ZGIWse/f4A21V+kt28OG9qfAv4jj5kxgRw1rdK1shj0RYm2mO3Z7SwVcCZ0yGI D03LsjmxObZX8VYs6nb0NqY8H/obTw5fDbSC9DIxYm7QWU5AnYjILSIly/wgoUVS9JzPME92 XI+jaJgJmLgrWc1gLW0XPV4tBtvObZjvFHBMCKl6EuW1LRtjo=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.81,309,1610409600"; d="asc'?scan'208,217";a="34799319"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 Apr 2021 14:12:54 +0000
Received: from [10.61.144.88] ([10.61.144.88]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 136ECrPF011155 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 6 Apr 2021 14:12:54 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <A9BD0E76-7E35-446B-A91E-FAC997BF86FC@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E563E995-B838-4C79-95DE-DF3E9ADFF327"; 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 16:12:52 +0200
In-Reply-To: <97452adf-4177-c3d4-608b-9346f67b344e@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> <90270CD1-23BA-455D-A5E4-BB15577D1276@cisco.com> <97452adf-4177-c3d4-608b-9346f67b344e@cdt.org>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-Outbound-SMTP-Client: 10.61.144.88, [10.61.144.88]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/7rivfq-kmY3UktzKJdR7ui1m0Ho>
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 14:13:02 -0000

Hi,

As the IETF we are supposed to be speaking as individuals, but in this case, because Cisco’s name is mentioned in an external reference, I feel the need to make that explicit: I speak only for myself here, and for nobody else.  Please see below.

> On 6 Apr 2021, at 14:52, Mallory Knodel <mknodel@cdt.org> wrote:
> 
> Hi,
> 
> On 4/6/21 1:01 AM, Eliot Lear wrote:
>> 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.
>> 
>>> On 5 Apr 2021, at 16:34, Mallory Knodel <mknodel@cdt.org <mailto: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.
>>> 
>>> 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.
> I don't see why the IETF shouldn't demonstrate leadership, where needed. In the case of the draft Niels and I wrote, we didn't come up with those arguments or the term pairs and their replacements. Other people did that. But what we did was coalesce research and draw conclusions in the form of arguments tailored to the IETF. Is that external?
> 
Mallory, you have to ask yourself: how many anthropological linguists, professional philosophers, and sociologists do we really have in the IETF to review such work?

If that sounds like a punt… it is.  But in the meantime, we can suffer through with some actionable advice.  But that means not having a lengthy treatise on the value of different lists.
> See also: https://github.com/ietf/terminology <https://github.com/ietf/terminology>
> This is really useful, even if it might eventually prove to be duplicative effort. In the beginning, it was the right step because as an exercise it demonstrated scale to the IETF audience. Other groups are doing the same thing, but it's not always clear what will emerge in perpetuity (independently updated). Something like the Inclusive Naming Initiative cites our draft, so is that objectionably self-referential?
> 
> 

Is it objectionably self-referential?  I don’t know.  If the basis for their decision is the basis for our decision is the basis for their decision, I suppose it would be.  Mostly that hasn’t been my concern, tho.  What I have seen is a lot of the industry pointing to your draft, something that we are ill equipped to review.

Returning to the charter, choosing one list will be hard enough for the WG to accomplish.   And establishing the well-studied and researched principles the charter mentions will also be difficult.  The best we do is to articulate some lay principles, as Bron did.  If anyone on the IESG doubts that, please imagine  how you would apply the expertise that brought you to your position to scrutinize language usage.

In summary, Carsten is right: the less original work we do here, the better.

On the other hand, the INI might provide a locus to attract the sort of professionals I mentioned.  I’d like that because there are some big name companies who might fund some research.  Who knows?  [Again, speaking only for myself here.]

Eliot