Re: [Json] In "praise" of UTF-16

Carsten Bormann <cabo@tzi.org> Tue, 03 September 2019 06:01 UTC

Return-Path: <cabo@tzi.org>
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 79E8A12003F for <json@ietfa.amsl.com>; Mon, 2 Sep 2019 23:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 8HPvGbQsBagb for <json@ietfa.amsl.com>; Mon, 2 Sep 2019 23:01:02 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 825761200FB for <json@ietf.org>; Mon, 2 Sep 2019 23:01:02 -0700 (PDT)
Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46MxC63l6Szyrc; Tue, 3 Sep 2019 08:00:50 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <2086bfc5-aa63-80ed-1a11-c0f770d1480d@gmail.com>
Date: Tue, 03 Sep 2019 08:00:39 +0200
Cc: "json@ietf.org" <json@ietf.org>
X-Mao-Original-Outgoing-Id: 589183237.978719-d144438870e0cbd8e49fc8292e81830f
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC5F04D0-D88A-410A-8688-85CDA7A85D05@tzi.org>
References: <cc3dc24d-3e13-e319-e48f-7b52ddd017d0@gmail.com> <00231270-86DF-4AD2-949E-25B04D518577@tzi.org> <20190902211744.GA7920@localhost> <40386571-301A-47BD-937D-55666566CFB5@tzi.org> <20190902214047.GB7920@localhost> <bde7a24d-8ae7-45e3-c8d8-86e9075c7f9b@gmail.com> <2086bfc5-aa63-80ed-1a11-c0f770d1480d@gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/oW-BS8NTh_RonUqDN6aE0-aarOE>
Subject: Re: [Json] In "praise" of UTF-16
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 03 Sep 2019 06:01:05 -0000

Any deterministic encoding scheme always has an application layer canonicalization issue.
It’s just slightly worse for (I-)JSON because its generic data model has so few common data types, so more work is at the application layer, mapping to those data types.

Grüße, Carsten


> On Sep 3, 2019, at 07:46, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
> 
> The (IMO) only real problem with JCS is in Appendix E:
> https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-06#appendix-E
> 
> Why is that?  Because you typically expect tools and libraries to do all the gory stuff.
> 
> In this particular case a part of the canonicalization process may spill over to the application.
> There are easy workarounds but workarounds is always a source of problems.
> 
> IF JCS gets firm adoption this problem could be more or less nullified but that's another story.
> 
> thanx,
> Anders
> 
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>