Historical Resolution Tracking Feature » 2011-03-18 - Creation of DNS Security Framework Working Group
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 - Creation of DNS Security Framework Working Group
Directs BGC to recommend a working group on DNS Risk Management Framework.
- Recommend working group to Board to oversee development of risk management framework.
- Responsible entity: BGC
- Due date: June 2011
- Completion date: 28 October 2011
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, 210], 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 18 March 2011, the Board approved the amendment to the Bylaws reflecting the removal of task area one from the SSAC Charter, which read "To develop a security framework for Internet naming and address allocation services that defines the key focus areas, and identifies where the responsibilities for each area lie. The committee shall focus on the operational considerations of critical naming infrastructure."
Whereas, the ICANN Board desires that the work foreseen within task area should be performed by ICANN.
Resolved (2011.03.18.07), the Board directs the Board Governance Committee to recommend to the Board a working group to oversee the development of a risk management framework and system for the DNS as it pertains to ICANN's role as defined in the ICANN Bylaws. The Board recommends that the BGC consider in its recommendation the inclusion of a member of the working group to come from the SSAC. The Board requests that the BGC submit its recommendation consideration at the Board meeting in Singapore in June 2011.
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.
- BGC meeting minutes discussing formation of DNS Risk Management Working Group available at: http://www.icann.org/en/minutes/minutes-bgc-18jun11-en.htm .
- SIC meeting minutes recommending that the Bylaws should be amended to achieve the recommendation of the Working Group on improvements to the SSAC, are available at: http://www.icann.org/en/minutes/minutes-bsic-14oct10-en.htm.
- Public comments on the proposed amendments are available at: http://www.icann.org/en/public-comment/public-comment-201012-en.htm#bylaws-xi2.
- ICANN Bylaws updated with these amendments to Art. XI, Sec. 2, available at: http://www.icann.org/en/general/bylaws.htm#XI .
- Information on the June 2011 Board meeting in Singapore is available at: http://singapore41.icann.org/.
- The resolution does not address funding for the items identified therein.