Centralized Whois Query system run by ICANN
Proposal: Summary: ICANN should set up and maintain a web interface to access all the WHOIS services in order to ease access to the WHOIS data. Presumption: The AoC requires that "ICANN implement measures to maintain timely, unrestricted and public access to accurate and complete WHOIS information, including registrant, technical, billing, and administrative contact information." Observation: An User Insight Report came up with the following results: + Almost nobody is aware of whois + Almost nobody is able to query a whois server correctly + Whois queries were done on websites which occur first in the search engine results. Usually those pages are overloaded with advertisments. Detailed recommendation: ICANN should set up a dedicated, multilingual website to allow "unrestricted and public access to accurate and complete WHOIS information" even for those people which have problems with the plain WHOIS protocol. The WHOIS information should be collected by following the thin WHOIS approach starting at whois.iana.org. The service should display the contractural relationships which are revealed by the WHOIS referals in a clear and understandable way. The results should be mark clearly the relevant information "including registrant, technical, billing, and administrative contact" data. The server needs to be run by ICANN itself, because the "timely, unrestricted and public access" is usually rate limited, stripped or even blocked by the various WHOIS server administrators for uncontractual third party access. ICANN itself is the only party having the power to overcome those limits using its contratual compliance.
Hi Susan, Kathy - I've been following your exchanges on Thick/Thin with interest. Susan mentioned Lutz's proposal on a central repository/portal run by ICANN. Here is his text for ease of reference. How about the two of you consider this outline and see whether this could meet your concerns/requirements (or if not, how could it be adapted to do so?) Kind regards Emily ---------- Forwarded message ---------- From: Lutz Donnerhacke <lutz@iks-jena.de> Date: 9 November 2011 11:22 Subject: [Rt4-whois] Centralized Whois Query system run by ICANN To: rt4-whois@icann.org Proposal: Summary: ICANN should set up and maintain a web interface to access all the WHOIS services in order to ease access to the WHOIS data. Presumption: The AoC requires that "ICANN implement measures to maintain timely, unrestricted and public access to accurate and complete WHOIS information, including registrant, technical, billing, and administrative contact information." Observation: An User Insight Report came up with the following results: + Almost nobody is aware of whois + Almost nobody is able to query a whois server correctly + Whois queries were done on websites which occur first in the search engine results. Usually those pages are overloaded with advertisments. Detailed recommendation: ICANN should set up a dedicated, multilingual website to allow "unrestricted and public access to accurate and complete WHOIS information" even for those people which have problems with the plain WHOIS protocol. The WHOIS information should be collected by following the thin WHOIS approach starting at whois.iana.org. The service should display the contractural relationships which are revealed by the WHOIS referals in a clear and understandable way. The results should be mark clearly the relevant information "including registrant, technical, billing, and administrative contact" data. The server needs to be run by ICANN itself, because the "timely, unrestricted and public access" is usually rate limited, stripped or even blocked by the various WHOIS server administrators for uncontractual third party access. ICANN itself is the only party having the power to overcome those limits using its contratual compliance. _______________________________________________ Rt4-whois mailing list Rt4-whois@icann.org https://mm.icann.org/mailman/listinfo/rt4-whois -- * * 76 Temple Road, Oxford OX4 2EZ UK t: +44 (0)1865 582 811 • m: +44 (0)7540 049 322 emily@emilytaylor.eu *www.etlaw.co.uk* Emily Taylor Consultancy Limited is a company registered in England and Wales No. 730471. VAT No. 114487713.
Hello again all, Thanks very much Lutz for following this recommendation through. I haven't seen any responses to this yet (but perhaps I missed them), and I also wonder if it was discussed at the teleconference this morning? While I'd be interested to hear others' views on the precise wording and the data collection mechanism, I wanted to say that in principle I think this is a very useful addition to our recommendations. Once implemented, I expect that it would go some way to addressing concerns about the public accessibility of WHOIS data, and as such I support it. Cheers, Peter -----Original Message----- From: rt4-whois-bounces@icann.org [mailto:rt4-whois-bounces@icann.org] On Behalf Of Lutz Donnerhacke Sent: Wednesday, 9 November 2011 10:22 PM To: rt4-whois@icann.org Subject: [Rt4-whois] Centralized Whois Query system run by ICANN Proposal: Summary: ICANN should set up and maintain a web interface to access all the WHOIS services in order to ease access to the WHOIS data. Presumption: The AoC requires that "ICANN implement measures to maintain timely, unrestricted and public access to accurate and complete WHOIS information, including registrant, technical, billing, and administrative contact information." Observation: An User Insight Report came up with the following results: + Almost nobody is aware of whois + Almost nobody is able to query a whois server correctly + Whois queries were done on websites which occur first in the search engine results. Usually those pages are overloaded with advertisments. Detailed recommendation: ICANN should set up a dedicated, multilingual website to allow "unrestricted and public access to accurate and complete WHOIS information" even for those people which have problems with the plain WHOIS protocol. The WHOIS information should be collected by following the thin WHOIS approach starting at whois.iana.org. The service should display the contractural relationships which are revealed by the WHOIS referals in a clear and understandable way. The results should be mark clearly the relevant information "including registrant, technical, billing, and administrative contact" data. The server needs to be run by ICANN itself, because the "timely, unrestricted and public access" is usually rate limited, stripped or even blocked by the various WHOIS server administrators for uncontractual third party access. ICANN itself is the only party having the power to overcome those limits using its contratual compliance. _______________________________________________ Rt4-whois mailing list Rt4-whois@icann.org https://mm.icann.org/mailman/listinfo/rt4-whois ------------------------------------------------------------------------------- NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This message has been content scanned by the Axway MailGate. 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. -------------------------------------------------------------------------------
Hi Peter Yes, it was discussed on our latest call, and Lutz's proposal found widespread support. The feeling seems to be that this nicely sidesteps some of the difficult industry issues related to mandating a thick whois service for .com. Lutz kindly agreed to update the language here as a result of our discussions. We're talking more in terms of a single, authoritative, * interface* rather than a "repository" (or anything like that which would imply some sort of deposit/escrow system, and also involve the database being held centrally. I believe that what Lutz has in mind is a look up system which addresses the consumer trust point, and the fact that our research shows how difficult consumers find it to understand the many layers of a thin whois query - that's the 20% or so who've actually heard of whois! Kind regards Emily On 24 November 2011 05:15, Nettlefold, Peter <Peter.Nettlefold@dbcde.gov.au>wrote:
Hello again all,
Thanks very much Lutz for following this recommendation through.
I haven't seen any responses to this yet (but perhaps I missed them), and I also wonder if it was discussed at the teleconference this morning?
While I'd be interested to hear others' views on the precise wording and the data collection mechanism, I wanted to say that in principle I think this is a very useful addition to our recommendations. Once implemented, I expect that it would go some way to addressing concerns about the public accessibility of WHOIS data, and as such I support it.
Cheers,
Peter
-----Original Message----- From: rt4-whois-bounces@icann.org [mailto:rt4-whois-bounces@icann.org] On Behalf Of Lutz Donnerhacke Sent: Wednesday, 9 November 2011 10:22 PM To: rt4-whois@icann.org Subject: [Rt4-whois] Centralized Whois Query system run by ICANN
Proposal:
Summary: ICANN should set up and maintain a web interface to access all the WHOIS services in order to ease access to the WHOIS data.
Presumption: The AoC requires that "ICANN implement measures to maintain timely, unrestricted and public access to accurate and complete WHOIS information, including registrant, technical, billing, and administrative contact information."
Observation: An User Insight Report came up with the following results: + Almost nobody is aware of whois + Almost nobody is able to query a whois server correctly + Whois queries were done on websites which occur first in the search engine results. Usually those pages are overloaded with advertisments.
Detailed recommendation: ICANN should set up a dedicated, multilingual website to allow "unrestricted and public access to accurate and complete WHOIS information" even for those people which have problems with the plain WHOIS protocol.
The WHOIS information should be collected by following the thin WHOIS approach starting at whois.iana.org. The service should display the contractural relationships which are revealed by the WHOIS referals in a clear and understandable way. The results should be mark clearly the relevant information "including registrant, technical, billing, and administrative contact" data.
The server needs to be run by ICANN itself, because the "timely, unrestricted and public access" is usually rate limited, stripped or even blocked by the various WHOIS server administrators for uncontractual third party access. ICANN itself is the only party having the power to overcome those limits using its contratual compliance. _______________________________________________ Rt4-whois mailing list Rt4-whois@icann.org https://mm.icann.org/mailman/listinfo/rt4-whois
-------------------------------------------------------------------------------
NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
This message has been content scanned by the Axway MailGate. 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.
-------------------------------------------------------------------------------
_______________________________________________ Rt4-whois mailing list Rt4-whois@icann.org https://mm.icann.org/mailman/listinfo/rt4-whois
-- * * 76 Temple Road, Oxford OX4 2EZ UK t: +44 (0)1865 582 811 • m: +44 (0)7540 049 322 emily@emilytaylor.eu *www.etlaw.co.uk* Emily Taylor Consultancy Limited is a company registered in England and Wales No. 730471. VAT No. 114487713.
All, Is this the current version of the Lutz proposal now in circulation? I thought it applied only to a centralized database of the current "thin registries," namely .COM and .NET. If so, I can see the advantages and support sending it out as a recommendation in the draft report. But if this is a single database of all registries, thick and thin, now and in the future, I think we creating a database problem. It's an enormous amount of data and creates a focal point for abuse, for warehousing, etc. It's the type of policing job that ICANN has never had to do, and is not operationally set up to do. So thought summary: If ICANN is helping remedy a bad situation by operating a single registry for .COM and .NET to fix a historical problem, I think I am OK for now (pending review of the draft with registries -- after publication is fine). One database of all Whois information to Rule the World, not so good. RECOMMENDATION EDIT: Detailed recommendation: ICANN should set up a dedicated, multilingual website to allow "unrestricted and public access to accurate and complete WHOIS information" **FOR .COM AND .NET, THE EXISTING "THIN REGISTRIES"** even for those people which have problems with the plain WHOIS protocol. The WHOIS information should be collected by following the thin WHOIS approach starting at whois.iana.org. The service should display the contractural relationships which are revealed by the WHOIS referals in a clear and understandable way. The results should be mark clearly the relevant information "including registrant, technical, ** DELETE BILLING** billing, and administrative contact" data. ** NOTE: Billing data, which includes credit cards Folks, is simply not displayed in any other Whois search results. It is only registrant, technical, and admin contact.** Best, Kathy
Proposal:
Summary: ICANN should set up and maintain a web interface to access all the WHOIS services in order to ease access to the WHOIS data.
Presumption: The AoC requires that "ICANN implement measures to maintain timely, unrestricted and public access to accurate and complete WHOIS information, including registrant, technical, billing, and administrative contact information."
Observation: An User Insight Report came up with the following results: + Almost nobody is aware of whois + Almost nobody is able to query a whois server correctly + Whois queries were done on websites which occur first in the search engine results. Usually those pages are overloaded with advertisments.
Detailed recommendation: ICANN should set up a dedicated, multilingual website to allow "unrestricted and public access to accurate and complete WHOIS information" even for those people which have problems with the plain WHOIS protocol.
The WHOIS information should be collected by following the thin WHOIS approach starting at whois.iana.org. The service should display the contractural relationships which are revealed by the WHOIS referals in a clear and understandable way. The results should be mark clearly the relevant information "including registrant, technical, billing, and administrative contact" data.
The server needs to be run by ICANN itself, because the "timely, unrestricted and public access" is usually rate limited, stripped or even blocked by the various WHOIS server administrators for uncontractual third party access. ICANN itself is the only party having the power to overcome those limits using its contratual compliance. _______________________________________________ Rt4-whois mailing list Rt4-whois@icann.org https://mm.icann.org/mailman/listinfo/rt4-whois
--
participants (4)
-
Emily Taylor -
Kathy Kleiman -
Lutz Donnerhacke -
Nettlefold, Peter