Re: [Json] Call for Consensus: Proposed Text for "8.1 Character Encoding"

"Matthew A. Miller" <linuxwolf+ietf@outer-planes.net> Mon, 08 May 2017 16:02 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 30EBE129477 for <json@ietfa.amsl.com>; Mon, 8 May 2017 09:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level:
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 Yp2aILXEtGZk for <json@ietfa.amsl.com>; Mon, 8 May 2017 09:02:30 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 ED467127F0E for <json@ietf.org>; Mon, 8 May 2017 09:02:29 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id h4so55778234oib.3 for <json@ietf.org>; Mon, 08 May 2017 09:02:29 -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:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=4+TZC0NlYkqcG6nlyvx2c++kuZyal/2ntMN6U9iARAw=; b=pRPz5+knv1w98IeSsHjGTc9sHaAqwZr8KwHhvRZgFXAixU6ucSfOwPFYgEmd97R+SC LWGtBUrkZuicsC8mSTvaheBOBbawFPpdp46feNN/whWS8/0dtkjRYwCkS05xillJsTNc JndaRiBAz6haf6RAQdEM9QGoRrrNvsv8Cp6mAq6F6GhF9r8YihYfW6dPuboshg7J9M/u O9aQR/7jPw7q1vNzHmKpHdXqdsPup5pyrok/Pi7l7pRqb5nrtn3lKv7aJMI9cYJ3jjgf m6z41zOow4+vaBnnOurLbgrOHVEEbSdjcMkb5XcpNwKvp4KiCQoGE9dRimUsUv0Ikrb3 vGTA==
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:references:cc:from:message-id :date:user-agent:mime-version:in-reply-to; bh=4+TZC0NlYkqcG6nlyvx2c++kuZyal/2ntMN6U9iARAw=; b=HiGdmkyOc9s9SfMITKjhty8VA1EqNwIa+13dybzrJP/UPAoKhCbGiIOtOdoBK70rii e+Fj9vH4O0XaJEjBPn1UuX8Wd716td40jLRtlLDj+Cy0OuOxfB3i7fatovUn6CA18DVG JUNxs/SCptyILtwtAV9czHz+Fc7QQbmbQYH3eXBKYu9wWgNbr9gWUyMTG61YIQADkuB1 /3Ga3+n7jjEngrXxlu37fqQ1VunM4jCPLdVzydUQjsXVTha4JRjJUDFeGEzLDNUY7mM4 Zl9LwFQbgwzs2lh/ya5Ivjseq/aPSq8KUEDrIhHtp3+COiT1EznEis5Sq2hL9BjpKDU8 h2/g==
X-Gm-Message-State: AN3rC/6mxN7obLtmUTevAuIZMXr2BpzKzDUlrgvAqga8EOX2WOW90EgY lc/3iyTb3Ncs6wU5FmY=
X-Received: by 10.202.199.79 with SMTP id x76mr12476641oif.185.1494259349329; Mon, 08 May 2017 09:02:29 -0700 (PDT)
Received: from [10.6.23.170] ([128.177.113.102]) by smtp.gmail.com with ESMTPSA id s23sm6777810ota.56.2017.05.08.09.02.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 May 2017 09:02:28 -0700 (PDT)
Sender: Matthew Miller <linuxwolf@outer-planes.net>
To: "json@ietf.org" <json@ietf.org>
References: <e69d7c21-85cb-45f4-c0c2-34c624e63049@outer-planes.net> <14252631-AD76-4537-89BF-6368F4A8CDF4@att.com> <7e6af21f-16ea-a3bc-9c01-595ae8acebba@gmx.de> <05100401-88D4-4158-A3FF-3EF144D85449@att.com> <CAD2gp_T0bfpnsCA_t4BAMtEhr7p8JkZggjnY4F+m9-M2hWLfmw@mail.gmail.com> <1e94516c-9c82-8b0e-0d2d-7dbaa83b21bd@outer-planes.net> <40e3207f-e047-c898-1f0c-4422de1d597a@it.aoyama.ac.jp> <1b3ec14a-927a-8d46-e3d3-9807a9588437@outer-planes.net> <CAHBU6ivsq8+Z=MMkUH+=Q0uwc5NCtaJLYw5cp0Qg8eX2hQQ6sA@mail.gmail.com> <b74cb31b-8e04-17d0-548a-fc164ce07c05@outer-planes.net> <20170417175627.GK23461@localhost> <10B651F1-7FE0-484D-BD2E-FD146BC5FB04@tzi.org> <eabbccb0-8d15-d595-7cd0-37acc0621c57@it.aoyama.ac.jp> <6eb23f90-6623-7888-bc1c-6640a9dababc@codalogic.com> <61bfad2b-850d-a11f-e80b-d5ed9ccb4dc9@codalogic.com> <08a88696-65ef-da05-0d77-1a07d04ebfc8@outer-planes.net> <bb9fead6-23e7-8c1d-bc80-b60c81c4b89a@codalogic.com>
Cc: Pete Cordell <petejson@codalogic.com>
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Message-ID: <6f047d01-ad72-59ab-9d34-20a8177ab3af@outer-planes.net>
Date: Mon, 8 May 2017 10:02:32 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:53.0) Gecko/20100101 Thunderbird/53.0
MIME-Version: 1.0
In-Reply-To: <bb9fead6-23e7-8c1d-bc80-b60c81c4b89a@codalogic.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="fXI6nVCfRjNt0oTG63CgXB72cVDILFjNG"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/A0ji177gjO652LnXkMcDcNJ1Mrc>
Subject: Re: [Json] Call for Consensus: Proposed Text for "8.1 Character Encoding"
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: Mon, 08 May 2017 16:02:31 -0000

Any other comments from the Working Group?  All things being on the
table, is mandating UTF-8 an acceptable outcome?

Is Pete's suggestion adequate?  I suspect not as it's very similar to
earlier text that was rejected, but confirmation would be helpful.


- m&m

Matthew A. Miller

On 4/28/17 8:23 AM, Pete Cordell wrote:
> Thanks.  I agree with your summary.
> 
> If you removed the sentence which mentions "UTF-16, or UTF-32" from the
> text that you proposed on 17 April, I'd be happy with that text.
> 
> Thanks again,
> 
> Pete.
> 
> On 27/04/2017 17:21, Matthew A. Miller wrote:
>> I see consensus for text in Section 8.1 pending an Appendix on encoding
>> detection, but nothing for the Appendix itself.
>>
>> Looking deeper in the threads again, it appears to me that:
>>
>> * There is consensus to say "just use UTF8" in many (most) scenarios
>> * There is rough consensus to say "always use UTF8", but concern this
>> change goes beyond the charter
>> * There is no consensus on a detection algorithm
>>
>> While the charter calls for "absolute minimal changes", it calls out RFC
>> 7159 (and its -bis) as documenting "interoperability concerns when
>> exchanging JSON over a network".  Documenting this interoperability is
>> one of its primary goals.
>>
>> Therefore, the argument is made that a change to the effect of "JSON
>> text MUST be encoded as UTF-8" is considered an "absolute minimum
>> change" in order to achieve the goal of network interoperability.
>>
>> To the working group:
>>
>> * Is there strong objection to mandating only UTF-8?
>> * Does anyone have suggested text to that effect?
>>
>>
>> - m&m
>>
>> Matthew A. Miller
>> JSONbis Chair