IDNs in Applications
For IDNs to be universally accepted, they must be able to be used anywhere a traditional domain name is used. However, many web applications and software tools make assumptions about domain names and email addresses.
One of the great challenges facing universal acceptance of IDNs is ensuring that the hardcoded assumptions built into applications don’t create barriers to the use of IDNs and EAI addresses.
One of the few bright spots for IDN Universal Acceptance is in the use of IDNs as content. If an application or service displays a URL, it should recognize that it is a link to an external resource and do the expected action when the text is clicked upon. When IDNs appear as part of a web page, they should display and function in the way that any URL. Also, web pages that have IDNs as “content” should handle the URL appropriately.
As the number of devices – the Internet of Things – connected to the Internet becomes ever larger, the pressure to control, deploy, update and retrieve information from those devices will be intense. Using the DNS to identify some of those devices will be the best choice in some deployments. Without universal acceptance, internationalisation of the infrastructure of the Internet of Things will be far more difficult.