Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03 [rfc7159bis scope]

Peter Cordell <petejson@codalogic.com> Thu, 16 March 2017 21:29 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 36493129A9C for <json@ietfa.amsl.com>; Thu, 16 Mar 2017 14:29:56 -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 tSmwgTfdlpyM for <json@ietfa.amsl.com>; Thu, 16 Mar 2017 14:29:55 -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 96D7E129AA2 for <json@ietf.org>; Thu, 16 Mar 2017 14:29:53 -0700 (PDT)
Received: (qmail 29718 invoked from network); 16 Mar 2017 21:22:33 +0000
Received: from host109-158-230-32.range109-158.btcentralplus.com (HELO ?192.168.1.72?) (109.158.230.32) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 16 Mar 2017 21:22:33 +0000
To: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>, John Cowan <cowan@ccil.org>
References: <otwresf20y4vnpmoboqqjnux.1489359742487@email.android.com> <0d3258fa-0f9d-cc5d-06d7-fcba943349ad@gmx.de> <f63c6a4a-dfbb-e03a-ea1e-38002f81ced8@it.aoyama.ac.jp> <0631d12c-f447-8904-6e2d-81e02cc6e8d3@codalogic.com> <1e075450-d958-db9c-ae63-3cbf3733024c@outer-planes.net> <cf6e35ba-6a67-4b35-d4e1-e99fee6e9f19@gmx.de> <1F1D1DCB-767F-490D-A425-AB5E66D51D3E@tzi.org> <CAD2gp_R7raq0mzfhATTYONdowBm0HvVHFAqJqoVcLmYABrgPpA@mail.gmail.com> <c20a17b7-0329-db5b-0983-23ebe11720f2@codalogic.com> <1f87f5d4-cbb0-9350-2d08-31350fa7438d@gmx.de> <24d37dc6-eee2-5e0c-6d33-d3450750e886@codalogic.com> <d520cf1f-bafd-6f62-c46c-482ad3a01f20@gmx.de> <EAF23716-FC94-478C-ACCF-9ED58B8A0ADF@fastmail.fm> <2b6f5439-18d1-9b7b-97e9-c683187ce452@codalogic.com> <7aaceb7a-45e9-b330-beee-fb66f933b3c9@outer-planes.net> <CAD2gp_Q0tg8MBC31x3v7CqkHwxikr=UyU6rL02u8ksh4LaSk+Q@mail.gmail.com> <942f4af5-ddb9-ed39-0013-6b75c3a8078c@outer-planes.net>
Cc: Julian Reschke <julian.reschke@gmx.de>, draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.org>
From: Peter Cordell <petejson@codalogic.com>
Message-ID: <84c01197-3690-f7d5-2a11-533998197757@codalogic.com>
Date: Thu, 16 Mar 2017 21:29:49 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <942f4af5-ddb9-ed39-0013-6b75c3a8078c@outer-planes.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/YUx7ypChMWs798IZ4OdXo4_vYaE>
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03 [rfc7159bis scope]
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: Thu, 16 Mar 2017 21:29:56 -0000

On 16/03/2017 20:25, Matthew A. Miller wrote:
> To keep the change from being too drastic, I think it necessary to leave
> in the text forbidding a byte order mark.
>
> For completeness, the complete text for 8.1 would be:
>
> """
>    JSON text SHALL be encoded in UTF-8 [UNICODE] (Section 3).
>
>    Implementations MUST NOT add a byte order mark to the beginning of a
>    JSON text.  In the interests of interoperability, implementations
>    that parse JSON texts MAY ignore the presence of a byte order mark
>    rather than treating it as an error.
> """
>
> That said, I'm not quite sure about going that far.  The web certainly
> uses UTF-8 and no other, but the scope is greater than that.  I would
> suggest keeping much of Peter's original text, with a small change to
> include the prohibition of encodings outside of UTF-8/-16/-32[1]:


I'm wondering, is it 'legally' permissible for the first paragraph of 
8.1 to be something along the lines of:

    JSON text SHOULD be encoded in UTF-8 [UNICODE] (Section 3).  JSON
    text associated with the application/json MIME media type MUST be
    encoded in UTF-8.

???

Cheers,

Pete Cordell
Codalogic Ltd