<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi All,<br>
I agree with Michele and James as well. A lack of response to a
reminder notice is hardly a indicator of problems or issues. As
Michele noted, people respond if they need to update information
-- and the annual reminder triggers action in those who have
recently moved or changed office locations. People respond when
there is a problem, but not when all is well.<br>
<br>
I thought we had agreed as a group to stick closely to the 2013
RAA requirements, perhaps with a new overlay for p/p providers to
reach out to their customers once a year as well. I agree with the
summary that "Non-delivery or error messages would then trigger
reverification" -- but not a mere lack of response. <br>
<br>
Requiring affirmative response to a mere notification is untold
extra work for registrants and registries - and unneeded work as
well since the Nominet study and reported experience indicate that
p/p contact data is more accurate, not less. It will create
confusion, frustration and disruption.<br>
<br>
Best and looking forward to our call tomorrow, <br>
Kathy<br>
<br>
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.3 (Win32)">
<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
-->
</style></div>
<blockquote
cite="mid:D1AC4482BED7C04DAC43491E9A9DBEC3995F5860@bkexchmbx02.blacknight.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<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:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 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:"Cambria","serif";}
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;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Segoe UI","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.emailstyle17
{mso-style-name:emailstyle17;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.balloontextchar0
{mso-style-name:balloontextchar;
font-family:"Tahoma","sans-serif";}
span.emailstyle20
{mso-style-name:emailstyle20;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
cannot agree with this.<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">Just
because somebody does not reply to an annual email does not
mean anything and expecting registrars or proxy / privacy
providers to do anything extra based on a lack of response
is completely unreasonable.<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">If
there’s a bounce or any other indication that the contact
details are invalid then let the 2013 RAA standards apply –
if any.<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">But
expecting registrars or privacy / proxy providers to do
extra validation simply because a customer hasn’t responded
to an annual whois data reminder simply will not fly.<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">We
send out thousands of these reminders every year. Only a
tiny percentage of our clients ever reply to them – and if
their details haven’t changed why on earth would they have
to?<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">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
Michele<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>
<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">Mr
Michele NeylonRequiement<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Blacknight
Solutions<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hosting
& Colocation, Domains<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a class="moz-txt-link-freetext" href="http://www.blacknight.co/">http://www.blacknight.co/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a class="moz-txt-link-freetext" href="http://blog.blacknight.com/">http://blog.blacknight.com/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a class="moz-txt-link-freetext" href="http://www.technology.ie">http://www.technology.ie</a><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Intl.
+353 (0) 59 9183072<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Locall:
1850 929 929<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Direct
Dial: +353 (0)59 9183090<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Fax.
+353 (0) 1 4811 763<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Twitter:
<a class="moz-txt-link-freetext" href="http://twitter.com/mneylon">http://twitter.com/mneylon</a><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">Blacknight
Internet Solutions Ltd, Unit 12A,Barrowside Business
Park,Sleaty<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Road,Graiguecullen,Carlow,Ireland
Company No.: 370845<o:p></o:p></span></p>
</div>
<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 #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Valeriya Sherman<br>
<b>Sent:</b> Monday, March 17, 2014 8:09 PM<br>
<b>To:</b> Metalitz, Steven; 'Williams, Todd'; Marika
Konings; <a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] For your review
- updated template Cat B - question 2<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Times New
Roman","serif";color:black">I, Jim Bikoff,
David Heasley, and Griffin Barnett agree with Todd's
assessment:
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Times
New Roman","serif";color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times
New Roman","serif";color:black">Contact
information that is ultimately revealed is valuable only
if it is accurate. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times
New Roman","serif";color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times
New Roman","serif";color:black">The
validation/verification requirements should be
consistent with the 2013 RAA requirements, but should go
above and beyond those requirements to
ensure the accuracy of contact information. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times
New Roman","serif";color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times
New Roman","serif";color:black">Registrars
already send an annual Whois Data Reminder Policy
notification to registrants, reminding them to provide
accurate and up-to-date information. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times
New Roman","serif";color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times
New Roman","serif";color:black">Similarly, the
privacy/proxy customer's contact information should be
verified upon initial registration of the domain name
(either by the registrar or the Privacy/Proxy Service
Provider) and periodically thereafter
by automated annual email re-verification notifications
that require an affirmative response by the P/P
customer. Absence of a response would trigger a
follow-up, reminding the privacy/proxy customer to
provide accurate and up-to-date information. <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Times New
Roman","serif";color:black"><br>
Regards,<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Times
New Roman","serif";color:black"><o:p> </o:p></span></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Times New
Roman","serif";color:black">Valeriya
Sherman<br>
Silverberg, Goldman & Bikoff, L.L.P.<br>
1101 30th Street, N.W.<br>
Suite 120<br>
Washington, D.C. 20007<br>
Tel 202.944.2330<br>
Cell 303.589.7477<br>
</span><a moz-do-not-send="true"
href="mailto:vsherman@law.gwu.edu"
target="_blank"><span
style="font-family:"Times New
Roman","serif";color:#1155CC">vsherman@sgbdc.com</span></a><span
style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<div>
<div class="MsoNormal" style="text-align:center"
align="center"><span style="font-family:"Times New
Roman","serif";color:black">
<hr align="center" size="2" width="100%">
</span></div>
<div id="divRpF216181">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
</span><a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">gnso-ppsai-pdp-wg-bounces@icann.org</span></a><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
[<a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a>] on behalf of
Metalitz, Steven [<a class="moz-txt-link-abbreviated" href="mailto:met@msk.com">met@msk.com</a>]<br>
<b>Sent:</b> Monday, March 17, 2014 6:13 AM<br>
<b>To:</b> 'Williams, Todd'; Marika Konings; </span><a
moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">gnso-ppsai-pdp-wg@icann.org</span></a><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] For your
review - updated template Cat B - question 2</span><span
style="font-family:"Times New
Roman","serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
agree with Todd’s characterization of the status of
this discussion, and that the questions he
highlights are still open.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Another
aspect of the second question below is how the p/p
service provider should handle situations in which
the contact information supplied by the customer
cannot be verified. In the parallel situation
involving non-proxy registrations, the RAA
specification calls either for suspension of the
registration, or “manual verification,” which is not
defined. How should this apply in the p/p service
scenario?
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Steve
Metalitz </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span
style="color:black"><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:black">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
</span><a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">gnso-ppsai-pdp-wg-bounces@icann.org</span></a><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
[</span><a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</span></a><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">]
<b>On Behalf Of </b>Williams, Todd<br>
<b>Sent:</b> Friday, March 14, 2014 4:53 PM<br>
<b>To:</b> Marika Konings; </span><a
moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">gnso-ppsai-pdp-wg@icann.org</span></a><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] For your
review - updated template Cat B - question 2</span><span
style="color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks
Marika. I missed part of the call on Tuesday where
this may have been discussed, but I don’t see how
the draft preliminary recommendation follows from
the attached Word document, insofar as it concludes
that p/p customer data should be validated and
verified in a manner consistent with the
requirements outlined in the 2013 RAA. I thought
the current posture was that the WG has basically
agreed to the 2013 RAA requirements as a floor, but
that there was not yet agreement on: 1) whether
validation/verification requirements should go
beyond the 2013 RAA; and 2) if so, how.</span><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">On
the first question (2013 RAA vs. “more”), it appears
that more of the responses in the attached argue for
“more” than not. That also seems to have been an
open topic in our email threads (see attached).
Just to reiterate from that thread, the basic
argument on the “more” side (which I agree with) is
that in order to partially offset the delay that
will inevitably occur when accessing p/p data, the
“more” should consist of whatever reasonable
validation/verification steps can be taken to
increase the likelihood that the information
ultimately obtained will be accurate enough to
facilitate contact. I suppose that if we ultimately
settle on a “reveal” procedure that is essentially
instantaneous in certain cases (once we get to
discussing “reveal” procedures), that may mitigate
this concern. But absent assurances on that point,
I would think we need to address it.</span><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">On
the second question: the attached appears to include
multiple proposals as to what may or may not
ultimately comprise the “more” (<i>e.g.</i>, email
<u>and</u> phone vs. or; periodic/annual
re-verification vs. re-verification with information
suggesting the contact information is incorrect;
etc.). Have we debated the relative merits of
those? Are some more likely to be effective than
others? I have my thoughts, but I’m curious to hear
what everybody else thinks.</span><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks
all.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Todd.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span
style="color:black"><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:black">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
</span><a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org"
target="_blank"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">gnso-ppsai-pdp-wg-bounces@icann.org</span></a><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">
[</span><a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org"
target="_blank"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</span></a><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">]
<b>On Behalf Of </b>Marika Konings<br>
<b>Sent:</b> Thursday, March 13, 2014 7:04 AM<br>
<b>To:</b> </span><a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org"
target="_blank"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">gnso-ppsai-pdp-wg@icann.org</span></a><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
<b>Subject:</b> [Gnso-ppsai-pdp-wg] For your
review - updated template Cat B - question 2</span><span
style="color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Dear
All,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"> </span><span
style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Following
our call earlier this week, please find attached
the updated template for Category B – question 2.
To facilitate your review, I've posted below the
draft preliminary recommendation in which we've
aimed to capture the conversation to date taking
into account the language of the Whois Accuracy
Specification Program of the 2013 RAA. If you are
of the view that this does not accurately capture
the WG's view to date and/or have specific
suggestions for changes / edits, please share
those with the mailing list. Also, if there are
any other issues that need to be addressed in
relation to this question and/or the preliminary
recommendation, please share those as well.</span><span
style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"> </span><span
style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Best
regards,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"> </span><span
style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Marika</span><span
style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"> </span><span
style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-family:"Calibri","sans-serif";color:black">Draft
Preliminary Recommendation – Category B –
question 2 (Should ICANN-accredited
privacy/proxy service providers be required to
conduct periodic checks to ensure accuracy of
customer contact information; and if so, how?)</span></b><span
style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"> </span><span
style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri","sans-serif";color:black">The
WG recommends that proxy and privacy customer data
be validated and verified in a manner consistent
with the requirements outlined in Whois Accuracy
Specification Program of the 2013 RAA. The WG
furthermore agrees that in the cases where
validation and verification of the P/P customer
data was carried out by the registrar,
reverification by the P/P service of the same,
identical, information should not be required. </span><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Calibri","sans-serif";color:black"> </span><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-family:"Calibri","sans-serif";color:black">Similar
to ICANN’s Whois Data Reminder Policy (</span><a
moz-do-not-send="true"
href="http://www.icann.org/en/resources/registrars/consensus-policies/wdrp"
target="_blank"><span
style="font-family:"Calibri","sans-serif"">http://www.icann.org/en/resources/registrars/consensus-policies/wdrp</span></a><span
style="font-family:"Calibri","sans-serif";color:black">),
the P/P provider should be required to inform the
P/P customer annually of his/her requirement to
provide accurate and up to date contact
information to the P/P provider. If the P/P
provider has any information suggesting that the
P/P customer information is incorrect (such as P/P
service receiving a bounced email notification or
non-delivery notification message in connection
with compliance with data reminder notices or
otherwise) for any P/P customer, the P/P provider
must verify or re-verify, as applicable, the email
address(es). If, within fifteen (15) calendar days
after receiving any such information, P/P service
does not receive an affirmative response from the
P/P customer providing the required verification,
the P/P service shall verify the applicable
contact information manually. </span><span
style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></pre>
</blockquote>
<br>
</body>
</html>