Page History
Summary: Phases 1&2
...
; Phase 3
Documents for Review:
GNSO Review Implementation Charter Rec 10-11 v1 07 June 2017.pdf
Consensus Call:
CONSENSUS CALL-GNSO Review Implementation Charter Rec 24-25 v3 08 June 2017.pdf - Closes COB 03 July 2017
Approved by Consensus:
CONSENSUS CALL-GNSO Review Implementation Charter Rec 8 v4 12 April 2017.pdf – 04 May 2017
...
Recommendation 8: That Working Groups should have an explicit role in responding to implementation issues related to policy they have developed.
Recommendation 14 & 15: 14 – That the GNSO further explores PDP ‘chunking’ and examines each potential PDP as to its feasibility for breaking into discrete stages. Recommendation 15 : – That the GNSO continues current PDP Improvements Project initiatives to address timeliness of the PDP.
...
Recommendation 19: As strategic manager rather than a policy body the GNSO Council should continue to focus on ensuring that a Working Group has been properly constituted, has thoroughly fulfilled the terms of its charter and has followed due process.
Phase 2: High Priority Recommendations
Approved by Consensus:
TBD
...
Recommendations 26, 27, 28, 29: 26 – That GNSO Council members, Executive Committee members of Stakeholder Groups and Constituencies and members of Working Groups complete and maintain a current, comprehensive Statement of Interest on the GNSO website. Where individuals represent bodies or clients, this information is to be posted. If not posted because of client confidentiality, the participant’s interest or position must be disclosed. Failing either of these, the individual not be permitted to participate. 27 – That the GNSO establish and maintain a centralized publicly available list of members and individual participants of every Constituency and Stakeholder Group (with a link to the individual’s Statement of Interest where one is required and posted). 28 – That section 6.1.2 Membership of Chapter 6.0 Stakeholder Groups and Constituencies: Operating Principles and Participation Guidelines of the GNSO Operating Procedures be revised to clarify that key clauses are mandatory rather than advisory, and to institute meaningful sanctions for non-compliance where appropriate. 29 – That Statements of Interest of GNSO Council Members and Executive Committee members of all Stakeholder Groups and Constituencies include the total number of years that person has held leadership positions in ICANN.
Phase 3: Medium and Low Priority Recommendations
Approved by Consensus:
TBD
Out for Consensus Call:
TBETBD
WG Reviewing Charters:
INSERTTBD
Staff to Draft Charters:INSERT
Recommendation 20: That the GNSO Council should review annually ICANN’s Strategic Objectives with a view to planning future policy development that strikes a balance between ICANN’s Strategic Objectives and the GNSO resources available for policy development.
Recommendation 21: That the GNSO Council should regularly undertake or commission analysis of trends in gTLDs in order to forecast likely requirements for policy and to ensure those affected are well-represented in the policy-making process.
Recommendation 7: That Stakeholder Groups and Constituencies engage more deeply with community members whose first language is other than English, as a means to overcoming language barriers.
Recommendation 35: That the GNSO Council establish a Working Group, whose membership specifically reflects the demographic, cultural, gender and age diversity of the Internet as a whole, to recommend to Council ways to reduce barriers to participation in the GNSO by non- English speakers and those with limited command of English.
Recommendation 22: That the GNSO Council develop a competency-based framework, which its members should use to identify development needs and opportunities.
Recommendations 1, 2, and 3: 1 – That the GNSO develop and monitor metrics to evaluate the ongoing effectiveness of current outreach strategies and pilot programs with regard to GNSO Working Groups. 2 – That the GNSO develop and fund more targeted programs to recruit volunteers and broaden participation in PDP Working Groups, given the vital role volunteers play in Working Groups and policy development. 3 – That the GNSO Council reduce or remove cost barriers to volunteer participation in Working Groups.
Recommendations 5 & 9: 5 – That, during each Working Group self-assessment, new members be asked how their input has been solicited and considered. 9 – That a formal Working Group leadership assessment program be developed as part of the overall training and development program.
Recommendation 12: That ICANN assess the feasibility of providing a real-time transcription service in audio conferences for Working Group meetings.
Recommendation 17: That the practice of Working Group self-evaluation be incorporated into the PDP; and that these evaluations should be published and used as a basis for continual process improvement in the PDP.
Recommendation 4: That the GNSO Council introduce non‐financial rewards and recognition for volunteers.
Recommendation 34: That PDP Working Groups rotate the start time of their meetings in order not to disadvantage people who wish to participate from anywhere in the world.
Recommendation 36: That, when approving the formation of a PDP Working Group, the GNSO Council requires that its membership represent as far as reasonably practicable the geographic, cultural and gender diversity of the Internet as a whole. Additionally, that when approving GNSO Policy, the ICANN Board explicitly satisfy itself that the GNSO Council undertook these actions when approving the formation of a PDP Working Group.
