<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><font style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
Classification: UNCLASSIFIED<br><br>Hello again all,<br><br>In terms of the options, I do not understand how a comprehensive service could have any privacy implications or impact registries, as it would simply ease access to information that is already required to be publicly available.<br><br>However, if we are unable to reach a consensus on this, I suggest that we adopt a similar approach to that which we took for proxies: i.e. highlight what we have agreed on (the need to assist users, and a portal to do this), and put forward alternatives for community comment on those issues we don't yet have consensus on (thin registries only, or all).<br><br>Below is a strawman for comment. I have drawn from the elements of both proposals for the langauge, and also the idea of a 'smart web portal' which seemed to receive positive comment yesterday. It's been drafted on my blackberry in the airport, so I'm not precious about the wording, but wanted to put some text out there to assist the discussion.<br><br>"To make WHOIS data more accessible for consumers, the review team recommends that ICANN should set up a dedicated, multilingual interface website to help users access thick gTLD WHOIS data. <br><br>This would be a smart web portal, that would assist users to access publicly available WHOIS data. It is not envisaged that this would replicate registry databases in any way, but instead help users by providing a single centralised site through which to search those databases, and to display the WHOIS data in an accessible way.<br><br>The review team has discussed the scope of this portal, and seeks community views on whether it should only apply to thin gTLD registries, or should instead provide a comprehensive gTLD search service."<br><br>I hope this helps.<br><br>Cheers,<br><br>Peter<br><br></font><br> <br>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<font style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<b>From</b>: Alice Jansen [mailto:alice.jansen@icann.org]
<br><b>Sent</b>: Friday, December 02, 2011 11:07 AM<br><b>To</b>: Kathy Kleiman <kathy@kathykleiman.com>; rt4-whois@icann.org <rt4-whois@icann.org>
<br><b>Subject</b>: Re: [Rt4-whois] No agreement on Lutz's recommendations
<br></font> <br></div>
<div><div><div>Hi Team,</div><div><br></div><div>With reference to Kathy's email - no agreement on Lutz' recommendations - , please note that I have added the two alternatives to the current draft for good measure.</div><div>I would be very grateful if you could clarify which language you would like to adopt. My priority is to make sure that the document captures your intent.</div><div><br></div><div>Many thanks in advance for your guidance.</div><div><br></div><div>Kind regards</div><div><br></div><div>Alice</div><div><br></div><div><div><div><div><div><div><b>Alice Jansen</b></div></div><div>Assistant, Organizational Reviews</div><div><i>6 Rond Point Schuman, Bt.5</i></div><div><i>B-1040 Brussels</i></div><div><i>Belgium</i></div><div>Direct dial: +32 2 234 78 64</div><div>Mobile: +32 4 73 31 76 56</div><div>Skype: alice_jansen<span style="font-style: italic; ">_</span>icann</div></div></div></div><div><br></div><div><br></div></div></div></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Kathy Kleiman <<a href="mailto:kathy@kathykleiman.com">kathy@kathykleiman.com</a>><br><span style="font-weight:bold">Date: </span> Thu, 1 Dec 2011 14:51:27 -0800<br><span style="font-weight:bold">To: </span> "<a href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a>" <<a href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a>><br><span style="font-weight:bold">Subject: </span> [Rt4-whois] No agreement on Lutz's recommendations<br></div><div><br></div><div>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<div bgcolor="#FFFFFF" text="#000000">
Hi Emily,<br>
As of this morning, there was considerable support for a rewording:<br> To improve access to <span style="background:yellow;mso-highlight:yellow"> the Whois data of
.COM and .NET gTLDs, the only remaining Thin Registries</span>,
ICANN should set up a dedicated, multilingual interface website to
provide thick WHOIS data for them.<o:p></o:p> <br>
<br>
And <u>no consensus </u>I could see on the other wording, namely:<br>
<br>
14. To make WHOIS data more accessible for consumers, ICANN should
set up a dedicated, multilingual interface website to allow
"unrestricted and public access to accurate and complete WHOIS
information" by querying the appropriate servers, not copying the
database.<br>
<br>
and a different variation floating around:<br>
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<br>
To make WHOIS data more accessible for consumers, ICANN should set
up a dedicated, multilingual interface website to allow
"unrestricted and public access to accurate and complete
WHOIS information". Such interface should provide thick WHOIS data
for all gTLD domain names.
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.3 (Win32)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
-->
</style><br>
<br>
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<font face="Calibri,serif"><br>
Note: this is not one that arrived at consensus earlier, so this
is minority report territory.<br>
Tx,<br>
Kathy<br>
<br>
</font><br>
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.3 (Win32)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
-->
</style><br>
<pre class="moz-signature" cols="72">--
</pre>
</div></div></span>
<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 www.axway.com.<br/>
<br/><B>-------------------------------------------------------------------------------</B><br/>
</P></body></html>