Historical Resolution Tracking Feature » 2011-03-18 - Approval of Revision of Bylaws re Implementation of SSAC Review Working Group Report

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.

2011-03-18 - Approval of Revision of Bylaws re Implementation of SSAC Review Working Group Report


Resolution of the ICANN Board
Topic: 
SSAC
Summary: 

Board approves Bylaws amendments regarding SSAC and directs BGC to recommend a working group on DNS Risk Management Framework.

Category: 
ICANN Structures
Meeting Date: 
Fri, 18 Mar 2011
Resolution Number: 
2011.03.18.06
Status: 
Complete
Implementation Actions: 
  • Not applicable
Resolution Text: 

Whereas, Article XI, Section 2, Subsection 2 of the Bylaws governs the Security and Stability Advisory Committee (SSAC).

Whereas, in its final report published 29 January 2010 <http://www.icann.org/en/reviews/ssac/ssac-review-wg-final-report-29jan10-en.pdf> [PDF, 282 KB], the Security and Stability Advisory Committee (SSAC) recommended that task area one of the SSAC Charter (Section 2(2)(a)(1) <http://www.icann.org/en/general/bylaws.htm#XI>) should be removed because it is out of scope of the activities of the SSAC.

Whereas, on 12 March 2010, the Board received the SSAC final report and directed the Structural Improvements Committee (SIC) to identify actions necessary to address the recommendations within the report, at <http://www.icann.org/en/minutes/resolutions-12mar10-en.htm#1.6>.

Whereas, the SIC, at its 14 October 2010 meeting, recommended that the Bylaws should be amended to achieve the recommendation of the Working Group on improvements to the SSAC by removing task area one and renumbering the other task areas.

Whereas, the SIC also considered the SSAC reviewer's recommendation that the Board should have the power to remove SSAC members, and recommended that the Bylaws should be amended to reflect this companion removal power. Any removal should be formed in consultation with the SSAC.

Whereas, in resolution 2010.28.10.11 the Board directed staff to post the proposed Bylaws amendments for a period of no less than 30 days.

Whereas, the proposed amendments were posted for public comment for a period of 30 days beginning 03 November 2010 and ending 02 December 2010.

Whereas, staff provided the Board with a summary and analysis of the public comments received and recommended that the Board approve the Bylaws amendments as posted at <http://www.icann.org/en/general/proposed-bylaw-changes-xi-2-03nov10-en.pdf> [PDF, 60 KB].

Resolved (2011.03.18.06), the Board approves the Bylaws revisions as posted for public comment in furtherance of the recommendations arising out of the SSAC review Working Group.

Rationale for Resolution: 

The proposed actions are in line with the adopted implementation plan following the SSAC Review and serve to fulfil the commitments agreed by the Board to that end. The Bylaws changes have been posted for public comments. No comments were received indicating any foreseen negative effects and there is no reason to delay the adoption of the amendment. The task to develop a security framework is intended to fulfil the Board's expressed desire that work within task area one of the SSAC Charter should be performed by ICANN. There is no reason to delay the scoping task as it there are no budgetary consequences to performing the scoping work. The outcomes of that scoping work should explicitly address resource estimates, to be considered and decided by the Board once the scoping task has been accomplished and a proposal put forward. The approval of initiating the scoping work will assist ICANN in continuing to work to maintain security, stability and resiliency of the DNS.

Additional Information: