On Nov 14, 2025, at 19:38, Dave Lawrence <[email protected]> wrote: > > Marco Davids \(IETF IMAP\) writes: >> I'm working on a draft (draft-davids-forsalereg) in which TXT >> records play an essential role. To avoid ambiguity I ended up >> dedicating an entire section (5.2) to character encoding. > > Okay, cool. I think for a new definition like this you can just > declare that the TXT RDATA should be interpreted as a continuous UTF-8 > string without regard to the 255 octet segment boundaries. It feels > like maybe 5.2 has slightly too many words for accomplishing this, but > seems okay enough.
Andrew suggests not doing that, and instead reading the PRECIS work. I propose not doing that, and instead read <https://datatracker.ietf.org/doc/rfc9839/> for a much simpler way to say what characters are acceptable. --Paul Hoffman _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
