Recommendations to the Board

The Board receives recommendations from a variety of sources from the ICANN community, including advice from the Advisory Committees as set forth in Article 12 of ICANN's Bylaws.

This page provides information on the status of advice to the Board from the Advisory Committees identified below:

  • At-Large Advisory Committee (ALAC)
  • Root Server System Advisory Committee (RSSAC)
  • Security and Stability Advisory Committee (SSAC)

Actions and updates on advice from the Governmental Advisory Committee (GAC) are not currently included on this page. Please refer to GAC Advice Scorecards adopted from time to time by the Board on the GAC website. Most recently, the Board adopted the scorecard for the ICANN 64 Kobe Communiqué.

Latest Advice to the ICANN Board

As of 31 July 2019

Advisory Committee Advice Document
At-Large Advisory Committee (ALAC)
Root Server System Advisory Committee (RSSAC)
Security and Stability Advisory Committee (SSAC)

Advice Status

As of 31 July 2019

The Board Advice Status Report [PDF | XLSX] provides status and details of related resolutions as well as the resulting implementation actions for information on advice items issued by the ALAC, RSSAC, and SSAC since 2010. Information on individual items by Advisory Committee can be found in the below sections "Open Advice Items" and "Advice Items Closed in the Last 12 Months."

Board Advice Register Phases and Descriptions

Board Advice Register Phases and Descriptions

Advice Items by Advisory Committee

Phase ALAC RSSAC SSAC Total Items by Phase
Phase 1 | Receive & Acknowledge - - - -
Phase 2 | Understand - - 1 1
Phase 3 | Evaluate & Consider - 11 - 11
Phase 3 | Deferred - - - -
Phase 4 | Implement 2 1 21 24
Phase 4 | Deferred - - 4 4
Phase 5 | Close 2 1 17 20
Total Open Items by
Advisory Committee
4 13 43 60
Total Items Closed in
Past 12 Months
2 12 15 29

Open Advice Items

Advice Item Phase Action(s) Taken

Enabling Inclusive, Informed and Meaningful Participation at ICANN: A Joint Statement by ALAC and GAC (R1)

(2 Nov 2017)

Phase 4 | Implement

The Information Transparency Initiative (ITI) team previewed new Announcements and Blog pages on feedback.icann.org in October 2018. Work on the authoring and content model in the document management system has begun and several content types have been completed. Since the launch of ITI in January 2018, the team has published eight blogs on icann.org and conducted several public sessions to provide the community with updates and input into the progress of this project.

Enabling Inclusive, Informed and Meaningful Participation at ICANN: A Joint Statement by ALAC and GAC (R2)

(2 Nov 2017)

Phase 4 | Implement

On 9 February 2018, the ICANN Board sent a letter to Alan Greenberg, chair of the ALAC, regarding this joint ALAC-GAC advice. Please see the letter here. The letter also refers to the GAC scorecard, which can be found here.

The 2nd At-Large Summit (ATLAS II) Final Declaration -- At-Large Community Engagement in ICANN (R-37)

(26 Jun 2014)

Phase 5 | Close Request

Staff, under the direction of At-Large leadership, has already begun to rework the website and Wiki to ensure that our "Policy Advice" pages are accurate and understandable. This will continue as volunteer and staff resources allow. We will also ensure that as documents are published, the classification of the document is clear. The goal is to address two issues:

  • Confusion about the type of document (ie "Advice" vs "Comment")
  • The "End user" justification for intervention.

Accordingly, staff together with At-Large leadership will categorize the existing documents (as advice, public comment, correspondence, etc.) in a more granular fashion and provided enhanced tools with which to filter search results based on these categories. Furthermore, staff will create a new field in the database for "End User Issue" and At-Large leadership will populate this field both in current documents and those generated going forward. The following items have been created to satisfy these goals:

  • An Executive Summaries: ALAC Policy Comments & Advice resource page has been created to address "type" of document (#1).
  • The At-Large Consolidated Policy Working Group (CPWG) meets weekly to discuss "end user" justification for intervention (#2).

With these simple modifications, it should be easier for a Wiki visitor to peruse the work of the At-large and to quickly understand the rationale for creating individual documents.

The 2nd At-Large Summit (ATLAS II) Final Declaration -- Future of Multi-Stakeholder Models (R-7)

(26 Jun 2014)

Phase 5 | Close Request

The Board in its 9 September 2014 resolution acknowledged the Final ATLAS II Declaration: https://www.icann.org/resources/board-material/resolutions-2014-09-09-en#3.e

This recommendation was discussed by the Board Organization Effectiveness Committee (OEC), which subsequently added the item to the OEC workplan: "Holistic Assessment of ICANN structures." The OEC agreed that the work underway on the current cycle of 11 reviews and the recommendations of WS2-Accountability should progress further, before the topic of "holistic assessment of ICANN structures" is to be addressed. Updates on OEC's progress on this work item are reported on the Semi-Annual Committee Report.

For further information on the OEC's consideration of this topic, see the latest OEC meeting minutes.

Advice Item Phase Action(s) Taken

RSSAC028: Technical Analysis of the Naming Scheme Used For Individual Root Servers R-1

(3 Aug 2017)

Phase 3 | Evaluate & Consider The ICANN org understands RSSAC028 Recommendation 1 to mean that no changes should be made to the current naming scheme used in the root server system until more studies have been conducted. ICANN received confirmation of understanding from the RSSAC on 1/17/18.

RSSAC028: Technical Analysis of the Naming Scheme Used For Individual Root Servers R-2

(3 Aug 2017)

Phase 3 | Evaluate & Consider The ICANN org understands RSSAC028 Recommendation 2 to that studies on current behaviors of DNS software and DNS resolvers should be conducted to understand different elements of root server responses to queries, both individually and in combination; for initial priming and standard responses; and for how well specific implementations, such as the DO bit are interpreted by root servers and the DNS software. ICANN received confirmation of understanding from the RSSAC on 1/17/18.

RSSAC028: Technical Analysis of the Naming Scheme Used For Individual Root Servers R-3

(3 Aug 2017)

Phase 3 | Evaluate & Consider The ICANN org understands RSSAC028 Recommendation 3 to mean that a study should be conducted to understand how the current infrastructure is susceptible to various cache poisoning attack scenarios, specifically node re-delegation attacks, and that proof-of-concept code for testing these scenarios should be made available to others in the DNS community for further studies. ICANN received confirmation of understanding from the RSSAC on 1/17/18.

RSSAC028: Technical Analysis of the Naming Scheme Used For Individual Root Servers R-5

(3 Aug 2017)

Phase 3 | Evaluate & Consider

The ICANN org understands that the RSSAC has also provided an additional, speculative recommendation, which states that if node re-delegation attacks pose a serious risk that needs to be mitigated, the following should also be considered:

  • The root server addresses should be signed with DNSSEC to enable a resolver to authenticate resource records within the priming response.
  • Because the root server IP address information and the root zone are closely correlated, both sets of information should continue to be hosted on the same servers.
  • Among the various options considered in this document, moving the root server names to the root zone (5.3), or adding a new TLD under the root zone (5.4) are both viable options that would result in signing the root server addresses.

Additional studies are needed to determine which of these options, if any, would be more favorable than the other in practice. ICANN received confirmation of understanding from the RSSAC on 1/17/18.

RSSAC038: RSSAC Advisory on a Proposed Governance Model for the DNS Root Server System R-2

(14 Jun 2018)

Phase 3 | Evaluate & Consider The ICANN org understands RSSAC038 Recommendation 2 is for the ICANN Board to estimate costs of the Root Server System and for developing the Model for implementation based on RSSAC037. The ICANN Board should refer to RSSAC037 section 5.5.3 in estimating these costs. Initial efforts should focus on developing a timeline for costing these. The RSSAC estimates the suggested costing effort should not take more than six months. ICANN sent this understanding to the RSSAC for review on 24 July 2018. ICANN received confirmation of understanding on 17 August 2018.

RSSAC038: RSSAC Advisory on a Proposed Governance Model for the DNS Root Server System R-3

(14 Jun 2018)

Phase 3 | Evaluate & Consider The ICANN org understands RSSAC038 Recommendation 3 is for the ICANN Board and community to implement the final version of the Model for implementation based on RSSAC037 based upon the principles of accountability, transparency, sustainability, and service integrity. ICANN sent this understanding to the RSSAC for review on 24 July 2018. ICANN received confirmation of understanding on 17 August 2018.

RSSAC041: RSSAC Advisory on Organizational Reviews (R-1)

(5 Oct 2018)

Phase 3 | Evaluate & Consider The ICANN org understands RSSAC041 Recommendation 5 to mean that at the conclusion of every organizational review, the ICANN org should report on how the process transpired. The ICANN org should demonstrate how the process will be modified if there are any lessons learned from the organizational review. The RSSAC confirmed this understanding on 13 June 2019.

RSSAC041: RSSAC Advisory on Organizational Reviews (R-2)

(5 Oct 2018)

Phase 3 | Evaluate & Consider The ICANN org understands RSSAC041 Recommendation 5 to mean that at the conclusion of every organizational review, the ICANN org should report on how the process transpired. The ICANN org should demonstrate how the process will be modified if there are any lessons learned from the organizational review. The RSSAC confirmed this understanding on 13 June 2019.

RSSAC041: RSSAC Advisory on Organizational Reviews (R-3)

(5 Oct 2018)

Phase 3 | Evaluate & Consider The ICANN org understands RSSAC041 Recommendation 5 to mean that at the conclusion of every organizational review, the ICANN org should report on how the process transpired. The ICANN org should demonstrate how the process will be modified if there are any lessons learned from the organizational review. The RSSAC confirmed this understanding on 13 June 2019.

RSSAC041: RSSAC Advisory on Organizational Reviews (R-4)

(5 Oct 2018)

Phase 3 | Evaluate & Consider The ICANN org understands RSSAC041 Recommendation 5 to mean that at the conclusion of every organizational review, the ICANN org should report on how the process transpired. The ICANN org should demonstrate how the process will be modified if there are any lessons learned from the organizational review. The RSSAC confirmed this understanding on 13 June 2019.

RSSAC041: RSSAC Advisory on Organizational Reviews (R-5)

(5 Oct 2018)

Phase 3 | Evaluate & Consider The ICANN org understands RSSAC041 Recommendation 5 to mean that at the conclusion of every organizational review, the ICANN org should report on how the process transpired. The ICANN org should demonstrate how the process will be modified if there are any lessons learned from the organizational review. The RSSAC confirmed this understanding on 13 June 2019.

RSSAC038: RSSAC Advisory on a Proposed Governance Model for the DNS Root Server System R-1

(14 Jun 2018)

Phase 4 | Implement The ICANN org understands RSSAC038 Recommendation 1 is for the ICANN Board to initiate a process to produce a final version of the Model for implementation based on RSSAC037. ICANN sent this understanding to the RSSAC for review on 24 July 2018. ICANN received confirmation of understanding on 17 August 2018.

Advice Item Phase Action(s) Taken

SAC102: SSAC Comment on the Updated Plan for Continuing the Root KSK Rollover
(8/20/18)

Phase 2 | Understand Request

ICANN received SAC102 on 21 August 2018. The ICANN org sent an initial statement of understanding to the SSAC on 7 September 2018 that stated the ICANN org understood there is no action for the ICANN Board in SAC102. On 16 July 2019, the SSAC provided feedback to ICANN org that SAC102 does contain actionable advice for the ICANN Board. The ICANN org is currently reviewing SAC102. The ICANN org understands SAC102 is the SSAC's response to ICANN Board Resolution 2018.05.13.09. ICANN org understands the SSAC has not identified any reason within the SSAC's scope why the rollover should not proceed as currently planned. The SSAC suggests that ICANN establish a framework for scheduling further rolls of the root KSK based on analysis of the outcomes of this initial roll of the KSK. The ICANN org also understands five members of SSAC provided a dissent in SAC102 in which they believe that the risks of rolling in accordance with the current schedule are larger than the risks of postponing and focusing heavily on additional research and outreach, and in particular leveraging newly developed techniques that provide better signal and fidelity into potentially impacted parties. There is no action for the ICANN Board. This understanding was sent to the SSAC on 7 September 2018.

SAC060: Active Variant TLDs (2 of 14)
(7/23/13)

Phase 4 | Deferred

RZ-LGR-3 integrating 16 scripts is being released in July 2019. The inclusion of RZ-LGR to validate TLD labels and their variant labels has also been recommended as part of managing IDN variant TLDs. GNSO and ccNSO are currently considering this recommendation. The Study Group on Technical Utilization of Root Zone Label Generation Rules took up this item to discuss. Recommendation four (4) of their report suggests a way forward. This work has been released for public comment and will be finalized afterwards for further consideration of the ICANN Board. See report at https://www.icann.org/en/system/files/files/recommendations-rz-lgr-14may19-en.pdf and public comment at https://www.icann.org/public-comments/technical-rz-lgr-2019-05-15-en. Further implementation of this item is deferred as of 30 June 2019 pending external activity. ICANN org will take up further work once the GNSO and ccNSO have considered these items as part of their policy development work.

SAC060: Active Variant TLDs (8 of 14)
(7/23/13)

Phase 4 | Deferred

ICANN org recently developed the Recommendations for Managing IDN Variant TLDs, published at https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-07-26-en. These have been adopted by ICANN Board at their meeting at ICANN64, where the Board asked the GNSO and ccNSO to consider these in their policy and procedures. Further implementation of this item is deferred as of 30 June 2019 pending external activity. ICANN org will take up further work once the GNSO and ccNSO have considered these items as part of their policy development work.

SAC060: Active Variant TLDs (9 of 14)
(7/23/13)

Phase 4 | Deferred

A detailed analysis has been publised as part of recommendations for managing IDN variant TLDs, which has been approved by ICANN Board at ICANN64. The analysis has been forwarded to the GNSO and ccNSO for their consideration for relevant policy and procedure development. The analysis is avaialble at https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-07-26-en. Specifically see section 3 of the report at https://www.icann.org/en/system/files/files/idn-variant-tld-recommendations-analysis-25jan19-en.pdf.

SAC095: SSAC Advisory on the Use of Emoji in Domain Names R-1
(5/25/17)

Phase 4 | Deferred

On 2 Nov 2017, the ICANN Board directed the ICANN org to engage with gTLD and ccTLD communities on the findings and recommendations in SAC095 in addition to requesting that the ccNSO and GNSO integrate conformance with IDNA2008 and its successor into their relevant policies so as to safeguard security, stability, resiliency and interoperability of domain names (see: https://www.icann.org/resources/board-material/resolutions-2017-11-02-en#1.e). IDN ccTLD Fast Track process already limits labels at top level to IDNA2008 which does not allow for emojis (see https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-28mar19-en.pdf). Further, GNSO is considering limiting the TLDs to IDNA2008 (through the use of Root Zone Label Generation Rules) for the subsequent procedures for the gTLDs. The policy work is still under development by the community. Limiting TLDs to Root Zone LGRs is also recommended in the recent recommendations for IDN variant TLDs published at https://www.icann.org/resources/pages/idn-variant-tld-implementation-2018-07-26-en and adopted by the ICANN Board at ICANN64 for further consideration by GNSO and ccNSO. Finally the recent work on technical use of Root Zone LGR by the study group also recommends the same: see recommendations 1 and 2 in the report at https://www.icann.org/en/system/files/files/recommendations-rz-lgr-14may19-en.pdf. Further implementation of this item is deferred as of 30 June 2019 pending external activity. ICANN org will take up further work once the GNSO and ccNSO have considered these items as part of their policy development work.

SAC045: Invalid Top Level Domain Queries at the Root Level of the Domain Name System (R-6)
(11/15/10)

Phase 4 | Implement

This advice item requires further policy determination. ICANN will refer this advice to the GNSO for consideration.

SAC046: Report of the Security and Stability Advisory Committee on Root Scaling (R-4)
(12/6/10)

Phase 4 | Implement

The plan will be updated to include actual measurement, monitoring, and datasharing capability of root zone performance, in cooperation with RSSAC and other root zone management participants to define the specific measurements, monitoring, and data sharing framework.

SAC051: SSAC Report on WHOIS Terminology and Structure (R-2)
(6/14/11)

Phase 4 | Implement

The Board accepted this advice in October 2011 and requested that a roadmap to implementation of SAC051 be developed (https://www.icann.org/resources/board-material/minutes-2011-10-28-en#5). A roadmap to implementing SAC051 was published for public comment in February 2012: https://www.icann.org/news/announcement-6-2012-06-04-en. Implementation of this specific advice item is ongoing. ICANN is determining how to implement the new protocol in the gTLD space. The Registries Stakeholder Group (RySG) has submitted proposals/correspondence to ICANN regarding the registration data access protocol (RDAP) implementation: Initial Proposal, May 2017: https://www.icann.org/en/system/files/correspondence/diaz-to-atallah-03may17-en.pdf ICANN's response, June 2017: https://www.icann.org/en/system/files/correspondence/atallah-to-diaz-16jun17-en.pdf Updated proposal, June 2017: https://www.icann.org/en/system/files/correspondence/diaz-to-atallah-22jun17-en.pdf Adoption of Temporary Specification, May 2018: https://www.icann.org/resources/pages/gtld-registration-data-specs-en

SAC059: R-1 Interdisciplinary studies of security and stability implications from expanding the root zone
(4/18/13)

Phase 4 | Implement

Issues related to the expansion of the root zone have been/are being considered through other means, including Name Collision and DNSSEC roll over. Other reports on the expansion of the root zone include: – Scaling the Root Report on the Impact on the DNS Root System of Increasing the Size and Volatility of the Root Zone: https://www.icann.org/en/system/files/files/root-scaling-study-report-31aug09-en.pdf – Summary of the Impact of Root Zone Scaling: https://archive.icann.org/en/topics/new-gtlds/summary-of-impact-root-zone-scaling-06oct10-en.pdf – Impact on Root Server Operations and Provisioning Due to New gTLDs: http://newgtlds.icann.org/en/about/historical-documentation/root-scaling-27jun12-en.pdf – Continuous Data Driven Analysis of Root Server System Stability Study Plan (Public Comment): https://www.icann.org/public-comments/cdar-study-plan-2015-12-02-en ICANN continues to work to address the issues identified in SAC059.

SAC060: Active Variant TLDs (4 of 14)
(7/23/13)

Phase 4 | Implement

The IDN Guidelines have been updated to encourage the use reference LGRs which allow for consistent set of rules between top-level and second level. See recommendations eight (8) and nine (9) of the guidelines: https://www.icann.org/en/system/files/files/idn-guidelines-10may18-en.pdf. The Guidelines are being considered by the ICANN Board. GNSO recently requested deferring their approval by the Board as it considers if some of these guidelines come under their policy remit. The reference second LGRs are posted at https://www.icann.org/resources/pages/second-level-lgr-2015-06-21-en. The root zone LGR is posted at https://www.icann.org/resources/pages/root-zone-lgr-2015-06-21-en. IANA also maintains a central repository for IDN tables for all TLDs.

SAC064: SSAC Advisory on DNS "Search List" Processing (R-2)
(2/13/14)

Phase 4 | Implement

The ICANN organization understands that SAC064 R-2 means that the SSAC recommends that ICANN organization work with the DNS community and the IETF to encourage the standardization of search list processing behavior, beginning with the submission of an Internet-Draft to the IETF and advocating for its standardization within the IETF process. Updates to RFC 1535 and other RFCs related to this topic should be included within the Internet-Draft. On 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation (https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b).

SAC064: SSAC Advisory on DNS "Search List" Processing (R-3)
(2/13/14)

Phase 4 | Implement

The ICANN organization understands that SAC064 R-3 means that the SSAC recommends that in the context of mitigating name collisions, ICANN should consider the following steps to address search list processing behavior: a. ICANN should consider whether to commission additional studies to further understand the cause of invalid queries to the root zone and the significance of search list processing as a contributor to those queries. b. ICANN should communicate to system administrators that search list behaviors currently implemented in some operating systems will cause collision with names delegated as new gTLDs from the 2012 application round for the New gTLD Program. On 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation (https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b).

SAC065: SSAC Advisory on DDoS Attacks Leveraging DNS Infrastructure (R-1)
(2/18/14)

Phase 4 | Implement

The ICANN organization understands that SAC065 R-1 means that ICANN should help to facilitate an Internet-wide community effort to reduce the number of open resolvers and networks that allow network spoofing. This initiative, which should involve measurement efforts and outreach, should be supported by ICANN with appropriate staffing and funding to promote the recommendations made in SAC065 Recommendations 2-5. On 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation (https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b).

SAC070: Advisory on the Use of Static TLD / Suffix Lists (R-5)
(5/28/15)

Phase 4 | Implement

The ICANN organization understands recommendation 5 of SAC070 as directing IANA staff to host an authoritative PSL containing information about the domains within the registries with which IANA has direct communication. This list should at least include all TLDs in the root zone. ICANN org hired a contractor to provide the materials. Estimated time to completion is end of August 2019. On 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation (https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b).

SAC070: SSAC Advisory on the Use of Static TLD/Suffix Lists (R-3)
(5/28/15)

Phase 4 | Implement

The ICANN organization understands this recommendation to mean that ICANN, in concert with the Mozilla Foundation, prepare educational materials on the Mozilla PSL covering the meaning of the resource and the impact of the resource. ICANN org hired a contractor to provide the materials. Estimated time to completion is end of August 2019. On 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation (https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b).

SAC095: SSAC Advisory on the Use of Emoji in Domain Names R-2
(25 May 2017)
Phase 4 | Implement On 2 Nov 2017, the ICANN Board directed the ICANN org to engage with gTLD and ccTLD communities on the findings and recommendations in SAC095 in addition to requesting that the ccNSO and GNSO integrate conformance with IDNA2008 and its successor into their relevant policies so as to safeguard security, stability, resiliency and interoperability of domain names (see: https://www.icann.org/resources/board-material/resolutions-2017-11-02-en#1.e). Registrations under gTLDs are limited to IDNA2008 under the new gTLDs program. So registrations for such gTLDs do not permit emojis. The same restrictions are also also extended for contracts for other gTLDs. There is active outreach to the ccTLDs for following the same practice, and not register emojis, by ICANN org's GSE team and the IDN program team. ICANN org has also translated the advice from SSAC to training materials, e.g. see the flyer and its translations at the bottom of the webpage www.icann.org/idn - which is being disseminated by the GSE team.

SAC097: SSAC Advisory Regarding the Centralized Zone Data Service (CZDS) and Registry Operator Monthly Activity Reports, R-1
(6/12/17)

Phase 4 | Implement

On 23 June 2018, the Board accepted this advice and directed the ICANN President and CEO or his designee to implement an auto-renew feature in the CZDS system (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). CZDS platform migration is complete, making it possible to add new features to address the problem of gaps in user access to zone files. The feature has been scoped and is in the process of being added to the next product road map for future system enhancements. A target completion date is not yet available, but a more substantive update should be available in 1QFY2020.

SAC097: SSAC Advisory Regarding the Centralized Zone Data Service (CZDS) and Registry Operator Monthly Activity Reports, R-2
(6/12/17)

Phase 4 | Implement

On 23 June 2018, the Board accepted this advice and directed the ICANN President and CEO or his designee to adjust the zone file access subscription agreement to the extent necessary to accommodate the implementation of Recommendation 1 (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). ICANN org is targeting to send necessary notification to the Subsequent Procedures WG in Q1 2019.

SAC097: SSAC Advisory Regarding the Centralized Zone Data Service (CZDS) and Registry Operator Monthly Activity Reports, R-3
(6/12/17)

Phase 4 | Implement

On 23 June 2018, the Board accepted this advice and directed the ICANN President and CEO or his designee to produce educational materials for registry operators to increase their awareness of ICANN's expectations with respect to zone file access (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). During CZDS platform migration, a new feature was added to provide an option to the registry operators to automatically approve a request as soon as it is received. Adoption rate of 38% percent of TLDs helped reduce the number of complaints due to delays.

SAC097: SSAC Advisory Regarding the Centralized Zone Data Service (CZDS) and Registry Operator Monthly Activity Reports, R-4
(6/12/17)

Phase 4 | Implement

On 23 June 2018, the Board accepted this advice and directed the ICANN President and CEO or his designee to clarify the Zone File Access (ZFA) metric and to support registry operators to increase the accuracy of the public reporting for Webbased WHOIS query statistics (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). ICANN org is targeting publication of educational materials to help registry operators report zone file access and web-based WHOIS query statistics more accurately, according to well-defined standards by the end of Q2 2019.

SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-1)
(12/11/18)

Phase 4 | Implement

On 23 June 2019 the ICANN Board considered SAC101v2 and accepted Recommendation 1 and directed the ICANN President and CEO, or his designee(s), to create a plan that reports on ICANN org's and the community's progress toward the four objectives identified in the advice (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "In accepting advice item one, the Board further notes that the creation of an "accredited RDDS access program," is a topic under discussion in the EPDP Phase 2. The Board cannot dictate outcomes of PDPs. Once the EPDP delivers its final Phase 2 report, the Board will consider the policy recommendations."

SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-2B)
(12/11/18)

Phase 4 | Implement

On 23 June 2019 the ICANN Board considered SAC101v2 and accepted Recommendation 1 and directed the ICANN President and CEO, or his designee(s), to work with the community to clarify existing contractual obligations relating to rate limits (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board state "Advice item 2B suggests that the Board direct ICANN org to work with the community to 'clarify current expectations for the use of rate limiting under existing policy and agreements.' In accepting advice item 2B, the Board notes that the community should be involved in the discussion to clarify existing contractual obligations relating to rate limits."

SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-6)
(11 Dec 2018)
Phase 4 | Implement On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item four suggests that 'initiation of charges for RDS access, or any significant future changes in fees for RDDS access, must include a formal assessment of user impacts and the security and stability impacts, and be conducted as part of a formal Policy Development Process (PDP).' As this is a policy matter and the topic is in the work plan for the EPDP Phase 2, the Board notes this advice and refers to the GNSO Council as the manager of PDPs."
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-6)
(11 Dec 2018)
Phase 4 | Implement On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item six suggests that the 'ICANN Board should direct the ICANN Organization to work to ensure that all methods of access to RDDS data provide an equivalent response to the same query.' As this is a policy matter and the topic is in the work plan for the EPDP Phase 2, the Board notes this advice and refers to the GNSO Council as the manager of PDPs."
SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-7)
(11 Dec 2018)
Phase 4 | Implement

On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item seven suggests that the 'ICANN Board should direct the ICANN Organization to work to ensure that RDDS access is provided in a measurable and enforceable framework, which can be understood by all parties.' As this is a policy matter and the topic is in the work plan for the EPDP Phase 2, the Board notes this advice and refers to the GNSO Council as the manager of PDPs."

SAC047: SSAC Comment on the ICANN gTLD Registry Transition Processes Model (2 of 7)
(15 Apr 2011)
Phase 5 | Close Request On 23 June 2018, the Board accepted this advice and directed the CEO or his designee to implement the advice (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g).

SAC058: R-3 SSAC Report on Domain Name Registration Data Validation
(3/27/13)

Phase 5 | Close Request

The ICANN organization understands SAC058 Recommendation 3 to mean that the ICANN community should seek to identify validation techniques to be used by registrars and registries for validating registration data. On 23 June 2018, the Board accepted this advice and directed the CEO or his designee to implement the advice (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g).

SAC061: R-2 SSAC Comment on ICANN's Initial Report from the Expert Working Group on gTLD Directory Services
(9/6/13)

Phase 5 | Close Request

On 23 June 2018, the Board accepted this advice and noted that implementation has been completed (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g). Subsequently, on 2 August 2018 the SSAC contacted the ICANN org to oppose this determination and requested the ICANN org change SAC061 Recommendation 2's status from 'Closed' to 'Open." Upon review of SAC061 and SAC101v2, the ICANN org has returned SAC061 to Phase 2 | Understand. SAC061 Recommendation 2 will be considered in conjunction with SAC101v2. On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item five reiterates Recommendation 2 from SAC061 and suggests that 'The ICANN Board should ensure that a formal security risk assessment of the registration data policy be conducted as an input into the Policy Development Process. A separate security risk assessment should also be conducted regarding the implementation of the policy.' The advice further suggests that 'These assessments should be incorporated in PDP plans at the GNSO.' As the advice suggests that the assessments be incorporated into PDP plans and the GNSO is the manager of PDPs, the Board notes and refers this advice to the GNSO Council."

SAC062: SSAC Advisory Concerning the Mitigation of Name Collision Risk (R-1)
(11/7/13)

Phase 5 | Close Request

On 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation (https://www.icann.org/resources/board-material/resolutions-2017-06-24-en#2.b).

SAC063: SSAC Advisory on DNSSEC Key Rollover in the Root Zone – Item 1
(11/7/13)

Phase 5 | Close Request

On 15 October 2018 ICANN org determined that the first-ever changing of the cryptographic key that helps protect the DNS has been completed with minimal disruption of the global Internet (https://www.icann.org/news/announcement-2018-10-15-en). The communication plan is part of the overall KSK Rollover Project. See: https://www.icann.org/resources/pages/ksk-rollover.

SAC063: SSAC Advisory on DNSSEC Key Rollover in the Root Zone – Item 2
(11/7/13)

Phase 5 | Close Request

On 15 October 2018 ICANN org determined that the first-ever changing of the cryptographic key that helps protect the DNS has been completed with minimal disruption of the global Internet (https://www.icann.org/news/announcement-2018-10-15-en). The communication plan is part of the overall KSK Rollover Project. See: https://www.icann.org/resources/pages/ksk-rollover.

SAC063: SSAC Advisory on DNSSEC Key Rollover in the Root Zone – Item 5
(11/7/13)

Phase 5 | Close Request

On 15 October 2018 ICANN org determined that the first-ever changing of the cryptographic key that helps protect the DNS has been completed with minimal disruption of the global Internet (https://www.icann.org/news/announcement-2018-10-15-en). The communication plan is part of the overall KSK Rollover Project. See: https://www.icann.org/resources/pages/ksk-rollover.

SAC073: SSAC Comments on Root Zone Key Signing Key Rollover Plan
(9/30/15)

Phase 5 | Close Request

On 15 October 2018 ICANN org determined that the first-ever changing of the cryptographic key that helps protect the DNS has been completed with minimal disruption of the global Internet (https://www.icann.org/news/announcement-2018-10-15-en). See: https://www.icann.org/resources/pages/ksk-rollover.

SAC074: SSAC Advisory on Registrant Protection: Best Practices for Preserving Security and Stability in the Credential Management Lifecycle – Item 4
(4/25/16)

Phase 5 | Close Request

At GDD Industry Summit 2019 in Bangkok in May 2019 (https://www.icann.org/gddsummit), a session on Credential Management Lifecycle was conducted. A team of community experts presented an educational material that was shared with the SSAC prior to the session for input and guidance. A community wiki space has been established for the community to share good practices in credential management. The sharing of the good practices and community awareness will continue with the participation of the community.

SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-1
(12/22/16)

Phase 5 | Close Request

On 23 June 2018, the Board accepted this advice and will ask the GNSO Subsequent Procedures PDP to include this recommendation in its work (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g).

SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-2
(12/22/16)

Phase 5 | Close Request

On 23 June 2018, the Board accepted this advice and will ask the GNSO Subsequent Procedures PDP to include this recommendation in its work (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g).

SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-3
(12/22/16)

Phase 5 | Close Request

On 23 June 2018, the Board accepted this advice and will ask the GNSO Subsequent Procedures PDP to include this recommendation in its work (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g).

SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-4
(12/22/16)

Phase 5 | Close Request

On 23 June 2018, the Board accepted this advice and will ask the GNSO Subsequent Procedures PDP to include this recommendation in its work (https://www.icann.org/resources/board-material/resolutions-2018-06-23-en#1.g).

SAC098: The Security, Stability and Resiliency of the DNS Review (SSR2)
(10/4/17)

Phase 5 | Close Request

On 28 October 2017, the Board issued a letter to the SSR2 Review Team instructing the team to pause all work related to the review, excepting only planned engagement meetings at ICANN 60 (https://www.icann.org/en/system/files/correspondence/crocker-to-ssr2-28oct17-en.pdf). On 7 June 2018 ICANN Org announced the formal restart of the SSR2 Review with four additional Review Team members (https://www.icann.org/news/announcement-2-2018-06-07-en).

SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-2A)
(12/11/18)

Phase 5 | Close Request

On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item 2A suggests that the Board direct ICANN org to work with the community to 'develop policy with clearly defined uniform purposes for RDDS rate-limiting and corresponding service level agreement requirements.' As policy is developed by the community and this topic is in the work plan for the EPDP Phase 2, the Board notes this advice and refers to the GNSO Council as the manager of PDPs. In taking this action, the Board also notes that in the Annex to the Temporary Specification for gTLD Registration Data, the Board asked that the topic of rate limit be discussed and resolved by the community as quickly as possible."

SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-3)
(12/11/18)

Phase 5 | Close Request

On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item three suggests that the 'Board and EPDP policy-makers should ensure that security practitioners and law enforcement authorities have access to domain name contact data, via RDDS, to the full extent allowed by applicable law.' As this is a policy matter and the topic is in the work plan for the EPDP Phase 2, the Board notes this advice and refers to the GNSO Council as the manager of PDPs."

SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-5)
(12/11/18)

Phase 5 | Close Request

On 23 June 2019 the ICANN Board considered SAC101v2 and noted advice items 2A and three through seven in SAC101 version 2 and referred them to the GNSO Council for consideration for inclusion in the EPDP Phase 2 work (https://www.icann.org/resources/board-material/resolutions-2019-06-23-en#1.c). In its rationale the Board states "Advice item five reiterates Recommendation 2 from SAC061 and suggests that 'The ICANN Board should ensure that a formal security risk assessment of the registration data policy be conducted as an input into the Policy Development Process. A separate security risk assessment should also be conducted regarding the implementation of the policy.' The advice further suggests that 'These assessments should be incorporated in PDP plans at the GNSO.' As the advice suggests that the assessments be incorporated into PDP plans and the GNSO is the manager of PDPs, the Board notes and refers this advice to the GNSO Council."

Advice Items Closed in the Last 12 Months

Advice Item Date Closed Action(s) Taken

Joint GAC-ALAC Statement on the EPDP

(25 Mar 2019)

5/7/19

The ICANN org understands that this is the Joint GAC-ALAC Statement on the EPDP. As this item will be considered via the Public Comment process, the item will be considered closed. The Board will provide its rationale for its action in the Board Resolution on the EPDP Recommendations. This understanding was sent to the ALAC on 7 May 2019.

Follow-Up to the Joint Statement by ALAC and GAC: Enabling Inclusive, Informed and Meaningful Participation at ICANN

(12 Dec 2018)

4/23/19

On 27 January 2019 the Board addressed this advice in their Barcelona Scorecard. Additionally, Cherine Chalaby included a response in his 6 February 2019 letter to Maureen Hilyard. On 23 April 2019 the ICANN org notified the ALAC this advice is considered closed due to these two responses.

Advice Item Date Closed Action(s) Taken
RSSAC043: Report from the RSSAC April 2019 Workshop
(4 Jun 2019)
7/10/19 The ICANN organization understands that RSSAC043 is a high-level summary of the outcomes of the Root Server System Advisory Committee (RSSAC) sixth workshop held from 23 April 2019 to 25 April 2019. There is no action for the ICANN Board. ICANN sent this understanding to the RSSAC on 10 Jul 2019.
RSSAC042: RSSAC Statement on Root Server Operator Independence
(17 May 2019)
6/11/19 The ICANN org understands RSSAC042 illustrates important aspects of Root Server Operator (RSO) independence: organizational independence, financial independence, architecture and engineering design, and network operations and administration. RSO independence is a vital quality of the RSS that must be preserved for the purposes recognized in this publication and to ensure the stability, security, and resilience of the DNS. As RSSAC042 does not contain any recommendations for the ICANN Board, the ICANN Org understands that there is no action for the ICANN Board and the item is closed. ICANN sent this understanding to the RSSAC for review on 11 Jun 2019.

RSSAC036: RSSAC Statement on the Draft Final Report of the Second Organizational Review of the RSSAC

(14 Jun 2018)

9/20/18

The ICANN org understands that this statement is the RSSAC036: RSSAC Statement on the Draft Final Report of the Second Organizational Review of the RSSAC. As this item will be considered via the Public Comment process, there is no action for the ICANN Board. This understanding was sent to the RSSAC on 19 July 2018.

RSSAC037: A Proposed Governance Model for the DNS Root Server System

(14 Jun 2018)

9/20/18

The ICANN org understands that this is a detailed proposal of a governance model for the DNS Root Server System. The ICANN org understands the proposal document itself does not contain any recommendation items for the ICANN Board. There is no action for the ICANN Board for RSSAC037. ICANN sent this understanding to the RSSAC for review on 24 July 2018. ICANN received confirmation of understanding on 17 August 2018.

RSSAC039: RSSAC Statement Regarding ICANN's Updated KSK Rollover Plan R-1

(7 Aug 2018)

9/17/18

The ICANN org understands the RSSAC has heard from some members of the technical community that have expressed concern that an increase in traffic from misconfigured resolvers may occur after the October 11th, 2018 date in the rollover plan. ICANN org also understands the RSSAC is not aware of any method able to estimate such a potential load increase and that the RSSAC believes that there is little risk of this occurring and that there will be no impact to the stability of the RSS even if such a load increase occurs. There is no action for the ICANN Board. The RSSAC confirmed this understanding on 17 September 2018.

RSSAC039: RSSAC Statement Regarding ICANN's Updated KSK Rollover Plan R-2

(7 Aug 2018)

9/17/18

ICANN org understands the RSSAC advises the KSK rollover back out plan should be reviewed by all parties in the rollover (RSOs, RZERC, and IANA) to ensure it remains adequate and implementable. There is no action for the ICANN Board. The RSSAC confirmed this understanding on 17 September 2018.

RSSAC040: Recommendations on Anonymization Processes for Source IP Addresses Submitted for Future Analysis R-1

(7 Aug 2018)

9/17/18

The ICANN org understands RSSAC040 Recommendation 1 is for the Root Server Operators to consider the advantages and disadvantages of harmonization of anonymization for DITL Data. There is no action for the ICANN Board. The RSSAC confirmed this understanding on 17 September 2018.

RSSAC040: Recommendations on Anonymization Processes for Source IP Addresses Submitted for Future Analysis R-2

(7 Aug 2018)

9/17/18

The ICANN org understands RSSAC040 Recommendation 2 is for each RSO to consider anonymization procedures in RSSAC040 individually. There is no action for the ICANN Board. This understanding was sent to the RSSAC on 7 September 2018.

RSSAC040: Recommendations on Anonymization Processes for Source IP Addresses Submitted for Future Analysis R-3

(7 Aug 2018)

9/17/18

The ICANN org understands RSSAC040 Recommendation 3 is for Autonomous System (AS) numbers of original addresses should be made available with the anonymized data if the origin AS is sufficiently general that it does not unnecessarily expose data that should have been anonymized. There is no action for the ICANN Board. The RSSAC confirmed this understanding on 17 September 2018.

RSSAC032: Feedback on the Independent Review of the Root Server System Advisory Committee (RSSAC) Assessment Report for Public Consultation

(28 Mar 2018)

8/22/18

The ICANN org understands this is the RSSAC's Feedback on the Independent Review of the Root Server System Advisory Committee (RSSAC) Assessment Report for Public Consultation. The RSSAC requests that the independent examiner reviews their stated concerns and applies them in the formulation of independent examiner's recommendations. There is no action for the ICANN Board. This understanding was sent to the RSSAC on 24 April 2018. ICANN received confirmation of understanding on 17 August 2018.

RSSAC033: RSSAC Statement on the Distinction Between RSSAC and Root-Ops

(24 Apr 2018)

8/22/18

The ICANN org understands that RSSAC033 is the RSSAC's statement on the distinction between RSSAC and Root-Ops. The RSSAC is providing this document to help explain the differences between the two functional bodies, as confusion between the two has been noted. The document is informational only and there is no action for the ICANN Board. This understanding was sent to the RSSAC on 5 June 2018. ICANN received confirmation of understanding on 17 August 2018.

RSSAC034: Report from the RSSAC May 2018 Workshop

(9 May 2018)

8/22/18

The ICANN organization understands that this is a high-level summary of the outcomes of the Root Server System Advisory Committee (RSSAC) sixth workshop held from 1 May 2018 to 3 May 2018. There is no action for the ICANN Board. This understanding was sent to the RSSAC on 16 May 2018. ICANN received confirmation of understanding on 17 August 2018.

Advice Item Date Closed Action(s) Taken

SAC105 The DNS and the Internet of Things: Opportunities, Risks, and Challenges

(3 Jun 2019)
6/3/19 The ICANN org understands that the aim of SAC105: The DNS and the Internet of Things: Opportunities, Risks, and Challenges is to trigger and facilitate dialogue in the broader ICANN community. The ICANN org understands that SAC105 does not contain any recommendations nor does it solicit any actions from the ICANN Community or Board and therefore the item will be considered closed. This understanding was sent to the SSAC on 3 June 2019.

SAC104: SSAC Comment on Initial Report of the Temporary Specification for gTLD Registration Data Expedited Policy Development Process

(21 Dec 2018)

1/3/19

The ICANN org understands that this statement is the SAC104: SSAC Comment on Initial Report of the Temporary Specification for gTLD Registration Data Expedited Policy Development Process. As this item will be considered via the Public Comment process, there is no action for the ICANN Board. This understanding was sent to the SSAC on 3 January 2019.

SAC103: SSAC Response to the new gTLD Subsequent Procedures Policy Development Process Working Group Initial Report
(3 Oct 2018)
11/1/18 The ICANN org understands that this statement is the SAC103: SSAC Response to the new gTLD Subsequent Procedures Policy Development Process Working Group Initial Report. As this item will be considered via the Public Comment process, there is no action for the ICANN Board. This understanding was sent to the SSAC on 1 November 2018.

SAC101: SSAC Advisory Regarding Access to Domain Name Registration Data R-1

(14 Jun 2018)

12/12/18

This recommendation is part of Version 1 of SAC101. ICANN closed recommendations under Version 1 on 12 December 2018 upon receipt of Version 2. As stated by the SSAC in SAC101v2, "Version 2 of SAC101 was published to reflect evolving circumstances related to ICANN's Temporary Specification for gTLD Registration Data, and the ongoing Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. Version 1 of SAC101 has been retired and version 2 is authoritative."

SAC101: SSAC Advisory Regarding Access to Domain Name Registration Data R-2

(14 Jun 2018)

12/12/18

This recommendation is part of Version 1 of SAC101. ICANN closed recommendations under Version 1 on 12 December 2018 upon receipt of Version 2. As stated by the SSAC in SAC101v2, "Version 2 of SAC101 was published to reflect evolving circumstances related to ICANN's Temporary Specification for gTLD Registration Data, and the ongoing Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. Version 1 of SAC101 has been retired and version 2 is authoritative."

SAC101: SSAC Advisory Regarding Access to Domain Name Registration Data R-3

(14 Jun 2018)

12/12/18

This recommendation is part of Version 1 of SAC101. ICANN closed recommendations under Version 1 on 12 December 2018 upon receipt of Version 2. As stated by the SSAC in SAC101v2, "Version 2 of SAC101 was published to reflect evolving circumstances related to ICANN's Temporary Specification for gTLD Registration Data, and the ongoing Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. Version 1 of SAC101 has been retired and version 2 is authoritative."

SAC101: SSAC Advisory Regarding Access to Domain Name Registration Data R-4

(14 Jun 2018)

12/12/18

This recommendation is part of Version 1 of SAC101. ICANN closed recommendations under Version 1 on 12 December 2018 upon receipt of Version 2. As stated by the SSAC in SAC101v2, "Version 2 of SAC101 was published to reflect evolving circumstances related to ICANN's Temporary Specification for gTLD Registration Data, and the ongoing Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. Version 1 of SAC101 has been retired and version 2 is authoritative."

SAC101: SSAC Advisory Regarding Access to Domain Name Registration Data R-5

(14 Jun 2018)

12/12/18

This recommendation is part of Version 1 of SAC101. ICANN closed recommendations under Version 1 on 12 December 2018 upon receipt of Version 2. As stated by the SSAC in SAC101v2, "Version 2 of SAC101 was published to reflect evolving circumstances related to ICANN's Temporary Specification for gTLD Registration Data, and the ongoing Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. Version 1 of SAC101 has been retired and version 2 is authoritative."

SAC101: SSAC Advisory Regarding Access to Domain Name Registration Data R-6

(14 Jun 2018)

12/12/18

This recommendation is part of Version 1 of SAC101. ICANN closed recommendations under Version 1 on 12 December 2018 upon receipt of Version 2. As stated by the SSAC in SAC101v2, "Version 2 of SAC101 was published to reflect evolving circumstances related to ICANN's Temporary Specification for gTLD Registration Data, and the ongoing Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. Version 1 of SAC101 has been retired and version 2 is authoritative."

SAC101: SSAC Advisory Regarding Access to Domain Name Registration Data R-7

(14 Jun 2018)

12/12/18

This recommendation is part of Version 1 of SAC101. ICANN closed recommendations under Version 1 on 12 December 2018 upon receipt of Version 2. As stated by the SSAC in SAC101v2, "Version 2 of SAC101 was published to reflect evolving circumstances related to ICANN's Temporary Specification for gTLD Registration Data, and the ongoing Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. Version 1 of SAC101 has been retired and version 2 is authoritative."

SAC084: SSAC Comments on Guidelines for the Extended Process Similarity Review Panel for the IDN ccTLD Fast Track Process
(31 Aug 2016)

8/13/18

Completion letter sent to Board on 12 June 2018 (https://www.icann.org/en/system/files/correspondence/namazi-to-chalaby-12jun18-en.pdf)

SAC060: Active Variant TLDs (3 of 14)

(23 Jul 2013)

8/13/18

Completion letter sent to Board on 12 June 2018.

SAC074: SSAC Advisory on Registrant Protection: Best Practices for Preserving Security and Stability in the Credential Management Lifecycle – Item 1

(25 Apr 2016)

8/13/18

Completion letter sent to Board on 12 June 2018.

SAC074: SSAC Advisory on Registrant Protection: Best Practices for Preserving Security and Stability in the Credential Management Lifecycle – Item 2

(25 Apr 2016)

8/13/18

Completion letter sent to Board on 12 June 2018.

SAC074: SSAC Advisory on Registrant Protection: Best Practices for Preserving Security and Stability in the Credential Management Lifecycle – Item 3

(25 Apr 2016)

8/13/18

Completion letter sent to Board on 12 June 2018.

Archived Status Reports

April 2019 [PDF | XLSX] | May 2019 [PDF | XLSX] | June 2019 [PDF | XLSX]

Historical Advice

In October 2016, ICANN issued a status report to the ALAC, RSSAC and SSAC on historical advice to the ICANN Board issued between 2010 and mid-2015. The Board's status reports on historical items can be found below. Updated Status on all items can be found in the reports listed above.

  • At-Large Advisory Committee (ALAC) (19 October 2016) [PDF]
  • Root Server System Advisory Committee (RSSAC) (19 October 2016) [PDF]
  • Security and Stability Advisory Committee (SSAC) (19 October 2016) [PDF]

Important note: The Board Resolutions are as reported in the Board Meeting Transcripts, Minutes & Resolutions portion of ICANN's website. Only the words contained in the Resolutions themselves represent the official acts of the Board. The text provided in this database explaining Resolutions is an interpretation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanation or interpretation modify or override the Resolutions themselves. Resolutions can only be modified through further action by the ICANN Board.