3,197
edits
Changes
Jump to navigation
Jump to search
Line 218:
Line 218: − + + + + + + + + + + + +
Root Server System Advisory Committee (view source)
Revision as of 19:56, 11 December 2020
, 3 years agono edit summary
<blockquote>And this reflects a process that MSSI has fairly recently adopted for doing organizational reviews, which is to divide them into two distinct phases. The first phase is an assessment phase in which the idea is not to anticipate what recommendations might be made but simply to report on what the independent examiner found after conducting interviews, and surveys, and document reviews, and so forth.<ref name="icann61transcript'>[https://static.ptbl.co/static/attachments/172550/1523576427.pdf?1523576427 Transcript of RSSAC Organizational Review Session at ICANN 61]</ref> </blockquote>Chapin presented the principal findings at the ICAAN 61 meeting, and received no questions from the attendees.<ref name="icann61transcript" />
<blockquote>And this reflects a process that MSSI has fairly recently adopted for doing organizational reviews, which is to divide them into two distinct phases. The first phase is an assessment phase in which the idea is not to anticipate what recommendations might be made but simply to report on what the independent examiner found after conducting interviews, and surveys, and document reviews, and so forth.<ref name="icann61transcript'>[https://static.ptbl.co/static/attachments/172550/1523576427.pdf?1523576427 Transcript of RSSAC Organizational Review Session at ICANN 61]</ref> </blockquote>Chapin presented the principal findings at the ICAAN 61 meeting, and received no questions from the attendees.<ref name="icann61transcript" />
On
On March 28, 2018, RSSAC issued '''RSSAC032:''' Feedback on the Independent Review of the Root Server System Advisory Committee (RSSAC) Assessment Report for Public Consultation.<ref name="assessfb">[https://www.icann.org/en/system/files/files/rssac-032-28mar18-en.pdf RSSAC032]</ref> RSSAC032 begins with a discussion of the [[ICANN Bylaws]] and the committees expectation of the focus of the review:
<blockquote>RSSAC’s interpretation of the stated assessment report’s purpose is that an organizational review would look at the organization – its chairs, its procedures, its guiding documents including charter and bylaws, its meetings, and the publications it has produced.<ref name="assessfb" /></blockquote>
This interpretation substantially diminished the scope of ICANN's announcement of the review, and the parameters defined in the RFP.
Based on that narrow definition of scope, the committee found "three...surprising categories of findings" that they viewed as outside the purpose of the review:
<blockquote>However, we found that the initial assessment report included three additional surprising categories of findings.
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.
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>
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 hew to the central tenets of that charter, the ICANN Bylaws, and RSSAC's "structure and procedures, <nowiki>[...]</nowiki> in line with relevant process documents and bylaws."
On May 1, 2018, ICANN and Interisle issued a 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, ICANN and Interisle issued a 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>