Page History
 Objective
|
|---|
Background Documents
- SAC051, Report on Domain Name WHOIS Terminology (2011)
- SAC054, Report on Domain Name Registration Data Model (June 2012)
- RDS/WHOIS Contractual Requirements - Sections pertaining to Data Safeguards, including
- 2013 Registrar Accreditation Agreement (RAA), Section 3.6 - Data Retention Specification
- 2014 New gTLD Registry Agreement, Specification 2 - Data Escrow Requirements
Further background documents may be found on the Review Team's overall Background Materials page.
|
|---|
Leader/Rapporteur: 
Subgroup Documents
Date | Document (Versions in Red are latest) | File |
|---|---|---|
| Subgroup report | ||
| v9 | DOCX |
| v8 | DOCX |
| v7 (incl. FtoF #3 Agreements) | DOCX |
| v6 | DOCX |
| v5 | DOCX |
| v4 | DOCX |
| v3 | DOCX |
| v2 | DOCX |
| v1 | DOCX |
| Face-to-Face Mtg #2 Slides - Findings | ||
| v2 | |
| v1 | PPTX |
| Work plan (as per Alan's email) | ||
| v1 | |
| Planning questions | ||
| v2 | PPTX |
| v1 | PPT |
| First Pass Document | ||
| v4 | DOCX |
| v3 | DOCX |
| v2 | DOCX |
| v1 | DOCX |
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 |
|---|
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 |
|---|---|---|---|---|---|---|---|---|
| 10 | #37 |
| Modify language to specify that level of data breach should be the subject of discussion with data security expert(s) | Alan |
| DOCX |
| |
| 9 | FtoF #3 |
| Update Rec SG.1 to reflect agreements reached. | Alan |
| DOCX |
| |
| 8 | #35 |
| Subgroup 5 | Safeguarding Registrant Data - Alan to update the draft recommendation text that appears in brackets [ICANN should similarly consider whether contractual requirement are needed to require registrars, registries and escrow provides to notify registrants in the event of data breaches.] regarding breach notification to serve as the basis for discussion at the face-to-face meeting #3. | Alan | ||||
| 7 |
| 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. |
| ICANN org |
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 | |
|---|---|---|---|---|---|---|---|---|---|
| 6 | #27 |
| Subgroup members to send a quick status update to the review team | Subgroup | CLOSED | Plenary Call #28 |
| ||
| 5 | #26 |
| Alan to confirm revisions made RT agreements. | Alan | CLOSED |
| |||
| 4 | #26 |
| Stephanie to provide draft formulation to Alan | CLOSED | Stephanie | Report |
| ||
| 3 | #26 |
| Alan to refine question number 3. | CLOSED | Alan | Report |
| ||
| 2 | #26 |
| Questions for ICANN org : ○ What are contractual requirements to secure stored escrow data ○ What are contractual requirements to notify ICANN in the event of breach ○ How do you secure registrant data under your control? | CLOSED | ICANN org |
| |||
| 1 | #25 |
| Alan plans to share his first draft of subgroup draft report with the subgroup/RT for review in parallel by the end of the weekend. | Alan |
|
Decisions Reached
| Source of request | Date | Decision |
|---|---|---|
| FtoF #3 |
| Update findings but retain recommendation for review by data security experts. Do not include a recommendation regarding registrant notification. |
