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

Julian Reschke <julian.reschke@gmx.de> Thu, 16 March 2017 20:40 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 0758A129A76 for <json@ietfa.amsl.com>; Thu, 16 Mar 2017 13:40:58 -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 zUpoH4pCF763 for <json@ietfa.amsl.com>; Thu, 16 Mar 2017 13:40:57 -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 B3748129A5B for <json@ietf.org>; Thu, 16 Mar 2017 13:40:56 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.116.59]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LlHsg-1cFpwp1fOQ-00b002; Thu, 16 Mar 2017 21:40:53 +0100
To: Paul Hoffman <paul.hoffman@vpnc.org>, Matthew Miller <linuxwolf+ietf@outer-planes.net>
References: <1fb5849e-8dbf-835d-65b7-2403686248f9@outer-planes.net> <0E32A94D-CE12-4F52-9ED6-8743C49751B4@vpnc.org>
Cc: "json@ietf.org" <json@ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <4d2f0fb3-a729-0c17-2394-bc1e005dd612@gmx.de>
Date: Thu, 16 Mar 2017 21:40:53 +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: <0E32A94D-CE12-4F52-9ED6-8743C49751B4@vpnc.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:VUTSDFxTVlPC83JKmmS4JyD2CPBZHo3SvfH9wjQIGvi27TQhlrW vYxuYVVxY9G6RDogv4U/M5+tJ9nB/4yC3si3GshloJwZmO47A0mlzEpZWDKl/j7FWHYeetl uM1io4jjWLKsLN3PeQp3n8Lev4VflULmvOxt9bcV3xKA5rNx5TlduDkMsObBYocjwXtKzyj Jv2DkBRpCFqS/zZkRFe+Q==
X-UI-Out-Filterresults: notjunk:1;V01:K0:ZLU8en5s7dE=:hKUN2Cmcs3OWc1Zw7lvHDF RD74Gdzh6qe9YTprPT/cUhReO+3xo8gfQ8ZnuVgG8ZQlR9OL0HTKfZ0x6a0LQmQSU9+XKmBlE Y770CdJEWnhe6vY3wwZYM21/yeh+X0D/O4yAqQfWDGlTAxLdS8yJHJix396dABXqthIyyRY03 TM1GNfwgQwaMfH9JOxsl1ZjAYAIAwuOZEqsC6EAypErwsyUqLXicAG0WuYiQWi5ZKfCgWc7h6 KgJBlrPKfwvrJa8UbHF5nVUhJmYBqzFMjJdWvc7NZ3pPkBagiAEY2FhwLpNyqdFgPM+AoFhS9 GoRSFd39wEddQdWE9z5bL95J/efEWgM/aIOXwE0ijVDmV4cBHU9coqS7pWGj2k/Qwqldt4Tp4 NcAoksLOnYYm11w4if5qfE0olakZxUIyJ8hWXe0OtADgCxL59RUge4T+eDmHjQItcQF6nAFPA A4tJZuJGCh6eH86gJr5IB1PP43RDnu5tkzPTSc9SYypxbib8FcUUqBeGo8d1e1xRgF1Lk53t7 1cL+mEHqu1dTda5ZkkmQPDbdLtfrmHGVl52pIqzMKSvxntize3sQcL+YEXzcNr6xHhBndl/jK jXrJTJBBEdxsX9w0OdgPCqKrPM8annpfl2o58/HaBSUlanQddCn+MggodFtdRuPrKvnwUEB+f hSRl362M/dIi8r0MJYms4ehtKGoSpadn57OBvcMojnXJVDBl6n4lnFhcsyBKpU5gcioAHYq/a nl2evkEAM1SqakulL18r7Qmn5HFfznVFtTaRAaLE0MgCvgbFxcKjJpRiBlWqHBuQRpc3grq9C pJGS5B7
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/hGU3jDPmn-bJGUWzHAtV56yHKjo>
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: Thu, 16 Mar 2017 20:40:58 -0000

On 2017-03-16 21:33, Paul Hoffman wrote:
> This whole thread feels like a regression from RFC 7159. The abstract of
> this document says:
>
>    This document removes inconsistencies with other specifications of
>    JSON, repairs specification errors, and offers experience-based
>    interoperability guidance.
>
> Opening up to new encodings reduces interoperability.

+1

> In addition:
>
>> 1) Does the working group think adding any text on how to detect the
>> encoding worthwhile?
>
> No. Adding a multi-step test that is easy to get wrong reduces
> interoperability.

-1 - this came up as unclear during IESG review, and it *is* unclear. If 
the media type doesn't have a charset parameter, the spec actually 
should state how detect the encoding.

Best regards, Julian