IETF Logo Mail Archive

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

Jay Daley <jay@nzrs.net.nz> Wed, 31 July 2013 08:01 UTC

Return-Path: <jay@nzrs.net.nz>
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 353F011E8165 for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 01:01:42 -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 tA0cvTaf+KTV for <dnsop@ietfa.amsl.com>; Wed, 31 Jul 2013 01:01:33 -0700 (PDT)
Received: from srsomail.nzrs.net.nz (srsomail.nzrs.net.nz [202.46.183.22]) by ietfa.amsl.com (Postfix) with ESMTP id A2B6121F9F9D for <dnsop@ietf.org>; Wed, 31 Jul 2013 01:01:30 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by srsomail.nzrs.net.nz (Postfix) with ESMTP id CBBB44B244C; Wed, 31 Jul 2013 20:01:29 +1200 (NZST)
Received: from srsomail.nzrs.net.nz ([202.46.183.22]) by localhost (srsomail.office.nzrs.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xI+kNCHOCxOR; Wed, 31 Jul 2013 20:01:29 +1200 (NZST)
Received: from [192.168.1.230] (121-74-100-115.telstraclear.net [121.74.100.115]) (Authenticated sender: jay) by srsomail.nzrs.net.nz (Postfix) with ESMTPSA id 67A6E4B22B5; Wed, 31 Jul 2013 20:01:29 +1200 (NZST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jay Daley <jay@nzrs.net.nz>
In-Reply-To: <7B662C88-D969-4586-A01F-5D36E5B8DA53@vpnc.org>
Date: Wed, 31 Jul 2013 20:01:27 +1200
Content-Transfer-Encoding: quoted-printable
Message-Id: <58D17552-D4DD-45FC-9975-236D61635347@nzrs.net.nz>
References: <77772FDC-CF32-4797-BB79-EABE559BA97E@nzrs.net.nz> <7B662C88-D969-4586-A01F-5D36E5B8DA53@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1508)
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: Wed, 31 Jul 2013 08:01:42 -0000

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


-- 
Jay Daley
Chief Executive
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 931 6977
mobile: +64 21 678840
linkedin: www.linkedin.com/in/jaydaley

v2.46.0 | Report a Bug | By Email | System Status