Security and Stability Advisory Committee (SSAC)
Ce contenu est uniquement disponible en
- English
SSAC Publications
The SSAC produces reports, correspondence, and comments on a range of topics. The SSAC undertakes ongoing risk analysis to identify a prioritized list of topics for SSAC work. However, the ICANN Board, Advisory Committees (ACs), Supporting Organizations (SOs) or other bodies within ICANN may request that the SSAC review, comment, or give feedback on a specific topic or issue at any time.
Reports are focused on providing information, recommendations, and advice on technical security, stability, and resiliency (SSR) issues to the ICANN Board, the ICANN community, and the broader internet community. They may investigate emerging or long-term issues or could be published in response to a security event or incident, where timely notification to the community is a priority concern. They may be informational without any findings or recommendations or they could contain specific recommendations for the ICANN Board or community, and if appropriate, organized according to the groups to which they are most applicable.
Correspondence comprises letters, comments, and other documents on administrative, community, and other non-SSR issues and are normally signed by the SSAC Chair. They may take the form of a letter or a response submitted to a public comment forum. They may present recommendations regarding the issue.
Comments are prepared in response to explicit questions posed to or requests made to the SSAC, or as a response to ICANN’s public comment forum. Comments may be brief or long, depending on the issue and the extent to which the SSAC studies it.
A goal of the SSAC is to ensure that its work results in specific actions whenever possible. In order to measure progress towards this goal, the SSAC tracks any effects of each recommendation. For documents that contain recommendations for the ICANN Board, the Board Action Request Register (ARR) captures the information required to understand the status of advice and tracks it from when it is given through implementation.
SAC 048 | SAC 048 | Domain Name System (DNS) Abuse | Comment | 12 May 2011 | ||
SAC 047 | SAC 047 | Registration Services | Comment | 15 Apr 2011 | ||
SAC 046 | SAC 046 | Root System | Report | 6 Dec 2010 | ||
SAC 045 | SAC 045 | Root System | Report | 15 Nov 2010 | ||
Additional Documents: | SAC 044 | SAC 044 | Registration Services | Report | 5 Nov 2010 | |
SAC 043 | SAC 043 | Addressing | Comment | 5 Oct 2010 | ||
SAC 042 | SAC 042 | Root System | Comment | 17 Dec 2009 | ||
SAC 039 | SAC 039 | Planning | Report | 15 Oct 2009 | ||
Available in: Additional Documents: | SAC 040 | SAC 040 | Registration Services | Report | 19 Aug 2009 | |
SAC 041 | SAC 041 | Domain Name System (DNS) Abuse | Advisory | 10 Jun 2009 | ||
Available in: Additional Documents: | SAC 037 | SAC 037 | Internationalized Domain Name (IDN) | Report | 20 Apr 2009 | |
Available in: Additional Documents: | SAC 038 | SAC 038 | Registration Services | Report | 25 Feb 2009 | |
Additional Documents: | SAC 036a | SAC 036a | Planning | Letter | 30 Jan 2009 | |
Additional Documents: | SAC 036b | SAC 036b | Planning | Comment | 9 Dec 2008 | |
SAC 035 | SAC 035 | Domain Name System (DNS) Security | Report | 16 Sep 2008 | ||
SAC 030 | SAC 030 | Domain Name System (DNS) Security | Report | 15 Jul 2008 | ||
Available in: Additional Documents: | SAC 032 | SAC 032 | Domain Name System (DNS) Abuse | Advisory | 20 Jun 2008 | |
Additional Documents: | SAC 033 | SAC 033 | WHOIS | Report | 20 Jun 2008 | |
SAC 034 | SAC 034 | Planning | Comment | 17 Jun 2008 | ||
Available in: Additional Documents: | SAC 028 | SAC 028 | Registration Services | Advisory | 26 May 2008 |