Re: [DNSOP] dnsxml - A standard XML representation of DNS data

Tim Wicinski <tim.wicinski@teamaol.com> Thu, 01 August 2013 11:21 UTC

Return-Path: <tim.wicinski@teamaol.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 7830221F9E6B for <dnsop@ietfa.amsl.com>; Thu, 1 Aug 2013 04:21:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 t+hZqY+DsWFE for <dnsop@ietfa.amsl.com>; Thu, 1 Aug 2013 04:21:49 -0700 (PDT)
Received: from omr-m04.mx.aol.com (omr-m04.mx.aol.com [64.12.143.78]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD9F21F9306 for <dnsop@ietf.org>; Thu, 1 Aug 2013 04:21:40 -0700 (PDT)
Received: from aoldtcmei32.ad.aol.aoltw.net (aoldtcmei32.office.aol.com [10.180.121.111]) by omr-m04.mx.aol.com (Outbound Mail Relay) with ESMTP id 07543700000B4; Thu, 1 Aug 2013 07:21:38 -0400 (EDT)
Received: from tjw.local (172.17.8.193) by aoldtcmei32.ad.aol.aoltw.net (10.180.121.111) with Microsoft SMTP Server id 14.3.123.3; Thu, 1 Aug 2013 07:21:37 -0400
Message-ID: <51FA44C0.4050304@teamaol.com>
Date: Thu, 01 Aug 2013 13:21:36 +0200
From: Tim Wicinski <tim.wicinski@teamaol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: Jay Daley <jay@nzrs.net.nz>, Paul Hoffman <paul.hoffman@vpnc.org>
References: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz> <7B662C88-D969-4586-A01F-5D36E5B8DA53@vpnc.org> <58D17552-D4DD-45FC-9975-236D61635347@nzrs.net.nz>
In-Reply-To: <58D17552-D4DD-45FC-9975-236D61635347@nzrs.net.nz>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.17.8.193]
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] dnsxml - A standard XML representation of DNS data
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 01 Aug 2013 11:21:53 -0000

Jay

I agree it's just "formats" and therefore it's just 'a simple bit of 
code', I tend to find the XML specifications get a bit heavy, and what I 
liked in Stephane's draft is that it has a very lightweight feel to it.

(I will mention that the IESG is looking for reviewers for 
draft-manderson-rdns-xml-01 in case anyone feels extra motivated to 
assist in this).

tim


On 7/31/13 10:01 AM, Jay Daley wrote:
> Hi Paul
>
> On 31/07/2013, at 7:53 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>
>> Please also see draft-bortzmeyer-dns-json. JSON encoders and parsers are lighter-weight than XML ones, and for the data in question (everything DNS), it seems like JSON might be a better text format for the use cases (particularly logging).
> I'm aware of Stephane's draft as noted in my original email but I haven't had a chance to read it.  I will though.
>
> Rather than picking a winner between JSON and XML I've always found it prudent to recognise that the two have different characteristics that support different uses.  Not only can JSON and XML co-exist but also, if needed, the JSON can be derived from the XML via XSLT:
>
> 	http://controlfreak.net/xml-to-json-in-xslt-a-toolkit/
>
> cheers
> Jay
>
>> --Paul Hoffman
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>