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<br><br><div class="gmail_quote">On 30 November 2011 16:06, James M. Bladel <span dir="ltr"><<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><span style="font-family:Arial;color:#000000;font-size:10pt"><div>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.</div><div><br></div>
<div>ICANN: Who? Staff? The Board? The GNSO? Contracted 3rd party?</div><div><br></div><div>Set up: How? By launching a PDP? Sending out an RFP?</div><div><br></div><div>Deadline? </div><div><br></div><div>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...)</div>
<div><br></div><div>Thanks--</div><div><br>J.</div><div><br></div>
<blockquote style="border-left:2px solid blue;margin-left:8px;padding-left:8px;font-size:10pt;color:black;font-family:verdana">
<div>
-------- 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><div><div class="h5"><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><br>
</div></div></div>
</blockquote></span></div>
<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><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><br><br><span style="color:rgb(153, 51, 153)"></span> <img 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 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 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. 730471. VAT No. 114487713.</span><br>
</div><br>