<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 HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{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:72.0pt 72.0pt 72.0pt 72.0pt;}
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=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Ram Mohan [mailto:ram.mohan@icann.org] <br><b>Sent:</b> 28 August 2014 13:04<br><b>To:</b> 'Jonathan Robinson'<br><b>Cc:</b> 'Ram Mohan'; 'Board Variant Working Group'<br><b>Subject:</b> RE: Interaction between the ICANN Board's IDN Variant Working Group and the GNSO <br><b>Importance:</b> High<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Dear Jonathan,</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>The Board’s IDN Variant Working Group (BV-WG) members thank the GNSO Council and its community for maintaining an active interest in the IDN program. We are pleased to learn that we were able clarify the status of the IDN Program during the discussion on topics of mutual interest with the GNSO Council and community members in London. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>The GNSO Council is correct in its assessment that the current work on the development of the Label Generation Ruleset (LGR) for the Root Zone (P2.2) is technical in nature and policy advise is not required at this stage. If the Integration Panel or the Generation Panels communicate any such need in the future, the ICANN staff will issue the call for the advisor position as per the </span><span lang=EN-US style='color:#1F497D'><a href="https://www.icann.org/en/system/files/files/lgr-procedure-20mar13-en.pdf"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>procedure</span></a></span><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> for developing the LGR for the Root Zone. ICANN staff will ensure that the GNSO Council is informed in this case. </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>BV-WG continues to oversee and guide the progress of the IDN Variant TLD program. The Program is currently being advised by the BV-WG to focus on organizing the community efforts for developing the LGR for the Root Zone, which is the necessary pre-requisite for further implementation. The BV-WG encourages active involvement of the GNSO community in this current phase of the work by volunteering for the Generation Panels for the various scripts, especially for Latin and Cyrillic. The BV-WG welcomes the GNSO community’s intention to self-organize to review the original New gTLD IDN WG recommendations, with a view toward assisting Program staff with preparation for P7 following maturation of the work on LGR.</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Based on our prior agreement, IDN Program staff will continue to provide regular updates to GNSO Council and GNSO members. The BV-WG also looks forward to the continued discussion on the status and the future of the IDN Variant TLD program. </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Ram Mohan<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Chair, Board Variant Working Group<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Jonathan Robinson [<a href="mailto:jonathan.robinson@ipracon.com">mailto:jonathan.robinson@ipracon.com</a>] <br><b>Sent:</b> Tuesday, August 19, 2014 4:39 AM<br><b>To:</b> Ram Mohan<br><b>Subject:</b> Interaction between the ICANN Board's IDN Variant Working Group and the GNSO <br><b>Importance:</b> High<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>Dear Ram,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>I write to follow up on the meeting in London between the ICANN Board’s IDN Variant Working Group and a number of GNSO Council and community members. I’d like to thank you and the other Board members for taking the time to meet with them to discuss the progress of ICANN’s IDN Variant Program. We believe the discussion was helpful to all of us, and appreciate the updates that ICANN staff has been providing to the GNSO regarding ongoing work on the Program.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>I’d like to follow up on a specific observation that had been shared by a few GNSO community members in Singapore and London, regarding a perceived need for policy input into the Program by individuals with experience and expertise in ICANN policy development. Our discussions in Singapore and now in London have served to clarify that the current work being done in the Program (and specifically in P2.2) is largely technical in nature. In addition, I understand that ICANN's call last summer for advisors and experts to assist the Label Generation Rule-set (LGR) panels provided that the LGR panels might call on advisors (including ICANN staff) as the need arises. I note further that an advisor has already been appointed to the Integration Panel and that ICANN has announced that any additional advisors to be appointed will be at the request of the panels, in accordance with the LGR Procedure.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>As the Program progresses, and particularly in the near future as the panels conclude their work, some GNSO community members have noted that should the need for policy expertise arise at any point there are individuals within the GNSO who will be willing to volunteer to assist. In this regard the GNSO Council will be happy to serve as a contact point for any such requests. Separately, I note that a suggestion was made at the London meeting for interested GNSO community members to “self-organize” to review the original New gTLD IDN WG recommendations, with a view toward assisting Program staff with preparation for P7. It is my hope as GNSO Chair that these suggestions, along with ICANN staff continuing to provide their regular update to the GNSO on the Program, will allow the GNSO community to be of assistance to the important work of the Program and, in particular, if and when any policy questions are encountered.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>Thank you again for your time. I look forward to continuing our discussion and to facilitating any appropriate involvement of interested members of the GNSO community in the current and future work of the IDN Variant Program. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>Best regards,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>Jonathan Robinson</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>GNSO Council Chair</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div></body></html>