It appears that Paul Hoffman <[email protected]> said: >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. ...
>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. In this application, the contents of the text field are supposed to be what I might call readable text strings. None of the subsets in section 4 of RFC 9839 work because they all include control characters which make no sense here. I'm with Andrew, if you want to say anything about what codes are allowed in this application, the PRECIS FreeformClass in RFC 8264 looks reasonable. R's, John _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
