<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 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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:Tahoma;
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;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.EmailStyle18
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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 bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I am Ok with the revisions. <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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regards,<br>
Sarmad<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'> rt4-whois-bounces@icann.org
[mailto:rt4-whois-bounces@icann.org] <b>On Behalf Of </b>Kathy Kleiman<br>
<b>Sent:</b> Friday, May 04, 2012 9:20 PM<br>
<b>To:</b> Emily Taylor<br>
<b>Cc:</b> rt4-whois@icann.org<br>
<b>Subject:</b> Re: [Rt4-whois] Fwd: IDN - a few more changes to bring it up to
the readability of the rest of the Summary [SEC=UNCLASSIFIED]<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I like it, tx Peter and Emily. However, I defer to our lead
IDN drafters, Sarmad and Michael, for final approval.<br>
<br>
What I like is that it helps makes the whole issue approachable -- and hopefully
the rest of the Community will spend more time and attention on this issue in
which a core of dedicated people have worked so hard and so well. <br>
<br>
Best,<br>
Kathy<br>
<br>
<br>
<br>
<br>
<o:p></o:p></p>
<p class=MsoNormal>Thank you Peter <o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I think this is a good synthesis. One extra element,
which is easily forgotten, is that internationalised WHOIS data isn't just an
IDN problem, but one which has been around ever since Chinese, Arabic and
Russian speakers have been registering domain names. So, the delay in
addressing this has not just been a year (since introduction of IDN.IDN) or a
decade (IDN.tld), it's even longer than that.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>So, I've added some language for this, based on the first
paragraph of the IDN chapter (highlighted below).<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Kind regards<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
Emily<o:p></o:p></p>
<div>
<p class=MsoNormal>On 4 May 2012 08:08, Nettlefold, Peter <<a
href="mailto:Peter.Nettlefold@dbcde.gov.au" target="_blank">Peter.Nettlefold@dbcde.gov.au</a>>
wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hello again all,</span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As I’ve said previously, I’m no expert in this area, but to
hopefully help move this forward I have attempted to pick up what seemed to be
the major themes from both sets of text.</span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I hope this helps, and please feel free to edit or discard as
needed.</span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Cheers,</span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Peter</span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><u><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:windowtext'>Findings</span></u><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:18.0pt'> </span><span lang=EN-AU><o:p></o:p></span></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
lang=EN-AU style='font-size:13.5pt;font-family:"Calibri","sans-serif";
color:windowtext'>Developments associated with the WHOIS protocol and
registration data have not kept pace with the real world. A significant example
of this is International Domain Names (IDNs). IDNs have been available for
registration at the second level for over a decade, and were introduced in 2010
at the root level. However, these developments were not accompanied by
corresponding changes related to WHOIS. In short, the current WHOIS protocol
has no support for non-ASCII characters, and cannot signal a non-ASCII script.</span><span
lang=EN-AU><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:13.5pt;font-family:"Calibri","sans-serif";
color:windowtext'>This means that while domain names can now be written in a
range of scrips (such as Arabic and Cyrillic), the contact
information must still be transliterated into a format ill-suited to the
purpose. The NORC Study on Data Accuracy highlighted IDN contact data as a
major cause of apparent inaccuracy. </span><span lang=EN-AU><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:18.0pt;font-family:"Calibri","sans-serif";
background:#FFFF33'>The failure to reflect internationalised registration data
does not just affect IDNs, however, and has existed for much longer - ever
since domain names have been registered by registrants globally. Global
users need to represent their local names, postal addresses and other contact
and technical information in the script(s) which they use. </span> <o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:13.5pt;font-family:"Calibri","sans-serif";
color:windowtext'> </span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
lang=EN-AU style='font-size:13.5pt;font-family:"Calibri","sans-serif";
color:windowtext'>These are difficult issues, and there is ongoing work within
ICANN in this area (e.g. the joint gNSO and SSAC working group on
Internationalised Registration Data – IRD WG). As the need is imminent, this
work needs to proceed with priority in coordination with other relevant work
beyond ICANN’s ambit, to make internationalised domain name registration data
accessible.<br>
</span><span lang=EN-AU><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><span lang=EN-AU><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 style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> <a
href="mailto:rt4-whois-bounces@icann.org" target="_blank">rt4-whois-bounces@icann.org</a>
[mailto:<a href="mailto:rt4-whois-bounces@icann.org" target="_blank">rt4-whois-bounces@icann.org</a>]
<b>On Behalf Of </b>Kathy Kleiman<br>
<b>Sent:</b> Thursday, 3 May 2012 11:43 PM<br>
<b>To:</b> <a href="mailto:rt4-whois@icann.org" target="_blank">rt4-whois@icann.org</a><br>
<b>Subject:</b> [Rt4-whois] Fwd: IDN - a few more changes to bring it up to the
readability of the rest of the Summary</span><span lang=EN-AU><o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-AU> <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
lang=EN-AU>Dear All,<br>
I appreciate the evolution of the IDNs text (and see nice changes in the
findings). Canwe go a bit further? I was wondering if we might take one more
attempt to a) define IDNs (for the many readers who will have no idea), b) and
define better the ambiguous term "this environment".<br>
<br>
For smarter (and more awake) people than I am, do you see a way to merge the
two texts below? I truly want to make sure that everyone understands the
importance and timeliness of our recommendations!<br>
<br>
Also, I saw that Peter has some ideas in this area, but did not propose wording
changes (I don't think). Does some of the text below cover your thoughts?<br>
<br>
Best and tx,<br>
Kathy<br>
<br>
<br>
<u>Findings/Kathy:<br>
</u>[from the Executive Summary] Policy and implementation of the Whois
protocol and registration data have not kept pace with the real world.
International Domain Names (IDNs) were introduced to great fanfare by ICANN in
2000, and in 2010 at the root level, without a corresponding change to its
policies related to WHOIS.<br>
<br>
What this means, is that while domain names can now be written in Arabic for
example, the contact information for these domains must still be transliterated
into a format ill-suited to the purpose. [from the Public Forum Slides] These
are difficult issues, and members of the ICANN Community have worked hard to
date, but the current Whois protocol has no support for non-ASCII characters
and cannot signal a non-ASCII script. Some ccTLD registries and registrars have
implemented ad hoc solutions and arbitrary mappings of local scripts onto ASCII
code points, and as a result, IDN Whois data today often appears as a nonsense
sequence of ASCII characters.<br>
<br>
<u>Findings/Sarmad<br>
</u>Perhaps it should be no surprise that within this environment [<i>Kathy:
which environment?] </i>, policy and implementation have not kept pace with the
real world. A significant example of this is Internationalised Domain
Names (IDN), which have been available for registration at the second level for
over a decade, and at the Top Level for more than a year. During this time,
WHOIS policies were not amended to accommodate the obvious need to support
non-ASCII character sets even though there was a recognition that
Internationalisation is essential for the Internet’s development as a global
resource. There is ongoing work within ICANN (e.g. joint gNSO and SSAC working
group on Internationalised Registration Data – IRD WG) in this area. As
the need is imminent, this work needs to proceed with priority in coordination
with other relevant work outside the ICANN’s ambit (e.g. WIERDS initiative at
IETF), to make internationalised domain name registration data accessible.<br>
<br>
The NORC Study on Data Accuracy highlighted IDN contact data as a major cause
of apparent inaccuracy. Having internationalized data will also address
this source of inaccuracy.<br>
<br>
[end]<o:p></o:p></span></p>
</div>
<p><span lang=EN-AU><br>
<b>-------------------------------------------------------------------------------</b><br>
NOTICE: This email message is for the sole use of the intended recipient(s) <br>
and may contain confidential and privileged information. Any unauthorized <br>
review, use, disclosure or distribution is prohibited. If you are not the <br>
intended recipient, please contact the sender by reply email and destroy all <br>
copies of the original message. <br>
<br>
This message has been content scanned by the Axway MailGate. <br>
MailGate uses policy enforcement to scan for known viruses, spam, undesirable
content and malicious code. For more information on Axway products please visit
<a href="http://www.axway.com" target="_blank">www.axway.com</a>.<br>
<br>
<b>-------------------------------------------------------------------------------</b><o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
_______________________________________________<br>
Rt4-whois mailing list<br>
<a href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/rt4-whois" target="_blank">https://mm.icann.org/mailman/listinfo/rt4-whois</a><o:p></o:p></p>
</blockquote>
</div>
<p class=MsoNormal><br>
<br clear=all>
<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'>-- <br>
<br>
<br>
<img border=0 id="_x0000_i1025"
src="http://www.etlaw.co.uk/images/stories/etlaw/etclogo250x60.gif"><o:p></o:p></p>
<div style='margin-left:60.0pt'>
<p class=MsoNormal><u><span style='color:#CC33CC'>
</span></u><span style='color:#993399'><br>
</span><br>
<span style='color:#999999'>76 Temple Road, Oxford OX4 2EZ UK<br>
t: +44 (0)1865 582 811 • m: +44 (0)7540 049 322<br>
<a href="mailto:emily@emilytaylor.eu" target="_blank">emily@emilytaylor.eu</a> <br>
<br>
<b><a href="http://www.etlaw.co.uk" target="_blank">www.etlaw.co.uk</a></b><br>
<br>
Emily Taylor Consultancy Limited is a company registered in England and Wales
No. 7630471. VAT No. 114487713.</span><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>