[Rt4-whois] Updated Recommendation 14 - Centralized Database

[Omar Kaminski]

Dear Lutz,

I agree with you from the users' pow, but how to make the access
"unrestricted and public" with proxy servers that have a restrictive
access by its own purposes, even for privacy reasons?

Omar



2011/11/30 Lutz Donnerhacke <lutz at iks-jena.de>:
> On Wed, Nov 30, 2011 at 04:15:21PM -0500, Kathy Kleiman wrote:
>> Tx for the many comments about the "centralized database" recommendation
>> (now #14).  I have worked with Michael and Omar on it, and would like to
>> propose the following, narrower, recommendation:
>>
>> ===>  Rec 14:  To improve access to the WHOIS data of .COM and .NET
>> gTLDs, the only remaining Thin Registries, ICANN should set up a
>> dedicated, multilingual interface website to provide thick Whois data
>> for them.
>>
>> Here's the original text.
>>
>> ===>  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".  Such interface should provide thick WHOIS data for all gTLD domain names.
>
> I oppose both texts. I really want to see an dependable tool run by the only
> instance which has the power to guarantee the AoC requirments when accessing
> other parties WHOIS services.
>
> So the text should be:
>  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.
> _______________________________________________
> Rt4-whois mailing list
> Rt4-whois at icann.org
> https://mm.icann.org/mailman/listinfo/rt4-whois