IETF Logo Mail Archive

Re: [DNSOP] DNS-in-JSON draft

Jerry Lundström <jerry@dns-oarc.net> Mon, 05 September 2016 08:42 UTC

Return-Path: <jerry@dns-oarc.net>
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 3A1A312B325 for <dnsop@ietfa.amsl.com>; Mon, 5 Sep 2016 01:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.509
X-Spam-Level:
X-Spam-Status: No, score=-3.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dns-oarc.net
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 w4l_6WpIEq8p for <dnsop@ietfa.amsl.com>; Mon, 5 Sep 2016 01:42:09 -0700 (PDT)
Received: from ix1.dns-oarc.net (ix1.dns-oarc.net [IPv6:2620:ff:c000::198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61E5012B04F for <dnsop@ietf.org>; Mon, 5 Sep 2016 01:42:09 -0700 (PDT)
Received: from [172.17.0.4] (212-181-207-169-no54.tbcn.telia.com [212.181.207.169]) (authenticated bits=0) by ix1.dns-oarc.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id u858g4qC004310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 5 Sep 2016 08:42:07 GMT
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <DB336274-A631-471E-8277-D6690A87C834@vpnc.org>
From: Jerry Lundström <jerry@dns-oarc.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <e0aded33-9026-9b58-931b-a7549f25cc75@dns-oarc.net>
Date: Mon, 05 Sep 2016 08:42:03 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <DB336274-A631-471E-8277-D6690A87C834@vpnc.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dns-oarc.net; s=ix1; t=1473064928; bh=57oFYh2i4QAFMnUyRgUUTXHGWXn5b5kRyEhahyusXpw=; h=Subject:To:References:From:Cc:Date:In-Reply-To; b=ReMBe2Wh4ph0oMKamY/b8MrhS4i8VPvISTAG8PradYSoqQMX/pM/AsT8a42nQQltO HxFgvAf9m+660vwRBpVtP32Dv2fBIFhvPymRdGi+n90qAICg69C9uwp07JA0S1qxMA t3CKY45ttaSPIh2iAnLPPv/AncWekLjtEjQPhj+U=
Authentication-Results: ix1.dns-oarc.net; dmarc=fail header.from=dns-oarc.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/RPgCRQI8CTwCmFZqb96SxCvHdTo>
Cc: dnsop WG <dnsop@ietf.org>
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: Mon, 05 Sep 2016 08:42:10 -0000

Hi Paul,

On 09/03/16 22:43, Paul Hoffman wrote:
> Greetings again. I have updated my draft on describing DNS messages in
> JSON. I still don't think that this WG needs to adopt this given that it
> is, as far as I can tell, thinly implemented. I think it's probably
> about baked enough for me to take it to the Independent Submissions
> editor to become an Experimental RFC. If y'all have any comments on it,
> please send them along and I'll incorporate before I move it along to
> RFChood.

Overall looks good, just a few minor concerns with adaptation/
interoperability:

- Non-ASCII octets escaping "\DDD" may lead to broken implementations
and/or encoding problem (oh so many printf()'ed JSON implementations out
there)

- The use of "!" and "*" in object attribute names will make it hard to
use in language that can read JSON and give out native objects such as
JavaScript.

Cheers,
Jerry

v2.23.0 | Report a Bug | By Email