
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>These last few emails are exactly why we need people with institutional memory in At Large and ALAC: so new people,  like I, can at least begin to grasp the deep complexities of some issues and not fall into the pitfalls caused when power is coupled with ignorance.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Thank you.</div><div id="AppleMailSignature"><br>Javier Rúa-Jovet<div><br></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">+1-787-396-6511</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">twitter: @javrua</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">skype: javier.rua1</span></div><div><font color="#000000" style="background-color: rgba(255, 255, 255, 0);"><a href="https://www.linkedin.com/in/javrua" style="background-color: rgba(255, 255, 255, 0);">https://www.linkedin.com/in/javrua</a> </font></div><div><br></div></div></div><div><br>On Jan 9, 2017, at 6:33 AM, Holly Raiche <<a href="mailto:h.raiche@internode.on.net">h.raiche@internode.on.net</a>> wrote:<br><br></div><blockquote type="cite"><div><span>And what I didn’t add was WHY this issue is so HUGE.</span><br><span></span><br><span>Essentially, the RAA requires that WHOIS information (as defined - including registrant’s name, address, contact details etc - see Clause 3.3.1 in the 2013 RAA)  be publicly available.  And, as many of you are aware - that goes absolutely up against data retention laws in the EU, Canada, and many other jurisdictions - which means that registrars are either breaking their contract with  ICANN or national data retention laws.  Fadi - and the Board - recognised those difficulties and established the Expert Working Group (Carlton, for his sins, was a member) that came up with proposals to address those difficulties including a concept of making only limited information on registrants publicly available, with gated access to more layers of information, depending on the status of the requestor. And the Board has approved of the RDS WG to work - within its charter - through EWG proposals.  So, in that way too truncated recitation of the outline of the issues, the RDS WG that ALan, Carlton and I are members of, are working through what we do about that fundamental contradiction between basic data retention law and ICANN’s RAA.  And trust me, there are many interest groups that have had access to that publicly available personal information and are not happy at the prospect of losing that access.</span><br><span></span><br><span>End result - we are YEARS away from a final policy on who has what access to what level of registrant personal information. Which is why i cringe at the thought of yet another RDS WG - without a final, agreed policy framework on access to registrant data.</span><br><span></span><br><span>And yes, that is only one of the issues raised by Whois.</span><br><span></span><br><span>and what Carlton, Alan and I should be doing is bringing you all in to participate in this issue - I promise you, there is plenty of policy work for years to come - and I”d love company.</span><br><span> BUT PLEASE, not yet another review</span><br><span></span><br><span>Holly</span><br><span></span><br><span>On 9 Jan 2017, at 1:07 pm, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>> wrote:</span><br><span></span><br><blockquote type="cite"><span>I am attaching a document from the GNSO on the proposed RDS (formerly WHOIS) Review to be started very soon.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>You will recall that we previously had approved a narrowing of the scope of the RDS Review to focus just on the extent to which the previous WHOIS Review Recommendations had been implemented. This GNSO proposal widens the scope considerably. Although there is no question that the wider scope is interesting and ptentially useful, it will also require far more community involvement that the earlier proposal.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The call for volunteers was to close on 13 January and a decision needs to be made quickly on exactly what the Review should be.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Comments please, with some urgency.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Alan</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>From: "James M. Bladel" <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Subject: Re: RDS Review</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Date: Sun, 8 Jan 2017 17:42:53 +0000</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Dear Karen and Community Leaders </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>The GNSO Council, working with its component Stakeholder Groups and Constituencies, has produced this document (attached), which outlines our feedback and concerns with the proposed âlimited scopeâ for the upcoming RDS review.  The document was submitted to ICANN Staff, and sharing with this team for your reference.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Thank you,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>J.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>----------------</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>James Bladel</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>GNSO Chair</span><br></blockquote></blockquote><blockquote type="cite"><span><GNSO Council feedback on RDS.pdf>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>ALAC mailing list</span><br></blockquote><blockquote type="cite"><span><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a></span><br></blockquote><blockquote type="cite"><span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>At-Large Online: <a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a></span><br></blockquote><blockquote type="cite"><span>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></span><br></blockquote><span></span><br><span>_______________________________________________</span><br><span>ALAC mailing list</span><br><span><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a></span><br><span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a></span><br><span></span><br><span>At-Large Online: <a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a></span><br><span>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></span></div></blockquote></body></html>