<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;}
@font-face
{font-family:"Source Sans Pro";
panose-1:2 11 5 3 3 4 3 2 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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;
text-decoration:none none;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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 bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear SSR2 Review Team members,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">In preparation for the face-to-face meeting scheduled in Los Angeles on 9-10 October 2017, we would like to highlight a few items for your information:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt">Non-Disclosure Agreement</span></u></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">There have been concerns raised in recent conversations regarding the need for SSR2 RT members to execute a non-disclosure agreement (or NDA) in order to access certain information or documents that are not
publicly available but are likely to be pertinent to the RT’s work. When the reviews were incorporated into the Bylaws, the need for NDAs to facilitated openness and transparency amongst the review team was specifically identified at Section 4.6 (a)(vi)(A):</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">(vi) Confidential Disclosure to Review Teams</span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">(A) To facilitate transparency and openness regarding ICANN's deliberations and operations, the review teams, or a subset thereof, shall have access to ICANN internal information and documents pursuant
to the Confidential Disclosure Framework set forth in the Operating Standards (the "<b>Confidential Disclosure Framework</b>"). The Confidential Disclosure Framework must be aligned with the following guidelines:</span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">(1) ICANN must provide a justification for any refusal to reveal requested information. ICANN's refusal can be appealed to the Ombudsman and/or the ICANN Board for a ruling on the disclosure request.</span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">(2) ICANN may designate certain documents and information as "for review team members only" or for a subset of the review team members based on conflict of interest. ICANN's designation of documents may
also be appealed to the Ombudsman and/or the ICANN Board.</span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">(3) ICANN may require review team members to sign a non-disclosure agreement before accessing documents.</span></i><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">ICANN organization, in beginning its preparations for conversations with the sub-team, noted that there might be certain information discussed for which an NDA would be appropriate. If the sub-team wishes
for all conversations at its October 9-10 meeting in L.A. to be on information that is publicly available, that can be arranged. If the subgroup wishes to have the ability to discuss more sensitive information with the ICANN organization reps while onsite,
then if topics of conversation come up that are deemed to be confidential, those who have not yet signed the NDA will be requested to step out of the room for that portion of the conversation. We will accommodate either path the sub-team wishes to take for
the onsite meeting.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Separately, there is the possibility that the sub-team will request documentation for which an NDA would be required. ICANN is committed to following the Confidential Disclosure Framework in identifying the
minimum amount of information as “Confidential” as possible. If the sub-team prefers, the decision to sign an NDA can be deferred until such time said documentation is ready to be distributed upon signature.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt">Subject Matter Experts</span></u></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Below, please find the list of subject matter experts who will attend the upcoming meeting in Los Angeles:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Steve Conte -- Director, Office of the CTO Programs</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">James Caulfield -- VP, Enterprise Risk Management</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Christine Willett -- VP, GDD Operations</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Francisco Arias – Sr. Director, GDD Technical Services</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Russ Weinstein – Director, Registry Services</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Darren Kara – DNS Engineering Strategy Manager</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Gary Petzer -- VP, Strategic IT Program Management</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Samuel Suh -- VP, Back Office Solutions</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Maguy Serad -- VP, Contractual Compliance Services</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> Thank you for your time, and please do not hesitate to reach out to us with any questions you might have.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">-- <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">Jennifer Bryce</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">Senior Reviews Coordinator </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">Internet Corporation for Assigned Names and Numbers (ICANN)</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">Email: jennifer.bryce@icann.org</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">Skype: jennifer.bryce.icann</span><span style="color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">www.icann.org</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>