<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.date-display-single
{mso-style-name:date-display-single;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=FR link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif"'><a href="https://www.icann.org/en/news/announcements/announcement-3-21mar13-en.htm"><span lang=EN-US>https://www.icann.org/en/news/announcements/announcement-3-21mar13-en.htm</span></a></span><span lang=EN-US style='font-size:12.0pt;font-family:"Arial","sans-serif"'><br><span class=date-display-single>21 March 2013</span><o:p></o:p></span></p><p><span lang=EN-US style='font-family:"Arial","sans-serif"'>The IDN Variant TLD Program continues to progress towards a future secure and stable delegation of IDN variant TLDs. We are announcing today the conclusion of the third (out of four) phase of the Program with the publication of two reports: the IDN Root Label Generation Rules (LGR) Procedure, and the User Experience Study for Active Variant TLDs.<o:p></o:p></span></p><p><span lang=EN-US style='font-family:"Arial","sans-serif"'>The Root LGR Procedure defines the process for creating and maintaining the Label Generation Rules (LGR) for the DNS root zone. The project team consisted of a team of Internet community volunteers from across the globe representing multiple scripts and languages, as well as ICANN staff and expert consultants. Following two face-to-face meetings, conference and email work discussions, and numerous community input processes, including two Public Comment processes, the team produced the document entitled "</span><span style='font-family:"Arial","sans-serif"'><a href="https://www.icann.org/en/resources/idn/variant-tlds/draft-lgr-procedure-20mar13-en.pdf"><span lang=EN-US>Procedure to Develop and Maintain the Label Generation Rules for the DNS Root Zone in Respect of IDNA Labels</span></a></span><span lang=EN-US style='font-family:"Arial","sans-serif"'>" [PDF, 1.39 MB].<o:p></o:p></span></p><p><span lang=EN-US style='font-family:"Arial","sans-serif"'>This document provides a procedure for establishing some of the Label Generation Rules for the root zone. The procedure provides a mechanism for creating and maintaining the rules with respect to IDN labels for the root. This mechanism can be used to determine which Unicode code points are permitted for use in U-labels in the root zone, what variants (if any) are possible to allocate in the root zone, and what variants (if any) are automatically blocked. The mechanism is not the last stage in making determinations about IDN labels for the root. Rather, its output is to be consumed by other ICANN procedures that actually determine whether a particular label is allocated to someone, and whether it is delegated in the root.<o:p></o:p></span></p><p><span lang=EN-US style='font-family:"Arial","sans-serif"'>The User Experience Study examines issues that end-users, system administrators, application developers, and other users might face when IDN variant TLDs are activated. Incorporating inputs from public sessions, a Webinar, and two Public Comment periods, ICANN staff and expert consultants produced the report entitled "</span><span style='font-family:"Arial","sans-serif"'><a href="https://www.icann.org/en/resources/idn/variant-tlds/active-ux-21mar13-en.pdf"><span lang=EN-US>Examining the User Experience Implications of Active Variant TLDs</span></a></span><span lang=EN-US style='font-family:"Arial","sans-serif"'>" [PDF, 1.38 MB].<o:p></o:p></span></p><p><span lang=EN-US style='font-family:"Arial","sans-serif"'>The report: 1) summarizes and compares, from a user experience and registry management perspective, variant practices in several ccTLD registries; 2) proposes a set of guiding principles to define an acceptable user experience; and 3) identifies how various user communities (e.g., end users, system/network administrators, application developers, registrants, registrars and registries) will be impacted by active variant top-level domains, and 4) based on 1, 2, and 3, proposes a set of recommendations to ensure the security, stability and acceptable user experience for active variant top-level internationalized domains.<o:p></o:p></span></p><p><span lang=EN-US style='font-family:"Arial","sans-serif"'>These documents benefited from significant community participation. ICANN wishes to express its gratitude to all of the volunteers, reviewers, commentators, and the subject matter experts who contributed to these reports.<o:p></o:p></span></p><p><span lang=EN-US style='font-family:"Arial","sans-serif"'>ICANN is holding a </span><span style='font-family:"Arial","sans-serif"'><a href="http://beijing46.icann.org/sched-overview"><span lang=EN-US>public session</span></a></span><span lang=EN-US style='font-family:"Arial","sans-serif"'> at the ICANN Beijing meeting on the IDN Variant TLD Program to explain the Procedure and the results from the Study. In the meantime, work continues to ensure a secure and stable delegation of IDN variant TLDs once the IDN Variant TLD Program has finished its work, which is expected by June 2014. The original plan is being followed as indicated by the </span><span style='font-family:"Arial","sans-serif"'><a href="https://www.icann.org/en/groups/board/documents/resolutions-25sep10-en.htm#2.5"><span lang=EN-US>Board resolution on 25 September 2010</span></a></span><span lang=EN-US style='font-family:"Arial","sans-serif"'> and the </span><span style='font-family:"Arial","sans-serif"'><a href="https://www.icann.org/en/resources/idn/fast-track"><span lang=EN-US>IDN ccTLD Fast Track Process</span></a></span><span lang=EN-US style='font-family:"Arial","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";mso-fareast-language:FR'>Glen de Saint Géry <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";mso-fareast-language:FR'>GNSO Secretariat <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";mso-fareast-language:FR'><a href="mailto:gnso.secretariat@gnso.icann.org">gnso.secretariat@gnso.icann.org</a> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial","sans-serif";mso-fareast-language:FR'><a href="http://gnso.icann.org">http://gnso.icann.org</a><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>