Page History
...
Active: Smartsheets Version
Date |
---|
Target Date
Responsible Council Member (if applicable)
Responsible Staff member (if applicable)
Additional Notes
Status / Action Item
Buenos Aires Meeting Planning
Develop the proposed agenda for GNSO weekend session in Buenos AiresDavid Cake / Jonathan Robinson
Council members are encouraged to complete the GNSO meeting survey (see https://www.surveymonkey.com/s/35M9C75) and encourage their respective groups to do likewise.
Archive: Smartsheets Version
Date | File |
---|---|
2021-2022 | TBD |
2020-2021 | GNSO_Council_Action_Items_2020_2021.pdf |
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 statement in support of the work done by all groups submitted (see http://gnso.icann.org/en/correspondence/gnso-iana-transition-28feb15-en.pdf).
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.
Template has been developed by staff to assist scoping of issues for SCI - completed template for this specific issue as well as reconsideration of motions submitted to the GNSO Council for consideration on 19/3.
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.
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.
COMPLETED - response letter sent to Akram Atallah (see http://gnso.icann.org/en/correspondence/robinson-to-atallah-01mar15-en.pdf)