Hi, I was wondering how well supported iDNA was in the more popular languages. A quick search for <programming language> iDNA shows that most of them support iDNA, some going back to 2006 or earlier. These languages and libraries support IDNA. I have used IDN is some of them and the support has generally been very good. java php node.js python .Net (C#, C++, F#, VB) ICU libIDN (C++, ruby) Most browsers also support IDNA very well. The one area that seems problematic (based on searching and problems reported) is JavaScript. Despite the browser support, native Javascript support seems problematic and the libraries (JQuery etc.) don’t do a good job. I am not surprised by the libraries as JS libraries often don’t do a good job of i18n support. However, I am surprised there isn’t a native dom function or ecmascript specification for ToUnicode or ToASCII. Maybe my quick search missed it. However, Node.js offers a punycode.js library for javascript users that is popularly recommended. I would normally consider the issue settled but I was concerned from the search that there may be several offerings out there called “punycode.js” that are not the same or the same quality. It bears a bit more research. I think the support for RFC 3490-3494 is very good. There could be a question about support for the newer specs RFC 5890-5895 since they have only been around since 2010. To me this raises the question of where UASG should focus. If the industry supports the older specs very well perhaps UASG should give attention to the newer features in the 2010 specs. I find myself questioning how much of a problem actually exists. UASG could consider a very superficial survey of where the problems are. For example, define a few test domains and perform the simplest tests with each of the programming environment. For example, in my own work I have an international domain I own (http://globalização.biz/) which I use for testing email and domain name support. UASG could set up its own international TLD and subdomains and email account, and ask its community of developers to verity they can access the site with both Unicode and punycode forms and then submit information thru a web page to update a google doc to identify the library/ or framework and success or fail. The email account would just have an auto reply that acknowledges receipt of the mail confirming sending to and from an IDN email address. The google doc would be something like: Language/Library Version Unicode Domain Test Punycode Domain Test Email Test Testers Name/Contact Info Tester’s Additional Notes … After the initial survey, if it proves helpful more elaborate tests can be surveyed. Or more focus can be given to those programming environments that seem problematic. tex