Paul, At 2016-09-03 15:43:34 -0700 "Paul Hoffman" <paul.hoff...@vpnc.org> 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.
Thanks for this draft! I would be happy to see DNS in JSON documented,
if not exactly standardized. :)
I apologize if this stuff has been discussed before.
First, it seems like it might be nice to have a way to express RDATA in
DNS presentation format. The document is very clear that no way is
provided for this, but it seems like it would be really, really useful.
Next, is compressedNAME likely to be useful? I'm not arguing strongly
against it, but since it involves pointers and those are not going to
be useful with a JSON object, I don't really see much point.
I don't see any mention of whether things like TYPEname and CLASSname
are case-sensitive and if they are not which case they should be. My
recommendation would be to make them case-insensitive, although not
every field can be so having to tag each might be a bit much?
It occurs to me that maybe we want an option to have arrays of RRset
instead of arrays of RRs?
"answerRRsets": [ { "NAME": "example.com",
"TYPE": 1, "CLASS": 1, "TTL": 3600,
"RR": [ { "RDLENGTH": 4, "RDATA*": "C0000201" },
{ "RDLENGTH": 4, "RDATA*": "CB007181" }
]
}
]
It's not super important, but it would save me having to build RRset in
my applications. (With the RRs only I have to loop through the entire
section and only when done can I know that I have gotten a complete
RRset.)
Also, I guess it's also not important, but you may want to consider
using the RFC 5737 addresses for the example answer (like I did here).
Finally, I note that the RIPE Atlas system uses a type of DNS JSON
representation when you use their API to query for DNS measurement
results. You can get a sample here:
https://atlas.ripe.net/api/v2/measurements/5009360/results?start=1472860800&stop=1472947199&format=txt
The RIPE Atlas results match your proposal pretty well - you can see
it in the "results" object there - although they use "abuf" instead of
"messageOctets!".
Cheers,
--
Shane
pgpSNe_Vx55gy.pgp
Description: OpenPGP digital signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
