Briefing Materials
- Alice Jansen
- Aleksey Khapchenko
- Jean-Baptiste Deroulez
This wiki page encapsulates the review team's requests for information and briefings and answers associated with them.
Plenary Requests
Written Implementation Briefing Request | Status | Link (also available on background materials page) |
|---|---|---|
| WHOIS1 - Rec 1 |  Submitted to review team on 14 April | here |
| WHOIS1 - Rec 2 | Submitted to review team on 20 March | here |
| WHOIS1 - Rec 3 | Submitted to review team on 29 March | here |
| WHOIS1 - Rec 4 | Submitted to review team on 12 March | here |
| WHOIS1 - Recs 5-9 | Submitted to review team on 28 March | here |
| WHOIS1 - Rec 10 | Submitted to review team on 27 March | here |
| WHOIS1 - Rec 11 | Submitted to review team on 23 March | here |
| WHOIS1 - Recs 12-14 | Submitted to review team on 7 March | here |
| WHOIS1 - Recs 15-16 | Submitted to review team on 16 March | here |
WHOIS1 Implementation Assessment Subgroups
| Subgroup | Request | Status | Link (also available on subgroups' pages) |
|---|---|---|---|
Written materials: * Information on incentivization measures for ICANN Org staff including CEO ([standard] contract clauses, internal guidance, memos, meeting minutes etc.) | Submitted to subgroup on 14 April | ||
| Questions: https://mm.icann.org/pipermail/rds-whois2-stratpriority/2018-March/000024.html | Submitted to subgroup on 14 April | ||
| Brussels face-to-face meeting #3 - requests for clarification pertaining to the BWG-RDS | Submitted to subgroup on 08 August | ||
| WHOIS1 Rec #3: Outreach | Question: What has ICANN done, on a one-time basis or ongoing, to address the requirement to reach out to communities outside of ICANN with an interest in WHOIS issues. | Submitted to subgroup on 10 April | |
| Meeting with ICANN org compliance | Held on 1 February |
| |
| Meeting with ICANN org compliance | Held on 28 March | ||
| Brussels meeting follow-up questions to ICANN Compliance: https://mm.icann.org/pipermail/rds-whois2-rec4-compliance/2018-April/000050.html | Submitted to subgroup on 1 May | ||
| Additional questions to ICANN org: https://mm.icann.org/pipermail/rds-whois2-rec4-compliance/2018-June/000065.html | Submitted to subgroup on 21 June | ||
| Additional questions to ICANN org: https://mm.icann.org/pipermail/rds-whois2-rt/2018-July/000762.html | Submitted to subgroup on 26 July | ||
Question: What are the process and criteria used to determine the domain names to review with ARS? | Submitted to subgroup on 27 July | ||
| Question: For domains rechecked after suspension, what % are found to be unsuspended in total and the % that are still non-compliant? | Submitted to subgroup on 31 July 2018 | ||
| WHOIS1 Rec #5-9: Data Accuracy | Questions: https://mm.icann.org/pipermail/rds-whois2-dataaccuracy/2018-March/000032.html | Submitted to subgroup on 30 March |
|
| Brussels meeting follow-up questions to ICANN Compliance: https://mm.icann.org/pipermail/rds-whois2-dataaccuracy/2018-April/000041.html | Submitted to subgroup on 1 May | ||
Is there a routine feedback process in place for Compliance to advise the ARS project of ARS-detected inaccuracies that were not ultimately found by Compliance to be inaccuracies (e.g., tickets generated because the state was missing in a country where states are not applicable)? | Submitted to subgroup on 31 July 2018 | ||
| Does ARS have access to non-public data under the Temporary Specification? Is the WHOIS data that is sampled by ARS obtained from the Registrar or Registry (for thick TLDs, since under GDPR much contact data may be redacted?) | Submitted to subgroup on 1 August 2018 | ||
| WHOIS1 Rec #10: Privacy/Proxy Services | Metrics for P/P Spec in the 2013 RAA | Submitted to subgroup on 11 March | |
| Briefing with ICANN Org staff leading the IRT staff support to learn how team will ramp up to manage PPSAI policy compliance | Held on 28 March | ||
| WHOIS1 Rec #11: Common Interface | 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. | Submitted to subgroup on 7 March | Link |
We have found several error messages in using the tool referenced below: The requested second-level domain was not found in the Registry or Registrar’s WHOIS Server. (the domain name was confirmed to be registered with the registry) Sorry, but the Registry or Registrar WHOIS Server responded with a rate limit message due to high query volumes or has closed the connection without a response. Please try your request again later. ICANN received a timeout while querying the Registry or Registrar’s WHOIS Server Are these error messages created by ICANN or do they come directly from the Registrar or Registry? Does ICANN track how often these error messages are presented in response to a WHOIS query? | Submitted to subgroup on 18 December | Link | |
| Requests for clarification regarding operating plan and annual report | Submitted to subgroup on 17 July | Link | |
| Over the period of WHOIS RT recommendation implementation, has there been anyone overseeing the entire package of work and, if so, did that entity issue ongoing reports and work plan, updated to track progress | Submitted to subgroup on 24 July | Link | |
| Summary of Improvements already underway, including under new Bylaws, such as annual progress plan that would include implementation of specific review recommendations, and confirmation from RT member(s) that implementation plan reflects the intent of the recommendation. | Submitted to subgroup on 2 August | Link |
New Assessment Subgroups
| Subgroup | Request | Status | Link |
|---|---|---|---|
| Subgroup 2 - Anything New | On AWIP and ERRP, what does compliance audit for these policies, and what compliance issues has compliance encountered | Submitted to subgroup on 09 April | Link |
| Subgroup 5 – Safeguarding Registrant Data | ICANN org to provide links to materials describing process for transfer of data to escrow providers | Submitted to subgroup on 11 March | Link |
Contract signed with escrow providers so that we may understand what processes, constraints or rules escrow providers are subject to regarding safeguarding data while under their custody and in relation to any data breaches that may be discovered. If the contracts are all substantially identical, then the standard boiler-plate contract will be sufficient. | Submitted to subgroup on 11 June | Link |