<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Perhaps I should clarify what at least I meant by change.<div><br></div><div>Look at Steve’s words - he is emphasising the need to do much of what we have been doing already:</div><div><br></div><div><ul><li>looking at what information is <u>necessary</u> to be gathered for the system to work - and we have made lots of progress on that</li><li>looking at what is feasible - we have had lots of discussion on what is/is not possible</li><li>working towards his ‘cleaner model’ that will not only satisfy the GDPR but other data protection regimes <u>globally</u>.</li></ul></div><div>You are right to question whether we need to ‘trash’ a lot of what we have done. I don’t think that is what is being asked. I think what must change is any frame of mind that thinks that the old WHOIS regime can remain as is. </div><div><br></div><div>Holly</div><div><br></div><div><br></div><div><br><div><div>On 15 Feb 2018, at 6:52 am, DANIEL NANGHAKA <<a href="mailto:dndannang@gmail.com">dndannang@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_default" style="font-size:small;color:#20124d">I dont think that it can totally change based on the strong milestones that we have achieved over period of time. </div><div class="gmail_default" style="font-size:small;color:#20124d">Critical reviews have been made and discussions have come to consensus. </div><div class="gmail_default" style="font-size:small;color:#20124d"><br></div><div class="gmail_default" style="font-size:small;color:#20124d">With the remarks from Steve, Bottom up approach work and we can not dispute the fact that the twist has come from the rise of GDPR. </div><div class="gmail_default" style="font-size:small;color:#20124d">The Deliberations have been working and we cannot trash the recommendation in the discussion. I still stand for compliance and building a benchmark regulation that meets all standards. It will take time to achieve global uniformity but what I know is that we shall get there. </div><div class="gmail_default" style="font-size:small;color:#20124d"><br></div><div class="gmail_default" style="font-size:small;color:#20124d">We have been consistent with the discussions apart from some minor issues like the Status Quo. Putting that aside, I will pose the question what must change, if we are derive consensus with basis on GDPR, the timeline is critical which we all know. In the System Requirements, all these issues, MUST and WILL be addressed. </div></div><div hspace="streak-pt-mark" style="max-height:1px"><img alt="" style="width:0px;max-height:0px;overflow:hidden" src="https://mailfoogae.appspot.com/t?sender=aZG5kYW5uYW5nQGdtYWlsLmNvbQ%3D%3D&type=zerocontent&guid=d557ad8e-c941-457e-82f9-a53d633baca6"><font color="#ffffff" size="1">ᐧ</font></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 14, 2018 at 10:35 PM, Chuck <span dir="ltr"><<a href="mailto:consult@cgomes.com" target="_blank">consult@cgomes.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 class="m_-7538284409350083394WordSection1"><p class="MsoNormal">John,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">You said ‘no’ but your qualification says it needs to change, albeit in what you think is a minor change.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Do you believe that changing the RDS to accommodate the GDPR is Europe is a minor tweak? If so, please tell me what that minor tweak is.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Chuck<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><b>From:</b> John Horton [mailto:<a href="mailto:john.horton@legitscript.com" target="_blank">john.horton@<wbr>legitscript.com</a>] <br><b>Sent:</b> Wednesday, February 14, 2018 11:26 AM<br><b>To:</b> Chuck <<a href="mailto:consult@cgomes.com" target="_blank">consult@cgomes.com</a>><br><b>Cc:</b> Sara Bockey <<a href="mailto:sbockey@godaddy.com" target="_blank">sbockey@godaddy.com</a>>; Steve Crocker <<a href="mailto:steve@shinkuro.com" target="_blank">steve@shinkuro.com</a>>; RDS PDP WG <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>></p><div><div class="h5"><br><b>Subject:</b> Re: [gnso-rds-pdp-wg] Using the GDPR as a basis for RDS Policy is backwards<u></u><u></u></div></div><div><br class="webkit-block-placeholder"></div><div><div class="h5"><p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#444444">Yes, I respectfully disagree with Sara's statement, Chuck. (With a small qualification.) I don't think you have consensus around that point, in my view. The qualification I'd make is: where there are specific regulatory reasons to either require or permit a change to existing Whois/RDS policy, provided that it's done in the most conservative way possible, I think that's reasonable to discuss. (The obvious example here is the GDPR.) Beyond that, I believe that one of the best alternatives that's (implicitly) presented so far is no change, as many (all?) of the proposed changes I've heard so far would be worse than the status quo. <u></u><u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#444444"><u></u> <u></u></span></p></div><div><p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#444444">So do I believe it "must" change? No, aside from a very limited tweak due to some specific regulatory issues. Do I believe it could be improved, and that improvements are worth discussing? Yes. But the answer to your question is: Yes, there is someone on this working group who respectfully disagrees with Sara's statement. <u></u><u></u></span></p></div></div><div><p class="MsoNormal"><br clear="all"><u></u><u></u></p><div><p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#073763">John Horton<br>President and CEO, LegitScript</span><u></u><u></u></p><div><p class="MsoNormal"><img width="96" height="36" style="width:1.0in;height:.375in" id="m_-7538284409350083394_x0000_i1025" src="https://docs.google.com/uc?export=download&id=0B13GfLt8zwZJRXE5UTAtclVxdTg&revid=0B13GfLt8zwZJSG9zOUVwN1lFKzFrRVlnaWU0NGZ4RmdkUjg4PQ"><u></u><u></u></p><div><div style="margin: 0in 0in 0.0001pt;"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><u></u> <u></u></span></div><div style="margin: 0in 0in 0.0001pt;"><b><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#444444">Follow</span></b><b><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#0b5394"> </span></b><b><span style="font-size: 9pt; font-family: Helvetica, sans-serif;">Legit</span></b><b><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#0b5394">Script</span></b><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">: <a href="http://www.linkedin.com/company/legitscript-com" target="_blank"><span style="color:#cc0000">LinkedIn</span></a> | <a href="https://www.facebook.com/LegitScript" target="_blank"><span style="color:#6aa84f">Facebook</span></a> | <a href="https://twitter.com/legitscript" target="_blank"><span style="color:#674ea7">Twitter</span></a> | <u><span style="color:#ff9900"><a href="http://blog.legitscript.com/" target="_blank"><span style="color:#1155cc">Blog</span></a></span></u> |<span style="color:#ff9900"> <a href="http://go.legitscript.com/Subscription-Management.html" target="_blank"><span style="color:#ff9900">Newsletter</span></a></span><u></u><u></u></span></div><div style="margin: 0in 0in 0.0001pt;"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><u></u> <u></u></span></div><div style="margin: 0in 0in 0.0001pt;"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:#ff9900"><img border="0" width="46" height="96" style="width:.4791in;height:1.0in" id="m_-7538284409350083394_x0000_i1026" src="https://www.legitscript.com/wp-content/uploads/2015/09/LegitScript-Workplace.png"><img border="0" width="47" height="96" style="width:.4895in;height:1.0in" id="m_-7538284409350083394_x0000_i1027" src="https://docs.google.com/uc?export=download&id=0B13GfLt8zwZJTmNWbmcwOTVJMXc&revid=0B13GfLt8zwZJQlZWOXVGbG9acC9nRGhzdEkxclFJVytCWVNjPQ"></span><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><u></u><u></u></span></div></div></div></div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">On Wed, Feb 14, 2018 at 11:08 AM, Chuck <<a href="mailto:consult@cgomes.com" target="_blank">consult@cgomes.com</a>> wrote:<u></u><u></u></p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><div><p class="MsoNormal">Is there anyone in this WG who disagrees with Sara’s statement that ‘RDS must change’, understanding that we still have large differences of opinion regarding how to change it?<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Chuck<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b>From:</b> gnso-rds-pdp-wg [mailto:<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-<wbr>bounces@icann.org</a>] <b>On Behalf Of </b>Sara Bockey<br><b>Sent:</b> Wednesday, February 14, 2018 9:22 AM<br><b>To:</b> Steve Crocker <<a href="mailto:steve@shinkuro.com" target="_blank">steve@shinkuro.com</a>>; <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br><b>Subject:</b> Re: [gnso-rds-pdp-wg] Using the GDPR as a basis for RDS Policy is backwards<u></u><u></u></p></div></div><div><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">I agree with Steve and look forward to additional feedback from him. <u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">RDS must change. Discussions to the contrary are a waste of time.<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Sara<u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><div><p class="MsoNormal" style="margin-bottom:1.0pt"><b><span style="font-size:9.0pt;font-family:"GD Boing",serif;color:#02c54c">sara bockey</span></b><u></u><u></u></p><p class="MsoNormal" style="margin-bottom:1.0pt"><b><span style="font-size:9.0pt;font-family:"GD Boing",serif;color:#111111">sr. policy manager | </span></b><b><span style="font-size:9.0pt;font-family:"GD Boing",serif;color:#02c54c">Go</span></b><b><span style="font-size: 9pt; font-family: 'GD Boing', serif;">Daddy<sup>™</sup></span></b><u></u><u></u></p><p class="MsoNormal" style="margin-bottom:1.0pt"><b><span style="font-size:9.0pt;font-family:"GD Boing",serif;color:#111111"><a href="mailto:sbockey@godaddy.com" target="_blank"><span style="color:#954f72">sbockey@godaddy.com</span></a> <a href="tel:(480)%20366-3616" target="_blank">480-366-3616</a></span></b><u></u><u></u></p><p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"GD Boing",serif;color:#111111">skype: sbockey</span></b><u></u><u></u></p><p class="MsoNormal"><i><span style="font-size: 10pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"> </span></i><u></u><u></u></p><p class="MsoNormal"><i><span style="font-size: 10pt; background-color: white; background-position: initial initial; background-repeat: initial initial;">This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments.</span></i><u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p></div><p class="MsoNormal"> <u></u><u></u></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: 12pt;">From: </span></b><span style="font-size: 12pt;">gnso-rds-pdp-wg <<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@<wbr>icann.org</a>> on behalf of Steve Crocker <<a href="mailto:steve@shinkuro.com" target="_blank">steve@shinkuro.com</a>><br><b>Date: </b>Wednesday, February 14, 2018 at 9:27 AM<br><b>To: </b>"<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>" <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>><br><b>Subject: </b>[gnso-rds-pdp-wg] Using the GDPR as a basis for RDS Policy is backwards</span><u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal"><a name="m_-7538284409350083394_m_-2648048273994446217__MailOriginalBody">I am only partially up to speed on the state of discussion within this WG, but I have been following the RDS situation for several years. In my view, the current focus on GDPR, while understandable because of the looming deadline, is logically backwards. The challenge, which we tried to address forcefully in 2012, is to rethink the RDS from the ground up. In my view, this is: </a><u></u><u></u></p><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">o necessary<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">o feasible<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">o will lead to a much cleaner model<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">o will make it relatively straightforward to satisfy the GDPR and all similar regulations around the world.<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">There are also some issues such as the relationship of name server operators that also need to be addressed.<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">There is obviously much more that needs to be said. I will contribute as much and as quickly as I can.<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">Steve<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div></div></div></div><p class="MsoNormal"><br>______________________________<wbr>_________________<br>gnso-rds-pdp-wg mailing list<br><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a><u></u><u></u></p></blockquote></div><p class="MsoNormal"><u></u> <u></u></p></div></div></div></div></div><br>______________________________<wbr>_________________<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/<wbr>listinfo/gnso-rds-pdp-wg</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div> <br>Regards <br>Nanghaka Daniel K.<br><span style="font-size:small">Executive Director - ILICIT Africa / Chair - FOSSFA / Community Lead - ISOC Uganda Chapter / Geo4Africa Lead / Organising Team - FOSS4G2018</span><br>Mobile +256 772 898298 (Uganda)<br></div><div>Skype: daniel.nanghaka<br></div><div><br></div><div>----------------------------------------- <i>"Working for Africa" </i>-----------------------------------------<br> <br><br></div></div></div></div></div></div></div></div>
</div>
_______________________________________________<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>https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</blockquote></div><br></div></body></html>