Marco Davids \(IETF\) writes: > Some protocols (like JSON) specifically mandate the use of UTF-8. In > RFC 1035 this was obviously never done and RFC1035 refers to octets, > noted as \DDD. > > But this can lead to confusion if it isn't clear which character > encoding is to be used.
The encoding to be used is octets, nothing more, nothing less. For the DNS protocol itself nothing else is needed. As to whether someone wants to stuff UTF-8 or UTF-16 or EBCDIC or whatever into the RDATA of a TXT record or something, that's between the producers and consumers of the data. The DNS doesn't care. While I am somewhat sympathetic to the issue implied by your example at https://www.whatsmydns.net/dns-lookup/txt-records?query=tmp.testdns.nl&server=google it's still just whatever octets the authority has decided to put there. Insisting that 40 years in it be explicitly some particular encoding would be a bad move. Are there indications of confusion causing notable issues that need to be addressed? _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
