<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:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" 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=windows-1250">
<meta name=Generator content="Microsoft Word 12 (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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
text-align:justify;
font-size:11.0pt;
font-family:"Tahoma","sans-serif";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Verdana","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:595.3pt 841.9pt;
margin:1.0in 89.85pt 1.0in 89.85pt;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Dear
At Large<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Please
take notice of the communication from the ccNSO Chairman below. IDNs are a very
important issue, especially to the individual internet user who uses other
scripts. The At Large also has a working group on IDNs, chaired by Hong Xue,
and you are encouraged to join. At Large IDN Policy work can be found at <a
href="https://st.icann.org/alac/index.cgi?idn_policy_formation">https://st.icann.org/alac/index.cgi?idn_policy_formation</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Thanks<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Jacqueline
A. Morris<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>ALAC
Chair<o:p></o:p></span></p>
<p class=MsoNormal><span style='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 0in 0in 0in'>
<p class=MsoNormal align=left style='text-align:left'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> Chris
Disspain [mailto:ceo@auda.org.au] <br>
<b>Sent:</b> Thursday, October 18, 2007 21:06<br>
<b>To:</b> 'Jacqueline A. Morris'<br>
<b>Cc:</b> Boswinkel, Bart<br>
<b>Subject:</b> ccTLD IDN<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal align=left style='text-align:left'><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN-GB>Greetings Jacqueline,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB>As you are aware, the ICANN Board resolved
in San Juan on 29 June 2007, inter alia, that the ICANN community including the
GNSO, ccNSO, GAC, and ALAC continue to work collaboratively, taking the
technical limitations and requirements into consideration, to explore both an
interim and an overall approach to IDN ccTLDs associated with the ISO 3166-1
two-letter codes and recommend a course of action to the Board in a timely
manner. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB>Since San Juan, the ccNSO Council has
undertaken a considerable program of work to determine the best way to respond
to the Board’s request. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p>
<p class=MsoNormal><i><span lang=EN-GB>Overall approach<o:p></o:p></span></i></p>
<p class=MsoNormal><span lang=EN-GB>At a meeting on 12 September 2007, in
accordance with ICANN bylaws, the ccNSO Council requested an Issue Report be
prepared to establish whether the ccNSO should launch a PDP to develop the
policy for the selection and delegation of IDN ccTLDs associated with the ISO
3166-1 two letter codes. In preparing the Issue Report the Issue Manager
(Bart Boswinkel) should take into account the joint ccNSO GAC Issues Paper, the
technical limitations and requirements, and any other matters that the Issues
Manager considers to be of relevance. The Issues Report is the first step
in the process of launching ccPDP and at large input will be sought throughout
the preparation of the Report. Should a ccPDP be launched following the Issues
Report, the ccNSO will seek to work closely with the at large community.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><i><span lang=EN-GB>Interim approach<o:p></o:p></span></i></p>
<p class=MsoNormal><span lang=EN-GB>The ccNSO Council agreed that the first
step in considering an interim approach should be to determine the extent of
the pressing need claimed by some in the community. On 5 October 2007 I
sent a letter to all ccTLD managers seeking answers to three questions. I
anticipate that the responses to this letter will provide guidance as to
whether an interim fast-track approach to enable the introduction of a limited
number of IDN ccTLDs is a desirable and necessary step.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB>As there is no pre-defined process to deal
with such an interim approach, the ccNSO has released two discussion documents
(attached) regarding a possible interim approach to IDN ccTLDs. The <i>Designing
an Interim Approach</i> document considers how an interim approach could be
managed and canvasses time lines. The <i>Charter IDNC</i> document is a
first draft of what the charter for an interim approach committee might look
like. The principle of having an interim approach, the results of my
letter to ccTLD managers, and these two documents will be discussed by the
ccNSO in Los Angeles.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB>As you will appreciate there is some
urgency to resolve the issue of an interim approach and this is why the ccNSO
is working to a tight schedule. I would hope, in the event that an
interim fast-track approach can be developed to enable the deployment of a
limited number of IDN ccTLDs into the root, that the timing for this be closely
aligned with the release of gTLD IDNs.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB>I shall be grateful if you will forward
this email to the ALAC, At Large and RALO lists for their information.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB>Kind Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Chris
Disspain</span><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Chair
– ccNSO </span><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB> <o:p></o:p></span></p>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:1.0pt 0in 0in 0in'>
<div style='mso-element:para-border-div;border:none;border-top:solid windowtext 1.0pt;
padding:1.0pt 0in 0in 0in'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
border:none;padding:0in'><b><span lang=EN-GB style='font-size:7.5pt;font-family:
"Verdana","sans-serif"'>Important Notice - </span></b><span lang=EN-GB
style='font-size:7.5pt;font-family:"Verdana","sans-serif"'>This email may
contain information which is confidential and/or subject to legal privilege,
and is intended for the use of the named addressee only. If you are not the
intended recipient, you must not use, disclose or copy any part of this email.
If you have received this email by mistake, please notify the sender and delete
this message immediately. Please consider the environment before printing this
email.<span style='background:silver;mso-highlight:silver'><o:p></o:p></span></span></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-GB> </span><span lang=EN-GB style='font-size:12.0pt;font-family:
"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal align=left style='text-align:left'><span style='font-size:
12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<p><span style='font-size:10.0pt'>No virus found in this incoming message.<br>
Checked by AVG Free Edition.<br>
Version: 7.5.488 / Virus Database: 269.15.0/1077 - Release Date: 10/18/2007
09:54</span><o:p></o:p></p>
</div>
</body>
</html>
<BR>
<P><FONT SIZE=2>No virus found in this outgoing message.<BR>
Checked by AVG Free Edition.<BR>
Version: 7.5.488 / Virus Database: 269.15.0/1077 - Release Date: 10/18/2007 09:54<BR>
</FONT> </P>
<P><FONT SIZE=2 FACE="Arial"> </FONT> </P>