1.MOTION TO APPROVE THE REPORT FROM THE GNSO BYLAWS IMPLEMENTATION DRAFTING TEAM
Made by: James Bladel
Seconded by:
WHEREAS:
1. On 30 June 2016 the GNSO Council approved[gnso.icann.org] the creation of a Drafting Team (DT) that was to work with ICANN staff to “fully identify all the new or additional rights and responsibilities that the GNSO has under the revised Bylaws, including but not limited to participation of the GNSO within the Empowered Community, and to develop new or modified structures and procedures (as necessary) to fully implement these new or additional rights and responsibilities”;
2. In creating the DT, the GNSO Council requested that the DT provide the GNSO Council with an implementation plan “which will have the consensus of the Drafting Team, including any recommendations for needed further changes to ICANN Bylaws and/or GNSO Operating Procedures to enable effective GNSO participation in ICANN activities under the revised ICANN Bylaws, not later than 30 September 2016”;
3. The DT submitted its report to the GNSO Council on [DATE] (also insert link to report when available);
4. The GNSO Council has reviewed the DT’s report;
RESOLVED:
1. The GNSO Council approves the consensus recommendations in DT’s report as submitted.
2. The GNSO Council directs ICANN staff to draft proposed language for any necessary modifications or additions to the GNSO Operating Procedures and, if applicable, those parts of the ICANN Bylaws pertaining to the GNSO, for the Council’s consideration by no later than [the end of February 2017].
3. The GNSO Council directs ICANN staff to post all recommended modifications to or proposed new procedures or structures for public comment prior to the Council’s consideration of the proposals. As resolved previously, the GNSO Council intends to intends to adopt new, or proposed modifications to existing procedures and structures to implement the revised Bylaws for the GNSO by a GNSO supermajority vote.
4. In drafting the proposed language, ICANN staff may wish to consult the DT as needed. The GNSO Council therefore requests that members of the DT make themselves available for consultation by ICANN staff for this purpose.
5. The GNSO Council thanks the DT for its hard work on the report, especially in view of the nature of the limited time frame available to the DT.
2. Motion on the GNSO Council Response to the ICANN Board Letter on New gTLD Subsequent Procedures
Made by: Carlos Raúl Gutiérrez
Seconded by:
WHEREAS,
On 5 August 2016, the GNSO Council received a letter from Dr. Stephen Crocker seeking an understanding of the New gTLD Subsequent Procedures Policy Development Process (PDP) Working Group’s (WG) requirements and timing related to advancing a new application process.
On 16 August 2016, the GNSO Council acknowledged receipt of the letter and informed the ICANN Board that initial discussions within the GNSO Council and more broadly, within the GNSO community and New gTLD Subsequent Procedures PDP WG, were anticipated.
On 12 September 2016, the GNSO Council sent a letter to all of the GNSO’s Stakeholder Groups, Constituencies, and the New gTLD Subsequent Procedures PDP WG seeking input to help formulate the Council’s response to the ICANN Board.
The GNSO Council received an important number of responses and divergent positions from many different individuals as well a constituencies within the GNSO community, as well as from the New gTLD Subsequent Procedures PDP WG.
RESOLVED,
The GNSO Council has synthesized the positions received and prepared a response to the ICANN Board.
The GNSO Council looks forward to ongoing discussions with the broader community, particularly at ICANN57 in Hyderabad, India.
The GNSO Council expects to continue to consult with the New gTLD Subsequent Procedures PDP WG to determine if there are any significant changes to its schedule or scope of work as defined in its charter.
3. MOTION TO APPROVE A PROPOSED FINAL FRAMEWORK FOR FUTURE CROSS COMMUNITY WORKING GROUPS
Made by: Donna Austin
Seconded by:
Whereas:
- In March 2012 the GNSO Council approved a set of initial draft principles relating to the formation and operation of cross community working groups (CCWGs) and directed ICANN staff to solicit feedback on the principles from the other ICANN Supporting Organizations and Advisory Committees (SO/ACs);
- In June 2013 the ccNSO provided detailed feedback suggesting further clarifications and possible additions to the initial draft principles;
- In October 2013 the GNSO Council approved the formation of a Drafting Team to develop a Charter for a new CCWG to take forward and synthesize the initial work of the GNSO and the ccNSO feedback, and develop a final framework of operating principles that can function effectively across all SO/ACs relating to the formation, operation, decision making and termination of future CWGs (the "Final Framework of Operating Principles for Future CCWGs");
- The ccNSO Council and GNSO Council approved the Charter for the new CCWG to develop the Final Framework for Future CCWGs in March 2014;
- The CCWG published a proposed initial Framework for public comment in February 2016;
- Following review of public comments received and further community deliberations at ICANN56 in June 2016, the CCWG completed its proposed Final Framework and submitted it to the ccNSO and GNSO Councils on 19 September 2016
RESOLVED:
- The GNSO Council approves the Final Framework of Operating Principles for Future CCWGs.
- The GNSO Council thanks the CCWG for its work on developing and finalizing the Final Framework.
- The GNSO Council directs ICANN staff, upon the ccNSO Council’s adoption of the Final Framework, to inform all SO/ACs of the two Councils’ adoption of the Final Framework, and recommends that the principles and recommendations contained in the Final Framework be consulted by the ICANN community in considering the creation of all future CCWGs.
