Well, I finally decided to pull the trigger by submitting an Internet-Draft defining An Internationalized Resource Identifier (IRI) Scheme for XMPP. This document supersedes the old draft defining a URI scheme for XMPP. What's the difference, you ask? Well, XMPP allows fully internationalized addresses (you're not limited to US-ASCII characters), so it makes sense to use IRIs rather than URIs. If people really need to convert an XMPP IRI into US-ASCII characters, they can use the conversion rules in RFC 3987. An IRI still conforms to the anyURI datatype, so no schemas need to change. All in all it seems like the right thing to do. Hopefully I've defined the IRI scheme correctly in that I-D, but I'm sure I'll hear about it if I haven't. ;-) Once again (cf. our use of stringprep), XMPP seems to be blazing a trail with regard to re-use of IETF internationalization technologies.
Peter Saint-Andre > Journal