Root Server System Advisory Committee (RSSAC) Advice Status

Board Advice Home | ALAC Advice Status | SSAC Advice Status | GAC Advice Status


Latest Advice to the ICANN Board

As of 29 February 2020

Advisory Committee Advice Document
Root Server System Advisory Committee (RSSAC)

Board Advice Register Phases and Descriptions

Board Advice Register Phases and Descriptions

Advice Items by Advisory Committee

Phase RSSAC
Phase 1 | Receive & Acknowledge -
Phase 2 | Understand 1
Phase 3 | Evaluate & Consider 9
Phase 3 | Deferred -
Phase 4 | Implement 1
Phase 4 | Deferred -
Phase 5 | Close 1
Total Open Items by Advisory Committee 12
Total Items Closed in Past 12 Months 6

Open Advice Items

See also "Advice Status Reports" on Board Advice Home for PDF/Excel versions of the information below.

Advice Item Phase Action(s) Taken

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

(3 Aug 2017)

Phase 2 | Understand Request

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.

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.

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

(14 Jun 2018)

Phase 4 | Implement

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. As the GWG begins its work to develop a final governance model for the Root Server System, ICANN org is working on a methodology for estimating the costs of the RSS. ICANN org will also work proactively with the GWG to estimate the costs of the final governance model.

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

(14 Jun 2018)

Phase 5 | Close Request

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. On 07 November 2019 a Board Resolution addressed RSSAC037 Recommendation 1 https://www.icann.org/resources/board-material/resolutions-2019-11-07-en.... The ICANN Board directed the ICANN President and CEO, or his designee(s), to publish the final charter, operating procedures, and work plan for the GWG and to convene the GWG. RSSAC037; the Concept Paper; and the GWG charter, operating procedures, and work plan provide a starting point for discussions in the ICANN community about evolving RSS governance. By convening the GWG, the ICANN Board completes its consideration of recommendation one from RSSAC038. Furthermore, the ICANN Board continues its evaluation and consideration of recommendations two and three from RSSAC038.

Advice Items Closed in the Last 12 Months

Advice Item Close Date Action(s) Taken

RSSAC046: RSSAC Statement on IANA's Proposal for Future Root Zone KSK Rollovers

(29 Jan 2020)

2/5/20

The ICANN organization understands this is the RSSAC's comment on IANA's Proposal for Future Root Zone KSK Rollovers. The respective public comment period closed on 31 January 2020. A Report of Public Comments will be published on 21 February 2020 and this comment will be included in that consideration (https://www.icann.org/public-comments/proposal-future-rz-ksk-rollovers-2...). There is no action for the ICANN Board. This understanding was sent to the RSSAC on 05 February 2020.

RSSAC044: Report from the RSSAC October 2019 Workshop

(29 Oct 2019)

12/19/19

The ICANN organization understands that RSSAC044 is a high-level summary of the outcomes of the Root Server System Advisory Committee (RSSAC) eighth workshop held from 01 October 2019 to 03 October 2019. There is no action for the ICANN Board. ICANN sent this understanding to the RSSAC for review on 05 Nov 2019. This item is considered complete as of the RSSAC's confirmation of understanding on 18 Dec 2019.

RSSAC045: RSSAC Statement on Threat Mitigation for the Root Server System

(3 Dec 2019)

12/18/19

ICANN understands that this is the Root Server System Advisory Committee's (RSSAC) Statement on Threat Mitigation for the Root Server System. The RSSAC would like to formally endorse the work of the RSOs on Threat Mitigation for the Root Server System.2 Furthermore, the RSSAC regards the ICANN Board's request for input fulfilled. There is no action for the ICANN Board. ICANN sent this understanding to the RSSAC for review on 16 Dec 2019. This item is considered complete as of the RSSAC's confirmation of understanding on 18 Dec 2019.

RSSAC000v4: RSSAC Operational Procedures

(23 Oct 2019)

11/19/19

ICANN understands that this is the Operational Procedures of the Root Server System Advisory Committee (RSSAC). This documents how the RSSAC will carry out its work, with the rationale for processes where it seems helpful. In case of conflict with the ICANN Bylaws, the ICANN Bylaws take precedence. There is no action for the ICANN Board. ICANN sent this understanding to the RSSAC for review on 18 Nov 2019. This item is considered complete as of the RSSAC's confirmation of understanding on 19 Nov 2019.

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.