Re: [Json] [abnf-discuss] Are the Core Rules (Appendix B.1 of RFC 5234) always present in an ABNF spec?

Carsten Bormann <cabo@tzi.org> Wed, 20 September 2023 15:44 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD3BC15153D; Wed, 20 Sep 2023 08:44:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 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, 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 rguCux4bOUt0; Wed, 20 Sep 2023 08:44:30 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 3EE6AC14CEF9; Wed, 20 Sep 2023 08:44:30 -0700 (PDT)
Received: from [192.168.217.124] (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (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 4RrNBN0TVSzDCcx; Wed, 20 Sep 2023 17:44:28 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <ZQsRoQ64h6JA3jA6@ubby21>
Date: Wed, 20 Sep 2023 17:44:26 +0200
Cc: "abnf-discuss@ietf.org" <abnf-discuss@ietf.org>, json@ietf.org
X-Mao-Original-Outgoing-Id: 716917466.794758-6541150245e429fb6fd9dab86ff598d5
Content-Transfer-Encoding: quoted-printable
Message-Id: <24A6BAEC-6432-4B78-B218-97897F6FAA82@tzi.org>
References: <A9C3993F-D73B-4529-A94B-A6A33589726E@tzi.org> <ZQsRoQ64h6JA3jA6@ubby21>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/pxzZA9LmmGgOjdXimghP924oKd0>
Subject: Re: [Json] [abnf-discuss] Are the Core Rules (Appendix B.1 of RFC 5234) always present in an ABNF spec?
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2023 15:44:32 -0000

On 2023-09-20, at 17:37, Nico Williams <nico@cryptonector.com> wrote:
> 
> RFC 9431?  "Message Queuing Telemetry Transport (MQTT) and 

We need check digits on RFC numbers.
RFC 9413, of course.

RFC 9413 Maintaining Robust Protocols. M. Thomson, D. Schinazi. June 2023.
(The one that used to be called “postel-was-wrong”.)

Grüße, Carsten