<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:x="urn:schemas-microsoft-com:office:excel" 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:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-US link=blue vlink=purple><div class=WordSection1><p class=MsoPlainText style='text-align:justify'><span style='color:#1F497D'>Thank you James for pointing that out. At ICANN, the Wiki space is being migrated to another platform, thus leaving behind many broken links. The new link is <a href="https://community.icann.org/display/croscomlgrprocedure/All+Panels+Status+Updates">https://community.icann.org/display/croscomlgrprocedure/All+Panels+Status+Updates</a>.<o:p></o:p></span></p><p class=MsoPlainText style='text-align:justify'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoPlainText style='text-align:justify'><span style='color:#1F497D'>Hope that helps.<o:p></o:p></span></p><p class=MsoPlainText style='text-align:justify'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoPlainText style='text-align:justify'><span style='color:#1F497D'>Fahd<o:p></o:p></span></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoPlainText style='text-align:justify;border:none;padding:0in'><span style='color:#1F497D'><o:p> </o:p></span></p></div><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-----Original Message-----<br>From: James M. Galvin [mailto:jgalvin@afilias.info] <br>Sent: Wednesday, January 29, 2014 7:05 PM<br>To: Fahd Batayneh<br>Cc: James M. Galvin; VIP Mailing List<br>Subject: Re: [vip] Update on the TF-AIDN</p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The link below does not seem to work, nor does the link from the Tweet.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Has the document been removed or perhaps moved? Would you please provide an updated link?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Thanks,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Jim<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On 23 Jan 2014, at 4:04 PM, Fahd Batayneh <<a href="mailto:fahd.batayneh@icann.org"><span style='color:windowtext;text-decoration:none'>fahd.batayneh@icann.org</span></a>> wrote:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> Friends and Colleagues,<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> The Task Force on Arabic Script IDNs (TF-AIDN) submitted to ICANN last week the “Arabic Script Generation Panel (GP) Document” as part of the Variant IDN Project (VIP). The Arabic script community is the only linguistic community to submit a GP document as shown at <a href="https://community.icann.org/display/croscomlgrprocedure/Project+Status+Updates"><span style='color:windowtext;text-decoration:none'>https://community.icann.org/display/croscomlgrprocedure/Project+Status+Updates</span></a>.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> After the submission, members of the TF-AIDN were in consensus that it would be wise to provide access to the document and request feedback from the IDN community at-large, and so ICANN obliged to this request. The above website was updated accordingly to provide access to the document and announce the call for feedback.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Please disseminate the message across your networks and relevant contacts. The deadline for receiving any feedback is February 12.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> As a final remark, ICANN tweeted about this from its main Twitter feed (#ICANN) as shown athttps://twitter.com/ICANN/status/426211436562370560.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Thank you,<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Fahd Batayneh<o:p></o:p></p><p class=MsoPlainText>> ICANN<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p></div></body></html>