Historical Resolution Tracking Feature » GNSO Policy & Implementation Recommendations – Proposed Changes to ICANN Bylaws
Important note: The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.
GNSO Policy & Implementation Recommendations – Proposed Changes to ICANN Bylaws
The Board approves ICANN to initiate a public comment period on potential changes to the ICANN Bylaws to implement certain recommendations resulting from the GNSO's non-PDP Policy and Implementation Working Group
Whereas, On 17 July 2013, the GNSO Council approved the charter for a GNSO non-PDP Policy and Implementation Working Group (http://gnso.icann.org/en/council/resolutions#201307) tasked to provide the GNSO Council with a set of recommendations on:
A set of principles that would underpin any GNSO policy and implementation related discussions, taking into account existing GNSO Operating Procedures.
A process for developing gTLD policy, perhaps in the form of "Policy Guidance", including criteria for when it would be appropriate to use such a process (for developing policy other than "Consensus Policy") instead of a GNSO Policy Development Process.
A framework for implementation related discussions associated with GNSO Policy Recommendations.
Criteria to be used to determine when an action should be addressed by a policy process and when it should be considered implementation.
Further guidance on how GNSO Implementation Review Teams, as defined in the PDP Manual, are expected to function and operate.
Whereas, the GNSO Policy and Implementation Working Group published its Initial Recommendations Report for public comment on 19 January 2015 (see https://www.icann.org/public-comments/policy-implementation-2015-01-19-en).
Whereas, the GNSO Policy and Implementation Working Group reviewed the input received (see public comment review tool) and updated the report accordingly.
Whereas, the Final Recommendations Report (see http://gnso.icann.org/en/drafts/policy-implementation-recommendations-01...), which contains a number of recommendations that will require changes to the ICANN Bylaws, has obtained the full consensus support of the GNSO Policy and Implementation Working. The Final Recommendations Report was submitted to the GNSO Council for its consideration on 2 June 2015.
Whereas, the GNSO Council unanimously adopted the recommendations during its meeting on 24 June 2015 (see http://gnso.icann.org/en/council/resolutions#20150624-2).
Whereas, any changes to the ICANN Bylaws may be adopted only upon action by a two-thirds (2/3) vote of all members of the Board.
Resolved (2015.07.28.03), the President and CEO, or his designee(s), is directed to post for public comment for a period of at least 40 days revised Bylaws reflecting the addition of a GNSO Guidance Process and a GNSO Expedited Policy Development Process. After taking public comments into account, the Board will consider the proposed changes for adoption.
The action being approved today is to direct the ICANN President and CEO, or his designee, to initiate a public comment period on potential changes to the ICANN Bylaws to implement certain recommendations resulting from the GNSO's non-PDP Policy and Implementation Working Group. The Board's action is a first step to consider the unanimous approval by the GNSO Council of the recommendations of the Policy & Implementation Working Group.
There is no anticipated fiscal impact from this decision, which would initiate the opening of public comments, but the fiscal impacts of implementing the GNSO Council's recommendations from the non-PDP Policy and Implementation Working Group will be further analyzed if adopted. Approval of the resolution will not impact the security, stability and resiliency of the domain name. The posting of the proposed Bylaws for public comment is an Organizational Administrative Action not requiring public comment.