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

S Moonesamy <sm+ietf@elandsys.com> Fri, 30 April 2021 11:23 UTC

Return-Path: <sm@elandsys.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 A4CC43A1147 for <terminology@ietfa.amsl.com>; Fri, 30 Apr 2021 04:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 P88U5oQrTtR5 for <terminology@ietfa.amsl.com>; Fri, 30 Apr 2021 04:23:43 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id B0E2A3A114B for <terminology@ietf.org>; Fri, 30 Apr 2021 04:23:43 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.174.25]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 13UBNH7o007208 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Apr 2021 04:23:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1619781812; x=1619868212; i=@elandsys.com; bh=ZfwUlyaVENiMzTZ5BGEpNokeUpPbwzBUO4Xahr+xkmM=; h=Date:To:From:Subject:In-Reply-To:References; b=gGfJLQ+i+2NtCKNOW39AY/FIo/z8SzmDJTI2Ogt3C9E1DJKRI71d0w6bBQZ7Pt1H4 h0cG9E6Ur/DkTeU7Sd1mUHZXYga5/GYJguHFDc2GdSM9zQrClB7JHtwKMcFXtpCKMo 1HRtif0p9e4R7NBjHQsneJSnVGH5PqV4+YU72v3w=
Message-Id: <6.2.5.6.2.20210430035412.0b9cee00@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 30 Apr 2021 04:22:38 -0700
To: Keith Moore <moore@network-heretics.com>, Niels ten Oever <lists@digitaldissidents.org>, terminology@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <a7628390-7f29-1d05-8509-ae008458894a@network-heretics.com>
References: <161918836800.7390.6996403788262551415@ietfa.amsl.com> <2563B42A-20A4-4A9F-B9CA-518A72A0A095@eggert.org> <5ecee462-e42b-ef6f-3841-4a33facf0e29@digitaldissidents.org> <a7628390-7f29-1d05-8509-ae008458894a@network-heretics.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/-ug1G9Tf20KBGXRRXWCmnBybbxg>
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 11:23:49 -0000

Hi Keith, Niels,
At 12:47 PM 29-04-2021, Keith Moore wrote:
>On 4/27/21 11:19 AM, Niels ten Oever wrote:
>
>>it is probably better to describe the actual situation, namely that 
>>the majority of the tech industry and other standards bodies have 
>>reached consensus on the topic, and the IETF is still making up its mind.
>
>IMO this is a bit unfair for multiple reasons.
>
>But it's certainly fair to say that IETF is slower than we'd like to 
>be at developing technical standards, and even slower at developing 
>standards for itself - because we never developed an effective 
>process for the latter.

It still comes down to the IETF is still up its mind.

A consensus-based approach is not suitable for quick decision-making 
as such as approach is meant to be slow.  The current proposed work 
does not even fit in the existing procedure given that it is an 
editorial matter.

Will an IETF decision be relevant after the publication of the 
guidance from NIST Staff?

Regards,
S. Moonesamy