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

"Matthew A. Miller" <linuxwolf+ietf@outer-planes.net> Thu, 16 March 2017 15:19 UTC

Return-Path: <linuxwolf+ietf@outer-planes.net>
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 3BEC2129613 for <json@ietfa.amsl.com>; Thu, 16 Mar 2017 08:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.com
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 E7neplXmv3UV for <json@ietfa.amsl.com>; Thu, 16 Mar 2017 08:19:05 -0700 (PDT)
Received: from mail-ot0-x242.google.com (mail-ot0-x242.google.com [IPv6:2607:f8b0:4003:c0f::242]) (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 174D61295B3 for <json@ietf.org>; Thu, 16 Mar 2017 08:18:54 -0700 (PDT)
Received: by mail-ot0-x242.google.com with SMTP id x37so8214268ota.1 for <json@ietf.org>; Thu, 16 Mar 2017 08:18:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=Yl/cNmn/2bDq9U2wuj1mVLZAXwstDumS4fRwh+QZK7A=; b=hiEMXwGdoWPoALbWv5RYJKazHmBMj07ceb8DBKbCQnrz2N7/f3Xk/m3RqGaSa9fGFR nB1D3mRQSFcrOViyP9NeCdqJ3b73vJ8maZow98KlvFKz2X3eoVb16pT4wLEOZHujLPpt vpBUbyqpmVQMT4QQZvUEzek2qczKyYr+cxIdBRy/oWVoTvZcs1VBKyk4WeIl8yxoRWFX I1n3MccvUfI4187b5bjeamFbnZGX/Zl/CqXJh6dCKcdMbQ2Lz+xY9hRX/iNQsSY/sYbZ m6tdfjpnxj2pMuu+nwNgrZ3y1zOi8nEjCYmROnvniIPbibfdxcPr9zBwTnrAtZ9ZAPDH 3J1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to; bh=Yl/cNmn/2bDq9U2wuj1mVLZAXwstDumS4fRwh+QZK7A=; b=KdUZC46yDYhH74zLdrwmTi48ckOTvQVQ3FR73fWVbMAW8Kc1uOqPQzJhvbwdRMmIyh AN/uq9NCii9ZxsI7knnesDYoHDUs1x0cUl/mRfZJS4DIAS6RA9OA684bcYTv/1gyEsZf qk68gmRiIxbg+FOC+XtlrrxMemz70hySnzVnNsBVdft9BI7scZ5pPHelRG4PgUIMhn6P HjSlGehgTVmBMQsHIMnwmMpLYfNyaGH98FXda+IzCiKShYFxCl+pFtdrtBN+MEeONt8g K/o/gIWLm6c2js+lbFTehj8D0InVvWcsmVIpthSEkH2buanFLiGpZc/p5gk8KISzzU6K cwXQ==
X-Gm-Message-State: AFeK/H2ZUFiloCf19Lx4lxvGF4M/LOvFwh8MIIv2sgCJj8OzdTttw4E8WxI+a/YnnkdmGA==
X-Received: by 10.157.26.3 with SMTP id a3mr5764448ote.62.1489677533436; Thu, 16 Mar 2017 08:18:53 -0700 (PDT)
Received: from [10.6.23.170] ([128.177.113.102]) by smtp.gmail.com with ESMTPSA id u76sm2211080oie.1.2017.03.16.08.18.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Mar 2017 08:18:52 -0700 (PDT)
Sender: Matthew Miller <linuxwolf@outer-planes.net>
To: Peter Cordell <petejson@codalogic.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, Julian Reschke <julian.reschke@gmx.de>
Cc: draft-ietf-jsonbis-rfc7159bis.all@ietf.org, "json@ietf.org" <json@ietf.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>
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Message-ID: <7aaceb7a-45e9-b330-beee-fb66f933b3c9@outer-planes.net>
Date: Thu, 16 Mar 2017 09:18:52 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <2b6f5439-18d1-9b7b-97e9-c683187ce452@codalogic.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="wo5CNdbPblPhhQ32sI37hvrjJA71ttJar"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/Joi_6YB8sHEMfrlZwidEZtwLhEE>
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 15:19:09 -0000

On 17/03/16 07:32, Peter Cordell wrote:
> On 16/03/2017 12:38, Alexey Melnikov wrote:
>>> On 16 Mar 2017, at 11:35, Julian Reschke <julian.reschke@gmx.de>; wrote:
>>>
>>>> On 2017-03-16 12:23, Peter Cordell wrote:
>>>>> On 16/03/2017 10:49, Julian Reschke wrote:
>>>>>> On 2017-03-16 11:28, Peter Cordell wrote:
>>>>>>
>>>>>> 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.
>>>>>>
> 
> ...
> 
>>>>> Not convinced.
>>>>>
>>>>> a) It's not constrained to UTF-8/16/32, so people might decide to
>>>>> support ISO-8859-1, or UTF-7-
>>>>
>>>> Why is that a problem if the generator knows the parser can read
>>>> it?  If
>>>> someone wants to use EBCDIC for whatever reason, are they not
>>>> allowed to
>>>> call it JSON?
> 
> ...
> 
>> As this document is intended to be Internet Standard, it should strive
>> to remove number of choices and generally non interoperable features.
>> So listing the minimal list of allowed encodings in this document
>> would be a good thing.
> 
> 
> I see rfc7159bis as a more generic description of JSON that may have
> applicability more periphery to the actual data bytes sent on the
> Internet.  As such it echoes the scope of ECMA-404.
> 
> I see I-JSON as the place to constrain things for the actual data on the
> Internet.
> 
> In some respects it would be nice to move the JSON MIME type from
> rfc7159bis to I-JSON, but since the MIME type is also applicable beyond
> describing bytes on the Internet it's not quite doable.
> 
> Regards,
> 
> Pete Cordell
> Codalogic Ltd
> Rules for Describing JSON Content, http://json-content-rules.org
> 

Overall I think your text, in spirit, lines up with the consensus of the
working group.

While I am generally sympathetic to accommodation, I don't think there
is support in the working group for expanding the allowed encodings
beyond what RFC 7159 already stated.


- m&m

Matthew A. Miller