<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;}
@font-face
{font-family:"Helvetica Neue";
panose-1:2 0 5 3 0 0 0 2 0 4;}
@font-face
{font-family:"Helvetica Neue Light";
panose-1:2 0 4 3 0 0 0 2 0 4;}
@font-face
{font-family:-webkit-standard;
panose-1:2 11 6 4 2 2 2 2 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:#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.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Helvetica Neue";
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">Hi- <o:p></o:p></p>
<p class="MsoNormal">I support the recommendation. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I believe that the issues raised by James can be addressed during the implementation phase. The proposed recommendation does not require a registrar to do anything extra to validate the data beyond what currently exists under the current
accuracy obligations under the 2013 RAA.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All the best,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Margie<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">Gnso-epdp-team <gnso-epdp-team-bounces@icann.org> on behalf of "James M. Bladel" <jbladel@godaddy.com><br>
<b>Date: </b>Thursday, February 7, 2019 at 10:49 AM<br>
<b>To: </b>Alan Greenberg <alan.greenberg@mcgill.ca>, Marika Konings <marika.konings@icann.org>, Ayden Férdeline <icann@ferdeline.com><br>
<b>Cc: </b>"gnso-epdp-team@icann.org" <gnso-epdp-team@icann.org><br>
<b>Subject: </b>Re: [Gnso-epdp-team] [Ext] Re: FW: Response from ICANN Compliance re. registrations under the 2009 RAA<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue"">Folks –
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><br>
I appreciate that this sounds easy on the outside, but from a Registrar perspective we can only take a “best guess” approach here. For example, we could detect contact roles like “Domain” or “Administrator”, but beyond a few obvious field values, it’s going
to be hit or miss. <br>
<br>
Also note that the Registered Name Holder is the entity that executes the Registration Agreement, so we also need to clear this with our legal folks as to whether or not these changes rise to the level of a Re-assignement of that contract, and how that should
be handled.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue"">Bottom line - It’s critical that whatever policy recommendations we make recognize these realities and provide Registrars some flexibility to make intelligence adaptations that
suit their customers.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""><br>
Thanks—</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue"">J.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica Neue Light"">-------------</span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-family:"Helvetica Neue Light";color:#00B050">James Bladel</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Helvetica Neue Light"">GoDaddy</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica Neue""> </span><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">Gnso-epdp-team <gnso-epdp-team-bounces@icann.org> on behalf of Alan Greenberg <alan.greenberg@mcgill.ca><br>
<b>Date: </b>Thursday, February 7, 2019 at 12:32<br>
<b>To: </b>Marika Konings <marika.konings@icann.org>, Ayden Férdeline <icann@ferdeline.com><br>
<b>Cc: </b>"gnso-epdp-team@icann.org" <gnso-epdp-team@icann.org><br>
<b>Subject: </b>Re: [Gnso-epdp-team] [Ext] Re: FW: Response from ICANN Compliance re. registrations under the 2009 RAA</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Thanks Marika,<br>
<br>
As long as we can be sure that "Registered Name Holder contact information" is interpreted as requiring both the phine number and e-mail, I am fine with that.<br>
<br>
Note that the list of RDS fields which currently omits Admin contacts needs to be suitably annotated since the date at which we implement the new policy could come before all registrations are known to be ok.<br>
<br>
Alan<br>
<br>
<br>
-- <br>
Sent from my mobile. Please excuse brevity and typos.<o:p></o:p></p>
<div>
<p class="MsoNormal">On February 7, 2019 1:07:35 PM EST, Marika Konings <marika.konings@icann.org> wrote:
<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal">Ayden, Alan, all,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Having followed this thread, could this be resolved by just adding the words in bold to the language suggested by Ayden:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">Recognizing that in the case of some existing registrations, there may be an Administrative Contact but no or incomplete Registered Name Holder contact information, the EPDP team recommends that prior to eliminating
Administrative Contact fields, all Registrars must ensure that each registration contains
<b>Registered Name Holder </b>contact information. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">Best regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">Caitlin, Berry and Marika</span><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">Ayden Férdeline <icann@ferdeline.com><br>
<b>Reply-To: </b>Ayden Férdeline <icann@ferdeline.com><br>
<b>Date: </b>Thursday, February 7, 2019 at 10:43<br>
<b>To: </b>Alan Greenberg <alan.greenberg@mcgill.ca><br>
<b>Cc: </b>Marika Konings <marika.konings@icann.org>, Kurt Pritz <kurt@kjpritz.com>, "gnso-epdp-team@icann.org" <gnso-epdp-team@icann.org><br>
<b>Subject: </b>Re: [Gnso-epdp-team] [Ext] Re: FW: Response from ICANN Compliance re. registrations under the 2009 RAA</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-family:-webkit-standard;color:black">Recognizing that in the case of some existing registrations, there may be an Administrative Contact but no or incomplete Registered Name Holder contact information, the EPDP team recommends
that prior to eliminating Administrative Contact fields, all Registrars must ensure that each registration contains contact information.<span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</div>
</div>
</body>
</html>