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 63 Barcelona Communiqué.

Latest Advice to the ICANN Board

As of 30 April 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 30 April 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.

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 - 5 9 14
Phase 3 | Evaluate & Consider - 7 - 7
Phase 4 | Implement 2 - 22 24
Phase 5 | Close 2 - 11 13
Total Open Items by
Advisory Committee
4 12 42 58
Total Items Closed in
Past 12 Months
10 13 14 37

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

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

(5 Oct 2018)

Phase 2 | Understand Request

The ICANN org understands RSSAC041 Recommendation 1 to mean that the ICANN org should define the ICANN organizational review. The definition should be documented and available to the community. Details should be straightforward and unambiguous in order to ensure complete clarity of scope. ICANN sent this understanding to the RSSAC for review on 29 March 2019.

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

(5 Oct 2018)

Phase 2 | Understand Request

The ICANN org understands RSSAC041 Recommendation 2 to mean that the ICANN org should document the intent of each organizational review, what information ICANN org hopes to obtain, and how the information from the review will be used. ICANN sent this understanding to the RSSAC for review on 29 March 2019.

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

(5 Oct 2018)

Phase 2 | Understand Request

The ICANN org understands RSSAC041 Recommendation 3 to mean that the ICANN org should continue to use its Request for Proposal process to select the Independent Examiner for reviews. The process should be modified to ensure that the Independent Examiners are experts in assessment frameworks and methodologies and that they are not from the ICANN community. ICANN sent this understanding to the RSSAC for review on 29 March 2019.

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

(5 Oct 2018)

Phase 2 | Understand Request

The ICANN org understands RSSAC041 Recommendation 4 to mean that the ICANN org should ensure there are actionable checkpoints in place to ensure that an organizational review is meeting its contractual obligations throughout the review process. The ICANN org should take appropriate action to ensure contractual compliance at each checkpoint. ICANN sent this understanding to the RSSAC for review on 29 March 2019.

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

(5 Oct 2018)

Phase 2 | Understand Request

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. ICANN sent this understanding to the RSSAC for review on 29 March 2019.

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-1

(14 Jun 2018)

Phase 3 | Evaluate & Consider

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.

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.

Advice Item Phase Action(s) Taken

SAC061: R-2 SSAC Comment on ICANN's Initial Report from the Expert Working Group on gTLD Directory Services

(6 Sep 2013)

Phase 2 | Understand Request

On 23 June 2018, the Board accepted this advice and noted that implementation has been completed. 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.

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

(11 Dec 2018)

Phase 2 | Understand Request

The ICANN organization understands SAC101v2 Recommendation 1 to mean that the ICANN Board should oversee the creation and execution of a plan by the ICANN Board, ICANN org and ICANN community that accomplishes the following tasks in a coordinated way and with timely deadlines:

  • A domain registration data policy that includes statements of purposes for the collection and publication of the data.
  • The ICANN Board and the ICANN Organization should require contracted parties to migrate from using the WHOIS protocol to using the RDAP protocol.
  • The ICANN Board and the ICANN Organization should require the remaining thin gTLD registries to move to thick status per the Thick WHOIS Consensus Policy and Board Resolution 2014.02.07.08.
  • The ICANN Board should support the creation of an accredited RDDS access program, with the ICANN Organization ensuring the creation, support of, and oversight of the supporting technical access mechanism.

ICANN sent this understanding to the SSAC on 20 March 2019.

SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-2)

(11 Dec 2018)

Phase 2 | Understand Request

The ICANN organization understands SAC101v2 Recommendation 2 to mean that the ICANN Board should direct the ICANN org work with the ICANN Community to: A) develop policy with defined uniform purposes for RDDS rate-limiting and corresponding service level agreement requirements and B) clarify current expectations for the use of rate limiting under existing policy and agreements. ICANN sent this understanding to the SSAC on 20 March 2019.

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

(11 Dec 2018)

Phase 2 | Understand Request

The ICANN organization understands SAC101v2 Recommendation 3 to mean that the ICANN 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 fullest extent allowed by applicable law. ICANN sent this understanding to the SSAC on 20 March 2019.

SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-4)

(11 Dec 2018)

Phase 2 | Understand Request

The ICANN organization understands SAC101v2 Recommendation 4 to mean the 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. ICANN sent this understanding to the SSAC on 20 March 2019.

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

(11 Dec 2018)

Phase 2 | Understand Request

The ICANN organization understands SAC101v2 Recommendation 5 to mean that the SSAC is reiterating its advice from SAC061 Recommendation 2, which states: "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 ICANN org also understands that the SSAC is recommending that these security risk assessments of registration data policy be incorporated into PDP plans by the GNSO. ICANN sent this understanding to the SSAC on 20 March 2019.

SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-6)

(11 Dec 2018)

Phase 2 | Understand Request

The ICANN organization understands SAC101v2 Recommendation 6 to mean that the ICANN Board should direct the ICANN org to work to ensure that all methods of access to RDDS data provide an equivalent response to the same query. ICANN sent this understanding to the SSAC on 20 March 2019.

SAC101v2: SSAC Advisory Regarding Access to Domain Name Registration Data (R-7)

(11 Dec 2018)

Phase 2 | Understand Request

The ICANN organization understands SAC101v2 Recommendation 7 to mean that the ICANN Board should direct the ICANN org to work to ensure that RDDS access is provided in a measurable and enforceable framework, which can be understood by all parties. ICANN sent this understanding to the SSAC on 20 March 2019.

SAC102: SSAC Comment on the Updated Plan for Continuing the Root KSK Rollover

(20 Aug 2018)

Phase 2 | Understand Request

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.

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

(15 Nov 2010)

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)

(6 Dec 2010)

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.

SAC047: SSAC Comment on the ICANN gTLD Registry Transition Processes Model (2 of 7)

(15 Apr 2011)

Phase 4 | Implement

On 23 June 2018, the Board accepted this advice and directed the CEO or his designee to implement the advice.

SAC051: SSAC Report on WHOIS Terminology and Structure (R-2)

(14 Jun 2011)

Phase 4 | Implement

The Board accepted this advice in October 2011 and requested that a roadmap to implementation of SAC051 be developed. A roadmap to implementing SAC051 was published for public comment in February 2012. 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:

SAC059: R-1 Interdisciplinary studies of security and stability implications from expanding the root zone

(18 Apr 2013)

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:

ICANN continues to work to address the issues identified in SAC059.

SAC059: R-2 Interdisciplinary studies of security and stability implications from expanding the root zone

(18 Apr 2013)

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:

ICANN continues to work to address the issues identified in SAC059.

SAC060: Active Variant TLDs (2 of 14)

(23 Jul 2013)

Phase 4 | Implement

The Study Group on Technical Use of RZ-LGR is currently reviewing, among other issues, this recommendation

See also for the latest information on the Root-Zone LGR and IDN Implementation Guidelines:

SAC060: Active Variant TLDs (4 of 14)

(23 Jul 2013)

Phase 4 | Implement

ICANN agrees with these recommendations. Implementation of this specific advice item is in progress, and there is an active working group that is working on the next version of IDN implementation guidelines as well as on second-level label generation rules (LGRs). IDN implementation guidelines update will soon be published and will go to the Board for consideration. See also the Draft Final Guidelines and their second Public Comment.

SAC060: Active Variant TLDs (8 of 14)

(23 Jul 2013)

Phase 4 | Implement

ICANN agrees with this recommendation and the entire Project 7 of the IDN Variant TLD Program is dedicated to developing the processes to handle variant mechanisms, including the life cycle of a variant label. Implementation of this specific advice item is in progress and is part of project 7. This recommendation is being looked at by the Study Group on Technical Use of RZ-LGR.

SAC060: Active Variant TLDs (9 of 14)

(23 Jul 2013)

Phase 4 | Implement

With regard to EBERO and variant TLDs, the discussion is included in the ongoing work on developing recommendations for the implementation of IDN Variant TLDs under the guidance of the Board IDN Working Group. All EBERO providers support variant TLDs; there is parity for variant support in all relevant systems and functions.

Please see the following links for more information on both IDN Variants and EBERO, including the EBERO Agreement, which stipulates requirements regarding IDN variants:

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

(13 Feb 2014)

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.

SAC064: SSAC Advisory on DNS "Search List" Processing (R-3)

(13 Feb 2014)

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:

  • 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.
  • 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.

SAC065: SSAC Advisory on DDoS Attacks Leveraging DNS Infrastructure (R-1)

(18 Feb 2014)

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.

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

(28 May 2015)

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.

On 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation.

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

(28 May 2015)

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.

On 24 June 2017, the ICANN Board accepted this advice and directed the ICANN organization to implement per the ICANN organization's recommendation.

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

(25 Apr 2016)

Phase 4 | Implement

A training session for Credential Management Lifecycle has been scheduled for GDD Industry Summit in May 2019. A community volunteer team with expertise in credential management has drafted an introductory material. The team is soliciting feedback on the draft from the technical community including SSAC.

SAC095: SSAC Advisory on the Use of Emoji in Domain Names R-1

(25 May 2017)

Phase 4 | Implement

The ICANN Organization understands recommendation 1 of SAC095 to mean that the SSAC recommends that the ICANN Board reject any TLD (root zone label) that includes emoji. This understanding was confirmed by the SSAC on 18 August 2017.

The ICANN Board considered this item at ICANN60 in Abu Dhabi. The Board directed the ICANN 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.

SAC095: SSAC Advisory on the Use of Emoji in Domain Names R-2

(25 May 2017)

Phase 4 | Implement

The ICANN Organization understands recommendation 2 of SAC095 to mean that the SSAC strongly discourages the registration of any domain name that includes emoji in any of its labels. The ICANN Organization also understands recommendation 2 to mean that the SSAC advises registrants of domain names with emoji that such domains may not function consistently or may not be universally accessible as expected. This understanding was confirmed by the SSAC on 18 August 2017.

The ICANN Board considered this item at ICANN60 in Abu Dhabi. The Board directed the ICANN 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.

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

(12 Jun 2017)

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.

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

(12 Jun 2017)

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.

ICANN org is targeting to send necessary notification to the Subsequent Procedures WG in 2019.

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

(12 Jun 2017)

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.

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

(12 Jun 2017)

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.

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.

SAC058: R-3 SSAC Report on Domain Name Registration Data Validation

(27 Mar 2013)

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.

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

(7 Nov 2013)

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.

SAC063: SSAC Advisory on DNSSEC Key Rollover in the Root Zone - Item 1

(7 Nov 2013)

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. The communication plan is part of the overall KSK Rollover Project.

SAC063: SSAC Advisory on DNSSEC Key Rollover in the Root Zone - Item 2

(7 Nov 2013)

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. The test pass is part of the overall KSK Rollover Project.

SAC063: SSAC Advisory on DNSSEC Key Rollover in the Root Zone - Item 5

(7 Nov 2013)

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. The data collection program is part of the overall KSK Rollover Project.

SAC073: SSAC Comments on Root Zone Key Signing Key Rollover Plan

(30 Sep 2015)

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. See here for information on the KSK rollover.

SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-1

(22 Dec 2016)

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.

SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-2

(22 Dec 2016)

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.

SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-3

(22 Dec 2016)

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.

SAC090: SSAC Advisory on the Stability of the Domain Namespace, R-4

(22 Dec 2016)

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.

SAC098: The Security, Stability and Resiliency of the DNS Review (SSR2)

(4 Oct 2017)

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. On 7 June 2018 the ICANN Org announced the formal restart of the SSR2 Review with four additional Review Team members.

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.

Release for Registration one .COM Domain Name with a Single-Character Label: O.COM

(5 Jun 2018)

7/5/18

The ICANN org understands that this is the ALAC statement regarding Release for Registration one .COM Domain Name with a Single-Character Label: O.COM. This statement was submitted as part of a public comment and there is no action for the ICANN Board.

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

(26 Jun 2014)

6/1/18

Completion letter sent to Board on 25 May 2018.

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

(26 Jun 2014)

6/1/18

Completion letter sent to Board on 25 May 2018.

ALAC Statement on ICANN Reserve Fund: Proposed Replenishment Strategy

(20 Apr 2018)

5/2/18

The ICANN org understands this is the ALAC statement on ICANN Reserve Fund: Proposed Replenishment Strategy and was submitted as part of a public comment. As this statement will be handled via the public comment process, there is no action for the ICANN Board.

ALAC Statement on Draft Project Plan for the Proposed Name Collision Analysis Project (NCAP)

(18 Apr 2018)

5/2/18

The ICANN org understands this is the ALAC Statement on Draft Project Plan for the Proposed Name Collision Analysis Project (NCAP) and was submitted as part of a public comment. As this statement will be handled via the public comment process, there is no action for the ICANN Board.

ALAC Statement on Plan to Restart the Root Key Signing Key (KSK) Rollover Process

(10 Apr 2018)

5/2/18

The ICANN org understands this is the ALAC statement on Plan to Restart the Root Key Signing Key (KSK) Rollover Process and was submitted as part of a public comment. As this statement will be handled via the public comment process, there is no action for the ICANN Board.

ALAC Statement on ICANN Fellowship Program Community Consultation

(10 Apr 2018)

5/2/18

The ICANN org understands this is the ALAC Statement on ICANN Fellowship Program Community Consultation and was submitted as part of a public comment/consultation. As this statement will be handled via the public comment/consultation process, there is no action for the ICANN Board.

ALAC Statement on Data Protection/Privacy Issues: ICANN-proposed Interim Model

(10 Apr 2018)

5/2/18

The ICANN org understands this is the ALAC statement on Data Protection/Privacy Issues: ICANN-proposed Interim Model. This statement was submitted as part of a public comment. As this will be handled via the public comment process, there is no action for the ICANN Board.

ALAC Statement on Draft Procedure for Community gTLD Change Requests

(2 Apr 2018)

5/2/18

The ICANN org understands this is the ALAC statement on Draft Procedure for Community gTLD Change Requests and was submitted as part of a public comment. As this will be handled via the public comment process, there is no action for the ICANN Board.

Advice Item Date Closed Action(s) Taken

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.

RSSAC003: RSSAC Report on Root Zone TTLs

(21 Aug 2015)

7/31/18

Closure notification letter sent to Board on 23 April 2018. RSSAC notified via ARR Tool as well.

RSSAC031: Response to the GNSO Policy Development Process (PDP) Working Group on the new Generic Top Level Domains (gTLDs) Subsequent Procedures

(2 Feb 2018)

6/18/18

The ICANN org understands that this is the RSSAC response to the GNSO Policy Development Process (PDP) Working Group on the new generic Top-Level Domains (gTLDs) Subsequent Procedures request for input on root scaling. There is no action for the ICANN Board.

RSSAC035: RSSAC Statement on the Draft Final Report of the Second Organizational Review of the Nominating Committee

(11 May 2018)

5/15/18

The ICANN org understands this is the RSSAC's Statement on the Draft Final Report of the Second Organizational Review of the Nominating Committee submitted during the public comment period to the independent examiner. There is no action for the ICANN Board. This understanding was sent to the RSSAC on 15 May 2018.

Advice Item Date Closed Action(s) Taken

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.

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."

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 RSSAC on 1 November 2018.

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.

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.

Archived Status Reports

January 2019 [PDF | XLSX] | February 2019 [PDF | XLSX] | March 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.