On 21 Dec 2018, at 21:28, Warren Kumari wrote: > On Fri, Dec 21, 2018 at 12:52 PM Wes Hardaker > <[wjh...@hardakers.net](<mailto:wjh...@hardakers.net>)> wrote: > >> Jared Mauch <[ja...@puck.nether.net](<mailto:ja...@puck.nether.net>)> writes: >> >> > We went through some of this in IDR about routing protocols and how to >> leave >> > a partner device a message. UTF-8 is the supported method. 7-bit ASCII >> lacks >> > language support. >> >> That's a fair point. I'd be happy with a change to it. > > +1. Wes and I had a chat about this before specifying ASCII - he was all for > specifying UTF-8, I suggested ASCII because it is the "standard" in DNS, and > I was arguing for simplicity.
RFC2130, updated by RFC6055. Be careful though as UTF-8 is only an encoding. Matching or comparing strings in UTF-8 is not something that should be done without a bunch of extra rules. See IDN. But for "display strings", perfect! UTF-8 please! Patrik
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
