ICANN Public Comment: Second Annual IDN ccTLD Fast Track Process Review

ICANN is now opening a public comment forum for the second annual review of the IDN ccTLD Fast Track Process. Community members and specifically those who were directly involved in the IDN ccTLD Fast Track Process, including requesters, public authorities, and end users of the delegated IDN ccTLDs, are kindly asked to provide feedback on their experience in the process.

Public Comment Box Link: http://www.icann.org/en/news/public-comment/fast-track-review-2012-09apr12-en.htm

AFNIC opening IDN registratons for .FR ccTLD

AFNIC will shortly be opening the registration of IDNs (Internationalized Domain Names) to their ccTLD portfolio. All those who already are owners of .FR domain names or wish to register new ones will benefit from this feature. Starting May 2012, web site owners will be able to buy domain names with accents and special characters.

On February 3, Afnic, the organization that manages French domain names, announced the introduction of special characters in web addresses ending with .FR (France), .RE (La Réunion), .TF (French Southern and Antarctic Lands), .WF (Wallis and Futuna), .PM (Saint-Pierre and Miquelon) and .YT (Mayotte).

A total of 30 new characters will be introduced, including almost all accented vowels (à, é, è, î, ô, ù …), also the “i” and some consonants like “ñ” or “ß” (double “s” in German). Prior to this, domain names were restricted to numbers and Latin letters without accents.

The AFNIC will implement the launch of IDNs (Internationalized Domain Names), in two stages;

• 3 May 2012: Launch of the IDN sunrise period with the “Grandfathering” rule.
• 3 July 2012: Opening with IDN attribution according to the “first come, first served” rule.

Between May 3 and July 3, 2012, the owners of a domain name will be given the opportunity to buy different versions of their name with special characters. For example, societe.fr will be the only buyer who can purchase société.fr. However, after this two-month period, purchase of domain names will be open to all buyers. No privilege will be given to domain owners with the equivalent name without the special characters and a domain name will be sold to the first person who wants to buy it.  So it is essential that one secures their web addresses and protect individual brand names before someone else does.

The “sunrise” or the “Grandfathering” is designed to protect the acquired rights of existing domain owners. The name requested should be the exact equivalent of the name previously held. The requested name is registered in the same extension as the name filed initially in the ASCII (the code that allows only unaccented characters). For .e.g. the owner of “societe.fr” may save “société.fr” but not “société.re”. On the other hand the holder of a name such as “Muller-strasse.fr” may choose three possible variants of this name, namely “Müller-straße.fr”, “Muller-straße.fr” and “Müller- strasse.fr “or only one of them. Registering one of these options will retain his rights for a possible subsequent registration because the accents do not induce any change in meaning of the name in ASCII.

This opening of IDNs only concerns 30 new characters: ß, to, á, â, ã, ä, å, æ, ç, è, é, ê, ë, ì, í, î, ï, ñ, ò, ó, ô, õ, ö, ù, ú, û, ü, ý, ÿ, ow. Cyrillic and Arabic characters are not accepted at this time.

gTLD Strategy: International Relations

Here on gTLD Strategy, we spend a lot of our time talking about English-language gTLDs, mostly because that’s the language we speak best. The FairWinds staff dabbles in Spanish, Korean, French, Arabic, Chinese, and even Polish, but you could say English is our forte.

But, of course, ICANN’s New gTLD Program is not limited to gTLDs in English, or even in Latin script characters (or ASCII). Organizations will also be able to submit applications for Internationalized Domain Names, or IDNs, in non-Latin scripts like Cyrillic, Japanese, Arabic, Hindi, and others. Some have touted this as one of the greatest innovations of the New gTLD Program: now, instead of having to switch scripts between the second level and the top level when typing out domain names, international Internet users will be able to type entire domain names in their native scripts.

While IDNs are, indeed, a great development for Internet users, there is also a strategic element about them for brand owners. Specifically, several companies that we have worked with have decided to pursue transliterated variants of their brands as IDNs.

What kinds of companies should consider applying for IDNs? Essentially, any company that has already transliterated its brand or brands into non-Latin scripts for foreign markets should consider doing so. If your company has a market presence in Saudi Arabia, for example, and is known by an Arabic-transliterated version of its brand, you should consider applying for that brand as an Arabic IDN. Brands should especially consider this option if they have this kind of presence in a key growth market like China, India, or Russia, or a key mature market like Japan or Korea.

Other brands, however, are the same everywhere. By that, we mean they are known by the same Latin-script term across all countries and markets. In that case, applying for an IDN version of their brands is probably not worth the time, price or effort, because their customers are not used to seeing transliterated versions of those brands. Read the rest of this entry »

Notice of Extension of ICANN Comment Period: IDN Variant Issues Project – Proposed Project Plan

In response to comments made by participants at the ICANN public meeting in Costa Rica, ICANN has extended this public comment period for 21 days until 8 April 2012.

ICANN has also received a number of constructive comments for amendments to the proposed project plan.  As a result, it is likely that ICANN will publish a revised project plan in April 2012, also for public comment.

Additional comments on the current published project plan are welcomed to help shape the revision.

The IDN Variant Issues Project

ICANN is pleased to announce the publication of the final Integrated Issues Report [PDF, 2.15 MB] and the posting of the proposed project plan [PDF, 211 KB] for the next steps of the IDN Variant Issues Project for public comment.  The report explores the issues associated with the potential inclusion of IDN variant TLDs in the DNS root zone. The report also includes recommendations for additional work for taking the issues identified in the report and identifying potential solutions.

On 23 December 2011, the IDN Variant Issues Team published the draft Integrated Issues Report [PDF, 1.06 MB] for public comment. The report has now been updated to reflect the community feedback and published as the final Integrated Issues Report to conclude the second phase of the project. A version of tracked changes [PDF, 1.02 MB] from the draft report is also provided.

The Report marks the completion of Phase II of the Variant Issues Project. Following the recommendations identified within, the project team has created a project proposed plan for the next steps of the project and seeks community feedback. The public comment box is available at: http://www.icann.org/en/public-comment/idn-vip-proposed-project-plan-20feb12-en.htm

The IDN Variant Issues Proposed Project Plan for Next Steps along with the final Integrated Issues Report will be presented to the community during the ICANN public meeting to be held in Costa Rica during March 2012.

The IDN Variant Issues Project [PDF, 195 KB] was initiated by the ICANN Board of Directors in 2010.

Afilias Announces Intention to Apply for Chinese IDN Versions of .INFO Domain

DUBLIN–(Afilias Limited, the ICANN-designated registry operator for the .INFO top level domain (TLD) and a global provider of technical registry services, today announced that it will apply for the Simplified and Traditional Chinese language equivalents of .INFO under ICANN’s new gTLD program.

“Given the global presence of Afilias, Internationalized Domain Names — informally known as IDNs — have always been of great interest to us. We were the first company to launch IDN email, and believe that having IDN equivalents of .INFO for the world’s most populated country, in its primary languages, will be a major benefit to all Internet users in China,” said Ram Mohan, Executive Vice President and CTO, Afilias.

Roland LaPlante, Afilias Senior Vice President and CMO, said, “ICANN will only accept applications for new gTLDs between January 12, 2012, and April 12, 2012. Since it will likely be several years before anyone can again apply for an IDN version of a gTLD, we’re pleased to lead the way for IDN use and adoption.”

Afilias will support the new Chinese versions of .INFO with the same technology that will support many other new TLD applications: a state-of-the-art EPP registry, a globally diverse and redundant Anycast DNS network, 24×7 call-center and technical support, and links to the global distribution channel. In addition, Afilias provides other premium solutions to augment its registry offerings, including technology to enable mobile phone compatibility for websites and a unique IDN-capable email solution.

All Afilias services are DNSSEC and IPv6 ready, and reflect more than 10 years of experience in supporting gTLDs operating under ICANN contracts.

IDN Variant Issues Project: Draft Integrated Issues Report

Section I: Description, Explanation, and Purpose
On 20 April 2011, ICANN announced the IDN Variant Issues Project to explore the benefits and risks associated with the potential inclusion of IDN variant TLDs in the DNS root zone. This project was initiated in response to a 2010 ICANN Board of Directors resolution

ICANN is publishing today for public comment the draft Integrated Issues Report [PDF, 1.1 MB], a study of the issues that this project has identified in relation to the management of IDN variant TLDs. It represents the result of the completion of the second phase of the project.

The first phase involved the formation of six case study teams for the Arabic, Chinese, Cyrillic, Devanagari, Greek and Latin scripts. These teams were comprised of community experts with support by ICANN and worked on identifying issues related to IDN variant TLDs for each particular script, resulting in the publication in October of six individual reports detailing their findings.

The second phase focused on integrating those six case study reports into the Integrated Issues Report. To complete this phase, ICANN formed a coordination team comprised of experts from each of the case study teams. The coordination team advised ICANN in completing the Integrated Issues Report, which summarizes and categorizes the various issues related to the identification and management of IDN variant TLDs.

ICANN is now seeking community input on the issues discussed in this draft report. The report will be updated to reflect community feedback and the final Integrated Issues Report will be presented to the ICANN Board of Directors during their meeting at the ICANN public meeting in Costa Rica in March 2012.

Following publication of the final Integrated Issues Report, ICANN will facilitate work toward determining the conditions under which certain types of variant TLDs could be implemented.  Future work may also involve developing tools, processes, and protocols to support specific solutions, in cooperation with the appropriate experts.  For the purpose of arriving at a determination on whether variant TLDs can be delegated, it is expected that the required work can be completed in calendar year 2012.

Section II: Background
On 25 September 2010 the Board of Directors of the Internet Corporation for Assigned Names and Numbers (ICANN) directed the CEO “to develop an issues report identifying what needs to be done with the evaluation, possible delegation, allocation and operation of gTLDs containing variant characters IDNs as part of the new gTLD process in order to facilitate the development of workable approaches to the deployment of gTLDs containing variant characters IDNs.” (http://www.icann.org/en/minutes/resolutions-25sep10-en.htm-2.5

In response, ICANN conducted six case studies of individual scripts to investigate any issues associated with delegating and using IDN variant TLDs that need to be resolved to facilitate a good user experience.

The next phase focused on integrating those six case study reports into the draft Integrated Issues Report, which is being posted here for public comment.

Section III: Document and Resource Links
Documents posted for comment 

Additional Resources

Section IV: Additional Information
None
Staff Contact: Kurt Pritz Email: kurt.pritz@icann.org

Revised IDN ccTLD Fast Track Process Implementation Plan

15 December 2011

Following the ICANN Board’s approval on 8 December 2011 of the amendment to the IDN ccTLD Fast Track Process Implementation Plan, ICANN is providing this notice of publication for the Revised Implementation Plan. This amendment was considered following guidance received from the ccNSO during the ICANN meeting in Dakar, Senegal.

Two versions are posted: 1) the revised IDN ccTLD Fast Track Process Implementation Plan (http://www.icann.org/en/topics/idn/fast-track/idn-cctld-implementation-plan-15dec11-en.pdf [PDF, 851 KB]) and 2) a version that tracks the changes from the previous version (http://www.icann.org/en/topics/idn/fast-track/idn-cctld-implementation-plan-redline-15dec11-en.pdf [PDF, 902 KB]). The community should take note that the original version of the IDN ccTLD Fast Track Process Implementation Plan is now archived and superseded by the Revised Implementation Plan.

Background

On 26 October 2011, the ccNSO Council approved a resolution and communicated it in a letter from ccNSO Chair to ICANN Board Chair asking the Board to direct staff to amend the relevant sections of the IDN ccTLD Fast Track Implementation Plan. The amendment is to address specific cases when a requested IDN ccTLD string may be confusingly similar with the two-letter ASCII ccTLD corresponding to the same country or territory.

This work was developed out of the ccNSO Council Resolution from the ICANN meeting in San Francisco in March 2011. This resolution requested a sub-group of the IDN ccPDP Working Group 1 to develop, as soon as possible, guidelines (within the framework of the existing rules for the Fast Track) to improve the predictability of the evaluation process relating to string confusion as defined in the IDNC WG Final Report and the Final Implementation Plan, as adopted by the ICANN Board in November 2009.

ICANN conducted an initial review of the IDN ccTLD Fast Track Process and its implementation between October 2010 – January 2011. A summary and analysis was published in February and the Board acknowledged the Fast Track review at the ICANN meeting in March 2011.

The IDN ccTLD Fast Track Process Implementation Plan was approved by the ICANN Board at its meeting in Seoul, Republic of Korea in October 2009. A link to the original Implementation Plan may be found at: http://www.icann.org/en/topics/idn/fast-track/idn-cctld-implementation-plan-16nov09-en.pdf [PDF, 498 KB]

Domain .РФ success is one of the major events in 2011

On 22 November 2011, the Federal Agency for Printed and Mass Media (Rospechat) in tandem with the Russian Association for Electronic Communications (RAEC) co-organized a press conference “Runet: year in review and prospects of expansion” at the RIA Novosti press center . Andrey Kolesnikov, the CC’s CEO, took part in the press conference.

In his presentation, Sergey Plutogarenko, the RAEC’s CEO, listed major 2011 Runet developments. One of those, in his opinion, was the success of the Cyrillic domain .РФ. “By the end of the year, the number of domain names registered in zone .РФ nearly hit one million; it can now be asserted that the domain not only exists and functions successfully, but is popular with users,” – noted S. Plutogarenko. As to other major highlights of the year, he noted IPOs by two leading Russian Internet companies, Yandex and Mail.ru Group, as well as a rapid expansion of mobile Internet and e- commerce in Russia.

Andrey Kolesnikov, the CC’s CEO, elaborated on domain .РФ. “Russian domain space keep expanding and by its size already holds leading positions worldwide,” – noticed he. As of today, domain .РФ boasts 930,567 registered domain names, with 58.7% of them already delegated and 35% – actively used by their owners. As of today, more than a half of domains registered in November 2010, in the first month of the open registration period, have already been extended. “I figure, next year, domain .РФ will hit a mark of 1,000,000 registered domain names, – added A. Kolesnikov, – and we will have new equally exciting projects. We kicked off preparations for the applying for another top-level domain – .ДЕТИ, which should for an Internet space reserved exclusively for the youngest users.”

Mikhail Seslavinsky, Head of Rospechat, noted that the Internet forms a main source of information for 25% of Russians. “It’s a very significant figure. Some 57 million people use the Internet weekly, and the young Internet audience is growing constantly. Gradually, the Internet becomes available in libraries and educational organizations. More and more people go online using mobile devices.” M. Seslavinsky also added that 70% of users go online in search of information, 59% – to log in social networks and another 53%- to read news. “People are learning to look for relevant information online and begin to trust the Internet as a source of information.”

The press conference was also attended by Olga Brukovskaya, Vice-President on marketing, Mail.ru Group; Oleg Rumyantsev, pr-director of Rostelekom; Marina Treschova, General Director, Fast Lane Ventures; and Denis Davydov, Director of the Safer Internet League.

cctld.ru

IDN Implementation Guidelines v.3

Following the ICANN Board’s acceptance at the October 2011 meeting in Dakar, Senegal, ICANN is today providing notice of implementation for version 3.0 of the Guidelines for Implementation of Internationalized Domain Names. The IDN Guidelines are a list of general standards that many top-level domain registries deploying IDNs are required to follow based on the Internationalized Domain Names for Applications (IDNA) protocol standard from the IETF.

The Guidelines document was developed by IDN Guidelines Revision Working Group (comprised of ccTLD and gTLD registry representatives with IDN experience supported by ICANN staff). The new version modifies the current Version 2.2 to reflect the IDNABIS revision (“IDNA2008 protocol”) of the initial IDNA protocol (“IDNA2003″). ICANN previously published a draft version of the guidelines for public comment (see http://www.icann.org/en/public-comment/idn-guidelines-revision-27jul11-en.htm). The ICANN Board of Directors endorsed version 3.0 of the IDN Guidelines during their meeting on 28 October 2011. Registries offering IDN registrations should begin transitioning to version 3.0 of the IDN Guidelines.

The Internationalized Domain Names for Applications (IDNA) protocol is the technical standard for the implementation of IDNs for TLD registries, registrars and software developers that make IDNs available for their customers. The IDNA protocol references and further detail about the 2008 revision can be found here: http://www.icann.org/en/topics/idn/rfcs.htm