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. I'd be curious to know how various operations portals handle the record creation via their normal "Create TXT" interface, but half expect that having UTF-8 pasted in will pretty much just work out. Generic consuming tools like dig won't necessarily know that it's UTF-8, but could be updated to be _for-sale-aware. For the domainers that are the primary audience of _for-sale, I would anticipate their tools to be made aware quickly. _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
