IETF Logo Mail Archive

Re: [DNSOP] DNS-in-JSON draft

Philip Homburg <pch-dnsop-1@u-1.phicoh.com> Tue, 06 September 2016 07:34 UTC

Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B53F12B101 for <dnsop@ietfa.amsl.com>; Tue, 6 Sep 2016 00:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 ezK4525rtlIf for <dnsop@ietfa.amsl.com>; Tue, 6 Sep 2016 00:34:56 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-he.hq.phicoh.net [IPv6:2001:470:d16a:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 15DA712B0C8 for <dnsop@ietf.org>; Tue, 6 Sep 2016 00:34:55 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1bhAuE-0000FnC; Tue, 6 Sep 2016 09:34:54 +0200
Message-Id: <m1bhAuE-0000FnC@stereo.hq.phicoh.net>
To: dnsop@ietf.org
From: Philip Homburg <pch-dnsop-1@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
References: <DB336274-A631-471E-8277-D6690A87C834@vpnc.org> <e0aded33-9026-9b58-931b-a7549f25cc75@dns-oarc.net> <6239FBFC-7EB2-449C-BBA7-D0EAE0BF25D5@vpnc.org> <404afaa4-757a-b41b-fc11-384a0716d9f2@dns-oarc.net>
In-reply-to: Your message of "Tue, 6 Sep 2016 06:26:58 +0000 ." <404afaa4-757a-b41b-fc11-384a0716d9f2@dns-oarc.net>
Date: Tue, 06 Sep 2016 09:34:53 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4ft27UEGHAuhiiRW_VfwQ3XMYTw>
Subject: Re: [DNSOP] DNS-in-JSON draft
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2016 07:36:29 -0000

In your letter dated Tue, 6 Sep 2016 06:26:58 +0000 you wrote:
> I was more commenting on the fact that it is escaping in a format
> that already support escaping. The JSON output would be double
> escaped and implementations would need to unescape it themselves
> rather then let JSON handle it.

JSON strings are defined to be UTF-8. You get all kinds of weird problems
if you try to store 8-bit binary data directly in JSON strings.
(I.e. using the \uXXXX escape sequence)

An encoding that only requires US-ASCII to be stored in JSON strings is
a lot safer.

v2.23.0 | Report a Bug | By Email