[Json] Wording on encoding; removing the table

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 22 November 2013 22:36 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 466D61AE383 for <json@ietfa.amsl.com>; Fri, 22 Nov 2013 14:36:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=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 O9nZbXzcGgQC for <json@ietfa.amsl.com>; Fri, 22 Nov 2013 14:36:51 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 60D4C1AE380 for <json@ietf.org>; Fri, 22 Nov 2013 14:36:51 -0800 (PST)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id rAMMafne047422 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Fri, 22 Nov 2013 15:36:43 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <v8av89128j49csd5bb5ba2rqrgschs4c79@hive.bjoern.hoehrmann.de>
Date: Fri, 22 Nov 2013 14:36:41 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE35B0E6-6C71-47EB-BA29-08A32935D20E@vpnc.org>
References: <v8av89128j49csd5bb5ba2rqrgschs4c79@hive.bjoern.hoehrmann.de>
To: JSON WG <json@ietf.org>
X-Mailer: Apple Mail (2.1822)
Subject: [Json] Wording on encoding; removing the table
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 22 Nov 2013 22:36:52 -0000

<hat on>

Please note that the chairs tried to find some consensus in the BOM discussion and found none. Given that, and given that the current table is now wrong, our proposal is to remove it, not try to doctor it.

Current Section 8.1:

   JSON text SHALL be encoded in Unicode.  The default encoding is
   UTF-8.

   Since the first two characters of a JSON text will always be ASCII
   characters [RFC0020], it is possible to determine whether an octet
   stream is UTF-8, UTF-16 (BE or LE), or UTF-32 (BE or LE) by looking
   at the pattern of nulls in the first four octets.

   00 00 00 xx  UTF-32BE
   00 xx 00 xx  UTF-16BE
   xx 00 00 00  UTF-32LE
   xx 00 xx 00  UTF-16LE
   xx xx xx xx  UTF-8

Proposed replacement:

   The default encoding for JSON transmitted over the Internet is UTF-8.
   Transmitting JSON using other encodings may not be interoperable
   unless the receiving system definitively knows the encoding.

Does anyone have a technical objection to the proposed replacement? If so, please state the error and (hopefully) a correction.

--Matt Miller and Paul Hoffman