Re: [rfc-i] RECOMMENDS

Carsten Bormann <cabo@tzi.org> Mon, 01 January 2024 10:18 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E18AC14F6BF for <rfc-interest@ietfa.amsl.com>; Mon, 1 Jan 2024 02:18:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32J7sfmWRRYc for <rfc-interest@ietfa.amsl.com>; Mon, 1 Jan 2024 02:18:19 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20666C14F6BE for <rfc-interest@rfc-editor.org>; Mon, 1 Jan 2024 02:18:17 -0800 (PST)
Received: from smtpclient.apple (p548dcbf2.dip0.t-ipconnect.de [84.141.203.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4T3X4Q55k3zDCc8; Mon, 1 Jan 2024 11:18:14 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <d2c2ffee-1af6-8441-7486-06115542690d@gmail.com>
Date: Mon, 01 Jan 2024 11:18:03 +0100
Cc: RFC Interest <rfc-interest@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <38153E77-F78D-4BDE-BCE6-C115290B4A9F@tzi.org>
References: <d2c2ffee-1af6-8441-7486-06115542690d@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/-bXcdqm_eTxgJYvsiyLsfE1x39E>
Subject: Re: [rfc-i] RECOMMENDS
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jan 2024 10:18:25 -0000

On Dec 31, 2023, at 20:24, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> Should we fix this with an erratum? (That has implications for XML2RFC, so it isn't quite a no-brainer.)

RFC 2119:

   3. SHOULD This word, or the adjective "RECOMMENDED", mean that there
      may exist valid reasons […]


RFC 2119 is quite explicit that the “adjective” is a keyword; it is not discussing other forms.

I don’t think the usage of the active verb RECOMMENDS as if it were included in RFC 2119 is an errata item on RFC 2119.

I wish all of us a great new year 2024.

Grüße, Carsten


FYI:
kramdown-rfc’s automatic <bcp14 markup feature, which is enabled by using:

   {::boilerplate bcp14-tagged}

… triggers on the exact words (and word sequences such as MUST NOT) listed in 2119 and 8174.

If you want to apply <bcp14 markup to words not listed there, for instance RECOMMENDS, just add this line surrounded by blank lines somewhere in your markdown source:

   *[RECOMMENDS]: <bcp14>

… or simply write:

   Carsten <bcp14>RECOMMENDS</bcp14> not using additional phrases as if they were BCP 14 keywords.

(you generally can use XML markup right in kramdown-rfc’s markdown).