Paul, On Wed, 20 Aug 2014 10:22:26 -0700 Paul Hoffman <[email protected]> wrote:
> Greetings again. I have a need for expressing DNS messages in JSON > for an application I have written. Stephane and I had started to work > on this but ended up dropping it. > draft-dulaunoy-kaplan-passive-dns-cof comes at the same problem from > another direction, but it is specific for one problem space and isn't > using real JSON. > > So, I whipped this one up. I intend it to be Experimental because I > have no idea if anyone other than me wants it. Also, I don't think it > should be a WG document if only a few folks have need for the format. > However, I would love to heard comments and suggestions. Interesting. Some comments... * I don't like the treatment of QNAME*/hostQNAME, NAME*/hostNAME, and so on. Since JSON includes encoded strings, wouldn't it make more sense just to always put the QNAME in there? (Especially since you'll end up with SRV queries always being encoded as they have underscore characters...) * In general I'm not super enthusiastic about the mixing of binary and formatted data - I tend to think an application will want one or the other. Perhaps it makes more sense to define two formats, one binary and one formatted? Or... * Maybe it makes sense to define a meta-record so consumers can know what to expect? Something that lists which names will (or may) appear. I'd be mildly curious to see a comparison of the compressed sizes of JSON-formatted data (without data duplicated as binary stuff) versus non-JSON-formatted data. My intuition is that compression will remove most of the horrible redundancy that is involved in JSON, but there's only one way to be sure. ;) Cheers, -- Shane _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
