Misplaced Pages

#735264

40-513: IDN can refer to: Internationalized domain names Institut Industriel du Nord , the former name of École Centrale de Lille Indonesia , the ISO 3-letter country code International Data Number , in the context of an X.121 address Identity driven networking Integrated data network, the digital data network developed by Reuters and dedicated to financial markets Integrated Delivery Network,

80-542: A long period of testing in a set of subdomains in the test top-level domain. Eleven domains used language-native scripts or alphabets, such as "δοκιμή", meaning test in Greek . These efforts culminated in the creation of the first internationalized country code top-level domains (IDN ccTLDs) for production use in 2010. In the Domain Name System, these domains use an ASCII representation consisting of

120-562: A network of healthcare organizations, see IDS Intradermal nevus , a type of skin mole See also [ edit ] IDK Topics referred to by the same term [REDACTED] This disambiguation page lists articles associated with the title IDN . If an internal link led you here, you may wish to change the link to point directly to the intended article. Retrieved from " https://en.wikipedia.org/w/index.php?title=IDN&oldid=1183359020 " Category : Disambiguation pages Hidden categories: Short description

160-443: A new class of top-level domains, assignable to countries and independent regions, similar to the rules for country code top-level domains . However, the domain names may be any desirable string of characters, symbols, or glyphs in the language-specific, non-Latin alphabet or script of the applicant's language, within certain guidelines to assure sufficient visual uniqueness. The process of installing IDN country code domains began with

200-454: A suitable ASCII-based form that could be handled by web browsers and other user applications. IDNA specifies how this conversion between names written in non-ASCII characters and their ASCII-based representation is performed. An IDNA-enabled application can convert between the internationalized and ASCII representations of a domain name. It uses the ASCII form for DNS lookups but can present

240-581: A unified IDN table for the Arabic script , and is an example of community collaboration that helps local and regional experts engage in global policy development, as well as technical standardization. In October 2009, the Internet Corporation for Assigned Names and Numbers (ICANN) approved the creation of internationalized country code top-level domains (IDN ccTLDs) in the Internet that use

280-639: Is a top-level domain in the Domain Name System (DNS) of the Internet . IDN ccTLDs are specially encoded domain names that are displayed in an end user application, such as a web browser , in their language-native script or alphabet , such as the Arabic alphabet , or a non-alphabetic writing system , such as Chinese characters . IDN ccTLDs are an application of the internationalized domain name system to top-level Internet domains assigned to countries, or independent geographic regions. Although

320-607: Is a technical solution to translate names written in language-native scripts into an ASCII text representation that is compatible with the DNS. Internationalized domain names can only be used with applications that are specifically designed for such use; they require no changes in the infrastructure of the Internet. IDN was originally proposed in December 1987 by Martin Dürst and implemented in 1990 by Tan Juay Kwang and Leong Kok Yong under

360-400: Is available for Internet Explorer 6 to provide IDN support. Internet Explorer 7.0 and Windows Vista 's URL APIs provide native support for IDN. The conversions between ASCII and non-ASCII forms of a domain name are accomplished by a pair of algorithms called ToASCII and ToUnicode. These algorithms are not applied to the domain name as a whole, but rather to individual labels. For example, if

400-461: Is different from Wikidata All article disambiguation pages All disambiguation pages Internationalized domain name The DNS, which performs a lookup service to translate mostly user-friendly names into network addresses for locating Internet resources, is restricted in practice to the use of ASCII characters, a practical limitation that initially set the standard for acceptable domain names. The internationalization of domain names

440-466: Is processed by Nameprep to give bücher , and then converted to Punycode to result in bcher-kva . It is then prefixed with xn-- to produce xn--bcher-kva . The resulting name suitable for use in DNS records and queries is therefore xn--bcher-kva.example . While the Arab region represents 5 percent of the world's population, it accounts for a mere 2.6 percent of global Internet usage. Moreover,

SECTION 10

#1732782374736

480-676: The IETF formed a new IDN working group to update the current IDNA protocol. In April 2008, UN-ESCWA together with the Public Interest Registry (PIR) and Afilias launched the Arabic Script in IDNs Working Group (ASIWG), which comprised experts in DNS, ccTLD operators, business, academia, as well as members of regional and international organizations. Operated by Afilias's Ram Mohan, ASIWG aims to develop

520-638: The Nameprep algorithm. This converts the label to lowercase and performs other normalization. ToASCII then translates the result to ASCII, using Punycode . Finally, it prepends the four-character string " xn-- ". This four-character string is called the ASCII Compatible Encoding ( ACE ) prefix. It is used to distinguish labels encoded in Punycode from ordinary ASCII labels. The ToASCII algorithm can fail in several ways. For example,

560-626: The IDNA standard for native language scripts. In May 2010, the first IDN ccTLDs were installed in the DNS root zone . Internationalizing Domain Names in Applications (IDNA) is a mechanism defined in 2003 for handling internationalized domain names containing non- ASCII characters. Although the Domain Name System supports non-ASCII characters, applications such as e-mail and web browsers restrict

600-774: The ISO 3166-1 two-letter codes in a short time frame to meet near term demand." The group proposed a methodology using ICANN's Fast Track Process based on the ICANN charter to work with the Internet Assigned Numbers Authority In October 2009, ICANN resolved to start accepting applications for top-level internationalized domain names from representatives of countries and territories in November. Starting 16 November 2009, nations and territories could apply for IDN ccTLDs. Egypt, Saudi Arabia,

640-411: The Internet more accessible and user friendly to millions around the globe, regardless of where they live or what language they speak," he added. Senior director for internationalised domain names Tina Dam said it was "the most significant day" since the launch of the Internet. According to ICANN, Arabic was chosen for the initial roll out because it is one of the most widely used non-Latin languages on

680-645: The Internet. There are problems entering a mixed left-to-right and right-to-left text string on a keyboard, making fully Arabic web addresses extra useful. Additional IDN ccTLDs had been implemented by the end of June 2010: one using Cyrillic , .рф (for Russia ), and five using Chinese characters (the first using a non-alphabetical writing system ) approved by the ICANN board on 25 June 2010: The dual domains delegated to each of CNNIC and TWNIC are synonymous, being purely orthographical variations differing only in using simplified forms ( 国 and 湾 ), as preferred in mainland China , versus traditional forms of

720-506: The URL wіkіреdіа.org is formed, which is virtually indistinguishable from the visual representation of the legitimate wikipedia.org (possibly depending on typefaces). Many top-level domains have started to accept internationalized domain name registrations at the second or lower levels. Afilias (.INFO) offered the first gTLD IDN second-level registrations in 2004 in the German language. DotAsia,

760-762: The United Arab Emirates, and the Russian Federation were among the first countries to apply for the new internationalized domain name country code top-level domains. In January 2010 ICANN announced that these countries' IDN ccTLDs were the first four new IDN ccTLDs to have passed the Fast Track String Evaluation within the domain application process. In May 2010, twenty-one different countries representing eleven languages, including Chinese, Russian , Tamil , and Thai , had requested new IDN country codes. On 5 May 2010,

800-437: The address bar. This limits their usefulness; however, they are still valid and universally accessible domains. Several registries support Punycode emoji characters as emoji domains . The use of Unicode in domain names makes it potentially easier to spoof websites as the visual representation of an IDN string in a web browser may make a spoof site appear indistinguishable from the legitimate site being spoofed, depending on

840-525: The characters that can be used as domain names for purposes such as a hostname . Strictly speaking, it is the network protocols these applications use that have restrictions on the characters that can be used in domain names, not the applications that have these limitations or the DNS itself. To retain backward compatibility with the installed base, the IETF IDNA Working Group decided that internationalized domain names should be converted to

SECTION 20

#1732782374736

880-793: The domain class uses the term code , some of these ccTLDs are not codes but full words. For example, السعودية (as-Suʻūdiyya) is not an abbreviation of "Saudi Arabia", but the commonwealth short-form name of the country in Arabic . Countries with internationalized ccTLDs also retain their traditional ASCII-based ccTLDs. As of August 2018 there are 59 approved internationalized country code top-level domains, of them at least 47 used. The most used are .рф (the Russian Federation ) with over 900,000 domains names, .台灣 (Taiwan) with around 500,000 and .中国 (China) with over 200,000 domains. Still as of 2018 around 20 countries using non-Latin script do not have an internationalized country code top-level domain, including Japan and Iran . The ICANN board approved

920-505: The domain name is www.example.com, then the labels are www , example , and com . ToASCII or ToUnicode is applied to each of these three separately. The details of these two algorithms are complex. They are specified in RFC 3490. Following is an overview of their workings. ToASCII leaves ASCII labels unchanged. It fails if the label is unsuitable for the Domain Name System. For labels containing at least one non-ASCII character, ToASCII applies

960-629: The establishment of an internationalized top-level domain name working group within the Country Code Names Supporting Organization (ccNSO) in December 2006. They resolved in June 2007 inter alia to proceed and asked the IDNC Working Group to prepare a proposal, which the group delivered in June 2008, "to recommend mechanisms to introduce a limited number of non-contentious IDN ccTLDs, associated with

1000-569: The final string could exceed the 63-character limit of a DNS label. A label for which ToASCII fails cannot be used in an internationalized domain name. The function ToUnicode reverses the action of ToASCII, stripping off the ACE prefix and applying the Punycode decode algorithm. It does not reverse the Nameprep processing, since that is merely a normalization and is by nature irreversible. Unlike ToASCII, ToUnicode always succeeds, because it simply returns

1040-479: The first implementations, all in the Arabic alphabet , were activated. Egypt was assigned the مصر. country code, Saudi Arabia السعودية. , and the United Arab Emirates امارات. , (all reading right to left as is customary in Arabic). ICANN CEO Rod Beckstrom described the launch as "historic" and "a seismic shift that will forever change the online landscape." "This is the beginning of a transition that will make

1080-554: The font used. For example, the Unicode character U+0430 – Cyrillic small letter a – can look identical to the Unicode character U+0061 ( Latin small letter a ), used in English. As a concrete example, using Cyrillic letters а , е , і , р ( a ; then "Ie"/"Ye" U+0435, looking essentially identical to Latin letter e ; then U+0456, essentially identical to Latin letter i ; and "Er" U+0440, essentially identical to Latin letter p ),

1120-553: The guidance of Tan Tin Wee. After much debate and many competing proposals, a system called Internationalizing Domain Names in Applications (IDNA) was adopted as a standard, and has been implemented in several top-level domains . In IDNA, the term internationalized domain name means specifically any domain name consisting only of labels to which the IDNA ToASCII algorithm (see below) can be successfully applied. In March 2008,

1160-413: The internationalized form to users who presumably prefer to read and write domain names in non-ASCII scripts such as Arabic or Hiragana. Applications that do not support IDNA will not be able to handle domain names with non-ASCII characters, but will still be able to access such domains if given the (usually rather cryptic) ASCII equivalent. ICANN issued guidelines for the use of IDNA in June 2003, and it

1200-460: The original string if decoding fails. In particular, this means that ToUnicode does not affect a string that does not begin with the ACE prefix. IDNA encoding may be illustrated using the example domain Bücher.example . ( German : Bücher , lit.   'books'.) This domain name has two labels, Bücher and example . The second label is pure ASCII and is left unchanged. The first label

1240-462: The percentage of Internet users among the population in the Arab world is a low of 11 percent, compared to the global rate of 21.9 percent. However, Internet usage in the region has grown by 1,426 percent between the years 2000 and 2008, which represents a large increase, particularly compared to the average world growth rate of 305.5 percent over the same period. It is reasonable to infer, therefore, that

IDN - Misplaced Pages Continue

1280-849: The prefix " xn-- " followed by the Punycode translation of the Unicode representation of the language-specific alphabet or script glyphs. For example, the Cyrillic name of Russia's IDN ccTLD is "рф". In Punycode representation, this is " p1ai ", and its DNS name is " xn--p1ai ". Other registries support non-ASCII domain names. The company ThaiURL.com in Thailand supports ".com" registrations via its own IDN encoding, ThaiURL . However, since most modern browsers only recognize IDNA/Punycode IDNs, ThaiURL-encoded domains must be typed in or linked to in their encoded form, and they will be displayed thus in

1320-2641: The registrar for the TLD Asia , conducted a 70-day sunrise period starting May 11, 2011 for second-level domain registrations in the Chinese, Japanese and Korean scripts . A   .ac .ad .ae .af .ag .ai .al .am .ao .aq .ar .as .at .au .aw .ax .az    B   .ba .bb .bd .be .bf .bg .bh .bi .bj .bm .bn .bo .br .bs .bt .bw .by .bz    C   .ca .cc .cd .cf .cg .ch .ci .ck .cl .cm .cn .co .cr .cu .cv .cw .cx .cy .cz    D   .de .dj .dk .dm .do .dz    E   .ec .ee .eg .er .es .et .eu    F   .fi .fj .fk .fm .fo .fr    G   .ga .gd .ge .gf .gg .gh .gi .gl .gm .gn .gp .gq .gr .gs .gt .gu .gw .gy    H   .hk .hm .hn .hr .ht .hu    I   .id .ie .il .im .in .io .iq .ir .is .it    J   .je .jm .jo .jp    K   .ke .kg .kh .ki .km .kn .kp .kr .kw .ky .kz    L   .la .lb .lc .li .lk .lr .ls .lt .lu .lv .ly    M   .ma .mc .md .me .mg .mh .mk .ml .mm .mn .mo .mp .mq .mr .ms .mt .mu .mv .mw .mx .my .mz    N   .na .nc .ne .nf .ng .ni .nl .no .np .nr .nu .nz    O   .om    P   .pa .pe .pf .pg .ph .pk .pl .pm .pn .pr .ps .pt .pw .py    Q   .qa    R   .re .ro .rs .ru .rw    S   .sa .sb .sc .sd .se .sg .sh .si .sk .sl .sm .sn .so .sr .ss .st .su .sv .sx .sy .sz    T   .tc .td .tf .tg .th .tj .tk .tl .tm .tn .to .tr .tt .tv .tw .tz    U   .ua .ug .uk .us .uy .uz    V   .va .vc .ve .vg .vi .vn .vu    W   .wf .ws    Y   .ye .yt    Z   .za .zm .zw .κπ ( kp , Cyprus ) - .日本 ( Nippon , Japan ) .bl .bq .eh .mf .su .xk .bv .gb .sj .an .bu .cs .dd .tp .um .yu .zr Internationalized country code top-level domain An internationalized country code top-level domain

1360-472: The same characters ( 國 and 灣 ), as used in Taiwan . The new country codes were available for immediate use, although ICANN admit they may not work properly for all users initially. According to Egypt's communication and information technology minister, three Egyptian companies were the first to receive domain licenses on the new "masr" [مصر transliterated ] country code. Egypt's Ministry of Communications

1400-462: The usage growth could have been even more significant if DNS was available in Arabic characters. The introduction of IDNs offers many potential new opportunities and benefits for Arab Internet users by allowing them to establish domains in their native languages and alphabets, and to create a whole range of services and localized applications on top of those domains. In 2009, ICANN decided to implement

1440-510: Was already possible to register .jp domains using this system in July 2003 and .info domains in March 2004. Several other top-level domain registries started accepting registrations in 2004 and 2005. IDN Guidelines were first created in June 2003, and have been updated to respond to phishing concerns in November 2005. An ICANN working group focused on country-code domain names at the top level

1480-720: Was approved by the ICANN BOARD on 7 January 2011 to represent Pakistan in Arabic script. On 4 February 2017, IDN ccTLD پاکستان. was delegated to the National Telecommunication Corporation and the zone was added to the root servers on February 15, 2017. The European Union applied in 2016 for the Cyrillic domain .ею and the Greek domain .ευ . ею was approved and put into operation, but ευ was rejected as being too similar to .eu also belonging to

1520-534: Was formed in November 2007 and promoted jointly by the country code supporting organization and the Governmental Advisory Committee. Additionally, ICANN supports the community-led Universal Acceptance Steering Group, which seeks to promote the usability of IDNs and other new gTLDS in all applications, devices, and systems. Mozilla 1.4, Netscape 7.1, and Opera 7.11 were among the first applications to support IDNA. A browser plugin

1560-490: Was possibly the first functional website with an entirely Arabic address. The ccTLD .рф for Russia launched on 13 May. Bulgaria 's .бг was rejected by the ICANN due to its visual similarity with .br . .бг was eventually approved in 2014. The Ukrainian string .укр was approved by the ICANN Board on 28 February 2013. The zone was added to the root servers on March 19, 2013. The Bulgarian string .бг

1600-468: Was rejected a second time in March 2011 but was approved by the ICANN Board in 2014, and the Greek .ελ string in 2015, both after controversies about possibilities of confusion with existing Latin strings. India has applied for top-level domains in each of its local scripts, at first seven, later eight more. The first one, .भारत , was approved 2011 and became active in 2014. The general flow of applications has ceased after 2016. The Pakistan string پاکستان.

#735264