Security and Stability Advisory Committee (SSAC)
هذا المحتوى متوفر فقط باللغة (أو اللغات)
- 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 085 | SAC 085 | Planning | Comment | 19 Oct 2016 | ||
SAC 084 | SAC 084 | Internationalized Domain Name (IDN) | Comment | 31 Aug 2016 | ||
SAC 083 | SAC 083 | Domain Name System (DNS) Security | Comment | 11 Jul 2016 | ||
SAC 082 | SAC 082 | Planning | Comment | 3 Jun 2016 | ||
SAC 081 | SAC 081 | WHOIS | Comment | 25 May 2016 | ||
SAC 080 | SAC 080 | Planning | Letter | 2 Mar 2016 | ||
SAC 079 | SAC 079 | Addressing | Advisory | 25 Feb 2016 | ||
SAC 078 | SAC 078 | Domain Name System (DNS) Security | Comment | 16 Feb 2016 | ||
SAC 077 | SAC 077 | Domain Name System (DNS) Security | Comment | 22 Jan 2016 | ||
SAC 076 | SAC 076 | Planning | Comment | 21 Dec 2015 | ||
SAC 075 | SAC 075 | Domain Name System (DNS) Abuse | Comment | 3 Dec 2015 | ||
SAC 074 | SAC 074 | Registration Services | Advisory | 3 Nov 2015 | ||
SAC 073 | SAC 073 | Domain Name System (DNS) Security | Comment | 5 Oct 2015 | ||
SAC 072 | SAC 072 | Planning | Comment | 24 Jun 2015 | ||
SAC 071 | SAC 071 | Planning | Report | 8 Jun 2015 | ||
Available in: | SAC 070 | SAC 070 | Domain Name System (DNS) Security | Advisory | 28 May 2015 | |
SAC 069 | SAC 069 | Root System | Advisory | 10 Dec 2014 | ||
SAC 068 | SAC 068 | Root System | Report | 10 Oct 2014 | ||
SAC 067 | SAC 067 | Root System | Report | 15 Aug 2014 | ||
SAC 066 | SAC 066 | Domain Name System (DNS) Security | Comment | 6 Jun 2014 |