<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Roboto Light";
panose-1:2 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Times;
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Roboto Light";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Roboto Light";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="SR-LATN-RS" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Roboto Light";mso-fareast-language:EN-US">Hi All,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Roboto Light";mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Roboto Light";mso-fareast-language:EN-US">I know I am late but just for the record, I agree with the proposed text. Nevertheless, I have to agree with those who believe that our communication
with SO/AC Chairs should be clear and short. At ICAN60, we had meetings where we agreed on the way to overcome this situation, and I do not think there is no need for further clarifications.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Roboto Light";mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Roboto Light";mso-fareast-language:EN-US">Zarko<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Roboto Light";mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Roboto Light";mso-fareast-language:EN-US"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt">From:</span></b><span lang="EN-US" style="font-size:11.0pt"> ssr2-review-bounces@icann.org [mailto:ssr2-review-bounces@icann.org]
<b>On Behalf Of </b>Denise Michel<br>
<b>Sent:</b> Tuesday, November 7, 2017 8:13 PM<br>
<b>To:</b> SSR2 <ssr2-review@icann.org><br>
<b>Subject:</b> Re: [Ssr2-review] Scope document - action needed<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Hi, All. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Included below is the version all Team members were asked to review and indicate whether they can support – deadline today (by
<u>11:30 PM Tuesday, UTC</u>). It includes some edits since we left our last Team meeting in Abu Dhabi, but the focus and substance remains the same. I think we are very close.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span lang="EN-US">Please send a yes or no on this draft by the deadline</span></u><span lang="EN-US">. Let us know if you need more time, or would like to discuss.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">We’re moving this to the email thread as we’re trying to get closure/agreement on one version of the document (not a changing google doc).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Attached is Geoff Huston’s preferred draft. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">As I noted, we hope to achieve full agreement. Absent that, we continue to operate by consensus and the Scope document will be delivered to the SO & AC chairs this week.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Denise<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Denise Michel<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Domain Name System Strategy & Management<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Facebook, Inc.<o:p></o:p></span></p>
<p class="MsoNormal"><u><span lang="EN-US" style="font-size:11.0pt"><a href="mailto:denisemichel@fb.com">denisemichel@fb.com</a></span></u><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:17.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.5pt;font-family:"Arial",sans-serif;color:black">Dear SO/AC Chairs;
</span><span lang="EN-US" style="font-family:"Times",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:17.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.5pt;font-family:"Arial",sans-serif;color:black">Please find enclosed a description of the SSR2 Review Team’s perspective of the scope of this review. As requested, the SSR2 is completing the requested item to “[</span><span lang="EN-US" style="font-size:16.0pt;font-family:"Times",serif;color:black">resolve]
the issues identified and discussed before and during ICANN60 related to scope.”
</span><span lang="EN-US" style="font-family:"Times",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:17.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.5pt;font-family:"Arial",sans-serif;color:black">We hope this meets your requirements regarding the Review Team’s perspective on the scope of this review. The current Terms of Reference for SSR2’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
</span><span lang="EN-US" style="font-size:14.5pt;font-family:"Arial",sans-serif;color:#103CC0">here</span><span lang="EN-US" style="font-size:14.5pt;font-family:"Arial",sans-serif;color:black">. Additional information on SSR2 activities, including the work
plan can be found on the Review Team’s </span><span lang="EN-US" style="font-size:14.5pt;font-family:"Arial",sans-serif;color:#103CC0">wiki</span><span lang="EN-US" style="font-size:14.5pt;font-family:"Arial",sans-serif;color:black">.
</span><span lang="EN-US" style="font-family:"Times",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:17.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.5pt;font-family:"Arial",sans-serif;color:black">Please let us know if you require anything further. Regards,
</span><span lang="EN-US" style="font-family:"Times",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:17.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.5pt;font-family:"Arial",sans-serif;color:black">The Second Security, Stability, and Resiliency of the DNS Review Team (SSR2)
</span><span lang="EN-US" style="font-family:"Times",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:18.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:16.0pt;font-family:"Times",serif;color:black">............
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:18.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.0pt;font-family:"Arial",sans-serif;color:#535353">Scope
</span><span lang="EN-US" style="font-size:14.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:18.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.0pt;font-family:"Arial",sans-serif;color:black">The Security, Stability and Resiliency of the DNS Review Team (SSR2 or Review Team) has operated and conducted its work according to its adopted scope (detailed in its
</span><span lang="EN-US" style="font-size:14.0pt;font-family:"Arial",sans-serif;color:#103CC0">Terms of Reference
</span><span lang="EN-US" style="font-size:14.0pt;font-family:"Arial",sans-serif;color:black">document), which was adopted by consensus of the Review Team on 4 May 2017.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:17.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.0pt;font-family:"Arial",sans-serif;color:black">We would like to offer an overview on the overarching tenets that were adopted and that guided the development of the scope of this review that we hope will be helpful to
the SO and AC chairs in considering the parameters associated with resuming this effort:
</span><span lang="EN-US" style="font-size:14.0pt;font-family:"Times",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;line-height:17.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.0pt;font-family:"Arial",sans-serif;color:black">Breadth vs. Depth: In such a review, we believe that it is, in general, more helpful to look at breadth and the broader aspects of security, stability and resiliency rather
than dive into depth in just a small number of issues. We believe this approach will lend itself to more informed conclusions that can be contextualized.
</span><span lang="EN-US" style="font-size:14.0pt;font-family:"Times",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;line-height:17.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.0pt;font-family:"Arial",sans-serif;color:black">Capability vs. Behaviors: 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 resiliency 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.
</span><span lang="EN-US" style="font-size:14.0pt;font-family:"Times",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;line-height:17.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.0pt;font-family:"Arial",sans-serif;color:black">Perspective vs. Prescription: We believe that it is more helpful to review aspects of institutional awareness and capability with respect to topics related to security, stability,
and resiliency, rather than provide a detailed prescription of the appropriate responses to be used in particular cases.
</span><span lang="EN-US" style="font-size:14.0pt;font-family:"Times",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;line-height:17.0pt;text-autospace:none">
<span lang="EN-US" style="font-size:14.0pt;font-family:"Arial",sans-serif;color:black">Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide recommendations that are specific,
measurable, attainable, realistic, and timely (SMART). Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review.
</span><span lang="EN-US" style="font-size:14.0pt;font-family:"Times",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:black">From: </span></b><span lang="EN-US" style="color:black">Denise Michel <<a href="mailto:denisemichel@fb.com">denisemichel@fb.com</a>><br>
<b>Date: </b>Monday, November 6, 2017 at 3:46 PM<br>
<b>To: </b>SSR2 <<a href="mailto:ssr2-review@icann.org">ssr2-review@icann.org</a>><br>
<b>Subject: </b>Scope document - action needed<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US">Hi, Team.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thank you for your edits and comments. Please take a look at the draft Scope document on google, and share your final thoughts before 23:30 am UTC Tuesday, 7 Nov.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">It seems like we’re close to full agreement but there are a few outstanding items.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Denise<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Denise Michel</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Domain Name System Strategy & Management</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt">Facebook, Inc.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><u><span lang="EN-US" style="font-size:11.0pt"><a href="mailto:denisemichel@fb.com">denisemichel@fb.com</a></span></u><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</body>
</html>