Changes

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