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

Adam Roach <adam@nostrum.com> Tue, 06 April 2021 00:46 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0222B3A2EF5; Mon, 5 Apr 2021 17:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level:
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, 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=nostrum.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 y42OCj4jEoX8; Mon, 5 Apr 2021 17:46:51 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB77B3A2EED; Mon, 5 Apr 2021 17:46:50 -0700 (PDT)
Received: from Zephyrus.local (76-218-40-253.lightspeed.dllstx.sbcglobal.net [76.218.40.253]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 1360kiVd008670 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 5 Apr 2021 19:46:44 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1617670005; bh=rwOoVl6LIzq9JztzwNqY4R0BDstSfKFxdz2YGImD59g=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=FJ6qq5+bbZbRzWFsIlThQslolePds6qfVilNMRxbwODNMTyZxaGMCm7O9ByNUvL0P 2GNjqh0gHWJAMO03kvjkiJ5VAb8NMpB33dLZWqqnY4esTM/GiOWJefXJfUfPWV/u/9 nokQftXyJ53A/Cfexku1kyBLlkskgvMpb6FlxD4U=
X-Authentication-Warning: raven.nostrum.com: Host 76-218-40-253.lightspeed.dllstx.sbcglobal.net [76.218.40.253] claimed to be Zephyrus.local
Subject: Re: WG Review: Effective Terminology in IETF Documents (term)
To: Lloyd W <lloyd.wood=40yahoo.co.uk@dmarc.ietf.org>, Michael StJohns <mstjohns@comcast.net>
Cc: ietf@ietf.org, The IESG <iesg@ietf.org>
References: <89383942-204e-a94e-3350-42bfb4165ba0@comcast.net> <EA0B9C35-4B71-43E5-9E44-FF180E44732C@yahoo.co.uk>
From: Adam Roach <adam@nostrum.com>
Message-ID: <7bbb8f88-4fbd-33f4-87fd-38750a8f9bd6@nostrum.com>
Date: Mon, 5 Apr 2021 19:46:38 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <EA0B9C35-4B71-43E5-9E44-FF180E44732C@yahoo.co.uk>
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/ietf/sod-LAD0Wtvm_nSuPABKP4bvBdY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2021 00:46:56 -0000

On 4/5/21 19:27, Lloyd W wrote:
> And I'd like to point out the CAPS standards keywords used  throughout 
> draft-knodel-terminology, which are not at all appropriate in 
> informational documents that cannot make such recommendations.


Not terribly relevant to the TERM working group; but just to help people 
understand how things work around here: there are 1,099 existing 
informational RFCs that implicitly disagree with Lloyd's characterization.

rfcs$ egrep --files-with-matches 
"(MUST|SHOULD|MAY|OPTIONAL|RECOMMENDED)" `grep --files-with-matches 
INFORMATIONAL rfc*.json | sed s/json/txt/` | wc

...
     1099    1099   13188

/a