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

Julian Reschke <julian.reschke@gmx.de> Thu, 16 March 2017 10:49 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 7BF8E127599; Thu, 16 Mar 2017 03:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.896
X-Spam-Level:
X-Spam-Status: No, score=-4.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-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 McVTyBCBo8Co; Thu, 16 Mar 2017 03:49:13 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 9E19012704B; Thu, 16 Mar 2017 03:49:12 -0700 (PDT)
Received: from [192.168.1.57] ([5.10.171.186]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Metpl-1cZHUM07Pl-00OYms; Thu, 16 Mar 2017 11:49:03 +0100
To: Peter Cordell <petejson@codalogic.com>, John Cowan <cowan@ccil.org>, Carsten Bormann <cabo@tzi.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>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.org>, secdir@ietf.org
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <1f87f5d4-cbb0-9350-2d08-31350fa7438d@gmx.de>
Date: Thu, 16 Mar 2017 11:49:03 +0100
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: <c20a17b7-0329-db5b-0983-23ebe11720f2@codalogic.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:SDb14aQDgdMjeZw2EkBAOt1KuhE5K6pJxb0Em0KbEu+w1WrJtEg 1/7Vs5oJISTu1tFeJcWo9RWKdhFAteNbt6PBkXZ0hFVMOShS+/f3Z8EoNk6SE7uW9M/RFlQ DVQcodpD0gVTP9dFnQNng+S7Eiv0sBCk3M/YrLa9DM75SoZuICihHfqVVzTULjypzLmQhMZ 7/nMjm6UPy/SNyFyKBfkg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:aticPsBUu1E=:VtK4KfPTHKShq4t+uI5T1+ 56aRoHYvNTjj5dEvS0u2kpsmh+/8YkfQZzSBKz4UHKIlvzu0ykSJwpEgifQA8C1SGGDBWrg0K MB+i16dTYCsDblU1TRFqpWEMAawC86/BC8/uh/VnK0LoADyt2BA7JTWHipObt4deiM5Fm/cFO 63z80NAGHLAxlWcjH3N79fnOvyQD1aYEwsO/aAO5tyUcuUlahbl/Mi0nu4CvoBLUyflpwWj3H b/imawiPeN1wQtcZOdSS58DsIaHvUNLMeIB8YzuvLzNkpOgvbmABFLVgjmiSmTshoIGcmib8M I8LrKR+2EKeIeKNoN0M1BmltCOXl7MQ9kwuPQq98ZeGUfNW7eYZQeISPOZXfRE+OZDYsTfpOu Hpi+JzJzT+d4NrTkylkC1/Qq3igCosUbeH6M6JUVM0mxftXk8R0/Tp6zDBJm96ZT1oskzVC8Y vvoENQtSV8AqxrS5Y9cBPJEWPvSHHBIZ1fZE9odVPpp8PZak+7JYAwgWdTpoKz2AMPUSabPbp YB2gJW4wCfJ9ueWKPVh6EqWyLZr7T7CYLAxYhyCSLxCEhv1b90oKIAlLd61B38LEX+qG6KnCg vvo+WUntxep0yA0Ztw0s/+NiJkIBryv3HCvFnZgxEL22uNAO1jPoRrJXyikgn7n6ZV31lLiSo 8l/SHZnxUr9eyjhIsnXfucZI/O81vjDS2BtOaymwYuOaWS5EA0FFYpMNOaB48bC4jCfrLudm+ EgfZOIhPuoq1nHm0exfQXaAxXcbscYtmIOjMgZecurwcH8bGE3k6mqiY3Z5wh8xQoxSy0QMiR 64yZYUF
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/dwsu7ou07nvCMPHbPtnhX_1gEi0>
Subject: Re: [Json] secdir review of draft-ietf-jsonbis-rfc7159bis-03
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 10:49:14 -0000

On 2017-03-16 11:28, Peter Cordell wrote:
> On 14/03/2017 13:58, John Cowan wrote:
>> In my opinion, we should either take all references to UTF-16 or UTF-32
>> out, or add back a correct detection algorithm. UTF-8 is what is
>> actually interoperable, and interoperability is what RFCs are supposed
>> to be all about.
>
> Combining the original (Tim's) & Martin's proposal with my tweak, plus
> John & Carsten's direction, how about:
>
>
> 8.1.  Character Encoding
>
>    JSON text SHOULD be encoded in UTF-8 [UNICODE] (Section 3).  JSON
>    texts that are encoded in UTF-8 are interoperable in the sense that
>    they will be read successfully by the maximum number of
>    implementations.
>
>    There are many implementations that cannot successfully read texts
>    in other encodings.  JSON text MAY be encoded in other encodings if
>    the generator is sure that the intended parsers can read them.
>
>    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.
>
> Are "generator" and "parser" the correct terms to use in this instance,
> or does that functionality sit above the character encoding layer?
> ...

Not convinced.

a) It's not constrained to UTF-8/16/32, so people might decide to 
support ISO-8859-1, or UTF-7-

b) It doesn't state that the only way to support encodings other than 
UTF-8 is to inspect the leading octets for zeros (or their lack of).

Best regards, Julian