Critical.
Authoritative.
Strategic.
Subscribe to CIO Magazine »

ICANN approves internationalized domain names

Now users of non-Latin scripts will be able to write domain names entirely in their own language

Starting in mid-November, countries and territories will be able to apply to show domain names in their native language, a major technical tweak to the Internet designed to increase language accessibility.

On Friday, the Internet's addressing authority approved a Fast-Track Process for applying for an IDN (Internationalized Domain Name) and will begin accepting applications on Nov. 16.

The move comes after years of technical testing and policy development, said the Internet Corporation for Assigned Names and Numbers (ICANN), which held a meeting in Seoul this week.

Currently, domain names can only be displayed using the Latin alphabet letters A-Z, the digits 0-9 and the hyphen, but in future countries will be able to display country-code Top Level Domains (cc TLDs) in their native language. ccTLDs are those that have a two-letter country designation at the end of a domain name.

In reality, the new domain names will be stored in the DNS as sequences of letters and numbers beginning xn-- in order to maintain compatibility with the existing infrastructure. The characters following the xn-- will be used to encode a sequence of Unicode characters representing the country name.

One of the primary concerns with implementing IDNs is the security and stability of the Domain Name System (DNS). That system enables the translation of domain names written with characters and digits into IP (Internet Protocol) addresses, which can then be queried by a Web browser.

ICANN said it would initially allow for a "limited" number of IDNs, which are subject to ICANN's approval and stability testing. Still, there are likely to be hiccups, ICANN warned.

"The usability of IDNs may be limited, as not all application software is capable of working with IDNs," ICANN said in a59-page proposal dated Sept. 30 that describes the Fast Track process. "It is up to each application developer to decide whether or not they wish to support IDNs. This can include, for example, browsers, email clients, and sites where you sign up for a service or purchase a product and in that process need to enter an e-mail address."

ICANN has set some language restrictions for IDNs: they must be in an official language of a country or territory and have legal status or at minimum "serve as a language of administration."

According to the proposal, ICANN will charge registries US$26,000 for an evaluation processing fee, which can be paid in the local currency. ICANN would also like an annual contribution fee of 3 percent of a registries revenue, which can be as low as 1 percent for low-volume registries. For both fees, registries can request a fee waiver, ICANN said.

Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.

More about: ICANN, Internet Corporation for Assigned Names and Numbers, NN, Unicode
References show all

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
Users posting comments agree to the CIO comments policy.
Login or register to link comments to your user profile, or you may also post a comment without being logged in.
Related Coverage
Related Whitepapers
Latest Stories
Community Comments
Tags: icann, internet, top level domain
Latest Blog Posts
Whitepapers
  • Risk management: ensuring the security of your hosted information
    Organisations of all sizes are becoming victims to cybercriminals, data breaches, information theft and security risks. But before you go out and spend a fortune on security software, solutions and consultants, the starting point is to identify and measure your business’s exposure to those risks. In this whitepaper, “Exploring, Identifying and Measuring” risk, we examine how to identify risk and share an approach for identifying and measuring risk in your organisation.
    Learn more »
  • Business Intelligence Best Practices for Dashboard Design
    Even if a dashboard’s appearance looks professional and is aesthetically pleasing, appearances can be deceiving. Although visual design is important, it is also important to ask yourself: Is the data reliable? Is it timely? Is any data missing? Is it consistent across all dashboards?. This paper offers an overview of best practice business intelligence (BI) dashboard design principles and discusses data integration options for getting data into a dashboard.
    Learn more »
  • Bend or break: Flexible Policy
    DON’T. PANIC. Aligning business and IT needs has always been a challenge. Finding the right balance between ensuring the safety of sensitive data and enabling the free flow of information is increasingly difficult in today’s evolving regulatory and threat environment. Read on.
    Learn more »
All whitepapers
rhs_login_lockGet exclusive access to Invitation only events CIO, reports & analysis.
Recent comments