<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks Volker. It is precisely because</span> “<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">the registrars obligation only
extends to the registrant of record, not to anyone who may use the domain name with permission of that registrant,” that there should be an independent obligation on the part of the p/p service provider to validate its customer’s contact information.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Steve.<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> Volker Greimann [mailto:vgreimann@key-systems.net]
<br>
<b>Sent:</b> Monday, March 03, 2014 5:32 AM<br>
<b>To:</b> Metalitz, Steven; gnso-ppsai-pdp-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] For review - updated templates Cat B, questions 1 and 2<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Steven,<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
<br>
<br>
</span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Even when this assertion is relevant, it may not be persuasive, for a number of reasons. For example,
the Whois data reminder obligation applies to the registrant of record. In the case of a proxy service, the registrant or record is the service, not its customer. If a Whois data reminder is sent to a non-proxy registrant and bounces back, then the RAA requires
the registrar to re-verify. But a data reminder sent to a proxy service will almost never bounce back, and therefore there may be no RAA obligation to re-verify. This is so even if the customer data provided to the service is inaccurate or outdated. In
this circumstance it is up to the p/p service accreditation standards to specify the conditions under which customer data must be re-verified.
</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
This depends on how the service is set up. One could suggest that if such required messages from the registrar do not reach the registrant, it could become the providers' obligation to perform the information requirements on its own. The registrar could then
rely on the provider to perform its duties under the accreditation agreement with ICANN just at it performs its own obligations under the RAA.<br>
<br>
Please also remember that the registrars obligation only extends to the registrant of record, not to anyone who may use the domain name with permission of that registrant.<br>
<br>
V.<o:p></o:p></p>
</div>
</body>
</html>