<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: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-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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 lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial",sans-serif;color:black">Dear EPDP team,</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial",sans-serif;color:black">We are writing to provide you with an update on ICANN org’s effort to produce a cost estimate based on the
</span><a href="https://docs.google.com/document/d/1YtLHw4ASPOLwI_77bXGJrGypCHzYePQ5vaIWXzPatww/edit"><span style="font-family:"Arial",sans-serif;color:#1155CC">answers</span></a><span style="font-family:"Arial",sans-serif;color:black"> provided in March in
response to our questions regarding this effort. We appreciate the team’s efforts to estimate the scope of use for the SSAD and provide answers to our questions. ICANN org is committed to supporting the EPDP team in its work and hopes that its estimates prove
useful for the team’s deliberations. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial",sans-serif;color:black">To that end, the org is preparing estimates that in some cases will reflect ranges of costs, because some critical factors remain unknown or undetermined by
the EPDP. This includes in the area of accreditation and identity verification, which we raised as concerns on today’s EPDP call. In particular, question #23 in the
</span><a href="https://docs.google.com/document/d/1YtLHw4ASPOLwI_77bXGJrGypCHzYePQ5vaIWXzPatww/edit"><span style="font-family:"Arial",sans-serif;color:#1155CC">Q&A document</span></a><span style="font-family:"Arial",sans-serif;color:black"> asks for greater
detail regarding the EPDP Team’s expectations about the depth and breadth of identity verification. In the org’s public comments on Preliminary Recommendation #1, we also cited concerns regarding the verification and management of signed assertions. Specifically,
we noted: “As there are no recommendations on how the Accreditation Authority must verify the identity of the requestor, ICANN org believes it is important to understand the scale of effort the EPDP expects for the verification process. For example, how and
to what type of standards would an IP attorney’s identity be validated? A cyber security researcher? If any possible SSAD user may be accredited, how would the Accreditation Authority or Identity Provider be expected to verify that an individual with the email
address NAME@SLD.TLD is who they say they are? Would it be up to the Accreditation Authority or the Identity Provider to set these parameters?” </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial",sans-serif;color:black">We understand from today’s discussion that the EPDP notes many of these details can be worked out in the implementation phase. With this discussion in mind,
the org will estimate costs to the best of its ability based on its past experiences, as suggested by the team. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial",sans-serif;color:black">Given the team’s timeline for reviewing public comments on the initial report, we are working to provide you with an estimate ahead of the scheduled discussion
on Preliminary Recommendation #15, which we understand to be 23 April. Our CFO Xavier Calvez and Vice President of Finance Becky Nash are available to join the team on that call, or whenever is most appropriate, to discuss these efforts as we work to produce
the estimates. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial",sans-serif;color:black">Thank you,<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial",sans-serif;color:black">Eleeza and Dan</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial",sans-serif;color:black">ICANN org liaisons
</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>