On Jul 1, 2019, at 4:11 PM, 神明達哉 <jin...@wide.ad.jp> wrote: > > At Sat, 29 Jun 2019 22:55:07 +0000, > Paul Hoffman <paul.hoff...@icann.org> wrote: > > > > - I think the RESINFO RDATA specification (at least its wire format, > > > and preferably also the presentation format) should be more clearly > > > specified. At least to me it was not very clear, and I'm afraid > > > this can lead to interoperability problems. > > > > It is a JSON object. What beyond that description would help? > > For example, if it can be a part of a standard zone file, what's the > expected presentation format? Is it a la TXT character string (but > there's no length limitation) or something special? How do we handle > non-ascii characters?
Ah, I had not considered the presentation format. We'll add something about that in the next draft. > Also, how do we compare RESINFO RDATAs? Should they be compared as > opaque binary, or should two semantically identical JSON objects > considered equal as RESINFO RDATA too (even if, for example, they are > different regarding white spaces)? As opaque binary, definitely. JSON has so many ways of doing character escaping, it would be unlikely to make a completely correct JSON text comparator. We'll add that in the next draft as well. --Paul Hoffman _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
