Difference between revisions of "Root Server System Advisory Committee"

From ICANNWiki
Jump to navigation Jump to search
Line 12: Line 12:
  
 
== WCL Independent Review on RSSAC==
 
== WCL Independent Review on RSSAC==
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.<ref>
+
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.<ref>
[http://www.icann.org/en/general/archive-bylaws/bylaws-15dec02.htm#IV ICANN Bylaws 2002]</ref> 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.<ref>[http://192.0.43.22/en/reviews/rssac/rfp-tor-request-11jul08-en.htm Request For Proposals]</ref> 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. <ref>[http://192.0.43.22/en/reviews/rssac/ RSSAC Review]</ref>
+
[http://www.icann.org/en/general/archive-bylaws/bylaws-15dec02.htm#IV ICANN Bylaws 2002]</ref> 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.<ref>[http://192.0.43.22/en/reviews/rssac/rfp-tor-request-11jul08-en.htm Request For Proposals]</ref> 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. <ref>[http://192.0.43.22/en/reviews/rssac/ RSSAC Review]</ref>
  
 
===Findings===
 
===Findings===
 
By April of 2009, WCL published its final report on the Independent Review on RSSAC with the following findings:<ref>[http://192.0.43.22/en/reviews/rssac/rssac-review-final-mar09-en.pdf WCL Final Report]</ref>
 
By April of 2009, WCL published its final report on the Independent Review on RSSAC with the following findings:<ref>[http://192.0.43.22/en/reviews/rssac/rssac-review-final-mar09-en.pdf WCL Final Report]</ref>
* RSSAC only provide reactions to issues instead of regularly giving updates to the ICANN Board regarding the activities and functions of the committee.
+
* 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.
 
* 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.
 
* 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 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 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.
+
* 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]].
 
* 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]].
  
Line 28: Line 28:
 
Based on its final report, WCL recommended the following to improve the operational functions of RSSAC:<ref>[http://192.0.43.22/en/reviews/rssac/rssac-review-final-mar09-en.pdf Final Report Independent Review on RSSAC]</ref>
 
Based on its final report, WCL recommended the following to improve the operational functions of RSSAC:<ref>[http://192.0.43.22/en/reviews/rssac/rssac-review-final-mar09-en.pdf Final Report Independent Review on RSSAC]</ref>
 
* Re-establish RSSAC as a strategy group which will be jointly supervised by ICANN and Root Server Operators.
 
* 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 which is to 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."  
+
* 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 shall shall be composed of composed of 4 Root Server Operators, 1 appointed by IANA; and 4 appointed by the  ICANN Board/[[Nominating Committee]].
+
* 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/[[NomCom|Nominating Committee]].
* The Chairman of the committee shall be appointed by its members with a two years term with a limited three consecutive 2-years term.
+
* 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]].
+
* 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 maybe 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 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==
 
==RSSAC Working Group Review on WCL Report==

Revision as of 22:24, 1 August 2011

The Root Server System Advisory Committee (RSSAC) 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 chairman of RSSAC.[1]

Responsibility[edit | edit source]

RSSAC was delegated to advise the ICANN Board regarding the operational requirements of the root name servers of the Domain Name System (DNS), which includes 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 | edit source]

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.

WCL Independent Review on RSSAC[edit | edit source]

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 | edit source]

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.
  • 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 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 | edit source]

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 | edit source]

On 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 needs 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]

RSSAC Working Group[edit | edit source]

The RSSAC Working Group is composed of:

References[edit | edit source]