Re: [abnf-discuss] [art] Should RFC 7405 be part of STD 68 now?

Carsten Bormann <cabo@tzi.org> Tue, 19 December 2023 17:56 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: abnf-discuss@ietfa.amsl.com
Delivered-To: abnf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D63DC09D2FF; Tue, 19 Dec 2023 09:56:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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 Gkj-xcaXoHez; Tue, 19 Dec 2023 09:56:23 -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 89ECDC151065; Tue, 19 Dec 2023 09:56:21 -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 4Svkry5fSNzDCbH; Tue, 19 Dec 2023 18:56:18 +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: <46769866-5e6e-477f-8f72-b4b0c6b6f10b@gmail.com>
Date: Tue, 19 Dec 2023 18:56:08 +0100
Cc: "abnf-discuss@ietf.org" <abnf-discuss@ietf.org>, art@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E1ABAFDE-D3E3-420F-A182-B8EF70A61AC2@tzi.org>
References: <4DD498CF-63E6-48E6-A75A-6E72B72F372E@tzi.org> <aa439241-3834-459f-a6bc-d7907e398566@gmail.com> <65ea22f3-90a2-4b53-acab-9e75e979f2d5@alum.mit.edu> <17282304-6c20-4394-aaac-40f39ec00ba7@gmail.com> <8E015488-DCB5-44DF-8C1D-7C3E1F3B5DAA@tzi.org> <c0facbd2-e9f7-4e31-b0b0-8956de922d1d@gmail.com> <E6A10C53-75F2-4024-A5F5-BD1D004D32EE@tzi.org> <46769866-5e6e-477f-8f72-b4b0c6b6f10b@gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/abnf-discuss/VdGQiysxHoCgmWbNuv0guk5rpEw>
Subject: Re: [abnf-discuss] [art] Should RFC 7405 be part of STD 68 now?
X-BeenThere: abnf-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "General discussion about tools, activities and capabilities involving the ABNF meta-language" <abnf-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/abnf-discuss>, <mailto:abnf-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/abnf-discuss/>
List-Post: <mailto:abnf-discuss@ietf.org>
List-Help: <mailto:abnf-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/abnf-discuss>, <mailto:abnf-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2023 17:56:26 -0000

> Your assessment of what I'm arguing is wrong.
> 
> I raised an issue.  I haven't stated my own view of what the outcome should be.

Ah, thanks for helping me understand your input.

>> I just checked, 17 published RFCs (beyond RFC 7405 itself) use %s”…”, in 249 lines of ABNF.
>> Among these heavyweights such as RFC 9110 (HTTP semantics) and RFC 9112 (the text-based variant of HTTP).
> 
> This says that the enhancement is used.  But you did not, for example, compare this number against the total number of RFCs using ABNF.  Or is the 401 count, you listed at the end of your note, the 'total' number we should compare against?

401 is the number I could quickly produce.
This is approximately the number of RFCs using ABNF since RFC 5234 was published.
That time span is very roughly twice the time since RFC 7405 was published, which would be the more interesting number.
Assuming the publication rate is about constant, some 17 out of ~ 200 specs opted in for RFC 7405, so about 10 %.

(I can produce more reliable numbers if I know what statistics we are looking for.)

> And while percentage of specs is probably a useful indicator, something closer to percentage of actual use would be much better, of course.
> 
> Note that I did not challenge the original assertion that the enhancement has widespread adoption.

I would actually be even more interested in a tally of ABNF implementations and their RFC 7405 support.
I know that bap supports RFC 7405, as does my own implementation of ABNF.
As Paul notes, RFC 7405 support really is almost trivial to implement as an addition, so an implementation that doesn’t, likely is one that hasn’t received a lot of attention in the last 5 years or so.

As Paul notes, adding RFC 7405 to STD 68 could help reach the corners that haven’t noticed RFC 7405 yet.

Grüße, Carsten