On Feb 27, 2013, at 8:27 AM, Tony Finch <[email protected]> wrote: > Paul Hoffman <[email protected]> wrote: >> >> But, even more significantly, draft-levine-dnsextlang is for defining >> the structure of RDATA, not the entire value of an RR. A JSON format for >> RRs would have data that is not in RDATA, such as TTL. The two proposals >> are for very different things. > > But you can't describe the structure of an RR without describing its > RDATA. They aren't different things: one is a sub-part of the other.
Of course. For the RDATA part of a JSON structure, you can be very JSON-y, or very masterfile-y like draft-levine-dnsextlang has gone. I would prefer being JSON-y because the rest of the data we are talking about is already in that format, and we would not be reliant on anyone understanding the new proposed format from draft-levine-dnsextlang. --Paul Hoffman _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
