Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <5AA83191-90E5-477F-BC8F-FF654D070A05@nzrs.net.nz>
Date: Thu, 21 Aug 2014 13:11:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE7DF194-6DE2-4759-B8A6-DF28757981A7@vpnc.org>
References: <B4ACD73A-25EF-4063-81D4-DCFE6DB78AB1@vpnc.org>
 <20140821102232.73071610@vulcan>
 <586AEB36-C10F-4E6E-AC55-BAADE7C00FD4@vpnc.org>
 <20140821172757.504f49b7@vulcan>
 <5AA83191-90E5-477F-BC8F-FF654D070A05@nzrs.net.nz>
To: Jay Daley <jay@nzrs.net.nz>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/Yq3z0LqjdZvnAhk-sUk4sgaOEJM
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] New draft on representing DNS messages in JSON
Precedence: list

On Aug 21, 2014, at 12:53 PM, Jay Daley <jay@nzrs.net.nz> wrote:

> I agree with all of Shane's points below, namely better encoding of =
data,

I have responded to this one, assuming you mean RR data.

> not making all fields optional,

I don't think Shane made that argument. To me, it sounded like Shane was =
fine with fields being optional as long as the records could be defined =
by a schema.

> handling of unknown rrtypes

Sure, but that's already in the document.

> and having a schema for the data.

He preferred an internal schema; I explained why we couldn't do that =
with current or soon-to-be-expected standards.

>  These are all points (and many more) that were thoroughly addressed =
in the following draft on representing DNS in XML
>=20
> 	http://tools.ietf.org/html/draft-daley-dnsxml-00

Not to be too picky about it, but your document doesn't describe "DNS in =
XML", it describes "DNS resource records in XML". You clearly say in =
section 2.5 that you don't try to cover the header data, which is very =
important for the use cases for this document.

> If it helps then I can produce XSLT that takes data in the XML format =
specified in that draft and validated against that schema and turn it =
into whatever flavour of JSON you require:
>=20
> 	http://controlfreak.net/xml-to-json-in-xslt-a-toolkit/
>=20
> *stands back and waits for the "but json is sooo much easier than xml" =
brickbats*

There is that. In fact, one could argue that it would be much simpler to =
cast your document in JSON, if you didn't need a schema. Nothing is =
stopping people from adopting yours, although I would have called yours =
as experimental as mine.

--Paul Hoffman=