Changes

==Responsibilities==

==Responsibilities==

RSSAC has the following responsibilities, per the ICANN bylaws:

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

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

# Report periodically to the Board on its activities.

# Report periodically to the Board on its activities.

# Make policy recommendations to the ICANN community and Board.

# Make policy recommendations to the ICANN community and Board.

==Structure==

==Structure==

===Representatives===

===Representatives===

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 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 [[RSSAC Caucus]] provides a pool of expertise, to which the representatives of the 13 root name servers can turn to form work parties and draft advice documents.  

The current composition is available at [https://www.icann.org/groups/rssac/ RSSAC's official web page].   

The current composition is available at [https://www.icann.org/groups/rssac/ RSSAC's official web page].   

|N/A

|N/A

|-

|-

|[[University of Southern California]]

|[[University of Southern California – Information Sciences Institute]]

|[[User:Hardaker|Wes Hardaker]]

|[[Wes Hardaker]]

|31 December 2023

|31 December 2023

|[[Suzanne Woolf]]

|[[Suzanne Woolf]]

|[[Brad Belanger]]

|[[Brad Belanger]]

|-

|-

|[[University of Maryland]]

|[[University of Maryland – ACIGS]]

|[[Karl Reuss]]

|[[Karl Reuss]]

|31 December 2022

|31 December 2022

|[[Gerry Sneeringer]]

|[[Gerry Sneeringer]]

|-

|-

|[[NASA]]

|[[NASA Ames Research Center]]

|[[Barbara Schleckser]]

|[[Barbara Schleckser]]

|31 December 2022

|31 December 2022

|[[Tom Miglin]]

|[[Tom Miglin]]

|-

|-

|[[Internet Consortium]]

|[[Internet Systems Consortium]]

|[[Fred Baker]] (Chair)

|[[Fred Baker]] (Chair)

|31 December 2021

|31 December 2021

|[[Jeff Osborn]]

|[[Jeff Osborn]]

|-

|-

|[[US Department of Defense]]

|[[Defense Information Systems Agency]]

|[[Kevin Wright]]

|[[Kevin Wright]]

|31 December 2022

|31 December 2022

|[[Ryan Stephenson]]

|[[Ryan Stephenson]]

|-

|-

|[[US Army Research Labratory]]

|[[U.S. Army Research Lab]]

|[[Howard Kash]]

|[[Howard Kash]]

|31 December 2022

|31 December 2022

|[[Hiro Hotta]]

|[[Hiro Hotta]]

|}

|}

{| class="wikitable"

{| class="wikitable"

!Partner Representative

! Organization || Liaison

|-

|-

|IANA Functions Operator

| [[IANA]] || [[James Mitchell]]

|[[James Mitchell]]

|-

|-

|<abbr>Root Zone</abbr> Maintainer

| [[Root Zone|Root Zone Maintainer]] ([[Verisign]]) || [[Duane Wessels]]

|[[Duane Wessels]]

 

|-

|-

|[[Internet Architecture Board]]

| Internet Architecture Board ([[IAB]]) || [[Daniel Migault]]

|[[Daniel Migault]]

|-

|-

|[[SSAC|Security and Stability Advisory Committee (SSAC)]]

| [[SSAC]] || [[Russ Mundy]]

|[[Russ Mundy]]

 

|}

|}

===RSSAC Liaisons to Other Organizations===

 

===Liaisons from RSSAC to Other Organizations===

RSSAC appoints liaisons to other groups and organizations to coordinate or communicate matters of common interest, as required by the [[RSSAC Operational Procedures]]

RSSAC appoints liaisons to other groups and organizations to coordinate or communicate matters of common interest, as required by the [[RSSAC Operational Procedures]]

{| class="wikitable"

{| class="wikitable"

!Affiliation

!Affiliation

|-

|-

|ICANN Board of Directors

|[[ICANN Board|ICANN Board of Directors]]

|[[Kaveh Ranjbar]]

|[[Kaveh Ranjbar]]

|RIPE NCC

|[[RIPE NCC]]

|-

|-

|Customer Standing Committee

|[[Customer Standing Committee]]

|[[Lars-Johan Liman]]

|[[Lars-Johan Liman]]

|

|[[Netnod]]

|-

|-

|Root Zone Evolution Review Committee

|[[Root Zone Evolution Review Committee]]

|[[Daniel Migault]]

|[[Daniel Migault]]

|

|[[IAB]]

|-

|-

|ICANN Nominating Committee

|[[NomCom|ICANN Nominating Committee]]

|[[Amir Qayyum]]

|[[Amir Qayyum]]

|

|[[ICANN]]

 

 

 

|}

|}

Since its inception, the committee continuously performs projects under a Cooperative Research and Development Agreement (CRADA)<ref>[http://www.icann.org/en/committees/dns-root/crada.htm CRADA]</ref> between [[ICANN]], the [[NIST|National Institute for Standards and Technology]] (NIST), and [[NTIA|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.<ref>[http://www.icann.org/en/committees/dns-root/ www.icann.org]</ref>

Since its inception, the committee continuously performs projects under a Cooperative Research and Development Agreement (CRADA)<ref>[http://www.icann.org/en/committees/dns-root/crada.htm CRADA]</ref> between [[ICANN]], the [[NIST|National Institute for Standards and Technology]] (NIST), and [[NTIA|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.<ref>[http://www.icann.org/en/committees/dns-root/ www.icann.org]</ref>

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.<ref>[http://www.icann.org/en/committees/dns-root/y2k-statement.htm RSSAC Statement on Root Nameserver Year 2000 Status]</ref>

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 are in compliance with the Y2K protocol by conducting administrative services and testing.<ref>[http://www.icann.org/en/committees/dns-root/y2k-statement.htm RSSAC Statement on Root Nameserver Year 2000 Status]</ref>

The committee is also conducting new technical developments on [[IPv6]], [[DNSSEC]], [[IDN]], and their effects to the root nameserver system.

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

== 2008-9 Independent Review of RSSAC by Westlake Consulting Limited==

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>

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

[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 an 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===

* 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 are 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 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 organizations 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 meetings in conjunction with the meetings of the [[IETF]].

===Recommendations===

===Recommendations===

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 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 should be composed of 4 Root Server Operators, 1 appointed by [[IANA]]; and 4 appointed by the  ICANN Board/[[NomCom|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 year term, with a limited three consecutive 2-years terms.

* 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 an 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 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===

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.<ref>[http://192.0.43.22/en/reviews/rssac/rssac-review-final-report-08jun10-en.pdf RSSAC Working Group Final Report]</ref>

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.<ref>[http://192.0.43.22/en/reviews/rssac/rssac-review-final-report-08jun10-en.pdf RSSAC Working Group Final Report]</ref>

===Advisories===

===Advisories===

At its regular meeting in November 2014, the RSSAC formally approved RSSAC001 and RSSAC002, the first two formal advisories produced under its reorganized structure.  

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.<ref>[http://www.domainpulse.com/2014/12/10/icann-rssac-approves-advisories-service-expectations/ ICANN RSSAC approves advisories on service expectations] Domainpulse, Retrieved 17th December 2014.</ref>

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 approaches is desirable in the root server system.<ref>[http://www.domainpulse.com/2014/12/10/icann-rssac-approves-advisories-service-expectations/ ICANN RSSAC approves advisories on service expectations] Domainpulse, Retrieved 17th December 2014.</ref>

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."<ref>[http://www.domainpulse.com/2014/12/10/icann-rssac-approves-advisories-service-expectations/ ICANN RSSAC approves advisories on service expectations] Domainpulse, Retrieved 17th December 2014.</ref>

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 the growing size of the root zone."<ref>[http://www.domainpulse.com/2014/12/10/icann-rssac-approves-advisories-service-expectations/ ICANN RSSAC approves advisories on service expectations] Domainpulse, Retrieved 17th December 2014.</ref>

==2017-19 Independent Review of RSSAC by Interisle Consulting Group, LLC==

==2017-19 Independent Review of RSSAC by Interisle Consulting Group, LLC==

After accepting and reviewing proposals through the RFP process, [[ICANN]] contracted with [[Interisle Consulting Group, LLC]] to conduct the second independent review of RSSAC.<ref>[https://www.icann.org/news/announcement-2017-09-28-en ICANN Announcement of Selection of Independent Examiner, Interisle - September 28, 2017]</ref> Interisle assembled a team of three consultants for the review, [[Lyman Chapin]], [[Jim Reid]], and [[Colin Strutt]]<ref>[https://community.icann.org/display/ACCRSSAC/Independent+Examiner ICANN's RSAAC2 Dashboard - Independent Examiner]</ref>

After accepting and reviewing proposals through the RFP process, [[ICANN]] contracted with [[Interisle Consulting Group, LLC]] to conduct the second independent review of RSSAC.<ref>[https://www.icann.org/news/announcement-2017-09-28-en ICANN Announcement of Selection of Independent Examiner, Interisle - September 28, 2017]</ref> Interisle assembled a team of three consultants for the review, [[Lyman Chapin]], [[Jim Reid]], and [[Colin Strutt]]<ref>[https://community.icann.org/display/ACCRSSAC/Independent+Examiner ICANN's RSAAC2 Dashboard - Independent Examiner]</ref>

===Review Methodology & Data Sources===

===Assessment Report & Findings===

Interisle's review included attendance at RSSAC meetings, [[ICANN Meeting]] sessions, and conference calls during the autumn of 2017 and winter of 2018.<ref name="finalreport2">[https://www.icann.org/en/system/files/files/rssac-review-final-02jul18-en.pdf Independent Review of the ICANN Root Server System Advisory Committee: Final Report; July 2, 2018 (PDF)]</ref> In addition, they conducted 48 interviews with individuals connected to or working within the RSSAC.<ref name="finalreport2" /> 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."<ref>[https://www.icann.org/news/announcement-2017-11-27-en ICANN Announcement of RSSAC Survey - November 27, 2017]</ref> In addition to publishing notice of the survey, ICANN specifically solicited responses from the [[RSSAC Caucus]].<ref name="finalreport2" /> The survey, which did not require participants to identify themselves, garnered 74 visits and 39 responses.<ref name="finalreport2" />

Interisle's review included attendance at RSSAC meetings, [[ICANN Meeting]] sessions, and conference calls during the autumn of 2017 and winter of 2018.<ref name="finalreport2">[https://www.icann.org/en/system/files/files/rssac-review-final-02jul18-en.pdf Independent Review of the ICANN Root Server System Advisory Committee: Final Report; July 2, 2018 (PDF)]</ref> In addition, they conducted 48 interviews with individuals connected to or working within the RSSAC.<ref name="finalreport2" /> 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."<ref>[https://www.icann.org/news/announcement-2017-11-27-en ICANN Announcement of RSSAC Survey - November 27, 2017]</ref> In addition to publishing notice of the survey, ICANN specifically solicited responses from the [[RSSAC Caucus]].<ref name="finalreport2" /> The survey, which did not require participants to identify themselves, garnered 74 visits and 39 responses.<ref name="finalreport2" />

* Interisle's "own extensive knowledge of ICANN, the RSSAC, and the DNS root server system."<ref name="finalreport2" />  

* Interisle's "own extensive knowledge of ICANN, the RSSAC, and the DNS root server system."<ref name="finalreport2" />  

Interisle subjected this data to a structured qualitative analysis<ref>[https://www.qualitative-research.net/index.php/fqs/article/view/2092/3904 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]</ref> and presented its findings in an initial Assessment Report to ICANN.<ref>[https://www.icann.org/news/announcement-2018-02-27-en RSSAC2 Review: Assessment Report Published - ICANN announcement, February 27, 2018]</ref> The draft assessment report was the topic of meetings between members of RSSAC's Review Work Party and Interisle's consultants.<ref>[https://participate.icann.org/p2zrcgd41jl/ Recording of RSSAC Review2 Work Party, February 15, 2018]</ref><ref>[https://community.icann.org/display/ACCRSSAC/RSSAC+Work+Party+Meetings The RSSAC Work Party Meetings Archive] lists a meeting on February 20, intended to cover feedback provided by the RWP. However, a recording is presently not available.</ref>

Interisle subjected this data to a structured qualitative analysis<ref>For a primer on structured qualitative analysis, see [https://www.qualitative-research.net/index.php/fqs/article/view/2092/3904 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]</ref> and presented its findings in an Initial Assessment Report to ICANN.<ref>[https://www.icann.org/news/announcement-2018-02-27-en RSSAC2 Review: Assessment Report Published - ICANN announcement, February 27, 2018]</ref> The draft assessment report was the topic of meetings between members of RSSAC's Review Work Party and Interisle's consultants.<ref>[https://participate.icann.org/p2zrcgd41jl/ Recording of RSSAC Review2 Work Party, February 15, 2018]</ref><ref>[https://community.icann.org/display/ACCRSSAC/RSSAC+Work+Party+Meetings The RSSAC Work Party Meetings Archive] lists a meeting on February 20, intended to cover feedback provided by the RWP. However, a recording is presently not available.</ref>

The Assessment Report listed a total of forty-two findings in response to the issues and questions posed by ICANN.<ref name="assessment">[https://www.icann.org/en/system/files/files/rssac-review-assessment-report-22feb18-en.pdf RSSAC Review - Assessment Report for Public Consultation]</ref> Of these, Interisle identified eight principal findings, which they highlighted in the report and its executive summary<ref>[https://www.icann.org/en/system/files/files/rssac-review-assessment-report-exec-summary-22feb18-en.pdf]</ref> of the assessment:

The Assessment Report listed a total of forty-two findings in response to the issues and questions posed by ICANN.<ref name="assessment">[https://www.icann.org/en/system/files/files/rssac-review-assessment-report-22feb18-en.pdf RSSAC Review - Assessment Report for Public Consultation]</ref> Of these, Interisle identified eight principal findings, which they highlighted in the report and its executive summary<ref>[https://www.icann.org/en/system/files/files/rssac-review-assessment-report-exec-summary-22feb18-en.pdf]</ref> of the assessment:

# The ongoing RSSAC reformation that began in 2013—revised RSSAC charter, new operating procedures, and creation of the RSSAC Caucus—has substantially improved the structure and operation of the RSSAC.

# The ongoing RSSAC reformation that began in 2013—revised RSSAC charter, new operating procedures, and creation of the RSSAC Caucus—has substantially improved the structure and operation of the RSSAC.

# The RSSAC’s continuing purpose in the ICANN structure may include serving as the focal point for issues of mutual concern to ICANN and the RSOs, such as future operational and funding scenarios for serving the root.

# The RSSAC’s continuing purpose in the ICANN structure may include serving as the focal point for issues of mutual concern to ICANN and the RSOs, such as future operational and funding scenarios for serving the root.

# Because RSSAC members do not agree on who its stakeholders should be, it is not clear for what and to whom it should be accountable.

# Because RSSAC members do not agree on who its stakeholders should be, it is not clear for what and to whom it should be accountable.

# The relative roles and responsibilities of the RSSAC, the RSSAC Caucus, the RZERC, and the SSAC are unclear to both outsiders and insiders.<ref name="assessment" />  

# The relative roles and responsibilities of the RSSAC, the RSSAC Caucus, the RZERC, and the SSAC are unclear to both outsiders and insiders.<ref name="assessment" />

===Response to Assessment Report===

===Response to Assessment Report===

i. Out of Scope Findings: Findings related to items that RSSAC could never include within its charter, such as items related to the technical day-to-day operation of the Root Server System (RSS) or the confusion surrounding a contributor’s lack of understanding of multiple ICANN bodies such as SSAC.

i. Out of Scope Findings: Findings related to items that RSSAC could never include within its charter, such as items related to the technical day-to-day operation of the Root Server System (RSS) or the confusion surrounding a contributor’s lack of understanding of multiple ICANN bodies such as SSAC.

ii. Factually Incorrect Findings: Findings that are factually incorrect about RSSAC and/or the RSS.

ii. Factually Incorrect Findings: Findings that are factually incorrect about RSSAC and/or the RSS.

iii. Tone: Findings and tone related to public opinion and sensational anonymous quotes about RSSAC or its purpose, but not providing any other insight.<ref name="assessfb" /><ref>RSSAC's surprise at "out of scope findings" is contrary to its behavior prior to this response. For example, it asked for clarity regarding certain questions in the Self Assessment, rather than a "narrowing of scope." The [http://mm.icann.org/pipermail/rssac-review2/attachments/20170908/af910e0d/RSSACOrganizationalReview2Self-Assessment.pdf Self Assessment] prepared and submitted by the committee in September 2017 does not contain objections to scope, except in response to some questions where it refers some questions to ICANN (presumably because those are not within RSSAC's charter to address and improve independently).</ref></blockquote>

iii. Tone: Findings and tone related to public opinion and sensational anonymous quotes about RSSAC or its purpose, but not providing any other insight.<ref name="assessfb" /></blockquote>

The committee argued that it is only empowered to do that which is within its [[RSSAC Charter|charter]], and that any findings or recommendations should specifically address the tenets of that charter, the ICANN Bylaws, and RSSAC's "structure and procedures, <nowiki>[...]</nowiki> in line with relevant process documents and bylaws."

The committee argued that it is only empowered to do that which is within its [[RSSAC Charter|charter]], and that any findings or recommendations should specifically address the tenets of that charter, the ICANN Bylaws, and RSSAC's "structure and procedures, <nowiki>[...]</nowiki> in line with relevant process documents and bylaws."

===Final Report & Recommendations===

===Final Report & Recommendations===

On May 1, 2018, ICANN and Interisle issued the Draft Final Report for public comment.<ref>[https://www.icann.org/public-comments/rssac2-review-final-2018-05-01-en Draft Final Report for Public Comment]</ref>  

 

 

On May 1, 2018, Interisle released its Draft Final Report for public comment.<ref>[https://www.icann.org/public-comments/rssac2-review-final-2018-05-01-en Draft Final Report for Public Comment]</ref>

# Clarify the role and responsibility of the RSSAC with respect to other groups with adjacent or overlapping remits, including the SSAC, the RZERC, and the RSSAC Caucus.<ref>[https://www.icann.org/en/system/files/files/rssac-review-final-02jul18-en.pdf RSSAC Organizational Review Final Report (PDF)]</ref>

==RSSAC Working Group==

The Draft Final Report received public comments from a variety of sources. On June 8, 2018, RSSAC published '''RSSAC036''': RSSAC Statement on the Draft Final Report of the Second Organizational Review of the RSSAC.<ref>[https://www.icann.org/en/system/files/files/rssac-036-14jun18-en.pdf RSSAC Statement on the Draft Final Report of the Second Organizational Review of the RSSAC (PDF)]</ref> The RSSAC repeated its objections to the scope and focus of the review in its statement. [[ALAC]] published a response that commented on three of the proposed recommendations.<ref>[https://atlarge.icann.org/advice_statements/11539 ALAC Statement Regarding RSSAC Organizational Review]</ref> Notably, its response to Recommendation 2 strongly favored action to ensure that ICANN had a sufficiently robust relationship with [[RSO|RSOs]]:

The RSSAC Working Group is composed of:

<blockquote>Although there is no clear way to address the issue, since ICANN has a part to play in ensuring that the DNS is a trusted and reliable resource, then it must have the ability to interact with all players who have a role in carrying that out and that must include the Root Server Operators. Simply lowering expectations does not address the issue. Whether this is done by widening the scope of the RSSAC or through some other mechanism is less important than noting that the current chasm must be bridged.<ref>[https://community.icann.org/download/attachments/84219445/AL-ALAC-ST-0618-01-01-EN.pdf?version=1&modificationDate=1546864796000&api=v2 Draft Statement of ALAC - ratified without change (PDF)]</ref></blockquote>

* [[Harald Alvestrand]]

The [[BC|Business Constituency]] agreed: "The BC requests that this recommendation be prioritized, noting it is 'highly concerned...that RSSAC does not consider itself accountable to ICANN Board and Community.<ref>[https://www.icann.org/en/system/files/files/report-comments-rssac2-review-final-15jun18-en.pdf Summary Report of Public Comment Proceeding, p.4 (PDF)]</ref>'"

* [[Steve Crocker]]

 

* [[Bruce Tonkin]]

RSSAC, for its part, "conclude<nowiki>[d]</nowiki> that neither the ICANN Board nor the ICANN community harbor the mismatch raised in the draft final report."<ref>[https://www.icann.org/en/system/files/files/rssac-036-14jun18-en.pdf RSSAC Statement on the Draft Final Report of the Second Organizational Review of the RSSAC, p. 4 (PDF)]</ref>

 

After the public comment period closed, the draft final report was a topic of an open session at ICANN 62.<ref name="icann62">[https://participate.icann.org/p4ynjd8bp6s/ Adobe Connect Archive - ICANN 62]</ref> Interisle released its final report on July 2, 2018.<ref>[https://www.icann.org/en/system/files/files/rssac-review-final-02jul18-en.pdf RSSAC Organizational Review Final Report (PDF)]</ref>

 

The [[ICANN Board]] instructed RSSAC to develop a Feasibility Assessment & Initial Implementation Plan in the wake of the publication of the Final Report.<ref name="icann62" /> The RWP released its plan on October 2, 2018.<ref name="faiip">[https://www.icann.org/en/system/files/files/rssac2-review-faiip-02oct18-en.pdf RSSAC2 Review - Feasibility Assessment & Initial Implementation Plan]</ref>

==References==

==References==

__FORCETOC__

__FORCETOC__

[[Category: ICANN Bodies]]

[[Category: ICANN Bodies]]