To: Stress Test Work party Over the weekend, we amended our 'Applying Stress Tests’ section to reflect the latest CWG proposal and our CCWG discussions last week. (see attached v10.2) In two places I've noted text in RED requiring your insights. While I know we are enabling challenge to board decisions, I don't see where are we recommending any proscriptive measure preventing ICANN from going beyond its limited technical mission. If I have that right, we should remove the red text on 2 Stress Tests: Another proposed measure is to amend ICANN bylaws to prevent the organization from expanding scope beyond what is needed for SSR in DNS operations and to meet mission and core values of ICANN. Also, co-chair Mathieu Weill added some edit suggestions (in blue underline). Mathieu also suggested we develop a sort of "management summary for stress tests". Reading the document overall, he observes that: - the stress tests demonstrate that our WS1 recommendations do increase Icann's accountability significantly, providing adequate mitigation measures in situations where that was not the case without these recommendations - we can confirm that some of the CWG proposals are providing a useful complement to our own measures. - our accountability measures do not transform Icann into a body that would be "above the laws", and that's a good sign. - there is one stress test we do not cover, pending ccTLD adequate process, about delegation and revocations. ICANN Staff suggested we add a brief guide for readers who come up with their own risks/contingencies/scenarios. Adam Peake suggested we add a ‘Do-It-Yourself’ section explaining how anyone can use our method to apply their own stress test to the existing and proposed accountability measures. Best, Steve — Steve DelBianco Executive Director NetChoice http://www.NetChoice.org<http://www.netchoice.org/> and http://blog.netchoice.org<http://blog.netchoice.org/> +1.703.615.6206