The meeting of the GNSO Review Working Group is scheduled for Tuesday, 15 November 2016 at 14:00 UTC for 60 minutes.
06:00 PST, 09:00 EST, 14:00 London, 15:00 CET, 01:00 Sydney (Wednesday)
For other places: http://tinyurl.com/hfmjlbz
Draft Agenda: GNSO Review WG Meeting
1. Roll Call/Statements of Interest
2. Review Agenda
3. Continue Discussion of Draft Implementation Plan Recommendations (see attached document), Section 3.3 Phase 3: Medium and Low Priority Recommendations on page 18
4. Next Steps
Please see below the deadlines/goals:
21 November: Send to GNSO Council with motion for approval (document and motion deadline for 01 December GNSO Council meeting)
01 December: GNSO Council votes on plan approval, or defers the motion to approve
15 December: GNSO Council votes on plan approval (if deferred from 01 December) – last opportunity to meet deadline to deliver plan to the Board
31 December: Deadline to deliver plan to the Board of Directors per the Board resolution
Documents: GNSO Review Impl Plan DRAFT 09 Nov 2016.pdf
Attendance: Amr Elsadr, Avri Doria, Heath Dixon, Jen Wolfe, Pascal Bekono, Rafik Dammak, Sara Bockey
Staff: Marika Konings, Julie Hedlund, Lars Hoffmann, Michelle DeSmyter
Apologies: Wolf-Ulrich Knoben, Lawrence Olawale-Roberts
On audio only: None
Notes/Actions:
Action items:
- Staff will produce a final draft implementation plan and send it to the WG on 15 November.
- WG members should provide any final edits or comments on the plan by Friday, 18 November, which staff will incorporate into the final implementation plan.
- Staff will produce a draft motion for Wolf-Ulrich Knoben to send to the GNSO Council along with the final implementation plan by the document and motion deadline of Monday, 21 November for the 01 December Council meeting.
Discussion Notes:
Overarching question: Is there a final step for the GNSO Review WG to agree that the implementation is complete? The WG is the accountability mechanism.
Rec 20: Comments? None.
Rec 21: Add a timeline -- recurring basis. Regular reporting/updating to the GNSO Council at every ICANN meeting as a status report to the GNSO. Put on the GNSO agenda.
Rec. 7: Comments? What are existing measures? There are some existing services, such as real-time translation (as being done in ALAC), determine costs -- cost-benefit analysis -- including an assessment of costs.
Rec. 35: Comments? Overlap with Accountability WS2-Diversity. A first step might be to review ongoing efforts in relation to the same subject to determine whether a separate WG is needed. Ensure it is coordinated with what is being done in WS2. Link the creation of new WG to the outcome of diversity subgroup.
Rec. 22: Comments? None.
Rec. 1, 2, 3: Comments? None.
Rec. 5&9: Comments? None.
Rec. 12: Comments? None.
Rec. 17: Comments? None.
Rec. 4: Comments? None.
Rec. 34: Comments? Avri Doria: 1. How do we define effectiveness? 2. We are not really doing this and I think that we are wiggling out of actually doing it with the way this is being 'done'. Rafik Dammak: Another element to have in mind for implementation -- use more standard times, such as UTC. Don’t favor a particular region. Care needs to be taken in how "effectiveness" is defined.
Rec. 36: Comments? None.
Timeframe: Is this reasonable? Provide more time for high-priority items (phase 2). Extend the timeframe to end of 2017.
