Re: [Json] Call for Consensus: Proposed Text for "8.1 Character Encoding"

Pete Cordell <petejson@codalogic.com> Tue, 18 July 2017 09:41 UTC

Return-Path: <petejson@codalogic.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 E3DA0131A67 for <json@ietfa.amsl.com>; Tue, 18 Jul 2017 02:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.92
X-Spam-Level:
X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 EI0gI4M9TFJd for <json@ietfa.amsl.com>; Tue, 18 Jul 2017 02:41:31 -0700 (PDT)
Received: from ppsa-online.com (lvps217-199-162-192.vps.webfusion.co.uk [217.199.162.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2EEB131DD1 for <json@ietf.org>; Tue, 18 Jul 2017 02:41:29 -0700 (PDT)
Received: (qmail 24107 invoked from network); 18 Jul 2017 10:33:12 +0100
Received: from host109-155-118-120.range109-155.btcentralplus.com (HELO ?192.168.1.72?) (109.155.118.120) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 18 Jul 2017 10:33:12 +0100
To: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Cc: "json@ietf.org" <json@ietf.org>
References: <e69d7c21-85cb-45f4-c0c2-34c624e63049@outer-planes.net> <b74cb31b-8e04-17d0-548a-fc164ce07c05@outer-planes.net> <20170417175627.GK23461@localhost> <10B651F1-7FE0-484D-BD2E-FD146BC5FB04@tzi.org> <eabbccb0-8d15-d595-7cd0-37acc0621c57@it.aoyama.ac.jp> <6eb23f90-6623-7888-bc1c-6640a9dababc@codalogic.com> <61bfad2b-850d-a11f-e80b-d5ed9ccb4dc9@codalogic.com> <08a88696-65ef-da05-0d77-1a07d04ebfc8@outer-planes.net> <bb9fead6-23e7-8c1d-bc80-b60c81c4b89a@codalogic.com> <6f047d01-ad72-59ab-9d34-20a8177ab3af@outer-planes.net> <be4d9f12-a4be-3723-e52a-56a60722a75f@gmx.de> <a3805f67-620b-67f0-9c06-c865b71029e7@codalogic.com> <bb1ef6a8-506c-344b-b903-980ed50ad2d3@gmx.de> <44b4523a-5e4b-ccad-af96-931d8b9ad1c2@codalogic.com> <ac1d1b68-67e7-c19f-a556-280df73f465b@outer-planes.net> <db3e4d88-d3bc-2ab5-fd8d-0a9ed90865e9@codalogic.com> <CAHBU6itmYDyBfz0qqr0LAUTuvdR1oBSUnz7VSie=pZRva=Ynzw@mail.gmail.com> <787b7e15-ea97-b458-c886-d21c4dd02803@outer-planes.net>
From: Pete Cordell <petejson@codalogic.com>
Message-ID: <9af0048b-8254-a651-3653-069503d6f0a8@codalogic.com>
Date: Tue, 18 Jul 2017 10:41:25 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <787b7e15-ea97-b458-c886-d21c4dd02803@outer-planes.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/vgtxazlXEsHq7-VgdRt0-cZNGLg>
Subject: Re: [Json] Call for Consensus: Proposed Text for "8.1 Character Encoding"
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 18 Jul 2017 09:41:33 -0000

On 18/07/2017 09:27, Matthew A. Miller wrote:
> Hello all,
> 
> I see consensus for the updated text below.  A note to the RFC editor is
> added to ensure publication does not move forward until section 8.1 is
> updated, and the change noted in the appendix.
> 
> """
> 8.1.  Character Encoding
> 
> When transmitting over a network protocol, or as a payload of a
> network protocol intended to be interpreted as part of a protocol,
> JSON text MUST be encoded in UTF-8 (Section 3 of [UNICODE]).

I struggle here with "over a network protocol".  Perhaps we have a 
different idea of what "over a network protocol" means, but these days 
everything goes over a network protocol at some point in my mind.

Here's another stab at some wording in place of the first proposed 
paragraph:

     When transmitted as part of an IETF defined protocol, JSON text
     MUST be encoded in UTF-8 (Section 3 of [UNICODE]).

     Protocols defined outside the IETF are strongly encouraged to adopt
     a similar "MUST be encoded in UTF-8" requirement, but mandating this
     recommendation is beyond the scope of this specification.

Regards,

Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com