3,197
edits
Changes
Jump to navigation
Jump to search
Line 202:
Line 202: + + + + + + + + + + +
Root Server System Advisory Committee (view source)
Revision as of 17:08, 10 December 2020
, 3 years agorestoration work - RSSAC2
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>
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>
===Findings===
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 RSSAC has become more open, transparent, and accessible since the last review, but this has not been widely recognized by outside observers.
# As the only visible interface between ICANN and the RSOs, the RSSAC is expected to deal with every root service issue that arises within ICANN, whether or not the issue is properly within its scope.
# The RSSAC’s ability to serve as a shared space for RSO–ICANN communication and cooperation is complicated by a persistent legacy of distrust of ICANN by some of its members.
# The current RSSAC membership model excludes non-RSO participants and their different skills and perspectives.
# 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.
# 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===