Versions Compared

Version Old Version 51 New Version 52
Changes made by

Alice Jansen

Alice Jansen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
(red star)Objective

Consistent with ICANN’s mission and Bylaws, Section 4.6(e)(iv), the Review Team will (a) evaluate the extent to which ICANN Org has implemented each prior Directory Service Review recommendation (noting differences if any between recommended and implemented steps), (b) assess to the degree practical the extent to which implementation of each recommendation was effective in addressing the issue identified by the prior RT or generated additional information useful to management and evolution of WHOIS (RDS), and (c) determine if any specific measurable steps should be recommended to enhance results achieved through the prior RT’s recommendations. This includes developing a framework to measure and assess the effectiveness of recommendations, and applying that approach to all areas of WHOIS originally assessed by the prior RT (as applicable). 

RT1 Recommendations to be assessed by this subgroup:

Recommendation #3 - Outreach

Background Documents

  • WHOIS1 Implementation Briefings on Recommendations 1, 2, 3, 6, 7, 9, 15, 16: PPT, PDF

Further background documents may be found on the Review Team's overall Background Materials page.

(red star)Leader/Rapporteur: Alan Greenberg

(red star)Members: Alan Greenberg, Carlton Samuels, Erika Mann

(red star)Mailing-list archives:  http://mm.icann.org/pipermail/rds-whois2-outreach/

(red star)Conference calls

(red star)Review Team Templates: see here


Subgroup Documents

Date

Document (Versions in Red are latest)

File

Subgroup Report

 

v11DOCX

 

v10DOCX

 

v9 (incl. FtoF #3 Agreements)DOCX

 

v8DOC

 

v7DOCX

 

v6DOCX

 

v5DOCX

v4DOCX

 

v3DOCX

v2DOCX

 

v1DOCX
Face-to-Face Mtg #2 Slides - Findings

 

v2PPTX

 

v1

PPTX
Planning Questions

v1PPTX
First Pass Document

 

v3DOCX

 

v2DOCX

 

v1DOCX

ICANN Org Briefings/Answers

Open Actions/Requests

*To be provided once reasonable date is determined by appropriate subject-matter expert

Item #Source of RequestDate of RequestAction Item RequestAction Owner

Anticipated Completion Date*

Progress Notes
5FtoF #3

 

Alan to update and finalize the text of recommendations R3.1 and R3.2, based on agreements reached.Alan



4#34

 


Alan to update the subgroup report to fill gaps.Alan

3#33

 

Review conclusions on outreach.


Alan

Completed Actions/Requests

*To be provided once reasonable date is determined by appropriate subject-matter expert

Item #Source of RequestDate of RequestAction Item RequestAction Owner

Anticipated Completion Date*

Progress NotesCompleted ResponseCompletion Date
6#37

 

Modify 3.1 and 3.2 to imply an ongoing action

Alan

 


DOCX

 

5FtoF #3

 

Alan to update and finalize the text of recommendations R3.1 and R3.2, based on agreements reached.Alan

 


DOCX
4#34

Alan to update the subgroup report to fill gaps.Alan





3#33

 

Review conclusions on outreach.Alan



2#19

 

Discuss who the targets for outreach are and how well was each target's needs metOutreach subgroup

Face-to-Face meeting

 

1Email

 

Question to SMEs: 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.

ICANN org

 


Briefing submitted via email.

 

Decisions Reached

SourceDateDecision
FtoF #3

 

R3.2, revised as follows (text to be finalized by Alan)
With community input, ICANN should decide which groups outside of those that routinely engage with ICANN should be targeted effectively through WHOIS outreach. A WHOIS outreach plan should then be developed, executed, and documented. WHOIS inaccuracy reporting was identified as an issue requiring additional education and outreach and may require a particular focus. The need for and details of the outreach may vary depending on the ultimate GDPR implementation and cannot be detailed at this point.
FtoF #3

 

R3.1, with the amendment that the recommendation ideally be implemented post-GDPR implementation, but no later than [TBD months] after the recommendation is adopted.