Changes

At the time that GNSO2 was initiated, the [[Organizational Effectiveness Committee|Structural Improvements Committee]] (as it was then known) was engaged in a discussion regarding the [[ICANN Reviews#2014-15 Standardization Efforts|standardization and streamlining of reviews]]. Ray Plzak's observation, above, that independent examiners were "charging around" appeared to be part of the impetus for implementing a standard framework for reviews and closely guiding the activities of the independent examiners. It also appears that GNSO2 was in some ways a pilot project for a new, restrictive, set of guidelines regarding the scope and intent or the review.<ref>For more background on the SIC's efforts at the time, see ICANNWiki's [[ICANN Reviews#2014-15 Standardization Efforts|ICANN Reviews]] article</ref>

At the time that GNSO2 was initiated, the [[Organizational Effectiveness Committee|Structural Improvements Committee]] (as it was then known) was engaged in a discussion regarding the [[ICANN Reviews#2014-15 Standardization Efforts|standardization and streamlining of reviews]]. Ray Plzak's observation, above, that independent examiners were "charging around" appeared to be part of the impetus for implementing a standard framework for reviews and closely guiding the activities of the independent examiners. It also appears that GNSO2 was in some ways a pilot project for a new, restrictive, set of guidelines regarding the scope and intent or the review.<ref>For more background on the SIC's efforts at the time, see ICANNWiki's [[ICANN Reviews#2014-15 Standardization Efforts|ICANN Reviews]] article</ref>

===NCPH Objection to Scope, January 2014===

===NCPH Objection to Scope, January 2015===

In January 2014, during the course of the review, the [[Non-Contracted Parties House]] of the GNSO met to discuss a variety of issues relevant to its constituency. Among those issues was the scope and focus of the GNSO2 review. The result was a letter to the ICANN Board regarding the failure of the review to address structural issues.<ref name="ncphletter">[https://www.icann.org/en/system/files/correspondence/ncph-participants-to-icann-board-16jan15-en.pdf ICANN.org Archive - NCPH Letter to ICANN Board], January 16, 2015</ref> In contradiction to Ray Plzak's position, above, the NCPH urged the Board to address the GNSO's structural issues:

In January 2015, during the course of the review, the [[Non-Contracted Parties House]] of the GNSO met to discuss a variety of issues relevant to its constituency. Among those issues was the scope and focus of the GNSO2 review. The result was a letter to the ICANN Board regarding the failure of the review to address structural issues.<ref name="ncphletter">[https://www.icann.org/en/system/files/correspondence/ncph-participants-to-icann-board-16jan15-en.pdf ICANN.org Archive - NCPH Letter to ICANN Board], January 16, 2015</ref> In contradiction to Ray Plzak's position, above, the NCPH urged the Board to address the GNSO's structural issues:

<blockquote>What is required is a thorough review of the current GNSO structure that takes full account of the evolution of the DNS and the interaction that is required between those players who have a major role to play in GNSO policy development. Without recognition of the need to undertake this exercise and commit to a program that is developed with the full cooperation of all impacted parties, an important part of ICANNs multi-stakeholder model will continue to be viewed as dysfunctional by many of those who remain committed to try and deliver coherent and progressive policy within the current structural architecture of the GNSO.<ref name="ncphletter" /></blockquote>

<blockquote>What is required is a thorough review of the current GNSO structure that takes full account of the evolution of the DNS and the interaction that is required between those players who have a major role to play in GNSO policy development. Without recognition of the need to undertake this exercise and commit to a program that is developed with the full cooperation of all impacted parties, an important part of ICANNs multi-stakeholder model will continue to be viewed as dysfunctional by many of those who remain committed to try and deliver coherent and progressive policy within the current structural architecture of the GNSO.<ref name="ncphletter" /></blockquote>