IETF Logo Mail Archive

Re: [Json] JSON: encodings

Julian Reschke <julian.reschke@gmx.de> Wed, 13 November 2013 20:43 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 D48E121F9FAB for <json@ietfa.amsl.com>; Wed, 13 Nov 2013 12:43:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.149
X-Spam-Level:
X-Spam-Status: No, score=-103.149 tagged_above=-999 required=5 tests=[AWL=-0.550, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XeEnvjF0OvlQ for <json@ietfa.amsl.com>; Wed, 13 Nov 2013 12:43:00 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id DEA2321E80F0 for <json@ietf.org>; Wed, 13 Nov 2013 12:42:51 -0800 (PST)
Received: from [192.168.2.117] ([84.187.57.221]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0Lkzph-1V8BTD3MkX-00annw for <json@ietf.org>; Wed, 13 Nov 2013 21:42:50 +0100
Message-ID: <5283E447.1070707@gmx.de>
Date: Wed, 13 Nov 2013 21:42:47 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Anne van Kesteren <annevk@annevk.nl>
References: <CEA92E3C.2CD06%jhildebr@cisco.com>
In-Reply-To: <CEA92E3C.2CD06%jhildebr@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:abIoq9anDqY7+WDp1c75QFXiiwcu8D/Snf5XZswC55V4uiheNeQ LyR71AGJR62B6G8pLXkT1XQOcO+JIvhp0/M+nvE6DolYrpWAWKpL1NAz2sPRiL/arbOFYVt F87f9O/8hD9XlFYZWO37scm8+aZo3Lrl9CzYkjXLqDMzWyCGTBH4WScaMjn36s97g9Y4Dt+ dW6aGO2EhuHJp6sYfYyGg==
Cc: Henri Sivonen <hsivonen@hsivonen.fi>, IETF Discussion <ietf@ietf.org>, JSON WG <json@ietf.org>
Subject: Re: [Json] JSON: encodings
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 13 Nov 2013 20:43:01 -0000

On 2013-11-13 21:38, Joe Hildebrand (jhildebr) wrote:
> On 11/12/13 8:28 AM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:
>
>> [[ Adding the JSON WG to this thread ]]
>>
>> On Nov 11, 2013, at 10:58 PM, Anne van Kesteren <annevk@annevk.nl> wrote:
>>
>>> Supporting encodings other than UTF-8 in new formats is not good.
>>>
>>> Supporting UTF-32 is actively harmful as support for it has been
>>> removed or is being removed from clients. You ought to actively
>>> recommend against it.
>>>
>>> In general ASCII incompatible encodings have very bad security
>>> characteristics, the IETF would do well to steer away from them, just
>>> like the W3C has.
>
> Although I hate UTF-32 with the heat of a several moderately-sized stars
> and completely agree that UTF-8 is the one true path, I don't think we can
> completely remove UTF-32 from the bis draft.  There may be existing
> conformant JSON documents stored in UTF-32 that would be made unparseable
> by this change.

+0.5

> What I think we *could* do is put a stronger recommendation for UTF-8 in
> section 8.1, rather than just saying it's the default.

+10

v2.23.0 | Report a Bug | By Email