<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" 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 11 (filtered medium)">
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1093669186;
mso-list-type:hybrid;
mso-list-template-ids:-1397183360 67698707 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:roman-upper;
mso-level-tab-stop:.5in;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Dear Councilors and colleagues,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>As requested at the Council call yesterday, following the Council’s
deliberations on the IDN Terms of Reference, I have consolidated the proposed changes
in the drafting below. The former ToR 1 and 5 a,c,d have been moved as
considerations to the preamble section and a new ToR 1 covers a) PDP timeline adaptation
and b) interaction. I hope this properly reflects the meeting outcome and I
look forward to any comments.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Very best regards<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Olof<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>PS. In view of the questions for clarification during the
call, some rephrasing of the former ToR 5 a-d could also be envisaged. Not done
in the version below, though. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><u><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>Preamble<o:p></o:p></span></font></u></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>The following terms of reference for further work are
focused on GNSO activities and therefore address gTLD considerations.
Subsequent to working group assessment of the Preliminary Issues Report, the
terms of reference were adopted by the GNSO Council on xx August 2006. In
addition, the GNSO Council resolved that policy development activities relating
to the introduction of generic Top-Level Domains with IDN Labels (IDN-gTLDs)
shall be guided by the following considerations:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-9.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><font size=3 face=Arial><span
style='font-size:12.0pt;font-family:Arial'><span style='mso-list:Ignore'><font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font>I.<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><font face=Arial><span
style='font-family:Arial'>Given the urgency of current interest in fully
localized domain names, and the limited range of potential outcomes of the impending
technical tests of devices for entering top-level IDN labels into the root
zone, the policy for the inclusion of IDN-gTLDs can begin to be assessed.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-9.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><font size=3 face=Arial><span
style='font-size:12.0pt;font-family:Arial'><span style='mso-list:Ignore'><font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font>II.<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><font face=Arial><span
style='font-family:Arial'>Policy development will proceed under the assumption
that top-level IDN labels will be added to the root zone, awaiting the outcome
of the requisite initial trials.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-9.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><font size=3 face=Arial><span
style='font-size:12.0pt;font-family:Arial'><span style='mso-list:Ignore'><font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font>III.<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><font face=Arial><span
style='font-family:Arial'>Determining that a proposed new IDN label is
adequately differentiated from a pre-existing label requires comp<st1:PersonName
w:st="on">ari</st1:PersonName>son in graphic, phonetic, and semantic
terms. Two levels of differentiation are necessary, of which the one
pertains to situations where the two labels are being considered for delegation
to the same operator, and the other where the labels are to be delegated to
independent registries. The former case can be further subdivided into
two situations. In the one, the intention is for the same set of
sub-domain names to appear under multiple TLD labels, and in the other
independent name trees are to be established.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-9.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><font size=3 face=Arial><span
style='font-size:12.0pt;font-family:Arial'><span style='mso-list:Ignore'><font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font>IV.<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><font face=Arial><span
style='font-family:Arial'>It is necessary to be particularly mindful of detail
which, although initially considered in the IDN context, may otherwise be
relevant to the New gTLD PDP. The association of two separate labels with the
same TLD is an example of this, given that the linguistic justification for
such action can as easily be derived from two languages that can be adequately represented
using ASCII characters as it can from a situation where one or both labels
require IDN representation.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-9.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><font size=3 face=Arial><span
style='font-size:12.0pt;font-family:Arial'><span style='mso-list:Ignore'><font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font>V.<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><font face=Arial><span
style='font-family:Arial'>The implementation of policies based on an aliasing
mechanism (as implicit in III above) may require the development of new technical
resources if the tests of the currently available alternatives (as referenced
in I above) determine that none are viable. In general, care should be taken to
recognize distinctions between technical and policy concerns, as well as
cultural and political considerations. Addressing their manifold
interdependencies should be approached as collaborative action with other
organizations as appropriate to any given case.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:-.5in;mso-text-indent-alt:
-9.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><font size=3 face=Arial><span
style='font-size:12.0pt;font-family:Arial'><span style='mso-list:Ignore'><font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font>VI.<font size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>
</span></font></span></span></font><![endif]><font face=Arial><span
style='font-family:Arial'>In view of the complexities and interdependencies
involved in the policy development task, the pre-determined standard PDP
timeline must be adapted to allow sufficient time for all the necessary
activities and interaction steps. <o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.25in'><font size=3 face=Arial><span
style='font-size:12.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><u><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>Terms of Reference<o:p></o:p></span></font></u></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>1. Initial and General Provisions<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>a. As an initial task, in line with Consideration VI above,
plan the necessary activities and interaction steps for this PDP in cooperation
with ICANN staff and develop a suitable timeline for the PDP.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>b. In general, during this PDP, identify and document any policy
issue for which it is essential that policy is harmonized for all IDN-TLDs and develop
the related policy for IDN-gTLDs in interaction with other relevant entities,
including other ICANN Supporting Organizations and Advisory Committees, in a
way that ensures harmonization of the policy outcome. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>2. Selection Criteria for Top-Level Domains with IDN Labels<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>a. Taking into account the background, considerations and findings
regarding selection criteria in the New gTLD PDP [PDP-Dec05], develop modified
or additional criteria for the inclusion of IDN labels in subsequent action
toward ICANN's goals of expanding the use and usability of the Internet.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>3. Allocation Methods for Top-Level Domains with IDN Labels<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>a. Taking into account the background, considerations and findings
regarding allocation methods in the New gTLD PDP [PDP-Dec05], develop modified
or additional allocation methods that may be applied to gTLDs with IDN labels.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>4. Policy to Guide Contractual Conditions for Top-Level
Domains with IDN<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>Labels<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>a. Taking into account the background, considerations and findings
regarding contractual conditions in the New gTLD PDP [PDP-Dec05], develop policies
to guide the specific contractual criteria needed for gTLDs with IDN labels, to
be made publicly available prior to any application rounds.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>5. Additional Policy Aspects Regarding Top-Level Domains
with IDN<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>Labels<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'>a. With specific regard to Consideration III above,
determine whether the script used for an IDN-gTLD label can, or should, be exclusively
propagated on all lower levels in the sub-domain tree (allowing for the general
exceptions attaching to that script as referenced in the ICANN IDN Guidelines).
If such a procedure is viable, intention to implement it may serve as a
differentiation criterion or otherwise be invoked in the consideration of a
request for a new label.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face=Arial><span style='font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
</div>
</body>
</html>