<html 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt">Hi. As I understand it, the recommendation – fully implement the previous SSR1 recommendations – is in the body of the report. More details on what that means for each and every recommendation is in the annex.
I support this construct. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">It tracks with keeping the information that’s most important for community engagement in the body of the report, keeping the body as streamlined as possible, and putting the rest in the annex.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Denise<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="color:black">Denise Michel</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><u><span style="color:black"><a href="mailto:denisemichel@fb.com" title="mailto:denisemichel@fb.com"><span style="color:#954F72">denisemichel@fb.com</span></a></span></u><span style="color:black"> </span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Ssr2-review <ssr2-review-bounces@icann.org> on behalf of Heather Flanagan <hlf@sphericalcowconsulting.com><br>
<b>Date: </b>Wednesday, February 19, 2020 at 9:50 AM<br>
<b>To: </b>SSR2 <ssr2-review@icann.org><br>
<b>Subject: </b>[Ssr2-review] SSR2 recommended actions to complete SSR1<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div name="messageBodySection">
<div>
<p class="MsoNormal">Hello SSR2 Review Team, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As a result of today’s call, I’ve copied over the contents of the SSR2 recommended actions to complete SSR1 into the Appendix D: Findings Related to SSR1. I’ve also added the specific recommended action to each SSR1 Recommendation, so it
can be viewed in context. The new content has not been edited beyond basic spell checking.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_10U0rR1bPIQo-2DOSOqLpYGWDXmNGFX-2DtyW_edit-23&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=ZHUa87RDw-IDv9s2-aL2joWjEvhqa38sYJ2pICKamS4&s=WUNxMbLhTXH9-EWM_RIa8jChJCZN4_TXDZ-Nkp_AQrg&e=">https://docs.google.com/document/d/10U0rR1bPIQo-OSOqLpYGWDXmNGFX-tyW/edit#</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">After viewing these in context, is there a step where we need to officially call consensus on the new recommendations? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Also, it’s important to note that we now have recommendations in an appendix and not in the body of the text. Kc has already pointed out that’s a problem; I agree. Is it time for Appendix D to go back to being a section in the body of
the document?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<div name="messageSignatureSection">
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Thanks! Heather<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>