...
| Relevant section | Source | Submitted by | Date of submission | |||
|---|---|---|---|---|---|---|
| Proponents of requiring thick Whois argue that being able to access the thick data at both the registry and the registrar level will ensure greater accessibility of the data. The draft report of the Implementation Recommendations Team put together by ICANN's Intellectual Property Constituency stated "the IRT believes that the provision of WHOIS information at the registry level under the Thick WHOIS model is essential to the cost-effective protection of consumers and intellectual property owners." http://icann.org/en/topics/new-gtlds/irt-draft-report-trademark-protection-24apr09-en.pdf. There are at least two scenarios in which the additional option of retrieving the data at the registry would be valuable: 1. Where the registrar Whois service might be experiencing a short- or long-term outage (in violation of the registrar's accreditation agreement), and 2. Where the registrar has implemented strong (or sometimes overly-defensive) measures to prevent large-scale automated harvesting of registrar data. | icann.org/en/topics/new-gtlds/thick-thin-whois-30may09-en.pdf | Marika | 21 Nov 2012 | |||
Also, in the event of a registrar business or technical failure, it could be beneficial to ICANN and registrants to have the full set of domain registration contact data stored by four organizations (the registry, the registry's escrow agent, the registrar, and the registrar's escrow agent) instead of just two organizations (the registrar and the registrar's escrow agent). | icann.org/en/topics/new-gtlds/thick-thin-whois-30may09-en.pdf | Marika | 21 Nov 2012 | |||