IETF Logo Mail Archive

Re: [Json] JSON or I-JSON?

Carsten Bormann <cabo@tzi.org> Fri, 26 February 2021 12:03 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 DEBD73A140D for <json@ietfa.amsl.com>; Fri, 26 Feb 2021 04:03:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 V-tr8DaZhbdm for <json@ietfa.amsl.com>; Fri, 26 Feb 2021 04:03:43 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AD893A140C for <json@ietf.org>; Fri, 26 Feb 2021 04:03:43 -0800 (PST)
Received: from [192.168.217.152] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Dn7bc48WqzysL; Fri, 26 Feb 2021 13:03:40 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <90cddfc3-c320-5ac0-210b-c77636383a6b@codalogic.com>
Date: Fri, 26 Feb 2021 13:03:40 +0100
Cc: "json@ietf.org" <json@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E254975-F9A7-4563-9C12-4FE52180C56A@tzi.org>
References: <90cddfc3-c320-5ac0-210b-c77636383a6b@codalogic.com>
To: Pete Cordell <petejson@codalogic.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/J1imgPcnTVwy4pLkD3KHugOwwHs>
Subject: Re: [Json] JSON or I-JSON?
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, 26 Feb 2021 12:03:46 -0000

> Quick question if I may...
> 
> When defining new IETF standards that want to use JSON, are they referencing JSON (RFC8259) or I-JSON (RFC7493)?

The answer requires Science (grep through rfc8[3-9]??.txt, so no-one references 7159):

7493 only
	8259 only
		both 7493 and 8259
--------------------------------------
	rfc8366.txt
	rfc8414.txt
	rfc8416.txt
	rfc8427.txt
	rfc8428.txt
rfc8460.txt
	rfc8485.txt
	rfc8520.txt
	rfc8522.txt
	rfc8555.txt
	rfc8572.txt
	rfc8576.txt
		rfc8610.txt
	rfc8618.txt
		rfc8620.txt
	rfc8628.txt
	rfc8639.txt
	rfc8688.txt
	rfc8693.txt
	rfc8725.txt
	rfc8727.txt
rfc8734.txt
	rfc8742.txt
	rfc8743.txt
	rfc8747.txt
	rfc8783.txt
		rfc8785.txt
	rfc8790.txt
		rfc8801.txt
	rfc8805.txt
	rfc8827.txt
	rfc8844.txt
rfc8877.txt
	rfc8895.txt
	rfc8896.txt
	rfc8908.txt
	rfc8921.txt
		rfc8927.txt
	rfc8935.txt
	rfc8936.txt
		rfc8941.txt
		rfc8949.txt
	rfc8977.txt

No indent is 7493 only, one indent is 8259 only, and double indent is both.
(Of course, RFC 8610 and RFC 8949 reference both, one for the JSON format and one for the I-JSON limitations.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email