<p dir="ltr">Thanks Lisa for this update, it helps a lot as I am not Helsinki.</p>
<p dir="ltr">Best Regards<br>
--ff--</p>
<p dir="ltr">Mail sent from my mobile phone. Excuse for brievety.</p>
<div class="gmail_quote">Le 27 juin 2016 10:37 PM, "Lisa Phifer" <<a href="mailto:lisa@corecom.com">lisa@corecom.com</a>> a écrit :<br type="attribution"><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">Dear all,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Many thanks to all who participated in Monday’s Cross-Community session on RDS. The full transcript of the session will be posted on the meeting page (<a href="http://sched.co/7NCc" target="_blank">http://sched.co/7NCc</a>) when available. In the meantime, below are rough notes capturing additional possible requirements suggested by attendees. <u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">These and other additions suggested through Outreach #2 will be recorded in the SO/AC/SG/C section of this WG’s wiki (<a href="https://community.icann.org/x/pYxlAw" target="_blank"><span style="color:#3b73af;background:white">https://community.icann.org/x/pYxlAw</span></a>) and addressed during our Tuesday F2F WG meeting. Thanks again to WG members serving as liaisons for working to relay further inputs from other groups.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Best,<u></u><u></u></p><p class="MsoNormal">Lisa<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal" style="text-autospace:none"><u><span style="color:black">Possible Requirements suggested by attendees:</span></u><u><span style="color:black"><u></u><u></u></span></u></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><span style="color:black"><u></u> <u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Uniform presentation of data across all registrars or registries</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Access to LEAs</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Ability to consult the history of a registration</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Consider whether a domain registration must require verification that there is a real person behind the domain name registration</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">In the spirit of many data protection laws around the world, users should know for what purposes their data is given and to whom</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">When using a domain name from a person perspective, I wish my data would not be available to marketing purposes</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">When I buy something on the web, I would like to be able to access the registration data for the web page I am using to know it is the real company</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">There are a lot of third parties (not just LEAs) who have legitimate reasons for access to avoid their rights being infringed upon</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">A key issue is translation or transliteration of registration data - including provision of contact data and address in local languages</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Related to TM Clearinghouse notices, when notices are received, analysis that is performed includes going to see who is the registrant - this often eliminates the need for further action (~60-70%)</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">For any registered domain, there should be a valid admin and technical contact and this information should be public, with "as of" date (as minimum)</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Instead of adding to list, we should subtract things in the spirit of minimization - for example, removing the address from RDS to reduce risk to individual registrants such as journalists, bloggers, and many civil society organizations</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Having fewer requirements might be helpful. One way to do that is to not include possible requirements where there may be a better alternative to achieve the result in a better way</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">Regarding new plan for transatlantic data protection (i.e., Privacy Shield) to replace the annulled Safe Harbor mechanism - WG should recognize this work is going on and keep track of its progress as it applied to possible requirements for data protection</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">In existing WHOIS there wasn't a clear interface to access registration data - it is a requirement to have a clear interface that makes access easier (i.e., restful API)</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal" style="margin-left:.5in;text-autospace:none"><u></u><span style="font-family:"Arial","sans-serif";color:black"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="color:black">There should be a fast real-time way to see whether a domain name has been registered through a proxy service provider or has privacy protection. This could ease up concerns about domains having information omitted</span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal"><u></u> <u></u></p></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>