<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=utf-8">
<meta name="Generator" content="Microsoft Word 14 (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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></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="RU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">It was also my position
</span><span lang="EN-US" style="font-size:11.0pt;font-family:Wingdings;color:#1F497D">L</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">…<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Rgds,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">M.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;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 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> rt4-whois-bounces@icann.org [mailto:rt4-whois-bounces@icann.org]
<b>On Behalf Of </b>James M. Bladel<br>
<b>Sent:</b> Wednesday, November 30, 2011 7:21 PM<br>
<b>To:</b> Emily Taylor<br>
<b>Cc:</b> rt4-whois@icann.org<br>
<b>Subject:</b> Re: [Rt4-whois] Centralized Whois Query system run by ICANN - Scope and concerns<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">No, I don't think we should attempt to answer these questions in RT4, nor presume that we have even identified all of the dependent questions.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">I believe our recommendation should task the Board, within a reasonable timeframe (90 days?), to request an issues report on a Centralized WHOIS system for all
gTLDs, including how it should be operated and what measures would be adopted to protect against abuse / privacy violations / data harvesting.
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">(This will initiate a PDP which, while slower, will be a more comprehensive approach)<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 6.0pt;margin-left:6.0pt;margin-top:5.0pt;margin-bottom:5.0pt" id="replyBlockquote">
<div id="wmQuoteWrapper">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">-------- Original Message --------<br>
Subject: Re: [Rt4-whois] Centralized Whois Query system run by ICANN -<br>
Scope and concerns<br>
From: Emily Taylor <<a href="mailto:emily@emilytaylor.eu">emily@emilytaylor.eu</a>><br>
Date: Wed, November 30, 2011 10:15 am<br>
To: "James M. Bladel" <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>><br>
Cc: Kathy Kleiman <<a href="mailto:kathy@kathykleiman.com">kathy@kathykleiman.com</a>>,
<a href="mailto:rt4-whois@icann.org">rt4-whois@icann.org</a><br>
<br>
Hi James<br>
<br>
Thanks for raising these points. Can you suggest some language which you think would work? Also, Kathy raised a good point about whether this is limited to thin registries (.com, .net) or all? I don't think we've ever discussed this.
<br>
<br>
Kind regards<br>
<br>
Emily<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">On 30 November 2011 16:06, James M. Bladel <<a href="mailto:jbladel@godaddy.com" target="_blank">jbladel@godaddy.com</a>> wrote:<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">I don't oppose this recommendation, but my issue with this is that we are once again being too vague in what we're asking.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">ICANN: Who? Staff? The Board? The GNSO? Contracted 3rd party?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Set up: How? By launching a PDP? Sending out an RFP?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Deadline?
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Are we confident that this group has considered all of the consequences to privacy, security, access, SLAs, etc.? (Reasons why a PDP can be more helpful for things
like this...)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Thanks--<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><br>
J.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 6.0pt;margin-left:6.0pt;margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">-------- Original Message --------<br>
Subject: Re: [Rt4-whois] Centralized Whois Query system run by ICANN -<br>
Scope and concerns<br>
From: Kathy Kleiman <<a href="mailto:kathy@kathykleiman.com" target="_blank">kathy@kathykleiman.com</a>><br>
Date: Wed, November 30, 2011 9:56 am<br>
To: <a href="mailto:rt4-whois@icann.org" target="_blank">rt4-whois@icann.org</a><o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><br>
<br>
All,<br>
Is this the current version of the Lutz proposal now in circulation? I <br>
thought it applied only to a centralized database of the current "thin <br>
registries," namely .COM and .NET. If so, I can see the advantages and <br>
support sending it out as a recommendation in the draft report.<br>
<br>
But if this is a single database of all registries, thick and thin, now <br>
and in the future, I think we creating a database problem. It's an <br>
enormous amount of data and creates a focal point for abuse, for <br>
warehousing, etc. It's the type of policing job that ICANN has never had <br>
to do, and is not operationally set up to do.<br>
<br>
So thought summary: If ICANN is helping remedy a bad situation by <br>
operating a single registry for .COM and .NET to fix a historical <br>
problem, I think I am OK for now (pending review of the draft with <br>
registries -- after publication is fine). One database of all Whois <br>
information to Rule the World, not so good.<br>
<br>
RECOMMENDATION EDIT:<br>
<br>
Detailed recommendation:<br>
ICANN should set up a dedicated, multilingual website to allow<br>
"unrestricted and public access to accurate and complete WHOIS<br>
information" **FOR .COM AND .NET, THE EXISTING "THIN REGISTRIES"** even for those people which have problems with the plain<br>
WHOIS protocol.<br>
<br>
The WHOIS information should be collected by following the thin WHOIS<br>
approach starting at <a href="http://whois.iana.org" target="_blank">whois.iana.org</a>. The service should display the<br>
contractural relationships which are revealed by the WHOIS referals in<br>
a clear and understandable way. The results should be mark clearly the<br>
relevant information "including registrant, technical, ** DELETE BILLING** billing, and<br>
administrative contact" data.<br>
<br>
** NOTE: Billing data, which includes credit cards Folks, is simply not <br>
displayed in any other Whois search results. It is only registrant, <br>
technical, and admin contact.**<br>
<br>
Best,<br>
Kathy<br>
<br>
<br>
> Proposal:<br>
><br>
> Summary:<br>
> ICANN should set up and maintain a web interface to access<br>
> all the WHOIS services in order to ease access to the WHOIS data.<br>
><br>
> Presumption:<br>
> The AoC requires that "ICANN implement measures to maintain timely,<br>
> unrestricted and public access to accurate and complete WHOIS information,<br>
> including registrant, technical, billing, and administrative contact<br>
> information."<br>
><br>
> Observation:<br>
> An User Insight Report came up with the following results:<br>
> + Almost nobody is aware of whois<br>
> + Almost nobody is able to query a whois server correctly<br>
> + Whois queries were done on websites which occur first in the search<br>
> engine results. Usually those pages are overloaded with advertisments.<br>
><br>
> Detailed recommendation:<br>
> ICANN should set up a dedicated, multilingual website to allow<br>
> "unrestricted and public access to accurate and complete WHOIS<br>
> information" even for those people which have problems with the plain<br>
> WHOIS protocol.<br>
><br>
> The WHOIS information should be collected by following the thin WHOIS<br>
> approach starting at <a href="http://whois.iana.org" target="_blank">whois.iana.org</a>. The service should display the<br>
> contractural relationships which are revealed by the WHOIS referals in<br>
> a clear and understandable way. The results should be mark clearly the<br>
> relevant information "including registrant, technical, billing, and<br>
> administrative contact" data.<br>
><br>
> The server needs to be run by ICANN itself, because the "timely,<br>
> unrestricted and public access" is usually rate limited, stripped or even<br>
> blocked by the various WHOIS server administrators for uncontractual<br>
> third party access. ICANN itself is the only party having the power to<br>
> overcome those limits using its contratual compliance.<br>
> _______________________________________________<br>
> Rt4-whois mailing list<br>
> <a href="mailto:Rt4-whois@icann.org" target="_blank">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><br>
<br>
<br>
-- <br>
<br>
<br>
<br>
_______________________________________________<br>
Rt4-whois mailing list<br>
<a href="mailto:Rt4-whois@icann.org" target="_blank">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></span></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><br>
_______________________________________________<br>
Rt4-whois mailing list<br>
<a href="mailto:Rt4-whois@icann.org" target="_blank">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></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><br>
<br clear="all">
<br>
-- <br>
<br>
<br>
<span style="border:solid windowtext 1.0pt;padding:0cm"><img border="0" width="100" height="100" id="Picture_x0020_1" src="cid:~WRD000.jpg" alt="Description: Image removed by sender."></span><o:p></o:p></span></p>
<div style="margin-left:60.0pt">
<p class="MsoNormal"><u><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#CC33CC">
</span></u><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#993399"><br>
</span><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><br>
</span><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";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. 730471. VAT No. 114487713.</span><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</blockquote>
</div>
</body>
</html>