It appears that Petr Menšík <[email protected]> said: >> If some application desperately wants UTF-8 in DNS RDATA, TXT records >> are not in my view the best vehicle for that.
The spec has always been clear that TXT records are strings of arbitrary 8-bit data. If you want to put a particular interpretation on some TXT records, pick an underscore _prefix and write a spec that says what the format of the records is. See this registry for a dozen examples: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#underscored-globally-scoped-dns-node-names >consumes them in wire format, it will not matter or change anything. Do >you know application, which consumes binary data from TXT record from >their presentation format? Every authoritative DNS server does that when it reads a master file. The binary stuff is represented with decimal escapes, but so what, it's mechanically generated and mechanically consumed. >Current way is selective. It does not use base64 or similar encoding for >normal ASCII letters. But it prevents using unicode text in useful form. That's how master files have been for 40 years. They're not going to change now. R's, John _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
