<div dir="ltr"><div class="gmail_default" style="font-family:comic sans ms,sans-serif;font-size:small">I have a more nuanced view of the ALAC's position. There is nothing that says a conscientious data controller within the DNS ecosystem - which to my understanding is a wider net than gTLDs - cannot implement from Day One the software feature set that makes differentiated access to RD possible. Because it is likely that by doing so, early adopters in the broader ecosystem could, by virtue of this endorsement, be encouraged to make use of it.</div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;font-size:small">Sure, the official ICANN use policy is lagging and that is not unusual. But the consensus for differentiated access is arguably well-formed. The perfect must not be allowed to become the enemy of the good. Such a position merely signals endorsement of the best practice and eschew its retardation.</div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;font-size:small">-Carlton </div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><br>==============================<br>Carlton A Samuels<br>Mobile: 876-818-1799<br><i><font color="#33CC00">Strategy, Planning, Governance, Assessment & Turnaround</font></i><br>=============================</div></div>
<br><div class="gmail_quote">On Sun, Jan 31, 2016 at 4:38 PM, Metalitz, Steven <span dir="ltr"><<a href="mailto:met@msk.com" target="_blank">met@msk.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks Holly. The IPC has also commented on the draft RDAP operational profile but contrary to ALAC’s position. See the following excerpt:
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;text-indent:.5in"><span>“Section II of the public comment notice (see
<a href="https://www.icann.org/public-comments/rdap-profile-2015-12-03-en" target="_blank">https://www.icann.org/public-comments/rdap-profile-2015-12-03-en</a> ) notes that one ICANN advisory committee has insisted that the RDAP profile “must include the feature set that will
support differentiated access” to domain name registration data. IPC supports ICANN’s response to this, that including such a requirement in the RDAP profile is premature, “[g]iven the ongoing discussions and work in the community on differentiated access.”
While it is correct that RDAP “does allow for differentiated access for those that have contracts that permit such a service, or in the event a consensus policy on differentiated access is completed,” the development of such a policy is still at an early phase.
The PDP working group on Registry Directory Services is still in the process of formation, and it will be some time before there is any consensus policy on whether differentiated access will be a required feature of any new Registration Data Directory Service
(RDDS) for gTLDs, and if so the particulars of such a requirement. <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;text-indent:.5in"><span>Throughout the development of RDAP, there has been a clear distinction made between the development of a replacement
<u>technical</u> protocol that could enable differentiated access, and the <u>policy</u> decision as to whether and if so under what circumstances that technical capability would be deployed. IPC commends ICANN for maintaining that vital distinction in this
draft proposal. As the public comment notice states, “once/if there is a consensus policy or some contractual provision allowing for differentiated access in RDP, the profile could be updated as needed.” Indeed, the draft RDAP profile specifically refers
to the capability to redact some data “[I]f permitted or required by an ICANN agreement provision ,waiver, or Consensus Policy.” Section 1.4.11.”<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">However, I am pleased to see that the ALAC and IPC submissions on the companion notice regarding Thick Whois are very much in sync! See
<a href="http://forum.icann.org/lists/comments-rdds-output-03dec15/msg00002.html" target="_blank">
http://forum.icann.org/lists/comments-rdds-output-03dec15/msg00002.html</a> and <a href="http://forum.icann.org/lists/comments-rdds-output-03dec15/msg00003.html" target="_blank">http://forum.icann.org/lists/comments-rdds-output-03dec15/msg00003.html</a>
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Steve Metalitz<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></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"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a> [mailto:<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Holly Raiche<br>
<b>Sent:</b> Sunday, January 31, 2016 2:56 PM<br>
<b>To:</b> <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>; Gomes, Chuck</span></p><div><div class="h5"><br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] Search Engines Indexing RDAP Server Content<u></u><u></u></div></div><p></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks Chuck<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">This is a very important component of the overall move to update the Whois protocol and the various policies associated with it. ALAC has specifically commented on this, concluding with the following:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p><i>Therefore, while existing ICANN policies do not now require differentiated access to DNRD, it is clear from Board decisions and EWG recommendations that future ICANN policies will likely have that requirement. </i><u></u><u></u></p>
<p><i>The Operational Profile of RDAP, therefore, should include an obligation on all gTLD registries and registrars that the basic functionality will support an authentication and authorisation framework.</i><u></u><u></u></p>
<p><i>Specifically, the features to allow differentiated access must be required now, as part of this protocol – even if at this stage all access seekers will be in one class - the public. In that way, when differentiated access requirements are imposed, protocol
features will already be deployed to provide such access.</i><u></u><u></u></p>
<div>
<p class="MsoNormal">Holly<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal">On 1 Feb 2016, at 2:03 am, Michele Neylon - Blacknight <<a href="mailto:michele@blacknight.com" target="_blank">michele@blacknight.com</a>> wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><br>
<br>
<u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">+1<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Ploughing ahead with RDAP in its current form<span> </span><i>without</i> a proper policy framework is a terrible idea, as the indexing issue
has shown.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Regards<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Michele<u></u><u></u></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">--<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Mr Michele Neylon<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Blacknight Solutions<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Hosting, Colocation & Domains<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><a href="http://www.blacknight.host/" target="_blank"><span style="color:purple">http://www.blacknight.host/</span></a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><a href="http://blog.blacknight.com/" target="_blank"><span style="color:purple">http://blog.blacknight.com/</span></a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><a href="http://ceo.hosting/" target="_blank"><span style="color:purple">http://ceo.hosting/</span></a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Intl. <a href="tel:%2B353%20%280%29%2059%20%C2%A09183072" value="+353599183072" target="_blank">+353 (0) 59 9183072</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Direct Dial: <a href="tel:%2B353%20%280%2959%209183090" value="+353599183090" target="_blank">+353 (0)59 9183090</a><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">-------------------------------<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Road,Graiguecullen,Carlow,Ireland Company No.: 370845<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></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-family:"Calibri","sans-serif"">From:<span> </span></span></b><span style="font-family:"Calibri","sans-serif""><<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank"><span style="color:purple">gnso-rds-pdp-wg-bounces@icann.org</span></a>>
on behalf of Chuck Gomes <<a href="mailto:cgomes@verisign.com" target="_blank"><span style="color:purple">cgomes@verisign.com</span></a>><br>
<b>Date:<span> </span></b>Sunday 31 January 2016 at 14:39<br>
<b>To:<span> </span></b>Carlton Samuels <<a href="mailto:carlton.samuels@gmail.com" target="_blank"><span style="color:purple">carlton.samuels@gmail.com</span></a>>, Scott Hollenbeck <<a href="mailto:shollenbeck@verisign.com" target="_blank"><span style="color:purple">shollenbeck@verisign.com</span></a>><br>
<b>Cc:<span> </span></b>"<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank"><span style="color:purple">gnso-rds-pdp-wg@icann.org</span></a>" <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank"><span style="color:purple">gnso-rds-pdp-wg@icann.org</span></a>><br>
<b>Subject:<span> </span></b>Re: [gnso-rds-pdp-wg] Search Engines Indexing RDAP Server Content<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">For those who are not aware, there is a comment period currently underway that has just been extended to February 15 regarding a proposed implementation of
RDAP:<a href="https://www.icann.org/public-comments/rdap-profile-2015-12-03-en" target="_blank"><span style="color:purple">https://www.icann.org/public-comments/rdap-profile-2015-12-03-en</span></a><span> </span>.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I encourage you to express your concerns in this comment period if you haven’t already done so.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Chuck</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank"><span style="color:purple">gnso-rds-pdp-wg-bounces@icann.org</span></a><span> </span>[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank"><span style="color:purple">mailto:gnso-rds-pdp-wg-bounces@icann.org</span></a>]<span> </span><b>On
Behalf Of<span> </span></b>Carlton Samuels<br>
<b>Sent:</b><span> </span>Sunday, January 31, 2016 1:13 AM<br>
<b>To:</b><span> </span>Hollenbeck, Scott<br>
<b>Cc:</b><span> </span><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank"><span style="color:purple">gnso-rds-pdp-wg@icann.org</span></a><br>
<b>Subject:</b><span> </span>Re: [gnso-rds-pdp-wg] Search Engines Indexing RDAP Server Content</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal">On Sat, Jan 30, 2016 at 2:32 PM, Hollenbeck, Scott <<a href="mailto:shollenbeck@verisign.com" target="_blank"><span style="color:purple">shollenbeck@verisign.com</span></a>> wrote:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">It's also an important data point in the discussion about deploying RDAP services before policies are in place that allow operators to take advantage of the new features provided by RDAP. Deploying RDAP with the same policies associated
with WHOIS gives us the same problems associated with WHOIS.<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS"">Totally agree.</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS""> </span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS"">-Carlton</span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><br>
<br clear="all">
<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><br>
==============================<br>
Carlton A Samuels<br>
Mobile: <a href="tel:876-818-1799" value="+18768181799" target="_blank">876-818-1799</a><br>
<i><span style="color:#33cc00">Strategy, Planning, Governance, Assessment & Turnaround</span></i><br>
=============================<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank"><span style="color:purple">gnso-rds-pdp-wg@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank"><span style="color:purple">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</span></a><u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
<br>_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br></blockquote></div><br></div>