Historical Resolution Tracking Feature » Proposed Process for GNSO Stakeholder Group and Constituency Charter Amendments
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.
Proposed Process for GNSO Stakeholder Group and Constituency Charter Amendments
Board approves the charter amendment process formulated and recommended by the Structural Improvements Committee and directs ICANN Staff to notify the leadership of the various GNSO Stakeholder Groups and Constituencies of the process and post a copy of the approved process on the GNSO web site within seven calendar days.
Whereas, The ICANN Bylaws (Article X, Section 5.3) state, "Each [GNSO] Stakeholder Group … and each of its associated Constituencies shall maintain recognition with the ICANN Board.”
Whereas, it is important that GNSO Stakeholder Groups and Constituencies have the flexibility to update, modify and evolve their organizational charters to reflect community changes while balancing the need for validation by the Board.
Whereas, there is currently no procedure for a GNSO Stakeholder Group or Constituency to obtain approval by the ICANN Board of Directors for an amendment of its charter.
Whereas, the Structural Improvements Committee of the ICANN Board has formulated and recommended a process by which GNSO Stakeholder Groups and Constituencies can amend their charters with the Board maintaining its appropriate validation responsibilities for recognition of those GNSO groups.
Whereas, the community has had the opportunity to review and comment on the proposed process and changes have been made to the proposed process to address community suggestions.
Resolved (2013.09.28.12), the Board approves the process formulated and recommended by the Structural Improvements Committee and directs ICANN Staff to notify the leadership of the various GNSO Stakeholder Groups and Constituencies of the process and post a copy of the approved process on the GNSO web site within seven calendar days.
In July 2009, as part of the comprehensive GNSO Improvements program, the ICANN Board approved the formal Charters of four new GNSO Stakeholder Groups (see ICANN Board Resolution 2009.30.07.09).
The ICANN Bylaws (Article X, Section 5.3) state, "Each Stakeholder Group … and each of its associated Constituencies shall maintain recognition with the ICANN Board.” Because the original GNSO organizational charters approved in 2009 were subject to exhaustive and rigorous negotiations and discussions between the community and Board members, it is appropriate that the Board have an opportunity to review and approve subsequent charter amendments. Further, the Board believes that review of GNSO charter amendments maintained by GNSO Stakeholder Groups and the Constituencies that populate those groups is an important obligation in maintaining recognition of formally approved GNSO Structures consistent with ICANN Bylaw principles.
The Board’s Structural Improvements Committee (SIC) developed this process and the proposal was shared with the community for review and comment. The final version approved by the Board reflects adjustments to the original SIC proposal after consideration of helpful community feedback regarding the timing of staff notifications and the timeline and process for Board review of community charter amendments.
This action will have no immediate or substantial impact on ICANN’s resources. At certain times, it will demand additional community work, staff support work and Board review time, but those efforts should be of limited duration and they will improve the transparency and ultimate efficiency of ICANN’s structural and management processes.
This action is not expected to have any impact on the security, stability or resiliency of the DNS.
DOCUMENT/BACKGROUND LINKS:
Link to Community Public Comment Forum.
This is an Organizational Administrative Function for which comment was received.