Page History
 Objective
|
|---|
Background Documents
- WHOIS1 Implementation Briefings on Recommendations 5, 8, 10, 11: PDF
- Answers to RDS-WHOIS2 Questions on Implementation Briefings
- WHOIS Review Team (WHOIS1) Final Report (2012) and Action Plan
- WHOIS Review Team (WHOIS1) Implementation Reports, including
- Documents cited in briefing on Recommendation 11 include
- Additional links specific to Recommendation 11 may be added here
Further background documents may be found on the Review Team's overall Background Materials page.
|
|---|
Subgroup Documents
ICANN Org Briefings/Answers
Open Actions/Requests
*To be provided once reasonable date is determined by appropriate subject-matter expert
| Item # | Source of Request | Date of Request | Action Item Request | Action Owner | Anticipated Completion Date* | Progress Notes |
|---|---|---|---|---|---|---|
| 9 | #37 |
|
| Volker |
|
Completed Actions/Requests
*To be provided once reasonable date is determined by appropriate subject-matter expert
| Item # | Source of Request | Date of Request | Action Item Request | Action Owner | Anticipated Completion Date* | Progress Notes | Completed Response | Completion Date |
|---|---|---|---|---|---|---|---|---|
| 9 | FtoF #3 | Finalize text for new recommendation R11.2 to make clear what publicly-available output is expected - for example, whether it is just port 43 output or web output in cases where port 43 is redacted. Note under feasibility that this recommendation will need to be assessed for compliance with applicable laws. | Volker |
| DOCX |
| ||
| 8 | FtoF #3 | Volker to expand findings to define what “displayed inconsistently” means. | Volker | |||||
| 7 | #34 | Address any concerns raised in a final draft to be sent to the full RT by the end of this week (22 July 2018). | Volker | |||||
| 6 | #34 | Propose edits to address increase in common interface timeouts since GDPR. | Susan | |||||
| 5 | #34 | Review the subgroup report, and submit comments via email or confirm they agree with the subgroup draft report as is. | Subgroup | |||||
| 4 | #31 |
| Provide Volker with a date/timestamp of the F2F2 discussion for this topic. Volker to review that discussion. | ICANN org |
| |||
| 3 | #25 |
| Share subgroup draft report with subgroup/review team asap. | Volker |
| |||
| 1 | #1 |
| Written briefing on query failures on WHOIS microsite - how frequent, cause, any efforts to alleviate. The subgroup would like to gather statistics (current) on use of the common interface, uptime, requests for help using the tool and what usage data is tracked by ICANN. In addition, it is seeking information on challenges encountered. | ICANN org |
| |||
| 2 | #1 |
| Draft answers to planning questions to share with Volker, who will then review/share with subgroup. | ICANN org |
|
Decisions Reached
| Source of request | Date | Decision |
|---|---|---|
| FtoF #3 |
| R11.2 ICANN should maintain the common interface to display all publicly-available WHOIS output for each gTLD domain name (i.e., both the registry and registrar WHOIS output.) |
| FtoF #3 |
| To address the issue raised: As a result of GDPR implementation, RR and Ry interpretations may result in different registration data returned by WHOIS for the same domain name (e.g., the Ry may redact data that the RR displays) |
| FtoF #3 |
| R11.1 Define metrics or SLAs to be tracked and evaluated to determine consistency of results of queries and use of any common interface (existing or future) used to provide one-stop access to registration data across all gTLDs and registrars/resellers. Specific metrics that should be tracked for any such common interface include: •How often are fields returned blank? •How often is data displayed (for the same domain name) inconsistently, overall and per gTLD? •How often does the tool not return results, overall and for specific gTLDs? |
| #1 |
| Subgroup to review briefing response to questions raised in work plan and then determine next steps. |
