Introduction to the Revised GNSO Policy Development Process By Marika Konings
Background As part of GNSO Improvements: GNSO tasked to develop a new GNSO policy development process that incorporates a working group approach and makes it more effective and responsive to ICANN s policy development needs Revised PDP Adopted by the ICANN in December 2011 Revised PDP rules now applicable to all ongoing and new PDPs 2
Is this issue intended to result in consensus policy? Yes No Follow other GNSO Process s not intended to result in a Consensus Policy may be referred to another GNSO process by the GNSO.
(What is the?) Request an GNSO and Staff to advise on additional research, discussion, or outreach. 45 days Advisory Committee Develop Peliminary of at least 1/4 of the members of the of each House or a Majority of one House Public Comment Period Final
(Moving ahead with a PDP or not?) No intermediate vote required for s requested by the ICANN Initiate PDP YES NO In Scope: 1/4 of each house or 2/3 of one house in favor of initiating PDP Out of Scope: GNSO Supermajority Create a Drafting Team to develop the PDP WG Charter Adopt a Charter. Same voting thresholds apply as for the Initiation of the PDP. Following rejection of a PDP requested by an Advisory Committee (AC), option to meet with AC representatives to discuss rationale for rejection, followed by possible request for reconsideration by AC
(Exploring the issue in depth and developing recommendations) Seek opinion of other ICANN Advisory Committees and Supporting Organizations Publish WG Initial Request for Stakeholder / Constituency Statements Required Public Comment Period Compilation of statements Recommendations and level of consensus achieved Statement concerning impact of the proposed recommendations Publish WG Final WG Review and Analysis of Public Comments WG and Finalization of
(Assess / Affirm WG recommendations) GNSO considers recommendations (discouraged from itemizing or modifying) Not Adopted - If there are concerns / modifications, council is encouraged to send back to PDP-WG Adopted, following voting thresholds * Recommendations to the * For voting thresholds, refer to Article X, Section 3(9) of the ICANN bylaws.
with the a PDP or not?) (What is the?) (Moving ahead (Assess / Affirm WG recommendations)(final Approval) (Exploring issue in depth and developing recommendations) Is this issue intended to result in consensus policy? If the and determines GNSO Staff that the policy is not in the best interest of the ICANN Request for Stakeholder community or ICANN, the can reject the GNSO Recommendation by a 2/3 In Scope: to advise on additional GNSO Constituency considers recommendations / Statements vote ofdiscussion, the (in case the PDP Recommendation was adopted by a GNSO 1/4 of each house or 2/3 of one research, (discouraged from itemizing or modifying) YES NO case theinpdp recommendation was adopted by favor of initiating PDP orsupermajority) outreach. or majority vote (in house Adopted, following voting thresholds * No intermediate Requestvote an required for s requested by of other ICANN Seek opinion the ICANN Advisory Committees and 45 days Yes No less than a GNSO Supermajority) Approval of Optional - Formation of PDP Recommendation Review Team to assist ICANN Staff in developing the implementation details for the policy. Initiate PDP Publish Out of Scope: Required Public Supporting Advisory Organizations articulates the reasons for rejection submits this Statement to the GNSO and Supermajority of at least Comment Period WG Initial Committee GNSO 1/4 of the members of the of Adopted, following Follow other Reviewvoting and Create a Drafting Not Adopted GNSO by the and schedule meeting to WG discuss Following rejection of a PDP each House or ato review statement thresholdsof Public GNSO Process Analysis requested by an Advisory Committee Team to develop the Majority of one Develop s not intended to shall meet to affirm or modify its option recommendation and communicate that (AC), to meet with AC repre-comments House PDP WG Charter Peliminary If there are concerns / result in a Consensus conclusion (the "Supplemental Recommendation") to the. sentatives to discuss rationale for Compilation of statements modifications, rejection, council is followed by possible WG Policy may be referred to Publish Recommendations and level of encouraged to for reconsideration and Finalization of another GNSO process request by ACRecommendations can reject Supplemental Recommendation consensus achievedif it determines WG Final send back to PDP-WG by the GNSO. Final to the that such policy is not in the interestsadopt of concerning the ICANN Community a Charter. Statement impact of Public Comment No Yes on Supplemental or ICANN (by 2/3 of the case ofvoting GNSO Supermajority the in proposed recommendations Same thresholds ort Period Recommendation on Supplemental majority vote of the Rep Recommendation apply asor for the Initiation * For voting thresholds, refer to Article X, in case of less than GNSO Supermajority ). Section 3(9) of the ICANN bylaws. of the PDP. ICANN Staff should inform the GNSO of proposed implementation of a new GNSO recommended policy. must conform to GNSO recommendation
Optional - Formation of Review Team to assist ICANN Staff in developing the implementation details for the policy. ICANN Staff should inform the GNSO of proposed implementation of a new GNSO recommended policy. must conform to GNSO recommendation
Questions 10
Thank You