Page History
...
Active: Smartsheets Version
Date |
---|
Target Date
Responsible Council Member (if applicable)
Responsible Staff member (if applicable)
Additional Notes
Status / Action Item
Singapore Meeting Planning
Archive: Smartsheets Version
Date | File |
---|---|
2021-2022 | TBD |
2020-2021 | GNSO_Council_Action_Items_2020_2021.pdf |
Volker Greimann / Jonathan Robinson
Councillors are encouraged to provide input on the mailing list and/or to ICANN staff as soon as possible on proposed topics for the GNSO weekend working sessions in Singapore.
CWG To Develop an IANA Stewardship Transition Proposal on Naming Related Functions
.
Council must take part of its shared responsibility as a chartering organization to uphold the dialogue with the other parties, including the Board.
Council could consider making a public statement where it applauds the work done from all the groups (the numbers, names and the protocols) and offer a public statement of support recognizing the good work and the benefit from obtaining a coherent approach even if it has taken longer than the set-out timeline. The statement could also note that while meeting the timeline is important, not doing so in the interest of finding the right solution attests to the success of the multi-stakeholder model. Avri Doria and Tony Holmes volunteered to provide a draft statement for Council review. Discussion item for Board GNSO meeting in Singapore on Sunday 8 February 2015.
ON HOLD
Jonathan to explore with Patrik Falstrom the options for a SSAC liaison to the GNSO and/or visa versa.
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.
ON HOLD
Jonathan volunteered to lead the discussion on common understanding of amendments to motions on the Council list as well as the role of the maker & seconder of motions. The Council will consider at a future meeting whether or not to refer this item to the SCI for further review.
COMPLETED
Schedule update from Susan Kawaguchi, chair of the Board-GNSO EWG Process Working Group during the GNSO Weekend Working Session.
Susan to share any preliminary documents as work in progress with the Council.
Meeting notices to be sent to Council mailing list so that those interested can observe the meetings of the Board-GNSO EWG Process Working Group. Note, the next meeting is scheduled for 8 January. For further information, please see https://community.icann.org/x/9SnxAg).
Awaiting feedback from NGPC to GNSO Council letter to determine next steps. Staff to pursue this issue internally with the appropriate staff to find out when a response can be expected.
Anticipate update in Singapore.
COMPLETED
Send letter to Heather to thank her for her work and letter to Thomas to welcome him to his new position.
In the 30 July 2014 resolution the New gTLD Program Committee of the ICANN Board directed staff to "provide information to, and work with the GNSO to consider whether policy work on developing a long-term plan to manage gTLD name collision issues should be undertaken." Staff provided a paper to the GNSO Council on this topic that was presented and discussed during the ICANN meeting in Los Angeles (see https://www.icann.org/en/system/files/files/name-collision-gnso-policy-07oct14-en.pdf)
COMPLETED
Final letter was sent by Jonathan on 28 January.
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.
- Jonathan Robinson to meet with Thomas Schneider the GAC chair and/or one or more of the GAC vice-chairs face to face in Singapore to socialize the draft proposal for a framework for discussing the GAC communiqué.
- Volker Greimann to review the Registry Stakeholder Group correspondence to the GAC, and a letter from Thomas Schneider to the ICANN Board on the 9th of November 2014, in moving forward with the proposed framework for discussion on the GAC communiqué.
- David Cake to take the lead on work to be done on the GAC communiqué in the interim in preparation for Singapore.
- Councillors are encouraged to provide comments and input on the Framework for Discussion (see http://gnso.icann.org/en/drafts/gac-communique-framework-11dec14-en.pdf).
COMPLETED
Final letter sent by Jonathan.
Based on follow up discussions, during the ICANN 51 meeting the BV-WG directed the staff to reach out to the GNSO and ccNSO to collect an initial list of issues which should be addressed if this update is undertaken. This request was further outlined in the letter.
Mary to resend original request from Akram (COMPLETED)
Council to consider at its upcoming meeting to approve formation of informal community group to review IDN Implementation Guidelines and approve draft GNSO Council letter in response to these.