According to Stephane Bortzmeyer <[email protected]>: >RFC 1035 : "<character-string> is treated as binary information" and >"TXT-DATA One or more <character-string>s" > >There is an unwritten assumption that TXT data is human-readable, >which today means ASCII or UTF-8 but it is not written, although RFC >1035 also says "TXT RRs are used to hold descriptive text" which could >imply readability.
RFCs 1034 and 1035 say that CNAMEs should not be chained, and the examples imply that they're for short-term address forwarding, sort of like postal change of address. But that was then. We all know that TXT can include any octets and I doubt I'm the only person who's written applications that take advantage of that. I can see arguments for a binary type and have considerable sympathy for Paul H's position that it should be CBOR so it can use CBOR type tags and not have to reinvent anything. If it's not typed, you can use TXT. R's, John -- Regards, John Levine, [email protected], Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
