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

Julian Reschke <julian.reschke@gmx.de> Fri, 21 July 2017 07:51 UTC

Return-Path: <julian.reschke@gmx.de>
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 269A8131DFE for <json@ietfa.amsl.com>; Fri, 21 Jul 2017 00:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 K8bq7MvZnnoX for <json@ietfa.amsl.com>; Fri, 21 Jul 2017 00:51:40 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB11312714F for <json@ietf.org>; Fri, 21 Jul 2017 00:51:39 -0700 (PDT)
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MDW9x-1dOFau1SFp-00GsUW; Fri, 21 Jul 2017 09:51:29 +0200
To: Pete Cordell <petejson@codalogic.com>, Carsten Bormann <cabo@tzi.org>
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> <2e6f5ead-1c20-d727-87a7-bbfe75ed4896@codalogic.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <82da41d9-ab0b-ae9b-55f8-d17dc65bb61f@gmx.de>
Date: Fri, 21 Jul 2017 09:51:27 +0200
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: <2e6f5ead-1c20-d727-87a7-bbfe75ed4896@codalogic.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:4t/b4ZSGea6mh4ZXyp2XW6Oc7mb46tB5TMKbuqS97Ksmzd83bK3 QM/cLoJa8S5oy62Rixy8eahDfpdOJv/YNg3VYpDnAnCrOjm+R9P2MLm5uCxBJQvgc8114Bq lsnv/EdotmEmyMbqmqX8SXrZg0OiS1aRRl3YeyOHUN2osuTrmdytG5YTpjZZSQdiM+SyiQK sN3FUwsCJLvEIIynaVqhg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:kqdIOUMLUXk=:NjHsN2TEIFiOGeMpzrdtoU rfTwdpfojDiV+QR/7WqzfYQtUojtAQltzdV/dzatq0WwbEZj8LcaUXYXIouC7ls6xvyx0kPVP VW1b+RZnTVxS1bMYIKec74QkrJW7FYIkenbudUQfIKO/ZXxZe8hZYuRb4/esz9usE9zxw+hcS glcX3oWwL1VE2/+etCRsI2LA+TKmNRU01E2pATELV4TMph9zRUaxHJM09BQHRmNIK2Nqt1nwJ t/tS3UbXzQ0NvXTUpivLKSNIDBefxCpRaDJ8DT30awZjp1URyiDo9Xq0axfg8SZaczLpXvqOU tpYe+oQvbuXyuV40Qzp7872go+c0qeFVLg0E+o2oRDyPIM67pOL+485FkmxTOQbbRRp4jJ7kR 3t7fSsufks8R0Omm4uPP940G4D9fb8dHQhT3MX1Cr6g04xNC6AC76B16oNp3XLmTA2W8L+n/Z 8dv5De6D/L45EKdFCy8xoa1bbz3pdxkGQTFIYLPPRWdEUyLEogXlw53BtBiDHEfAhjBVLrI6q TEmZ9TYxQIFQx2tdY0RmEj5riwVwr/p1SzrqJjF6GLn1REECAvx1R85yZhy8xqCKFz6Mdxc/L aczCIN2cbUHp/AUdhLIhEKkcj0YuT+13fS/v+tiBkDeazZi7eoOzWGkt+3M5gJqah5o3g2xIo dETEqaknB7BLHivAFN8GFCLWldCqQHQGUE2smjw9KYXGHK5mLQafmjRUZlrdzh9pYbU1xv4bA BVQQhH8hS/zUcEjVeRSbelSllxPChK7SG+bI4GXRiH8eC7Ls49Ao2FvBxunJt07DMm9deyTNT Bl/R0ABLU92EoNClJuz8lUA4Pu3Bz43pXKlwidzgXQiTjQ6Afc=
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/1KZzo2S_oKNfWsePbayQBLWuzDQ>
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:51:42 -0000

On 2017-07-21 09:42, Pete Cordell wrote:
> 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)!

+1

> 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

-1

So if a specify a protocol outside the IETF, and use application/json as 
HTTP payload, I *can* use UTF-16?

Best regards, Julian