Hi, Staff: Would you please allow all SSR2 Team members to edit the “Scope of the Review” draft google doc, ASAP. Hi, Team Members: I’m in transit. Please let us know if you have problems accessing the google doc and we’ll make alternate arrangements. The current text is included below, FYI. Feel free to share edits/comments on the email list. Best, Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel@fb.com<mailto:denisemichel@fb.com> DRAFT GOOGLE DOC Dear SO/AC Chairs; Please find enclosed a description of the SSR2 Review Team’s perspective the Scope of this review. As requested, the SSR2 is completing requested item to “[resolve] the issues identified and discussed before and during ICANN60 related to scope”. Scope The SSR2 RT has operated and conducted its work according to its adopted scope (detailed in its Terms of Reference<https://community.icann.org/download/attachments/64076120/SSR2-TermsofRefere...> document), which was adopted by consensus of the SSR RT on 4 May 2017. We would like to offer some general clarifications and comments about the choices in the approach to scope that we hope will be helpful to the SO and AC chairs in considering the parameters associated with resuming this effort: Breadth vs. Depth: We believe that it is more helpful to look at breadth in such a review, and look at the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues. Capability vs. Behaviours: We believe that it is more helpful in the context of this review to look at the capability of ICANN to manage issues related to security, stability and resilience rather than being overly prescriptive as to how ICANN should respond to particular circumstances that have arisen in the past or may arise in the future. Perspective vs. Prescription: We believe that it is more helpful to review aspects of institutional awareness and capability of topics related to security, stability, and resiliency, rather than provide a detailed prescription of the appropriate responses to be used in particular cases. We hope this meets your requirements regarding the review team’s perspective on the scope of this review. The current working terms of references for the review team’s efforts up to the point of this pause in our actions, including a detailed view of the scope of the review, can be found in the reference document cited above. Please let us know if you require anything further. Regards, The Second Security, Stability, and Resiliency Review Team (SSR2 RT)