Re: [DNSOP] DNS-in-JSON draft

["Paul Hoffman" <[e-mail]>]

On 3 Sep 2016, at 20:20, Robert Edmonds wrote:

> In section 3:
>
>    A paired DNS query and response is represented as an object.  Two
>    optional members of this object are names "queryRecord" and
>    "responseRecord", and each has a value that is an message object.
>    This design was chosen (as compared to the more obvious array of 
> two
>    values) so that a paired DNS query and response could be
>    differentiated from a stream of DNS messages whose length happens 
> to
>    be two.
>
> Why do you call these fields "queryRecord" and "responseRecord"? It 
> seems
> to me that "queryMessage" and "responseMessage" would be more 
> intuitive.

Good call, yes. Will fix.

> In section 7:
>
>     This document has no effect on IANA registries.
>
> Do you plan to register a media type for this format? There is some
> precedent: the "application/dns" media type was registered for the
> experimental format defined in RFC 2540 "Detached Domain Name System
> (DNS) Information".

<sigh> I guess I should. Prediction: things will rathole on this 
section, not on the meat of the document.

> Nit: "Questing section" → "Question section"

Fixed.

Thanks!

--Paul Hoffman