Idns: Internationalized Domain Names Did You Know?

I N T E R N E T C O R P O R AT I O N F O R A SS I G N E D N A M E S A N D N U M B E R S

IDNs: Internationalized Domain Names Did you know?

· Internationalized Domain Names (IDNs) are domain names with characters other than a, b…, z; 0, 1,…, 9; and “-“. · IDNs on the second and third levels exist in some generic top-level domains (gTLDs) and in some country code top-level domains (ccTLDs). TLD

registries determine the choice of characters available under these TLDs. · Some languages, like Arabic, are written from right to left. IDNs at the second level are not very useful for the communities that use these languages because users would need to change both the type direction and script in the middle of entering a domain name. · IDN TLDs will be made available through two separate processes, initially through the New gTLD Program and the IDN ccTLD Fast Track Process. · 60 percent of Internet users are non-English speakers, while the dominant language used on the Internet is English (see Global Reach at www.glreach.com).

One of the most significant innovations in the Internet since its incep- tion is the introduction of Internationalized Domain Names (IDNs) in the Internet’s address space. You may be familiar with some of the larger top- level domains: dot-com, dot-cn, and dot-org are just three examples. IDN top-level domain names will offer many new opportunities and benefits for Internet users around the world by allowing them to establish and use domains in their native languages and scripts.

ICANN, the Internet Corporation for Assigned Names and Numbers, is responsible for managing and coordinating the Domain Name System

(DNS) to ensure that every address is unique and that all of us who use the Internet can find all valid Internet addresses. It does this by overseeing the Although many websites contain multilingual content, if you look distribution of unique IP (Internet Protocol) addresses and domain names. closely at the site’s web address on your browser, you will find IDNs It also ensures that each domain name maps to the correct IP address. represented only on the second level or lower levels. This representation happens in some gTLDs and some ccTLDs, and each registry decides One of ICANN’s top priorities is its IDN Program. This program is made up which characters are available for registration in domain names. of several initiatives that involve a significant cross-section of the global A map showing the IDN implementation across TLDs is available at Internet community and are aimed at providing a secure method for im- http://www.icann.org/en/maps/idntld.htm. plementing internationalized top level domains in the root zone. Through this program, users will be able to register and use domain names based Soon users around the globe will have access to IDN TLDs made up of on their local language scripts. This includes users of languages based on non-ASCII characters to the right of the dot. ICANN is carrying out three right-to-left scripts such as Arabic and users of languages based on non- initiatives to bring this about. Two are being implemented and one is at alphabetic scripts such as Mandarin Chinese. End users will be able to the policy development stage. These three processes are described briefly more easily identify localized online content by using fully localized identi- in the graphic on page 2. fiers. One example is http:// (“example.test” in Korean Hangul 실례.테스트 IDN usage in emails—or, more specifically, in the domain name part of the script), which is used for testing and illustration purposes only. email address—is not yet fully available. The technical standard that will Most of the program’s objectives are related to: make this possible is being developed by the Internet Engineering Task Force, or IETF. Some implementations are now available for users to try out. · The secure and stable technical and operational deployment of IDNs in the Domain Name System (DNS) at the root level. More information and test environments can be found at: · Engaging the global Internet community in the policy processes that · http://cslab.kr/eai-test/index.php/Main-Page will guide the deployment, allocation and secure management of IDNs. · http://global-email.info/intro.html · http://www.ietf.org/html,charters/eai-charter.html What are IDNs? IDN is the short name for an Internationalized Domain Name. These domain names are represented by local language characters. Such domain names could contain characters with diacritical marks as required by many European languages, or characters from non-Latin scripts (for example, Arabic or Chinese). Why are IDNs important? In Implementation: IDN ccTLD Fast Track Process IDNs are important for many reasons. The most important is the • To introduce a limited number of IDN TLDs in non-Latin scripts growing number of Internet users around the world for whom it is • Requires strings to be meaningful representations of country or difficult to use ASCII characters. The fact is, the Internet is accessed by territory names • Only for countries or territories represented in the ISO 3166-1 list more people who do not use Latin languages and scripts than those who do. This means that it is difficult for them to recognize ASCII In Policy Development: IDN ccTLDs – Long Term characters and reproduce them on keyboards or use software to enter • Full policy that caters for all website addresses in browsers. • Follows the ccNSO policy development process • Was initiated formally on 13 April 2009 by the ccNSO Council For example: http://www.icann.org/en/announcements/announcement-13apr09- en.htm • IDNs in your native language make navigating the Internet much easier. If you read an online newspaper in Russian and there is a link In Implementation: New Generic TLD Program to more information, then it can be a challenge to reproduce an ASCII • New process for applying for new gTLDs web address. It also makes more sense to have a Cyrillic-based ad- • Includes IDN TLDs dress for a site with Russian content. • Technical string requirements are the same for all IDN TLDs • If you see a billboard advertisement that contains a link or email ad- • Includes a mechanism for avoiding confusingly similar strings

dress, it is more useful if the website or email address is based on characters that you can reproduce. In other words, in many countries and territories this link must be in scripts other than the basic Latin script. What is the IDN ccTLD Fast Track Process? • Suppose your child comes home from school with an assignment that The IDN ccTLD Fast Track Process focuses on meeting a near-term demand requires obtaining information online on a specified website. What if by allocating a limited number of IDN ccTLDs based on non-Latin scripts the website address is in a different script than your native language? while a full IDN ccTLD policy is being developed. The process is further It may be hard to recognize the characters and reproduce the address limited to countries and territories represented in the ISO 3166-1 list. The in a browser. Fast Track Process is expected to be launched in Q4 2009, and a separate • Sometimes a website address is not a name that makes sense or has factsheet for this process is available at www.icann.org/topics/idn. any meaning attached. In such cases it is even more important to use the script or alphabet that intended users can recognize and be able What is the IDN ccTLD Policy Development? to reproduce on a computer keyboard. The IDN ccTLD policy development process is a long-term process for Certainly, IDNs have clear advantages in targeting local markets and non- countries and territories that do not qualify for the Fast Track Process. English speaking Internet users, and for local promotions and advertise- The first step in developing a long-term process for introducing IDN ments. So if you are a user not familiar with the basic Latin script, or if you ccTLDs is to develop an IDN ccTLD policy. ICANN’s Country Code Names wish to reach such users (with information, products or services), then Supporting Organization (ccNSO) is doing this. As soon as the process IDNs will be very important for your ability to reach these markets. is completed, implementation efforts will begin for all IDN ccTLDs. The

long-term process will incorporate the experience gained in the Fast How can I register an IDN? Track Process. If you want an IDN at the second level, or lower levels, you should select a TLD that meets your purpose. Check with you registrar and registry What is the New gTLD Applicant Guidebook? whether IDNs and the characters you wish to use are available. For a good The New gTLD Program focuses on expanding choices for generic top- overview, go to http://www.icann.org/en/maps/idntld.htm. This map shows level domains, or gTLDs. This expansion includes IDNs at the top level in where IDNs are available. Currently, more than 47 TLD registries and order to meet growing diversity and encourage competition for more registry managers support IDNs. innovation, choice and change to the Internet’s addressing system. If you want to register a domain name with the entire string in local characters, or if you want to apply to become an IDN TLD operator, you can ICANN is developing both a process for registries to apply for new gTLDs choose from three possible programs. Each program has its own specific and an Applicant Guidebook that takes applicants through the process qualification requirements, rules and launch time. and explains the implications of the many complicated issues surround- ing these new top-level domains. The Internet community is currently The diagram here gives an overview of the three programs available. As working on resolving string contention, protecting intellectual property these initiatives continuously progress, please view the latest status at: rights, handling internationally recognized issues of morality and public • IDN ccTLD Fast Track Process: http://www.icann.org/en/topics/idn/fast- order, and the geographical names process, among other issues. After track/ The shorthand term IDN ccTLDs refers to new top-level domains going through several rounds of public comment, the process and the associated with entries in the ISO 3166-1 list. guidebook are expected to be fully implemented in 2010. • New gTLD Program (including IDN gTLDs): http://www.icann.org/en/ topics/new-gtld-program.htm For more information about the Applicant Guidebook and the New gTLD Program, go to http://icann.org/en/topics/new-gtld-program.htm. • IDN ccNSO PDP: http://ccnso.icann.org/

2 Where can I try IDNs? What are the IDN Guidelines? ICANN created a dedicated IDNwiki facility to introduce users to the The guidelines list general standards for IDN registration in addition to testing of IDN top-level domains. The test is based on eleven IDN TLDs those in the IDNA standard. Registries must follow the guidelines’ policies representing “example.test” in non-Latin based scripts. The table below and practices for IDN TLDs to minimize the risk of cybersquatting and con- shows the languages and scripts initially selected for the IDNwiki. You can sumer confusion, and to ensure that the interests of local languages and enter the Wiki by typing in any of the illustrated domains, or by going to character sets are respected. Registries that deploy IDNs will be required http://idn.icann.org. to follow these guidelines.

Public participation in the evaluation of these domains is an important In addition all new TLD managers, either through the IDN ccTLD Fast Track Pro- aspect of the project. To participate, access one or more of the addresses cess or the New gTLD Program, will be required to meet all existing or future in the table and report your experience on the wiki discussion pages. versions of the IDN Guidelines. The latest version of the guidelines is available at http://www.icann.org/en/topics/idn/implementation-guidelines.htm. More languages and scripts are being added as requests come in from the various language communities. The IDN Guidelines will be revised right after the IDNA protocol revision is completed to ensure they are consistent.

Brief history of internationalization and the

Internet’s Domain Name System

Internationalization measures, including IDNs, might be the largest change in Internet operation since the TCP/IP (Transmission Control

Protocol/Internet Protocol) was introduced. Furthermore, IDN deployment might be more significant and complex than the original DNS introduc-

tion. To fully understand the difficulties of internationalization of the domain name space, it is important and useful to give a brief history of

IDN technology development.

The idea of internationalizing domain names goes back to the devel- What is the IDNA protocol revision? opmental stages of the Internet in the 1970s. Discussions centered The IETF is creating the standards for using non-ASCII characters in the on the usability of languages and scripts. However, the technology Domain Name System. In 2003, an international IDN working group devel- deployed in the Domain Name System today, which allows practically oped the IDNA standards, which since have been used by TLD registries any character in the registration of a domain name, was not developed and application developers. Since then, the IETF IDN working group has at that time. Therefore, the characters available for registering domain been evaluating the experience gained in implementing the IDNA names was limited to ASCII characters: the letters a-z, the digits 0-9, and protocol. They have identified several key areas of work now under way. the hyphen “-“. The core components still being revised include: In 2003, technical bodies raised the topic again, and the Internet Engi- • Eliminating Unicode version dependencies, thereby permitting more neering Task Force released the standards (RFCs 3490, 3491, and 3492), characters to be used automatically in IDNs now and in the future. also often referred to as IDNA, or IDNs in Application. These standards • Clear defining valid IDN labels. provide technical guidelines for successful deployment of IDNs; that is, a • Fixing the complications and errors in the existing protocol for many mechanism to handle non-ASCII characters in domain names in a stan- right-to-left domains. These domains will become valid when the dard fashion. It works by converting names with non-ASCII characters to revised protocol is implemented. ASCII labels that the Domain Name System will understand. The issues with the current IDN model that led to the revision work are discussed in RFC4690. The Internet drafts with proposed revisions are Later, ICANN and several top-level domain registries released version available at http://icann.org/topics/idn/rfc.htm. 1.0 of the IDN Guidelines. These guidelines were created for generic TLD (gTLD) registries to follow when implementing IDNs at the second level These proposed revisions are currently going through Last Call in the only. The current guidelines, version 2.1, is available at http://icann.org/ IETF, after which they will become final standards and can be used by topics/idn/implementation-guidelines.htm. TLD registries and application developers that want to be IDN capable. ICANN is expecting the standards to be completed in time for the launch Work is under way to revise the IDNA protocol, based on experience since of IDN TLDs. Although additional time will be needed to implement the the 2003 introduction. Additional work is under way by an IDN TLD registry standards in applications, ICANN will follow the technical standards in working group to amend the guidelines further to ensure that the guide- the IDN TLD string requirements right away. line directions will be used deeper into the DNS hierarchy, particularly as a set of principles for implementing internationalized top-level labels.

For a more detailed history of technical development see http://www.isoc. org/pubpolpillar/docs/i18n-dns-chronology.pdf.

3 Intrnet Corporation for Assigned Names and Numbers (September 2009)

. . “

- of

- a

xn IDN on to has sole more

“

8649 2714 7913

with

that

7848 and

this ASCII

in Inter local

( role

p1b

be ]

823 429 The The http:// -- confusion application and

ICANN doesn’t 234 8236 doesn’t was

way

local an 2 2 the

at registrants xn For

al provides provides 310 202 will

understand

impact because languages

forward

web address

address s

is:

i collaborative

+1 +1 +32 +61 a more more

avoid

of to include Without

s name.

F F F F

each other. handling type and that

ICANN ICANN makers, IDNs as to name found

participate That looks .

of corporation parties.

for

critical that

competition keeping all

be to

name standard. (DNS)

coordination

[

is each

world. variety

level spam

n to http://www.unicode.org

domain important example need the the need

policy

its

have pints scheme can

expand ICANN how

domain

the

find Internet. benefit an

capable we

visit

wide of number.

stop to

identifiers. System domai you to a solutions

“example.test”) “example.test”)

interested interested

organization founded to founded organization Unicode

code that registry

promotes e

characters

9358 7900 2407

of approach version version only 7870

or have experts,

It th

form form

across www.icann.org

through the

dedicated global Program Program is f the public

the Internet.

823

429

resolve for

encoding

Name 234 8236 -

cannot

across across global Internet, of

where

unique ASCII conventions. 2 2 at

continue continue But 310 202

does

Internet IDN

the one

name DNS

hold of

stakeholders. stakeholders. visit: version version

it nonprofit

+1 +32 +61 +1 use profit

world a

- single T T T T

ersio - linguistic able the the

punycode decoded

know

v forums for all for forums The The bottom

is Domain tables have for

identifiers e the requires requires

cultural -

be other

reserved character Tables script, the

The intention is intention The

and

this

used

more information on information more

please

Internet’s Internet. od

Internet.

interoperable.

c system, not open

sequence and promote over

These These a see

For ny

each the the the often . evolution

unique is DNS and computer more information, please information, more all

the pu

person

is names. network

[email protected].

wouldn’t and

characters.

IDNs. for

on computers

Unicode on

is users

example, example,

technical

and the

never never of participative, participative, order for the for order Consortium

th naming

and --11b5bs3a9aj6g.

the

we so facilitate

Devanagari

commonly

your

of from these

The The

local For a o stable This prefix end for are digitalized. are

to f in will a fully internationalized secure secure identified.

1998.

information

ICANN USA USA Australia Belgium access

extend

policy is is contact x

another

number into f open, in

content into this

e and r

unique Unicode users scripts. manage

p with

Hindi,

more secure, Internet’s expansion

registration reach

achieve be

6ci4b4b3a.xn the characters. characters. containing containing purpose and coded and Punycode characters character unique and membership Unicode Hence develop, develop, in T The stable activities, ICANN’s icann.org/topics/idn/ continuing continuing about information Additional About To For languages, characters, and characters, languages, To developers, developers, involvement address to coordinates coordination formed participants net develops control deal the the

20006

90292 labels only

for

terms for

easier s is Code script).

Such

only

2000 used DC CA

“LDH and

-Latin as

level

. that TLD

can be characters. I code

here

name NSW

Brussels

speech characters

non

converts names to are provided are term related

all such all

applications Hangul -

Internet

understand.

by marks ASCI only

1040 representation - in Standard -

alternative the o

207.151.159.3, Engineering were allowedin for Sydney Los Angeles, B Washington,

local

IDN t from from

characters). the

IDNA “

these - or languages domain glossary n

name) “ of characters used

ASCII domain name

numerical

domain

ASCII and

Computers Computers represented by local by represented Glossary

convert

tio

for Greek). with

a to before internationaliza before The The

using

typing are --“, to -ASCII

in are

el “ diacritical accurately

Internet Application) protocol Application)

r ASCII

possible

numerical

text.

various

(American n

hyphen it being

i in 5 that domain

330

characters

(non

glossary the characters. names

alphabets the Originally, Originally, IDNs d the

with

common Bt.

makes the with (“example.test”

Name the

of by fact

Floor

]

(the Suite hyphen languages be availablewill languages

use

ASCII

characters is name communications around interna around communications

instead

ASCII makes

5th

Explanations -

Languages DNS Names and online understand. the

work write the Way, for level remains in remains level

code subset.

Name)

So domain hen

to Schuman, characters. to NW,

– subset to non ASCII ASCII that letters W 테스트

characters The

0 Hunter Street . . Chinese) world’s

)

characters IDNA isIDNA not able top ” and

] (“example.test” ] that of A this RFC3490

use the DNS can can DNS the use space. space. of domain

Code ASCII reference for internationalized top internationalized for reference Point

-9 “@ Street widely

in to

non

2, I Domain Admiralty with

r 0 Domain refers refers used the corresponding

dynamic

실례

an [ o

Domain digits address.

simpler that

”

Rond Alphabets

Hence

subset z, name

are entire entire string so short |

IP 1875 Level 6 4676 System)

contain contain this “a the devices

with

used

labels.

–

language

refers refers s

a reference for for reference while digits Hyphen) more

names topic defined

this a the used the in used the

are

Standard h

-z, Interchange)

a other to could to ASCII using

example:

Name names.

arcane Scripts

strings this level, level, παράδειγμα.test names, names, suc

domain

Scripts familiar

www.internic.net.

[

Digit, Digit, letters

usually r

| by numbers,

http://www.ietf.org and For applications into

(

t http://www.icann.org/en/topics/idn/idn-glossary.htm

the broader,

Usually

domain Usually

the

protocol the letters

a a type

names make at names.

name

of systems.

acronyms (for example, Arabic Arabic example, (for

that done referring referring second (Internationalized (Internationalized (American (American

domain is

on to points” restricted

(Domain

(Letter,

Force

only (Internationalized (Internationalized

SLDs TLDs can

is cha

example:

Information

handle a the

Angeles f

characters. labels by allowing a allowing by IDN DNS tion For ASCII domain instead o were were at IDN code contains contains computers understand or languages, European many by required scripts LDH you Task domain writing this for IDNA IDNA to local by represented communities. Languages IDN labels labels domain ASCII Not all characters use in domain domain in use characters

based below tionalizing available

Various Internationalized Sydney Los Washington, Brussels