Topic | Entry Date | Target Date | Responsible Council Member (if applicable) | Responsible Staff member (if applicable) | Additional Notes | Status / Action Item |
Buenos Aires Meeting Planning
| 12/2 | 20/6 | David Cake / Jonathan Robinson | Glen de Saint Gery / Marika Konings |
| |
CWG To Develop an IANA Stewardship Transition Proposal on Naming Related Functions | 23/1 | 16/4 | Jonathan Robinson | Marika Konings | . | Council must take part of its shared responsibility as a chartering organization to uphold the dialogue with the other parties, including the Board.
|
| CWG on Enhancing ICANN Accountability | 13/11 | 16/4 | Thomas Rickert | Marika Konings | Keep the Council regularly informed of developments in the CWG on Enhancing ICANN Accountability. Councilors to take on the responsibility to keep their groups informed. For further information, see https://community.icann.org/x/ogDxAg). | |
| SSAC Liaison to GNSO Council / GNSO Council liaison to the SSAC | BA wrap up session | Jonathan Robinson | Julie Hedlund | ON HOLD Jonathan to explore with Patrik Falstrom the options for a SSAC liaison to the GNSO and/or visa versa. | ||
| Issues for the SCI - voting thresholds | 6/6 | Avri Doria / Alan Greenberg | Marika Konings | ON HOLD Alan and Avri volunteered to scope out the issue of voting thresholds in relation to implementation changes to adopted PDP recommendations for Council review. The Council will consider at a future meeting whether or not to refer this item to the SCI for further review. | ||
| Issues for the SCI - amendments to motions | 6/6 | 16/4 | Avri Doria | Julie Hedlund / Mary Wong | COMPLETED - issue transmitted to the SCI for review
| |
| Outstanding IGO/INGO PDP Recommendations | 26/6 | 16/4 | Thomas Rickert | Mary Wong | In June 2014, the NGPC wrote to the GNSO Council 'with an update on the ongoing work in response to the GNSO policy recommendations regarding Protection of IGO-INGO Identifiers in All gTLDs and the advice from the GAC in its Buenos Aires Communiqué addressing the same topic'. Furthermore the letter noted that 'the NGPC is considering available options to reconcile the differences at issue, including recommending that the ICANN Board reject the conflicting GNSO policy advice (pursuant to the procedure established in the Bylaws). However, before the NGPC recommends any course of action, the NGPC wanted to provide an update to the GNSO to highlight the concerns, and to give the GNSO an opportunity to consider modifying the elements of the approved policy recommendations in accordance with the procedure established in the GNSO Operating Procedures'. | Letter received from Cherine Chalaby (http://gnso.icann.org/en/correspondence/chalaby-to-robinson-15jan15-en.pdf) noting that the NGPC plans to talk further with the GAC and IGOs at ICANN 52 and would share any updates immediately following those meetings.
|
| GAC Communique | 13/11 | 16/4 | Volker Greimann | Marika Konings | During the GNSO Council Development Session in Los Angeles, the Council discussed a proposal for dealing with GAC advice: The timing of GAC Advice and how that fits into the policy making cycle as current cycle is problematic as GAC advice is developed in parallel to policy making efforts going on as well as during discussions at ICANN meetings. GAC Advice is often a mixture of policy and implementation, which should be reviewed and parsed by the GNSO since otherwise, it draws the Board into implementation. Typically, the GNSO never responds to the GAC Advice. A possible approach is for the community (led by the Council) to separate GAC Advice into issues of policy and implementation and then to come up with a GNSO response. Consideration of this approach could be a topic for discussion at the first GNSO Council meeting after an ICANN meeting. Policy advice could be further broken down into “in scope” and “out of scope” topics for ICANN policy and thereafter, what, if anything, the GNSO plans to undertake to address policy topics identified. This approach will permit the Board to then go back to the GAC to indicate what policy issues are being worked on. Dealing with the communiqué is a suggested topic for discussion in the joint GAC-GNSO meeting during ICANN 52. The Council had an initial exchange of views on this topic during its meeting on 13/11. | Mason Cole to prepare an update for the GAC/GNSO Consultation Group on the process to set expectations for the GAC about the Council engagement on the Communiqués.
GNSO Council chair and vice chairs and Mason Cole to meet with the GAC Chair and Vice Chairs to inform them of the potential process being undertaken by the Council. (COMPLETED)
Add Stephanie Perrin to the group of volunteers, Carlos Raúl Gutierrez and David Cake in Volker Greimann's absence. Anyone who would like to join the group is welcome. (COMPLETED) Check the latest version of the template
Although the timeline has been missed for the Singapore Communiqué, finish the current template and share it with the GAC and the ICANN Board as a test exercise. Councillors are encouraged to participate via the Council mailing list. At the ICANN meeting in Buenos Aires in June 2015 Set definite timelines for delivering the work. |
Proposed ICANN FY16 Budget
| 16/4 | 1/5 | COMPLETED - comment submitted Form a drafting team to address this concern and provide a comment to the public comment forum before the closing date, 1 May 2015 | |||
| Remaining Items from the GNSO’s Strategic Discussion Session in Singapore | 16/4 | 21/5 | Recirculate the Update that Marika Konings provided (completed) and comment on the Council mailing list. | |||
| CWG on Auction Proceeds | 16/4 | 21/5 | Further discussion on the Council mailing list to determine the response to Steve Crocker's letter |
For comments, suggestions, or technical support concerning this space, please email: ICANN Policy Department
© 2015 Internet Corporation For Assigned Names and Numbers
© 2015 Internet Corporation For Assigned Names and Numbers
