IETF Logo Mail Archive

Re: [Json] JSON: encodings

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Wed, 13 November 2013 20:38 UTC

Return-Path: <jhildebr@cisco.com>
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 2154F21F9FF3; Wed, 13 Nov 2013 12:38:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.164
X-Spam-Level:
X-Spam-Status: No, score=-10.164 tagged_above=-999 required=5 tests=[AWL=0.435, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 FeXqMzQFJv50; Wed, 13 Nov 2013 12:38:33 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id CA1C821F85EC; Wed, 13 Nov 2013 12:38:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1074; q=dns/txt; s=iport; t=1384375112; x=1385584712; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=xR2vHpm8s/Z2aDbhG9IefKZ6eBUVgy5PtS2csDHqQUg=; b=JE6dn9AjdhZJtfsxfkL5bnuYWAtE8QGR0RNEWrO2hFWJb+GOgOWThWkY NzX9W0pFsMcf0hrs+aYcI3E4aXTrrIHW+3W2Og4YavDQ+TrNsIgAPeOVb Ao/vX+bpbPOZ36OjCyArmf0WOnoCeyxjugwSSKyL8QzL2Fy1S2EfBeGen w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAPzig1KtJXHA/2dsb2JhbABZgweBC78sgSgWdIIlAQEBBDo/EgEIGB5CJQIEAQ0FiAHAMY9fB4QxA4xZizeHOIpTgyiCKg
X-IronPort-AV: E=Sophos;i="4.93,695,1378857600"; d="scan'208";a="284451012"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-8.cisco.com with ESMTP; 13 Nov 2013 20:38:10 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id rADKc9ec027096 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Nov 2013 20:38:09 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.47]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Wed, 13 Nov 2013 14:38:09 -0600
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Anne van Kesteren <annevk@annevk.nl>
Thread-Topic: [Json] JSON: encodings
Thread-Index: AQHO37v9xjk3Oc0cjEWcneEucZMQiJojkEcA
Date: Wed, 13 Nov 2013 20:38:08 +0000
Message-ID: <CEA92E3C.2CD06%jhildebr@cisco.com>
In-Reply-To: <99EE3A2D-D1CF-44EF-BA61-156ED8E72F79@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [10.129.24.62]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F47F239C976D7847A02920BBB8E5F647@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:38:39 -0000

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.

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.

-- 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email