You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Comment Close
Date
Statement
Name 

Status

Assignee(s) and
RALO(s)

Call for
Comments
Call for
Comments
Close 
Vote
Announcement 
Vote Open
Vote 
Reminder
Vote Close
Date of Submission
Staff Contact and Email
Statement Number
20.04.2013ICANN's FY 14 Security, Stability and Resiliency FrameworkAdopted
14Y, 0N, 0A 
Julie Hammer (APRALO)26.03.201309.04.2013n/a

11.04.2013
(ALAC Meeting in Beijing) 

n/a11.04.201311.04.2013Patrick Jones
patrick.jones@icann.org
AL/ALAC/ST/0413/2
Comment / Reply Periods (*)
Comment Open Date: 
6 March 2013
Comment Close Date: 
20 April 2013 - 23:59 UTC
Reply Open Date: 
21 April 2013
Reply Close Date: 
20 May 2013 - 23:59 UTC
Important Information Links
Brief Overview
Originating Organization: 
ICANN Security
Categories/Tags: 
  • Security/Stability
Purpose (Brief): 
ICANN is publishing its FY 14 Security, Stability and Resiliency Framework for community review. The Framework is an annual document, referenced in the Affirmation of Commitments. The Framework describesICANN's role in the ecosystem and priorities for the next fiscal year in promoting a healthy, stable and resilient unique identifier system.
Current Status: 
This Framework is being posted now for discussion at the ICANN Beijing meeting and as part of ICANN's annual process for a security, stability and resiliency framework.
Next Steps: 
Comments will be incorporated in a final Framework and will influence the FY14 budget and operating plan process.
Staff Contact: 
Patrick Jones
Detailed Information
Section I: Description, Explanation, and Purpose: 

ICANN is publishing its FY 14 Security, Stability and Resiliency Framework for community review. The Framework is an annual document, referenced in the Affirmation of Commitments. The Framework describesICANN's role in the ecosystem and priorities for the next fiscal year in promoting a healthy, stable and resilient unique identifier system.

New for FY 14 is the adoption of the SSR Review Team Final Report and recommendations by the ICANNBoard of Directors in October 2012, and reactions to developments in the Internet ecosystem since the previous Framework was published in June 2012. Projected activities will support a healthy ecosystem, to provide a foundation for a more stable, reliable and resilient Internet for the global community.

The FY 14 Framework retains the two-part structure from past versions, but is being published in a Word format for ease of translation in advance of the ICANN Beijing meeting (translations will be posted as soon as available).

Part A describes the foundation for ICANN's role, its role and remit in security, stability and resiliency of the Internet's unique identifiers, definitions for the Framework and an overview of the Internet ecosystem and the challenges in the environment.

Part B describes the Affirmation of Commitments review and priorities for ICANN in security, stability and resiliency for the fiscal year commencing in July 2013. This section also includes a new and evolving visualization of ICANN Security graphic and an overview of international SSR developments in the ecosystem during FY 13.

Appendix A provides an update on implementation of the 28 SSR Review Team Recommendations, while Appendix B provides a status review of FY 13's activities.

Comments on the FY 14 Security, Stability and Resiliency Framework are encouraged and may be sent tocomments-ssr-fy14-06mar13@icann.org and viewed at http://forum.icann.org/lists/comments-ssr-fy14-06mar13/through 20 April 2013 (with a reply comment period open from 20 April to 20 May 2013, 23:59 UTC).

Further community consultations will occur at the upcoming ICANN meeting in Beijing and between March and May 2013.

Section II: Background: 

PDF of FY 14 SSR Framework [PDF, 5.93 MB] 
(Translations of the Framework will be posted as soon as possible)

Section III: Document and Resource Links: 

Learn more about the SSR Framework

Previous versions of ICANN's Security, Stability and Resiliency Framework may be found on the ICANNSecurity team page.

Section IV: Additional Information: 
None

(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.

FINAL VERSION TO BE SUBMITTED IF RATIFIED

Please click here to download a copy of the PDF below.

Error rendering macro 'viewpdf'

com.atlassian.confluence.macro.MacroExecutionException: com.atlassian.confluence.macro.MacroExecutionException: The viewfile macro is unable to locate the attachment "ALAC Statement on the ICANN's FY 14 Security, Stability and Resiliency.pdf" on this page

 

FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

The ALAC welcomes the publication of the FY14 SSR Framework and commends the ICANN Security Team for the quality of the document.  The change in format from the PowerPoint presentation of recent years to a formal written document does not detract from the clarity of the information contained.

The focus of Part B of this document provides excellent detail on the activities of the ICANN Security Team.  The ALAC strongly supports the many and varied activities of the ICANN Security Team focused on technical engagement, outreach, training and capability building both within and beyond the ICANN Community.  It is important that funding for these activities continues to be made available in the ICANN Budget.

Noting that the intention of Part B is to present the SSR activities being undertaken and planned across ICANN the Community, the ALAC suggests that some additional detail of activities being undertaken outside the Security Team would be helpful.  While a number of these are mentioned in the document, this tends in some cases to be in the context of the Security Team providing (very worthwhile) support to the activities of other groups, rather than the work of the other groups themselves.  The report would benefit from broadening its perspective from ICANN the Organization to ICANN the Community.  This can probably be achieved by presenting the existing information in a slightly different way, with slightly more detail.

Related to the above comment, the ALAC suggests that an additional dot point might be added to the following section on p16 as highlighted in bold underline below:

"Security at ICANN can be viewed as:

  • A Core Value for ICANN, in the Affirmation of Commitments
  • One of the Four Focus Areas of the Strategic Plan
  • An overall thematic area cutting across the organization 
  • An Advisory Committee within the ICANN Community 
  • A department within the ICANN Organization
  • An essentially element in projects and activities"

Tracking of implementation progress of the SSR Review Team Recommendations is particularly useful in Appendix A.

FIRST DRAFT SUBMITTED

The ALAC welcomes the publication of the FY14 SSR Framework and commends the ICANN Security Team for the quality of the document.  The change in format from the PowerPoint presentation of recent years to a formal written document does not detract from the clarity of the information contained.

The focus of Part B of this document provides excellent detail on the activities of the ICANN Security Team.  The ALAC strongly supports the many and varied activities of the ICANN Security Team focused on technical engagement, outreach, training and capability building both within and beyond the ICANN Community.  It is important that funding for these activities continues to be made available in the ICANN Budget.

Noting that the intention of Part B is to present the SSR activities being undertaken and planned across ICANN the Community, the ALAC suggests that some additional detail of activities being undertaken outside the Security Team would be helpful.  While a number of these are mentioned in the document, this tends in some cases to be in the context of the Security Team providing (very worthwhile) support to the activities of other groups, rather than the work of the other groups themselves.  The report would benefit from broadening its perspective from ICANN the Organization to ICANN the Community.  This can probably be achieved by presenting the existing information in a slightly different way, with slightly more detail.

Related to the above comment, the ALAC suggests that an additional dot point might be added to the following section on p16 as highlighted in bold underline below:

"Security at ICANN can be viewed as:

  • A Core Value for ICANN, in the Affirmation of Commitments
  • One of the Four Focus Areas of the Strategic Plan
  • An overall thematic area cutting across the organization 
  • An Advisory Committee within the ICANN Community 
  • A department within the ICANN Organization
  • An essentially element in projects and activities"

Tracking of implementation progress of the SSR Review Team Recommendations is particularly useful in Appendix A.

 

  • No labels