Re: [Json] [Technical Errata Reported] RFC7493 (6861)

Chris Morgan <rfc7493-errata@chrismorgan.info> Fri, 25 February 2022 16:07 UTC

Return-Path: <rfc7493-errata@chrismorgan.info>
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 9B6A93A093B for <json@ietfa.amsl.com>; Fri, 25 Feb 2022 08:07:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.1
X-Spam-Level:
X-Spam-Status: No, score=-7.1 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=chrismorgan.info header.b=Y2k3YTs4; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=NE1AS/PA
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 VEqIC-pul3RR for <json@ietfa.amsl.com>; Fri, 25 Feb 2022 08:07:32 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D2F03A091C for <json@ietf.org>; Fri, 25 Feb 2022 08:07:32 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id C34865C0192; Fri, 25 Feb 2022 11:07:31 -0500 (EST)
Received: from imap42 ([10.202.2.92]) by compute4.internal (MEProxy); Fri, 25 Feb 2022 11:07:31 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= chrismorgan.info; h=cc:cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to; s=fm2; bh=HW73AeraGsZJEvIo3BDhQ11OXV+tRKgLE7/1nyQ1muM=; b=Y2k3Y Ts4qBq/HVPElFcCm+mpnu+TVTOK3v5zxtvEo/MDcw8nzYBVGC4FpTvHI9NanAF2b jCj3BfGzkwygmdPYloNMuM3qz/RTqVlen07pDy1wR1HmC0vnbyB/t5mJMpX3UsL8 83klMHeccRJqOJp2NQGZ7RzE1WpQc9bsKRHH6amVWnm67JBQwRMCzszKN/Pc7Ywd BvyxC1o1Q4hHDhSo/Cpv3xZeZ9KhJB5loqudpDdYRI/xA1uQSjbPHKqG6s0/1l/N EvzHGfBlhzqVHFxilRl9dtoViSsIh2k8jGiuMxakQmt7bEWAHjdLJhJZO61n+NVW vZI/QzaqMmxeXQgyw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=HW73AeraGsZJEvIo3BDhQ11OXV+tRKgLE7/1nyQ1m uM=; b=NE1AS/PAGDMZTeYGWG0s2+o51vh3FPsgQdFTkj8Vyo3/YxyB3PpjVl6qx bfraxRSyTNXwgGFxas0qNiIFMwapMsfjLNqcJ8fPZiwAqFLfumOrH0c6v6z1VXJA Z0nz9LmjGr7HwCVzOl6umuRJLvxq33hiemm64SJl2+tq3Gri9uE2lad3XFuDI1m1 jNoxiDJWBKP0vqikEUOeAG0WDTbd4mnMmMs/47WvUEPJlkwchAxhv/e4my4PheHU 75vVJaZoMdK5Yi8daUc2HN0OOku+mHP+2VR+eB5QUSHHExwReQb6jFfVWLZM++lH xp0YC/nWKtmohTjS6Keqh/XqyRJIA==
X-ME-Sender: <xms:w_4YYpNM860Waxy35UArY9fV6TDtnePm0z7J0VAp30acelfT3UOHyw> <xme:w_4YYr_I3QDjEQKFGEWzIrFXzIXQOutFnC1YuCZot1iS7YnnOScvHUREQjAkospWU A-8J5ukogby35RtIg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrleeggdekhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhepfdevhhhr ihhsucfoohhrghgrnhdfuceorhhftgejgeelfedqvghrrhgrthgrsegthhhrihhsmhhorh hgrghnrdhinhhfoheqnecuggftrfgrthhtvghrnhepjeevveduhffhjedvffehleelleeg udekjeevueeugffgieefueeukeeufeejleegnecuffhomhgrihhnpehgihhthhhusgdrtg homhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehr fhgtjeegleefqdgvrhhrrghtrgestghhrhhishhmohhrghgrnhdrihhnfhho
X-ME-Proxy: <xmx:w_4YYoRrPkr52K1CqA2-MY-vBOdyFKYURfCn8WEcCWmajU32KM14zg> <xmx:w_4YYlvLv4vO8IaHxMP7Rjv4fV7ZEs5mqlJAqK-SczbPWRBqmuTrKA> <xmx:w_4YYhcchW9ASb_mHUXZCdx1aEXiHgUEhWzLeBDkS_c7sU2qkyXyWQ> <xmx:w_4YYl4ouwVKI5IbZKnwDFToaBjZDPky2UfjyfetX5Fg5a5NsC5JeQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3E06B2180078; Fri, 25 Feb 2022 11:07:31 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4778-g14fba9972e-fm-20220217.001-g14fba997
Mime-Version: 1.0
Message-Id: <e7a52a08-af09-4035-a153-2dbb28da88c8@www.fastmail.com>
In-Reply-To: <686AEC59-F051-49A2-A953-B26831E77C3D@vpnc.org>
References: <20220225033322.ECC44289E1@rfc-editor.org> <CAHBU6iu7AdA8FQyCSOE5=-5wZJ590b0sYxmazFiTebDQUdUN9A@mail.gmail.com> <F6608CF3-AE49-4A0C-A222-1558A84C53A6@vpnc.org> <CAHBU6itDUPOpUU6z9tqUEj4+S8=pXjXeTYHU73_frEM211=EOw@mail.gmail.com> <686AEC59-F051-49A2-A953-B26831E77C3D@vpnc.org>
Date: Sat, 26 Feb 2022 03:07:10 +1100
From: Chris Morgan <rfc7493-errata@chrismorgan.info>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Tim Bray <tbray@textuality.com>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, "Murray S. Kucherawy" <superuser@gmail.com>, Francesca Palombini <francesca.palombini@ericsson.com>, JSON WG <json@ietf.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/laN3Ya9YJB7UuBzPh2LgTVrPlsE>
X-Mailman-Approved-At: Fri, 25 Feb 2022 08:36:45 -0800
Subject: Re: [Json] [Technical Errata Reported] RFC7493 (6861)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 25 Feb 2022 16:08:49 -0000

On Sat, 26 Feb 2022, at 2:56 AM, Paul Hoffman wrote:
> I agree it would be stupid; it was also kinda stupid for us to have
> missed this in the creation of I-JSON. I am arguing agains the
> acceptance of this erratum from the standpoint of the long-established
> erratum rules, not from whether the proposed change is a good idea.
As an outsider (so after this I’ll say no more on the matter, deferring
to you lot), I’m surprised to hear of such a strong position on such
matters. I thought the whole point of the Technical category of errata
was for such cases. As the submission page says, “Technical is an error
in the technical content (This includes changes to the usage of RFC 2119
keywords.)”. This is a case where no reasonable implementer would
implement the exact wording even if they grasped the error. (I’m about
to join those ranks via <https://github.com/serde-rs/json/issues/862>,
having no intention as I implement of following the error).

> If you feel strongly enough about this, we could revise RFC 7493
> (and deal with the other open erratum), and maybe try to get it to
> be an STD.
The other erratum is incorrect, by the way.