Thick Whois Topics Poll This is a quick survey to collect two kinds of information – your interest in participating in sub-groups focused on each of our topics, and your suggestions as to sources of information or experts about those topics. You are welcome to offer information-source and expert suggestions for all topics, not just the ones that you are volunteering to focus on. Question Title * 1. Your name Authoritativeness: what are the implications of a 'thin' Registry possibly becoming authoritative for registrant Whois data following the transition from a thin-registry model to a thick-registry model. The Working Group should consider the term "authoritative" in both the technical (the repository of the authoritative data) and policy (who has authority over the data) meanings of the word when considering this issue. Question Title * 2. I would like to participate in the sub-team for this topic Yes No Question Title * 3. Here are my suggested information-sources (or experts who would be good advisors) about this topic: Stability: 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), which would be the case in a 'thick' registry. Question Title * 4. I would like to participate in the sub-team for this topic Yes No Question Title * 5. Here are my suggested information-sources (or experts who would be good advisors) about this topic: Data escrow: 'thick' Whois might obviate the need for the registrar escrow program and attendant expenses to ICANN and registrars. Question Title * 6. I would like to participate in the sub-team for this topic: Yes No Question Title * 7. Here are my suggested information-sources (or experts who would be good advisors) about this topic: Synchronization/migration: what would be the impact on the registry and registrar WHOIS and EPP systems for those Registries currently operating a thin registry, both in the migration phase to 'thick' WHOIS as well as ongoing operations? Question Title * 8. I would like to participate in the sub-team for this topic Yes No Question Title * 9. Here are my suggested information-sources (or experts who would be good advisors) about this topic: Response consistency: a 'thick' Registry can dictate the labeling and display of Whois information to be sure the information is easy to parse, and all Registrars/clients would have to display it accordingly. This could be considered a benefit but also a potential cost. This might also be a benefit in the context of internationalized registration data as even with the use of different scripts, uniform data collection and display standards could be applied. Question Title * 10. I would like to participate in the sub-team for this topic Yes No Question Title * 11. Here are my suggested information-sources (or experts who would be good advisors) about this topic: Accessibility: is the provision of Whois information at the registry level under the 'thick' Whois model more effective and cost-effective than a 'thin' model in protecting consumers and users of Whois data and intellectual property owners? Question Title * 12. I would like to participate in the sub-team for this topic Yes No Question Title * 13. Here are my suggested information-sources (or experts who would be good advisors) about this topic: Impact on privacy and data protection: how would 'thick' Whois affect privacy and data protection, also taking into account the involvement of different jurisdictions with different laws and legislation with regard to data privacy as well as possible cross border transfers of registrant data? Question Title * 14. I would like to participate in the sub-team for this topic Yes No Question Title * 15. Here are my suggested information-sources (or experts who would be good advisors) about this topic: Competition in registry services: what would be the impact on competition in registry services should all Registries be required to provide Whois service using the 'thick' Whois model – would there be more, less or no difference with regard to competition in registry services? Question Title * 16. I would like to participate in the sub-team for this topic Yes No Question Title * 17. Here are my suggested information-sources (or experts who would be good advisors) about this topic: Existing Whois Applications: What, if anything, are the potential impacts on the providers of third-party WHOIS-related applications if 'thick' WHOIS is required for all gtLDs? Question Title * 18. I would like to participate in the sub-team for this topic Yes No Question Title * 19. Here are my suggested information-sources (or experts who would be good advisors) about this topic: Registrar Port 43 Whois requirements: 'thick' Whois could make the requirement for Registrars to maintain Port 43 Whois access redundant. Question Title * 20. I would like to participate in the sub-team for this topic Yes No Question Title * 21. Here are my suggested information-sources (or experts who would be good advisors) about this topic: Cost implications: what are the cost implications of a transition to 'thick' Whois for Registries, Registrars, registrants and other parties for all gTLDs? Conversely, what are the cost implications to Registries, Registrars, registrants and other parties if no transition is mandated? Question Title * 22. I would like to participate in the sub-team for this topic Yes No Question Title * 23. Here are my suggested information-sources (or experts who would be good advisors) about this topic: Done