AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Review Implementation Plan Development
Page History
Comment Period | Important Information Links | |
Open Date: | 21 November 2011 | |
Close Date: | 30 December 2011 | |
Time (UTC): | 23:59 | |
Originating Organization: | ICANN Policy Department | |
Purpose: | ICANN Staff is seeking comments on the Preliminary Issue Report on 'Thick' Whois | |
Current Status: | The Preliminary Issue Report explores the issue of 'thick' Whois and makes recommendations on whether the GNSO Council should initiate a policy development process on the requirement of 'thick' Whois for all incumbent gTLDs. This Public Comment solicitation represents an opportunity to share perspectives on 'thick' Whois, the Preliminary Issue Report contents, and whether the GNSO Council should initiate a Policy Development Process on this issue. | |
Next Steps: | The Preliminary Issue Report will be updated to reflect community feedback submitted through this forum. A Final Issue Report will then be presented to the GNSO Council for its consideration as to whether a Policy Development Process should be initiated. | |
Staff Contact: | Marika Konings | |
Email: |
Click here to download the ALAC Statement on the Thick Whois Preliminary Report in PDF format.
ALAC Statement on the Thick Whois Preliminary Report
...
We believe that the Preliminary Issue Report reasonably reflect the issues and specifications for a PDP, with one exception. Specifically the following is problematic:
...
*Are there other models that could / should be considered?* For example, in the context of registrar deliberations on this issue, it was suggested that ‘depositing the \ [W\]hois at a common third party across all ICANN-contracted TLDs’ could be considered.
We find this problematic for three reasons:
- Looking at the specific example, having a common third party for all gTLDs is, to some extent, counter to the intent of having registries spread around the world. It centralizes where the long-term intent is to decentralize. Even if a less centralized approach is taken where there are multiple Whois providers, presumably certified or acredited accredited by ICANN, we end up with ICANN taking on a new responsibility without any real substantive benefits. Moreover, it takes a level of control out of the hands of the Registry. This level of control has been important when one looks at the tiered access that some Registries provide to meet local/regional privacy concerns.
- In the more general case, opening up this PDP to an overall review of Whois models (and perhaps ultimately the Whois concept itself) will take what appears to be a relatively straight-forward issue and transform it into the global Whois debate, That debate is being addressed in a number of other ways at the moment, and the GNSO should take care to ensure that this limited PDP does not morph into the larger and far more contentious issue.
- Lastly, consideration of alternate Whois models does not make sense in relation to just a few gTLDs, all the more so when there are other activities in ICANN that are at this time considering the more general Whois question, potentially including alternative models.
...
In summary, with the one exception noted above, the ALAC supports the Preliminary Issue Report, and supports the initiation of a PDP on the narrow issue of requiring that all Registries move to or continue to use the thick Whois model. Moreover we encourage the completion of all such deliberations within a time-frame comparable to the expected go-live launch of the new gTLDs.
...
(Draft version and comments
...
follow)
...
Draft ALAC Statement on the Thick Whois Preliminary Report
...
We believe that the Preliminary Issue Report reasonably reflect the issues and specifications for a PDP, with one exception. Specifically the following is problematic:
Are there other models that could / should be considered?
For example, in the context of registrar deliberations on this issue, it was suggested that ‘depositing the \ [W\]hois at a common third party across all ICANN-contracted TLDs’ could be considered. Wiki Markup
We find this problematic for two reasons:
...