On Tue, 12 Aug 2025 09:17:14 +1000 Mark Andrews <[email protected]> wrote:
> Every character. You encode non ascii printable using \DDD. You escape > double quotes and back slash. If semicolon or left and right bracket are > outside of double quotes and you don’t want them to be treated as specials > you escape them. This is all documented in STD13. This is basically the > same encoding as for domain names except @ isn’t the origin and periods are > not specials. > > Remember this is all presentation format. On the wire it is length tagged > binary data. > > If someone is restricting the record size below protocol limits and it is > impacting you file a bug report. OK, then simple question: why nobody uses full binary in TXT records, then? E.g. DKIM uses base64; https://isc.sans.edu/diary/25142 also says about printable only. It seems that because in practice that doesn't work, e.g. Web-panels of hoster/registrary could allow only some subset (and "file a bug" could take years to really fix), like, https://my.f5.com/manage/s/article/K20940935 is written something I can't fully comprehend. That is, people prefer to stick to some "safe" subset, and I'm asking about practical experience with that (it would be funny if a thing has a real need and not be joke format, though Unicode variant I've designed may be useful separately due to effectiveness). Mainly I ask if I should publish format as a 1 April RFC or a real RFC, because (if) it can be useful to someonie e.g. for TXT records. -- WBR, @nuclight _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
