<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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
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-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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks, Marc. As explained by Dan on the call earlier today, there is indeed an existing process for RRA amendments (pre Temp Spec). This process involves approval by ICANN and also requires action by the
RrSG for each individual amendment. Absent a recommendation, the process would revert back to the pre Temp Spec one, once the Temporary Specification expires.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Caitlin, Berry and Marika<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">"Anderson, Marc" <mcanderson@verisign.com><br>
<b>Date: </b>Wednesday, February 6, 2019 at 15:16<br>
<b>To: </b>Marika Konings <marika.konings@icann.org>, "gnso-epdp-team@icann.org" <gnso-epdp-team@icann.org><br>
<b>Subject: </b>[Ext] RE: [Gnso-epdp-team] Proposed language in relation to process for amendments to RRAs<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">There already is a process for amending Registry Registrar Agreements (RRAs). I don’t see that this language addresses a need or what it is trying to accomplish. Absent a clearly defined need I don’t support
this as a new recommendation.</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">Best,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Marc</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"> </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"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Gnso-epdp-team <gnso-epdp-team-bounces@icann.org>
<b>On Behalf Of </b>Marika Konings<br>
<b>Sent:</b> Wednesday, February 06, 2019 3:00 PM<br>
<b>To:</b> gnso-epdp-team@icann.org<br>
<b>Subject:</b> [EXTERNAL] [Gnso-epdp-team] Proposed language in relation to process for amendments to RRAs</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear EPDP Team,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline">In relation to the process for amendments to Registry – Registrar agreements, as discussed during today’s EPDP Team meeting, please find hereby the proposed language for inclusion in the implementation
section of the report:<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><i>New Recommendation:</i><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><i>The EPDP Team recommends that, as part of the implementation, a process for amendments to Registry - Registrar agreements (RRAs) needed to implement the EPDP recommendations is considered.
</i><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline">If you have <span style="color:black">
any concerns about this language, please indicate this by Thursday 7 February COB.
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="color:black"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="color:black">Best regards,</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="color:black"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="color:black">Caitlin, Berry and Marika</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><i><span style="font-size:10.0pt;color:black">Marika Konings</span></i></b><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) </span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Email: <a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a> </span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black"> </span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Follow the GNSO via Twitter @ICANN_GNSO</span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Find out more about the GNSO by taking our <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses_gnso&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=Cg5uQf0yAfw-qlFZ0WNBfsLmmtBNUiH0SuI6Vg-gXBQ&e=">interactive
courses</a> and visiting the <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=tT-E2RoAucUb3pfL9zmlbRdq1sytaEf765KOEkBVCjk&e=">GNSO
Newcomer pages</a>. </span></i><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</body>
</html>