IETF Logo Mail Archive

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

John Levine <johnl@taugh.com> Fri, 25 February 2022 20:49 UTC

Return-Path: <johnl@iecc.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 71B183A03EC for <json@ietfa.amsl.com>; Fri, 25 Feb 2022 12:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=iecc.com header.b=PQzBrY52; dkim=pass (2048-bit key) header.d=taugh.com header.b=m8AaSVDl
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 ji3BU0FYRQ2Z for <json@ietfa.amsl.com>; Fri, 25 Feb 2022 12:49:24 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA00E3A0060 for <json@ietf.org>; Fri, 25 Feb 2022 12:49:23 -0800 (PST)
Received: (qmail 46618 invoked from network); 25 Feb 2022 20:49:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=b617.621940d1.k2202; bh=MB3K1T1QGh+T0SctaCxWwzJCFp64kYbfEMXfvC4l86M=; b=PQzBrY52IWrlnYVHYs72C8QL//DwVirfKuM9s9VrfOrs0Qft4NS9xP4ijgAqXtJC0dWe78FKJrF0NON/V3U+EHNow/TDm5PVxLwmp9jdOiaZlVIq/jozCrEFXwk/f87KnRLRpGLGNT70hwR+HXPztMjRFWzEiyGQ71F8d2TgPj+eo+Eiq8kxqfE02D56AyhhG0RAua6XCwZlS26bLEKQpq2/Ur3YXsrCn0UAWVPrUGozbUW/f2nQkU1RRAQIM3ON2vxxbsD/5qD0mn3hoh6ZRJ6uqui9Oy0P007tFOeXSilMFhq9tu/4HQYkIANNJre6FRAezWCLwrvGbNYs4LrwzQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=b617.621940d1.k2202; bh=MB3K1T1QGh+T0SctaCxWwzJCFp64kYbfEMXfvC4l86M=; b=m8AaSVDlPbH0MVfFj+mZ/XXlrsA/jCr0asWPNiLTYtoqo23dpSiWfir5k7zxj7FZenJQQ3uWYtF4FjDgxDonYFrfbO0m0OcbTH4s/pKY2+1mNIPcBKzCo2KnF7yj5S79y7INKHGSC0RSY/UUN3Vpa9l6JrFs/QfPIjqJzGUwUb3qrh1a4JvYxgl1+4UB4Xxx7Ii3PI6eW2i0A/sAnpIk2FA04d6NQ14u7Wjcprn+QLFacFtm+HEH3BgFbG91dEPN0G+jF8ULV/PCHBgBCdn+1hKcR3RqD3+DyZHKzuSKJPlOU+DFmA+YDt68d7ti4+v0CU8Mc/qhBerH18Ggkb9jAQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Feb 2022 20:49:21 -0000
Received: by ary.qy (Postfix, from userid 501) id AD30337E87AF; Fri, 25 Feb 2022 15:49:18 -0500 (EST)
Date: Fri, 25 Feb 2022 15:49:18 -0500
Message-Id: <20220225204920.AD30337E87AF@ary.qy>
From: John Levine <johnl@taugh.com>
To: json@ietf.org
Cc: cabo@tzi.org
In-Reply-To: <1B1A9A76-4960-4410-A077-2F91734A54D4@tzi.org>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/b2iZIUk3WrmtZq5cYmUywWdiagM>
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 20:49:30 -0000

It appears that Carsten Bormann  <cabo@tzi.org> said:
>On 2022-02-25, at 16:56, Paul Hoffman <paul.hoffman@vpnc.org> 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.
>
>I’m not sure I understand what you mean.
>
>This is clearly a case where the English words turn out not to express what the consensus of the WG was (*).  That
>needs to be fixed, and the fix is obvious to anyone skilled in the art.

We get lots of errrata that say the text in the RFC says X but that is
clearly wrong, it should say Y. We approve them without any trouble. I
don't see why this one is any different.

I also concur with the Tim's observation about stray surrogates. In my
experience, either the code catches them and returns an error, or it
doesn't and it crashes.

R's,
John

v2.23.0 | Report a Bug | By Email