<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Im sure some of you have seen this but important for everyone to read this.
<div class=""><br class="">
</div>
<div class=""><a href="https://www.icann.org/en/system/files/correspondence/faltstrom-to-icann-board-03oct17-en.pdf" class="">https://www.icann.org/en/system/files/correspondence/faltstrom-to-icann-board-03oct17-en.pdf</a></div>
<div class=""><br class="">
</div>
<div class="">I copy the core text below:</div>
<div class=""><br class="">
</div>
<div class="">Dear ICANN Board, The SSAC is strongly committed to the aims of the quintennial Security, Stability and Resiliency of the DNS Review (now SSR2) and our members have given and will continue to give, considerable time in support of SSR2. It is therefore
 with considerable regret that we inform you that SSAC has serious concerns that the SSR2 effort may fail, and we request that you give it urgent and serious attention. One basic problem with the SSR2 work is that the review team seems neither to have sufficient
 external instruction about what to study nor to have been able to formulate a clear direction for itself. </div>
<div class=""><br class="">
</div>
<div class="">Whatever the case, the Review Team has spent hundreds of hours engaged in procedural matters and almost no progress has been made on substantive matters, which in turn has damaged the goodwill and forbearance of its members, some of whom are SSSAC
 members. We are concerned that, left to its own devices, SSR2 is on a path to almost certain failure bringing a consequential loss of credibility in the accountability processes of ICANN and its community. Some seven months into the review process, the last
 SSR2 scorecard <https: community.icann.orgdisplayssrfact+sheet?preview="/64076875/69279474/SSR2%20Review" %20fact%20sheet%20participation%20(31july2017)%20final.pdf="" class="">
shows 15% of milestones being accomplished, but all of these accomplishments have been process issues – for example, determining the role of observers, adopting terms of reference, determine terms of communications with the Board, and so on. </https:></div>
<div class=""><https: community.icann.orgdisplayssrfact+sheet?preview="/64076875/69279474/SSR2%20Review" %20fact%20sheet%20participation%20(31july2017)%20final.pdf="" class=""><br class="">
</https:></div>
<div class=""><https: community.icann.orgdisplayssrfact+sheet?preview="/64076875/69279474/SSR2%20Review" %20fact%20sheet%20participation%20(31july2017)%20final.pdf="" class="">On 28 September 2017, ICANN called for proposals by external consultants to perform
 a gap analysis of the Implementation of SSR1 Recommendations <https: www.icann.orgnewsannouncement-2-2017-09-28-en="" class="">
, but this analysis will not necessarily identify new or emerging SSR issues. While it may provide useful input to the SSR2 work, it does not change the view of the SSAC. </https:></https:></div>
<div class=""><https: community.icann.orgdisplayssrfact+sheet?preview="/64076875/69279474/SSR2%20Review" %20fact%20sheet%20participation%20(31july2017)%20final.pdf="" class=""><https: www.icann.orgnewsannouncement-2-2017-09-28-en="" class=""><br class="">
</https:></https:></div>
<div class=""><https: community.icann.orgdisplayssrfact+sheet?preview="/64076875/69279474/SSR2%20Review" %20fact%20sheet%20participation%20(31july2017)%20final.pdf="" class=""><https: www.icann.orgnewsannouncement-2-2017-09-28-en="" class=""> The SSAC believes
 that the existing composition, structure, and processes of the SSR2 Review Team lack the necessary effectiveness to achieve the desired results. The SSAC recommendation to the ICANN Board of Directors and the ICANN Community is to take immediate action to
 temporarily halt the SSR2 review and produce a detailed plan before resuming work. The current approach, if continued without significant change, will ultimately result in a report that does not have the quality expected by the ICANN Community</https:></https:></div>
</body>
</html>