Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt

Pete Cordell <petejson@codalogic.com> Fri, 21 July 2017 07:42 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 979CF12714F for <json@ietfa.amsl.com>; Fri, 21 Jul 2017 00:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.919
X-Spam-Level:
X-Spam-Status: No, score=-0.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 jHzOybmsF9vN for <json@ietfa.amsl.com>; Fri, 21 Jul 2017 00:42:30 -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 2E4F7124217 for <json@ietf.org>; Fri, 21 Jul 2017 00:42:30 -0700 (PDT)
Received: (qmail 31805 invoked from network); 21 Jul 2017 08:34:11 +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); 21 Jul 2017 08:34:11 +0100
To: Carsten Bormann <cabo@tzi.org>, Julian Reschke <julian.reschke@gmx.de>
Cc: Peter Saint-Andre - Filament <peter@filament.com>, json@ietf.org
References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <DB9BA7EA-D393-4079-B347-620A09280B26@isode.com> <CAC4RtVBYMrRCrUZ1qqD+_rH4M8N23GOgbbh=921fEYqH+gCm5Q@mail.gmail.com> <c06e583a-965e-9eaf-975f-e6876ac056ed@filament.com> <f1a6b553-c787-e248-67bd-74d68d98a845@gmx.de> <262E8314-263A-4443-B912-AFCF1A3277B2@tzi.org>
From: Pete Cordell <petejson@codalogic.com>
Message-ID: <2e6f5ead-1c20-d727-87a7-bbfe75ed4896@codalogic.com>
Date: Fri, 21 Jul 2017 08:42:24 +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: <262E8314-263A-4443-B912-AFCF1A3277B2@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/90bs6F8zRoo575nbCB_qO7RVlSE>
Subject: Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt
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: Fri, 21 Jul 2017 07:42:33 -0000

On 21/07/2017 06:14, Carsten Bormann wrote:
> On Jul 21, 2017, at 06:20, Julian Reschke <julian.reschke@gmx.de> wrote:
>>
>>>
>>> I suggest:
>>>     When an entity transmits JSON text over a network, e.g. as the
>>>     payload of an application protocol, it MUST encode that text using
>>>     UTF-8 [RFC3629].
>>
>> This gets us back to the suggestion to apply this rule to the use of the application/json media type (and types derived from it).
> 
> The nit-picking opportunity here is that we don’t want to change NFS in case someone accesses a file with UTF-32 JSON in it over the network protocol NFS.  We could recognize this as nit-picking, or use a phrase such as “intended by the protocol to be JSON” — media types are not the only way such an intention could take shape.

Clearly one person's nit-picking is another person's attempt to reduce 
confusion (especially of those not party to this discussion)!

I think Allen Wirts-Brock's "IETF-specified protocol" is the clearest 
and simplest 
(https://mailarchive.ietf.org/arch/msg/json/0TVI13NELfsuC7FscgDvXZThenE 
).  e.g.

     IETF-specified protocols MUST encode JSON text using UTF-8
     [RFC3629].

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