Page History
#14, the WHOIS1 Rec #4 Compliance subgroup and the Topic 7 Compliance subgroup have been merged into one subgroup, and this wiki page will be the page used by that combined subgroup moving forward. | As per the decision reached on plenary call
---|
| Objectives
---|
Susan Kawaguchi Carlton Samuels, Chris Disspain, Susan Kawaguchi, Thomas Walden Members: Erika Mann,http://mm.icann.org/pipermail/rds-whois2-rec4-compliance/ Mailing-list archives: Conference calls: seesee here Review Team Templates: |
---|
Subgroup Documents
Date | Document (Versions in Red are latest) | File |
---|---|---|
| Face-to-Face Mtg #2 Slides - Findings v2 v1 Subgroup Report v3 v2 v1 Planning Questions v1 Next Steps v1 First Pass Document Compliance v2 (merged doc) Compliance v1 (merged doc) Assembled topic 1 rec #4 v3 & topic 7 v1 (Draft for subgroup rapporteur and subgroup's approval) Topic 1 Rec #4 v3 Topic 1 Rec #4 v2 Topic 1 Rec #4 v1 Topic 7 v1 |
Background Documents
- WHOIS Review Team (WHOIS1) Final Report (2012) and Action Plan
- WHOIS Review Team (WHOIS1) Implementation Reports, including
- WHOIS1 Implementation Briefings on Recommendations 4, 12, 13, 14: PPT, PDF
- Answers to RDS-WHOIS2 Questions on Implementation Briefings
- Documents cited in briefing on Recommendation 4 Compliance include
- Contractual Compliance Outreach information and Metrics Reporting
- Process and approach for enforcing the contract
- Contractual Compliance staff information
- Contractual Compliance annual reports and financials
- Chief Compliance Officer 2017 announcement and 2014 announcement
- Consumer Safeguards Director announcement
- Additional documents relevant to Topic 7 Compliance include
- WHOIS Review Team (WHOIS1) Final Report (2012), Section 1: The Effectiveness of ICANN’s WHOIS Compliance Effort
- Documents relevant to WHOIS1 Recommendations 5-9 - Accuracy
- ICANN Contractual Compliance web pages
- Competition, Consumer Trust and Consumer Choice Review Team Draft Report
- 2 February Meeting with Compliance Management - Q&A, citing additional documents
- FY18 Operating Plan and Budget
- Contractual Compliance 2017 Annual Report
- Contractual Compliance Audit Program
- Contractual Compliance Monthly Dashboards
- WHOIS ARS Contractual Compliance Metrics
- ICANN's Contractual Compliance Approach and Processes
- Notices of Breach, Suspension, Termination and Non-Renewal
- Registrar Formal Notices (Enforcement)
- Additional links specific to Compliance Objectives may be added here
Further background documents may be found on the Review Team's overall Background Materials page.
ICANN Org Briefings/Answers
- Rec 4 Written Implementation Briefing
- Meeting #3 - with Compliance Management (1 February 2018)
- Meeting #5 - with ICANN Compliance (28 March 2018)
- Brussels mtg follow-up questions
- ICANN compliance input includes:
- Written answers to 1 February questions
- Written answers to 8 February questions
- Written answers to 20 April questions
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 |
---|---|---|---|---|---|---|
22 | #28 |
| ICANN org to schedule a follow-up call for compliance subgroup | ICANN org | ||
21 | #6 |
| Carlton to draft finding/recommendation on use of DAAR to improve accuracy of WHOIS. | Carlton | ||
20 | #6 |
| Question 1: Susan to formulate a follow-up question for Compliance (possibly also GDD) regarding counting of null fields and the subset of null fields that occur for grandfathered domains. | Susan | ||
17 | #26 |
| Susan to research 2013 RAA negotiation materials to determine any reasons for allowing grandfathering. | Susan | ||
16 | #26 |
| Susan to examine CCT recommendation on DAAR to build this subgroup’s recommendation | Susan | ||
15 | #26 |
| Susan to formulate recommendation to include compliance taking a risk-based approach that is not just reactive - addressing systemic complaints and taking a risk-based approach | Susan | ||
14 | #26 |
| Subgroup to try testing recommendation on WHOIS policies that are being examined by this review (e.g., PP, IDN) to see if metrics/monitoring/reporting and enforcement have been defined for those | Susan |
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 |
---|---|---|---|---|---|---|---|---|
19 | #27 |
| Susan to liaise with ICANN org on a Doodle poll for a subgroup call | Susan | Email sent individually to Alice & Jean-Baptiste |
| ||
18 |
| Brussels follow-up list of questions to ICANN compliance | ICANN org |
|
| |||
13 | #26 - Email |
| Susan to confirm questions for ICANN compliance. | Susan | Email |
| ||
12 | #5 |
| Subgroup members to read ICANN compliance's answers and to advise of any follow-up questions. | Subgroup |
| |||
7 | #3 |
| Susan to reach out to Thomas to identify policies (from above list) that he will volunteer to review. | Susan | ||||
6 | #3 |
| Susan to include her findings about grandfathered domain names in draft subgroup report (see decisions reached, #3). | Susan | Draft Subgroup Report | |||
5 | #3 |
| Subgroup members to review and attempt to answer questions prior to F2F meeting as follows:
Questions to be addressed (at minimum):
| Subgroup, Carlton, ERika | Draft Subgroup Report | |||
11 | #23 |
| MSSI Secretariat to send out a new doodle. | MSSI-Secretariat |
|
| ||
10 | Interview/discussion questions - second set | ICANN org |
| |||||
9 |
| Interview/discussion questions - first set | ICANN org |
| ||||
8 | #3 |
| Suggest timeline for completing briefing questions and desired timeframe for that briefing with ICANN Org compliance. | Susan |
| |||
4 | #2 |
| Subgroup 2-day face-to-face meeting: Alan and Susan requested to hold a two days subgroup face-to-face meeting with Compliance Department at ICANN org office in Los Angeles, only a small conference room would be needed. This would happen before the next plenary face-to-face meeting. ICANN org to liaise with meetings team to confirm notification time needed with meetings teamto prepare such meeting to identify a possible date (also taking into consideration compliance department staff would be available). | ICANN org |
| |||
3 | #2 |
| Next Week’s Kick-Off Meeting with ICANN org Compliance Team (exact date to be confirmed): Initial 1hour kickoff meeting between subgroup members who are in LA next week and members of the compliance Department - Questions raised on today's call to be shared with the subgroup (see below), subgroup members not attending the call to share input/edits by Wednesday COB. - Subgroup members to review attached first pass planning document and raise any questions, edits, by tomorrow COB. - ICANN org to look into the possibility to add remote participation during the meeting with compliance for remote subgroup members. | Subgroup/ICANN org | ||||
2 | #1 |
| Susan to take a first look at filling in the work statement based on today's discussion, and share it with the subgroup for input. | Susan | ||||
1 | #1 |
| Susan to provide ICANN org with dates for future subgroup call. Doodle to be sent out to subgroup based on this. | Susan |
Decisions Reached
Source of Request | Date | Decision |
---|---|---|
#6 |
| Question 4: subgroup agreed to Susan's draft recommendation. |
#6 |
| Question 2: Recommendation that a policy or best practice be developed to flag in WHOIS when a domain name has been suspended for inaccurate data. subgroup may suggest a policy such as updating the inaccurate record. |
#3 |
| Include in briefing questions:
|