<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="Title" content="">
<meta name="Keywords" content="">
<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: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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText"><span style="font-size:12.0pt">Hi Patrik,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">Thank you for your (below) email on what you and the SO/AC chairs are doing. The SSR2 Review Team (SSR2) (cc’d) has been making progress and has cleared several milestones, but we certainly welcome any
additional resources that the SO/AC chairs want to offer. We are more than happy to point out and/or provide any additional information from SSR2 to illustrate these activities, so please let us know if that would be helpful.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">The SSR2 Review Team has made public all of its plans, information review, deliberations, and activities. The Review Team has been (and remains) open to comments, advice, and critiques of its work from
the entire ICANN community during its entire period of operation because we believe that transparency is critical to our success. Naturally, a part of that includes clear lines of communication. In addition to sending all of the ICANN constituencies, SOs,
and ACs regular updates and links to our work, we are eager to meet with each of them in Abu Dhabi at ICANN 60. We continue to appreciate the contributions of SSAC’s appointees to SSR2 and we also think that both SSAC and the full SSR2 will benefit from an
opportunity for direct face-to-face discussions at ICANN 60. <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">The cancelation notice we received for the SSAC/SSR2 meeting at ICANN 60 was disappointing and surprising. In particular, considering the amount of progress SSR2 has made, the points raised to the Board
and in the email below seem to illustrate an inaccurate assessment of the SSR2’s progress and direction, in our opinion. We request that you please put the SSR2 meeting back on SSAC’s calendar at ICANN 60 so all the Review Team members can get clarity on SSAC’s
views and objectives.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">Sincerely,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">Denise Michel and Eric Osterweil<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">Co-Chairs, Security, Stability & Resiliency of the DNS Review Team<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On 10/11/17, 10:04 PM, "Patrik Fältström" <paf@frobbit.se> wrote:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Hi,<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> I wanted to bring you up to speed on what myself and the SOAC chairs are doing.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> We have since already when SSR2 team was to be appointed have some issues with the appointment process. We where tasked to appoint people that had self-nominated themselves, asking for endorsement from the various SOAC groups. And
do it before the scope and charter for the SSR2 team was created, so in reality it was a bit unclear what we where looking for. On top of this, we appointed people individually, while at the same time we had a responsibility to try to ensure the aggregate
had the skills and diversity required and sought for.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> A very difficuly task. Specifically as it at that point in time was confusing what the difference is between SO/AC Chairs and the larger group that also included the various leaders of for example ALAC RALOs and GNSO SGs. For pure
administrative reasons. As simple things as not having separate mailing lists / aliases for the two different, but overlapping groups did not help.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> This is something we have been discussing since then, and we have had since a while back scheduled a session Friday before Abu Dhabi to discuss this meta issue.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> After being contacted by the Organizational Effectiveness Committee of the Board we started to reach out to our respective groups on the situation in SSR2. Within SSAC we already (as you understand) had a discussion ongoing as our
appointed members in SSR2 had in their reporting rised dissatisfaction with the process as a whole which included the view that you in the leadership do very hard work, but did not get much help.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> We SO/AC chairs had a call Monday this week to talk about the situation and we reconfirmed the session in Abu Dhabi.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Our hope is to be able to help you get forward movement with more active, and more happy members of the SSR2 team.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> If you have any questions, do not hesitate reaching out to me.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> That said, we SO/AC chairs do not want having us do end-run around the communication channel we already have between SSR2 and us via our respective appointed/endorsed members.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Best,<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Patrik Fältström<o:p></o:p></p>
<p class="MsoPlainText"> SSAC Chair<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Cc: Rod Rasmussen, on Jan 1 2018 incoming chair of SSAC<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
</div>
</body>
</html>