OPEN ACTIONS/REQUESTS
| Item # | Source of Request | Date of Request | Action Item Request | Action Owner | Request Clarified (link to email archive; date) | Anticipated Completion Date |
|---|---|---|---|---|---|---|
| 51 | #10 | Adjust work plan /ToR submissions to Nov 28th | ICANN org | |||
| 50 | #10 | Staff to check time of leadership call with ALAC/GNSO call 1630 UTC, and to check with Cathrin that new time calls work | ICANN org | |||
| 49 | #10 | Scope of review - remove required action from plenary agenda | ICANN org | |||
| 48 | #10 | Cochairs to run in-depth analysis of ToR. Reach out to Cathrin separately. Send out the Tor to list with call for changes at plenary meeting | Co-chairs | |||
| 47 | #10 | On plenary call, ask for volunteers for in-depth analysis of work plan | Alan | |||
| 46 | #10 | Ask RT members to select two subgroups they would be interested in leading (Leader/Rapporteur). Include definition of what role entails. Ask RT members to select two with priority order by next RT call | ICANN org | |||
| 45 | #9 | Workplan: Send a reminder to rt members to share comments/questions on the work plan | Alan | |||
| 44 | #9 | Consensus policy: Draft a document based on today's discussion | Alan | |||
| 43 | #9 | Scope: latest version (word) will be sent to Katrina. | Alan | |||
| 42 | #9 | Briefing on contractual compliance/RAA: ICANN org to liaise with Stephanie | ICANN org | |||
| 30 | #7 | Scan through Terms of Reference and see how he can contribute | Alan | |||
| 29 | #7 | Review the Terms of Reference reporting section | Susan |
COMPLETED ACTIONS/REQUESTS
| Item # | Source of Request | Date of Request | Action Item Request | Action Owner | Request Clarified (link to email archive; date) | Anticipated Completion Date | Completed Response | Completion Date |
|---|---|---|---|---|---|---|---|---|
| 41 | #9 | Subgroup report:
| ICANN org | Updated version sent with plenary agenda via email. | ||||
| 40 | #9 | First Pass Planning Document: Target to send refined version by the end of this week. Cathrin to refine the document with Alice's help. | Cathrin | Updated version sent with plenary agenda via email. | ||||
| 39 | #9 | Scope and Objectives Document: Update document with two draft action items and circulate to the review team | ICANN org | Updated version sent with plenary agenda via email. | ||||
| 38 | #8 | FtoF Meeting #1 Action items:
|
| email including updated documents sent to the Review Team. | ||||
| 37 | #8 | Scope & Objectives: ICANN org to circulate Scope & Objectives document to the RT. | ICANN org | email including updated documents sent to the Review Team. | ||||
| 36 | #8 | RDS-WHOIS2 Objectives & Expressions of interest from RT members: ICANN org to update Table to reflect the decisions that were made on the call and shared with the Review Team as updated for discussion on Thursday. | ICANN org | email including updated documents sent to the Review Team. | ||||
| 35 | #8 | Questions on WHOIS1 Implementation Briefings: Leadership to raise any objections on implementation briefing questions by COB, today. | Leadership | Alan shared comments via email. | ||||
| 34 | #8 | Work plan: ICANN org to share work plan with Review Team and ask for in-detail review of the document in preparation for the cal | ICANN org | email including updated documents sent to the Review Team. | ||||
| 27 | #6 | Provide leadership with a comparison of costs between a face to face meeting outside of and within ICANN Meeting dates. | ICANN org | Presentation scheduled during the first face-to-face meeting / day 2 | ||||
| 9 | #3 | Brussels FtoF meeting: Send arrival date/time to leadership (if available) | ICANN org | / | CLOSED | |||
| 31 | #7 | Send a reminder to Review Team on scheduling of ICANN 60 informal meeting and to flag it during plenary call | ICANN org | email sent to the Review Team. | ||||
| 28 | #6 | Circulate the workplan to the review team. It will be presented at later stage (plenary call on Sept 28 or face to face meeting #1) | ICANN org | Workplan was presented during the first face-to-face meeting. | ||||
| 20 | #5 | Include information on logistics (how to get to the meeting/hotel from the airport), security | ICANN org | email sent to the review team. | ||||
| 25 | #6 | Provide an analysis of what would be the best timing taking into consideration time zones of RT members, and schedule plenary calls each week (after the face-to-face meeting) based on this analysis of the most appropriate meeting time. | ICANN org | Analysis sent via email to leadership. | ||||
| 26 | #6 | Send out a doodle to request review team members availability at ICANN60 (breakfast/dinner), send a copy to Alan/Gisela first to confirm availability on proposed dates. | ICANN org | Doodle sent via email to Review Team | ||||
| 24 | #5 | Draft dependencies section to replace "Across-Field" by "Cross-Field" | ICANN org | Change made to Terms of Reference and shared via email to Review Team. | ||||
| 13 | #4 | Cathrin to produce draft text reflecting RT's discussion on law enforcement objectives, including possible methodology to obtain targeted community input on objectives, for RT to formulate recommendations w/r/t WHOIS meeting them. | Cathrin | Document sent via email to leadership. | ||||
| 33 | #7 | Scope: Incorporate issues raised in Alan's document into the scope document prepared by ICANN org, and to circulate merged scope doc (including Susan's feedback) to leadership for approval to relay to RT. | ICANN org | Document sent via email to leadership. | ||||
| 18 | #4 | Leadership to encourage Review Team members at next plenary meeting to attend/listen to future RDS PDP calls. | ICANN org | Done on plenary call #6. | ||||
| 21 | #5 | ICANN org to reach out to Cathrin and confirm this a supporting document. | ICANN org | Lisa reached out directly via email to Cathrin | ||||
| 22 | #5 | Share Scope document ahead of plenary call, and posted on the wiki | ICANN org | Scope document sent via email to the Review Team. | ||||
| 19 | #5 | Send out FtoF meeting agenda asap to the review team and invite for comments | ICANN org | FtoF meeting agenda sent via email to the Review Team. | ||||
| 25 | #5 | Review and approve Fact Sheet, to be published on the RDS-WHOIS2-RT | Alan | Approval sent via email. | ||||
| 23 | #5 | Draft OECD Objective: Replace RDS by RDS/WHOIS and add footnote after high-level recommendations stating "This will not include detailed analysis of data protection laws and specific requirements for compliance with those laws." Draft to be provided to the RT for consideration and discussion. | ICANN org | email sent to the Review Team. | ||||
| 17 | #4 | Alan to send a reminder on Scope discussion and on WHOIS implementation briefings preliminary questions. | Alan | Reminder sent via email to the Review Team. | ||||
| 15 | #4 | ICANN Org to send a reminder to Stephanie Perrin on suggested language on effectiveness component. | ICANN org | Reminder sent via email to Stephanie. | ||||
| 14 | #4 | ICANN Org to produce draft text for leadership to refine reflecting OECD component of bylaws mandate. | ICANN org | Document sent via email to the Review Team. |
| |||
| 16 | #4 | Alan to suggest draft text on replacement and removal of members for Review Team Consideration; and share it with the leadership. | Alan | Alan sent paragraph via email. | ||||
| 12 | #4 | ICANN org to update table to split bylaws item (ii) into effectiveness and meeting needs, and to expand the issue column to include the actual bylaws text. Result to be shared with leadership for review of especially decision column to ensure accurate reflection of call #5. Updated table, including leadership feedback if any, to be distributed to RT in advance of call #6. | ICANN org | Email sent to leadership. |
| |||
| 10 | #3 | Include leadership slide, brief Brussels schedule, implementation slides (after welcome) on Thursday call’s agenda | ICANN org | Slides circulated via email to the RT. | ||||
| 11 | #3 | Send homework reminder to list | Alan | / | / | Homework sent via email to the RT. | ||
| 8 | #2 | Email PDFs of latest WHOIS RT1 Implementation Reports to Review Team for information, with request to please read report going forward to identify questions to be addressed by implementation briefings. | ICANN org | / | Sent via email to the RT. | |||
| 7 | #2 | Email RT requesting all to review WHOIS RT1 Report / list of recommendations: http://www.icann.org/en/about/aoc-review/whois/final-report-11may12-en.pdf. | Alan | / | Sent via email to the RT. | |||
| 6 | #2 | Terms of Reference Template to be distributed to Review Team no less than 24 hour in advance of Thursday's plenary call, and briefly introduced during call. | ICANN org | / | Sent via email to the RT | |||
| 5 | #2 | Send page on limited scope and responses to leadership team to serve as intro to scope discussion. | ICANN org | / | Sent via email to the RDS-WHOIS2 leadership | |||
| 4 | #2 | Create Skype group chat for RDS-WHOIS2-RT leadership including leaders and staff. | ICANN org | / | Confirmation message sent via Skype. | |||
| 3 | #2 | Prepare the draft plenary call agenda and materials to be sent to the leadership for review before its circulated to the RT members. | ICANN org | / | Sent via email to the RDS-WHOIS2 leadership. | |||
| 2 | #1 | Send out a doodle poll for Monday & Tuesday to determine the right timing for leadership calls. | ICANN org | Sent via email to the RDS-WHOIS2 leadership. | ||||
| 1 | #1 | Leadership mailing list can be made public. | ICANN org | Email list made public. |
