Re: [Json] [Technical Errata Reported] RFC8259 (7650)

Tim Bray <tbray@textuality.com> Wed, 20 September 2023 15:56 UTC

Return-Path: <tbray@textuality.com>
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 E4A6CC15153E for <json@ietfa.amsl.com>; Wed, 20 Sep 2023 08:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=textuality.com
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 LI9K3nM5zXVX for <json@ietfa.amsl.com>; Wed, 20 Sep 2023 08:56:51 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 DD594C14CE51 for <json@ietf.org>; Wed, 20 Sep 2023 08:56:51 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-529fb04a234so8681357a12.3 for <json@ietf.org>; Wed, 20 Sep 2023 08:56:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality.com; s=google; t=1695225410; x=1695830210; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DlQgQrJ1qrKrHoyZIc1cL/sgLfB8Y0zg80qzVmJhbU8=; b=dsDHact9uZzuuWv4+910bqGK1vHUo8417WFMChFqFe6DO6HYVAaOuyM5VFSaKbolJj iUbubXgebslHWKDVdcIVkxbMVt73qze1PXkfA0eceXkEJlGP57iqixWD4HB88iflXTOo TROD+kt/ipCgTkuLvUeFG5mI8AmcjyQUFUXDQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695225410; x=1695830210; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DlQgQrJ1qrKrHoyZIc1cL/sgLfB8Y0zg80qzVmJhbU8=; b=OSoCKyvWqvwrnJLcj9m1BKTXyhkEoCjMRsHQ6STGTppD3T0D0DwUtyY41ERM2WtWJs C/Fh3Gn21GC/UHV8VVyddayQMpH/JOb/d4/1f6ROv2OUBUuVacKG4SPYsUK0uA0LfwvX sZBOsZx9YzHUvvsTesXGo0H0n/xBZwitKMNHSn9+yEs7/2xQnsT9/oyLv4HbR/JJgmV9 DZLkAymQQMzM/BMSThro2Q6Ne4rCa5ve0TRLc2pRAcOAE8Gso6ahK5SZsE1s2yaGJV0v HA22Pa2upsAa/o1ttsQM0oKYy8SQf53Vo6jZxdUEQyJm79ESl5M3cK71BHA9hqTqkcps n4Aw==
X-Gm-Message-State: AOJu0Yx0nLPc3Z6mWmJd/RnXxb2qR+wJ8F1Zy5NsUOk/QTxIMRFOT8LE RT/r8ZWdJX/QJ9gcj1/qHU9w10yprL8Msj/Nm6WXzA==
X-Google-Smtp-Source: AGHT+IGCJQeR6CwZz2u8APrLZ8FKb0msUOny2sMVSD11pDx9bQUrGYjus9vxRMtQ61hH+yvy9VXW6Nu/gYDbiElPYYI=
X-Received: by 2002:aa7:d3ca:0:b0:527:3a95:3fa4 with SMTP id o10-20020aa7d3ca000000b005273a953fa4mr2682685edr.20.1695225409849; Wed, 20 Sep 2023 08:56:49 -0700 (PDT)
Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Wed, 20 Sep 2023 08:56:48 -0700
Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Wed, 20 Sep 2023 08:56:45 -0700
Mime-Version: 1.0 (Mimestream 1.1.1)
References: <20230920145716.EEC11E5EAB@rfcpa.amsl.com> <2E8A9E99-D72C-40C9-BA39-CFAE0743E977@tzi.org> <lGNo9VERN-EwB6GH-pB04uUsrul7JEEIKo7ARPkLzu3rkxizItep_OJ340aqIis-M-xqeD-rADfCh4TFLnJJn27n3FcrjtLZMVnSYhcwIzY=@protonmail.com>
In-Reply-To: <lGNo9VERN-EwB6GH-pB04uUsrul7JEEIKo7ARPkLzu3rkxizItep_OJ340aqIis-M-xqeD-rADfCh4TFLnJJn27n3FcrjtLZMVnSYhcwIzY=@protonmail.com>
From: Tim Bray <tbray@textuality.com>
Date: Wed, 20 Sep 2023 08:56:48 -0700
Message-ID: <CAHBU6itRhnMeKhPoXq-zo-n8nVxDSnX1yu5KmPai+kvhBE+5GA@mail.gmail.com>
To: Lucas TESSON <lucastesson@protonmail.com>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, superuser@gmail.com, francesca.palombini@ericsson.com, linuxwolf+ietf@outer-planes.net, json@ietf.org, Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="0000000000005e5c330605cc6c7c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/lhdq_fANGSxnlIQj1fLdK58yvKI>
Subject: Re: [Json] [Technical Errata Reported] RFC8259 (7650)
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:56:56 -0000

On Sep 20, 2023 at 8:46:30 AM, Lucas TESSON <lucastesson@protonmail.com>
wrote:

> Hi,
>
> thanks for your response.
> Indeed it is not clear whether the "core rules" are always present, but I
> think that is the idea behind the name "core".
>
> For instance, multiple RFCs makes use of those core rules without ever
> redefining them or clearly define that they "import" it from RFC 5234:
> - RFC 5147: DIGIT, HEXDIG
> - RFC 5321: CRLF, ALPHA, DIGIT, SP, DQUOTE, HEXDIG
> - RFC 5954: DIGIT, HEXDIG
> - RFC 6338: ALPHA, DIGIT, HEXDIG
> - RFC 5404: HEXDIG, DIGIT
> - ... and so on, even in NIST-IR and other specifications
>

So, de facto, 5234 is assumed to be silently imported.   This needs to be
made clear somewhere. Erratum against 5234?

Is it a common case that RFCs define rules that name-collide with 5234?  In
that case, it seems that the RFC’s definition must be authoritative, i.e.
5234 is overridden.  This should also be said in 5234, no?