<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
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>
<blockquote
cite="mid:CAKWYFsf9=twKW5hAts_FP-oDXncTzWCh8o8KVt9Nz14Lv0cA+Q@mail.gmail.com"
type="cite">Thank you Peter
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>So, I've added some language for this, based on the first
paragraph of the IDN chapter (highlighted below).</div>
<div><br>
</div>
<div>Kind regards</div>
<div><br>
Emily<br>
<br>
<div class="gmail_quote">
On 4 May 2012 08:08, Nettlefold, Peter <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:Peter.Nettlefold@dbcde.gov.au"
target="_blank">Peter.Nettlefold@dbcde.gov.au</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-AU">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hello
again all,</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
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></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
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></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Cheers,</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Peter</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><u><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">Findings</span></u></p>
<p class="MsoNormal"><span style="font-size:large"> </span></p>
</div>
</blockquote>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-AU">
<div>
<p class="MsoNormal"><span
style="font-family:Calibri,sans-serif;color:windowtext"><font
size="4">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.<br>
<br>
</font></span></p>
</div>
</div>
</blockquote>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-AU">
<div>
<p class="MsoNormal">
<span
style="font-family:Calibri,sans-serif;color:windowtext"><font
size="4">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. </font></span></p>
<p class="MsoNormal"><span
style="font-family:Calibri,sans-serif;color:windowtext"></span></p>
</div>
</div>
</blockquote>
<div><span
style="background-color:rgb(255,255,51);font-family:Calibri;font-size:large"><br>
</span></div>
<div><span
style="background-color:rgb(255,255,51);font-family:Calibri;font-size:large">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> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-AU">
<div>
<p class="MsoNormal"><span
style="font-family:Calibri,sans-serif;color:windowtext"><font
size="4"> </font></span></p>
<p class="MsoNormal"><span
style="font-family:Calibri,sans-serif;color:windowtext"><font
size="4">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>
</font><br>
<br>
</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<div>
<div style="border:none;border-top:solid #b5c4df
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"
lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"
lang="EN-US"> <a moz-do-not-send="true"
href="mailto:rt4-whois-bounces@icann.org"
target="_blank">rt4-whois-bounces@icann.org</a>
[mailto:<a moz-do-not-send="true"
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 moz-do-not-send="true"
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></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal" style="margin-bottom:12.0pt">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]</p>
</div>
<p><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
moz-do-not-send="true" href="http://www.axway.com"
target="_blank">www.axway.com</a>.<br>
<br>
<b>-------------------------------------------------------------------------------</b><br>
</p>
</div>
<br>
_______________________________________________<br>
Rt4-whois mailing list<br>
<a moz-do-not-send="true" href="mailto:Rt4-whois@icann.org">Rt4-whois@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/rt4-whois"
target="_blank">https://mm.icann.org/mailman/listinfo/rt4-whois</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<br>
<br>
<span style="color:rgb(153,51,153)"></span> <img
moz-do-not-send="true"
src="http://www.etlaw.co.uk/images/stories/etlaw/etclogo250x60.gif"><br>
<br>
<div style="margin-left:80px">
<u style="color:rgb(204,51,204)">
</u><br style="color:rgb(153,51,153)">
<br>
<span style="color:rgb(153,153,153)">76 Temple Road, Oxford
OX4 2EZ UK</span><br style="color:rgb(153,153,153)">
<span style="color:rgb(153,153,153)">t: +44 (0)1865 582 811 •
m: +44 (0)7540 049 322</span><br
style="color:rgb(153,153,153)">
<span style="color:rgb(153,153,153)"><a moz-do-not-send="true"
href="mailto:emily@emilytaylor.eu" target="_blank">emily@emilytaylor.eu</a>
</span><br style="color:rgb(153,153,153)">
<br style="color:rgb(153,153,153)">
<b style="color:rgb(153,153,153)"><a moz-do-not-send="true"
href="http://www.etlaw.co.uk" target="_blank">www.etlaw.co.uk</a></b><br
style="color:rgb(153,153,153)">
<br style="color:rgb(153,153,153)">
<span style="color:rgb(153,153,153)">Emily Taylor Consultancy
Limited is a company registered in England and Wales No.
7630471. VAT No. 114487713.</span><br>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>