Root Server System Advisory Committee
The Root Server System Advisory Committee (RSSAC) was created under the Article VII Section 3 (b) of the ICANN Bylaws which gave ICANN Board the mandate to appoint the initial Chairman of the Committee, after which the following chairman will be elected by the members of the committee. Jun Murai, who was one of the nine initial directors of the ICANN Board in 1998 was appointed chairman of RSSAC.[1]
Responsibility edit
RSSAC was delegated to advise the ICANN Board regarding the operational requirements of the root name servers of the Domain Name System (DNS) which include hardware capacities, operating systems, name server versions, network connectivity, physical environment as well as its security aspects. RSSAC was also tasked to review the number, location, and distribution of the root name server and its total system performance, robustness, and reliability.[2]
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 is to make sure that the operations of the root nameserver system is in compliance with Y2K by conducting administrative services and testing.[5]
The committee is also conducting new technical developments on IPv6, DNSSEC, and IDN and their effects to the root nameserver system.
WCL Independent Review on RSSAC 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 of if certain changes in the structure or operations is necessary to improve its functions.[6] To be able to comply with the Bylaws, the ICANN Board issued a Request For Proposal (RFP) and Terms of Reference (TOR) to conduct and independent review on RSSAC on July 2008.[7] ICANN selected Westlake Consulting Limited (WCL) and on 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 provide 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.
- RSAAC 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 is 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
RSSAC Working Group edit
The RSSAC Working Group is composed of: