Root Server System Advisory Committee
The Root Server System Advisory Committee (RSSAC) advises the ICANN Community and Board on issues pertaining to the operation, administration, security, and integrity of the Internet's Root Server System.[1] RSSAC was also tasked to review the number, location, and distribution of the root name server and its total system performance, robustness, and reliability .It was created under the Article VII Section 3 (b) of the ICANN Bylaws, which gave the ICANN Board the mandate to appoint the initial Chairman of the Committee, after which the following chairman was to be elected by the members of the committee. Jun Murai was appointed as the first chairman of the RSSAC.[2]
Responsibilities edit
RSSAC has the following responsibilities, per the ICANN bylaws:
- Communicate on matters relating to the operation of the Root Servers and their multiple instances with the Internet technical community and the ICANN community. The RSSAC shall gather and articulate requirements to offer to those engaged in technical revision of the protocols and best common practices related to the operation of DNS servers.
- Communicate on matters relating to the administration of the Root Zone with those who have direct responsibility for that administration. These matters include the processes and procedures for the production of the Root Zone File.
- Engage in ongoing threat assessment and risk analysis of the Root Server System and recommend any necessary audit activity to assess the current status of root servers and the root zone.
- Respond to requests for information or opinions from the Board.
- Report periodically to the Board on its activities.
- Make policy recommendations to the ICANN community and Board.
Structure edit
Representatives edit
The RSSAC consists of voting representatives from each of the 12 organizations responsible for operating the 13 root name servers, and alternates to each of these. It also includes non-voting liaisons from a number of functions related to services pertaining to the root zone.
The current composition is available at RSSAC's official web page.
Voting Members
Root Server Operator | Representative | Term Expires | Alternate |
---|---|---|---|
Verisign | Brad Verd (Vice Chair) | 31 December 2021 | N/A |
University of Southern California | Wes Hardaker | 31 December 2023 | Suzanne Woolf |
Cogent | Paul Vixie | 31 December 2023 | Brad Belanger |
University of Maryland | Karl Reuss | 31 December 2022 | Gerry Sneeringer |
NASA | Barbara Schleckser | 31 December 2022 | Tom Miglin |
Internet Consortium | Fred Baker (Chair) | 31 December 2021 | Jeff Osborn |
US Department of Defense | Kevin Wright | 31 December 2022 | Ryan Stephenson |
US Army Research Labratory | Howard Kash | 31 December 2022 | Kenneth Renard |
Netnod | Lars-Johan Liman | 31 December 2021 | Patrik Fältström |
RIPE NCC | Kaveh Ranjbar | 31 December 2023 | Anand Buddhdev |
ICANN | Matt Larson | 31 December 2021 | Terry Manderson |
WIDE Project | Jun Murai | 31 December 2023 | Hiro Hotta |
Partner Member Representatives edit
The RSSAC includes two non-voting representatives from the organizations responsible for the maintenance of the authoritative root zone:
Partner Representative | Name | Affiliation |
---|---|---|
IANA Functions Operator | James Mitchell | PTI |
Root Zone Maintainer | Duane Wessels | Verisign |
RSSAC Liaisons edit
There are two liaisons to the RSSAC from other organizations within the Internet community:
Liaison From | Name | Affiliation |
---|---|---|
Internet Architecture Board | Daniel Migault | |
Security and Stability Advisory Committee (SSAC) | Russ Mundy |
RSSAC Liaisons to Other Organizations edit
RSSAC appoints liaisons to other groups and organizations to coordinate or communicate matters of common interest, as required by the RSSAC Operational Procedures
Liaison To | Name | Affiliation |
---|---|---|
ICANN Board of Directors | Kaveh Ranjbar | RIPE NCC |
Customer Standing Committee | Lars-Johan Liman | |
Root Zone Evolution Review Committee | Daniel Migault | |
ICANN Nominating Committee | Amir Qayyum |
RSSAC Projects edit
Since its inception, the committee continuously performs projects under a Cooperative Research and Development Agreement (CRADA)[3] between ICANN, the National Institute for Standards and Technology (NIST), and National Telecommunications and Information Administration (NTIA), to conduct a collaborative study to address the operational and technical requirements of the root name servers to be able to establish a more robust and secure management of the Internet DNS root server system.[4]
The RSSAC was also involved in the Y2K Project between 1999 to 2000. Its objective was to make sure that the operations of the root nameserver system is in compliance with Y2K protocol by conducting administrative services and testing.[5]
The committee is also conducting new technical developments on IPv6, DNSSEC, IDN, and their effects to the root nameserver system.
2008-9 Independent Review of RSSAC by Westlake Consulting Limited edit
Article IV, Section 4, Paragraph 1 of the ICANN Bylaws stipulated that a review on the performance and operations of the RSSAC by an independent organization is required to determine if the committee is still serving its purpose in the ICANN structure and if certain changes in the structure or operations are necessary to improve its functions.[6] To be able to comply with the Bylaws, the ICANN Board issued a Request For Proposal and Terms of Reference to conduct and independent review on the RSSAC in July, 2008.[7] ICANN selected Westlake Consulting Limited, and in November of 2008, the company started performing face to face interviews with some individuals during the ICANN Meeting in Cairo and during the IETF meeting in Minnesota regarding RSSAC. WCL also conducted telephone interviews and accessed all available written-records regarding the committee. [8]
Findings edit
By April of 2009, WCL published its final report on the Independent Review on RSSAC with the following findings:[9]
- RSSAC only provides reactions to issues instead of regularly giving updates to the ICANN Board regarding the activities and functions of the committee.
- Communication and agreement about the expectations of the Board towards the committee is insufficient.
- RSSAC provides minimal strategic advice to the ICANN Board because the committee is dominated by independent root server operators that are focused on operations.
- The records of the RSSAC meetings are poor and incomplete.
- The election process of the members of the committee and its chairman is not clear.
- The Root Server Operators believed that some of the functions of RSSAC identified in the Bylaws of ICANN are their responsibility, and because of that the committee's reported little of its responsibilities.
- Interaction between RSSAC and the different organization within ICANN is limited because most of the committee's members do not or seldom participate in ICANN Meetings. RSSAC committee members frequently attend or conduct their meeting in conjunction with the meetings of the IETF.
Recommendations edit
Based on its final report, WCL recommended the following to improve the operational functions of RSSAC:[10]
- Re-establish RSSAC as a strategy group which will be jointly supervised by ICANN and Root Server Operators.
- Amend the Terms of Reference of the ICANN Bylaws and set out a new role for RSSAC to "provide a source of unbiased strategic advice to ICANN, the Root Server Operators and the Internet Community about the best way ahead for the Root Server System."
- Reconstitute RSSAC's membership with 9 initial members who have strong technical backgrounds. The committee should be composed of 4 Root Server Operators, 1 appointed by IANA; and 4 appointed by the ICANN Board/Nominating Committee.
- The Chairman of the committee shall be appointed by its members with a two year term, with a limited three consecutive 2-years terms.
- Appoint non-voting liaison members, which include Outward liaison from the RSSAC to the ICANN Board and the SSAC and an Inward liaison to the RSSAC from IETF/IAB.
- RSSAC should meet in conjunction with ICANN meetings and may be able to hold additional meetings as necessary; meetings shall be open for public participation and hold a closed meeting if necessary; Root Server Operators and members of the ICANN Board should be invited to the meeting even during closed sessions and shall be given the right to speak under the RSSAC Chairman's discretion.
RSSAC Working Group Review on WCL Report edit
In June, 2010, the RSSAC Working Group submitted its final report regarding the findings of WCL's independent review. The Working Group acknowledged that the committee was not able to fully serve its purpose in the ICANN structure because of lack of regular communication between ICANN and RSSAC, the committee has insufficient knowledge about ICANN and vice versa, the role and responsibilities of RSSAC as stipulated in the ICANN Bylaws need amendment and the shared understanding between the RSSAC role, Root Server Operators responsibilities and the ICANN mission is not clear. The Working Group recommended that the full cooperation of the Root Server Operators is necessary to implement structural and operational changes to improve the operations of RSSAC.[11]
Advisories edit
At its regular meeting in November 2014, the RSSAC formally approved RSSAC001 and RSSAC002, the first two formal advisories produced under its reorganized structure. RSSAC001 defines the best practice service to be provided by root servers and defines the operational expectations that users might reasonably anticipate of both that service and the root server operators. This document highlights that a diversity of approach is desirable in the root server system.[12]
RSSAC002 "identifies and recommends an initial set of parameters that would be useful to monitor for establishing a baseline and trends for the root server system. The implementation of these measurements (and future refinements to them) by root server operators will form an early warning system that will assist in detecting and mitigating any effects (or the absence of such effects) associated with growing size of the root zone."[13]
2017-19 Independent Review of RSSAC by Interisle Consulting Group, LLC edit
Pursuant to Article 4, Section 4.4 of the ICANN Bylaws, ICANN initiated a second RSSAC independent review process on April 19, 2017.[14] ICANN drafted and distributed a Request for Proposals for this review.[15]
Scope of Review edit
In both the announcement and the RFP, ICANN presented a broad scope of subjects for review. For example, the announcement stated that the goal was a "comprehensive assessment" of the RSSAC, "includ[ing], but [...] not limited to:
- The continued purpose of RSSAC within the ICANN structure;
- How effectively RSSAC fulfills its purpose;
- Whether any change in structure or operations is needed; and
- The extent to which RSSAC as a whole is accountable to the wider ICANN community."[16]
The RFP echoed the need to investigate those issues, and also provided a "non-comprehensive" list of proposed questions to be addressed regarding the RSSAC's composition, mission, procedures, transparency, and communication.[17] On April 18, 2017, on behalf of RSSAC, Carlos Reyes submitted comments to ICANN requesting more specificity in some of the proposed questions.[18] However, in correspondence back to the RSSAC, ICANN submitted a draft "Self Assessment" tool for the committee utilizing the RFP's proposed questions as part of the assessment template, with changes to some questions that appear to align with the RSSAC requests.[19]
After accepting and reviewing proposals through the RFP process, ICANN contracted with Interisle Consulting Group, LLC to conduct the second independent review of RSSAC.[20] Interisle assembled a team of three consultants for the review, Lyman Chapin, Jim Reid, and Colin Strutt[21]
Review Methodology & Data Sources edit
Interisle's review included attendance at RSSAC meetings, ICANN Meeting sessions, and conference calls during the autumn of 2017 and winter of 2018.[22] In addition, they conducted 48 interviews with individuals connected to or working within the RSSAC.[22] At the end of 2017, Interisle conducted an online survey "to collect input from those who have interacted with RSSAC and/or have ideas for ways to improve it."[23] In addition to publishing notice of the survey, ICANN specifically solicited responses from the RSSAC Caucus.[22] The survey, which did not require participants to identify themselves, garnered 74 visits and 39 responses.[22]
Other data utilized by Interisle came from:
- RSSAC's Self-Assessment, completed in September 2017;[24][25]
- publicly available documents from a wide variety of sources that discuss the RSSAC and related activities; and
- Interisle's "own extensive knowledge of ICANN, the RSSAC, and the DNS root server system."[22]
Interisle subjected this data to a structured qualitative analysis[26] and presented its findings in an initial Assessment Report to ICANN.[27]
Response to Assessment Report edit
Public comment was solicited on the Assessment Report.
On May 1, 2018, ICANN and Interisle issued a Draft Final Report for public comment.[28]
RSSAC Working Group edit
The RSSAC Working Group is composed of:
References edit
- ↑ Root Server System Advisory Committee
- ↑ www.icann.org
- ↑ CRADA
- ↑ www.icann.org
- ↑ RSSAC Statement on Root Nameserver Year 2000 Status
- ↑ ICANN Bylaws 2002
- ↑ Request For Proposals
- ↑ RSSAC Review
- ↑ WCL Final Report
- ↑ Final Report Independent Review on RSSAC
- ↑ RSSAC Working Group Final Report
- ↑ ICANN RSSAC approves advisories on service expectations Domainpulse, Retrieved 17th December 2014.
- ↑ ICANN RSSAC approves advisories on service expectations Domainpulse, Retrieved 17th December 2014.
- ↑ Approved Board Resolutions - ICANN Special Board Meeting, April 19, 2017
- ↑ Request for Proposal for the RSSAC Organizational Review
- ↑ Request for Proposal for the RSSAC Organizational Review
- ↑ [https://www.icann.org/en/system/files/files/rfp-rssac-review-05jun17-en.pdf Project Overview to the Request for Proposal For REVIEW OF THE ICANN Root Server System Advisory Committee - June 5, 2017 (PDF)]
- ↑ Email: Carlos Reyes to Lars Hoffman, April 18 2017
- ↑ Email: Angie Graves to RSSAC-Review2 listserv, May 4, 2017
- ↑ ICANN Announcement of Selection of Independent Examiner, Interisle - September 28, 2017
- ↑ ICANN's RSAAC2 Dashboard - Independent Examiner
- ↑ 22.0 22.1 22.2 22.3 22.4 Independent Review of the ICANN Root Server System Advisory Committee: Final Report; July 2, 2018 (PDF)
- ↑ ICANN Announcement of RSSAC Survey - November 27, 2017
- ↑ Email: Carlos Reyes to MSSI staff, September 8, 2017
- ↑ RSSAC Organizational Review 2: Self-Assessment (PDF)
- ↑ For a primer on structured qualitative analysis, see Herz, Peters, & Truschkat: "How to Do Qualitative Structural Analysis: The Qualitative Interpretation of Network Maps and Narrative Interviews;" Forum: Qualitative Social Research, Vol. 16 No. 1, January 2015
- ↑ RSSAC2 Review: Assessment Report Published - ICANN announcement, February 27, 2018
- ↑ Draft Final Report for Public Comment