<div dir="ltr">Thank you Sarah.<div><br></div><div>Greg just for completeness, an EU data subject will of course still be entitled to exercise their rights against the 'SSAD' also. If their data is processed within the SSAD then whoever is the guardian of that system, shall have to have </div><div>a) a viable and robust process for dealing with such requests directly themselves (assuming they are a controller), and/or</div><div> b) provide the necessary information and aid to other controllers dealing with such requests in this data processing ecosphere (especially Art 17). </div><div><br></div><div>But I do agree, expecting them to have to be a "subscribed" or "credentialed" user in order to exercise such rights is a <b><u>very</u></b> bad idea. </div><div><br></div><div>Alan</div><div><br></div><div> <br><div><div><div dir="ltr" class="m_1496788725533117473gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><table style="padding:0px;margin:10px 0;border:none"><tbody><tr><td style="vertical-align:middle;padding:0px 7px 0px 0px"><a href="http://donuts.domains" rel="nofollow" target="_blank"><img alt="Donuts Inc." height="75" src="https://storage.googleapis.com/signaturesatori/customer-C02zzlf7k/images/-54f9d8ac97e7f575bf497d10ac1f1aafafddf8afceab5f269d49034f01b3217b.png" width="75"></a></td><td style="vertical-align:middle;padding:0px 7px 0px 0px;text-align:left">
<div style="font-family:'tahoma',sans-serif;font-size:14px;line-height:17px;font-weight:bold;color:black"><span style="font-size:12px"><span style="font-family:'arial','helvetica',sans-serif"><span style="color:rgb(51,51,51)">Alan Woods</span></span></span></div>
<div><span style="font-size:12px"><span style="font-family:'arial','helvetica',sans-serif"><span style="color:#333333">Senior Compliance & Policy Manager, Donuts Inc.</span></span></span>
<hr><span style="font-size:11px"><span style="font-family:'arial','helvetica',sans-serif"><span style="color:#333333">The Victorians, </span></span></span></div><div><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:11px">15-18 Earlsfort Terrace<br style="background-color:rgb(34,34,34)">
Dublin 2, County Dublin</span></font><br style="color:rgb(214,214,214);font-family:'open sans';font-size:12px;background-color:rgb(34,34,34)"><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:11px">
Ireland</span></font><br>
<span style="font-size:11px"><span style="font-family:'arial','helvetica',sans-serif"></span></span><br>
<span style="line-height:36px"><a href="https://www.facebook.com/donutstlds" rel="nofollow" target="_blank"><img src="http://storage.googleapis.com/signaturesatori/icons/facebook.png"></a> <a href="https://twitter.com/DonutsInc" rel="nofollow" target="_blank"><img src="http://storage.googleapis.com/signaturesatori/icons/twitter.png"></a> </span><a href="https://www.linkedin.com/company/donuts-inc" rel="nofollow" target="_blank"><span style="font-size:14px"><img src="http://storage.googleapis.com/signaturesatori/icons/linkedin.png"></span></a></div>
</td></tr></tbody></table><br>
</div><div><span style="font-size:12pt;font-family:Cambria,serif">Please NOTE: This electronic message, including any attachments, may include privileged, confidential and/or inside information owned by Donuts Inc. . </span><span style="font-size:12pt;font-family:Cambria,serif">Any distribution or use of this communication by anyone other than the intended recipient(s) is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by replying to this message and then delete it from your system. Thank you.</span><br></div></div></div></div></div></div></div></div></div></div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 7, 2019 at 3:33 PM Greg Aaron <<a href="mailto:greg@illumintel.com" target="_blank">greg@illumintel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="white" lang="EN-US"><div class="gmail-m_1496788725533117473gmail-m_2952629986958181326WordSection1"><p class="MsoNormal"><span style="color:windowtext">Agree. Registrants already have the appropriate means to view their own sensitive data fields and update their domain data: the registrar’s system. And that provides controlled, permissioned access for the registrants to see their data and theirs only. And registrants will have public access to RDS to see non-sensitive data about their domains.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:windowtext"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:windowtext">To offer registrants access to the SSAD System on top of that would be a nightmare from an access management view. (How would registrants get credentials into a SSAD, and how would that system know what records the registrant is allowed to see?) SSAD is for third parties who need to access non-public data.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:windowtext"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:windowtext">All best,<u></u><u></u></span></p><p class="MsoNormal"><span style="color:windowtext">--Greg<u></u><u></u></span></p><p class="MsoNormal"><span style="color:windowtext"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:windowtext"><u></u> <u></u></span></p><div><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in"><p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank">gnso-epdp-team-bounces@icann.org</a>> <b>On Behalf Of </b>Sarah Wyld<br><b>Sent:</b> Thursday, June 6, 2019 9:36 AM<br><b>To:</b> <a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a><br><b>Subject:</b> [Gnso-epdp-team] RrSG initial comment on SSAD Registrant user group<u></u><u></u></span></p></div></div><p class="MsoNormal"><u></u> <u></u></p><p>Hello all,<u></u><u></u></p><p style="margin-bottom:12pt">The RrSG has significant concerns with the inclusion of Registrants as a user group for the System for Standardized Disclosure of non-public gTLD registration data, and strongly recommends that this group be removed from the proposed list of users. We are curious as to the origin of these proposed user groups, and suggest that instead of working through this list we begin by reviewing the purposes for processing data (Recommendation 1) and assessing the potential user group applicable to each purpose. <br><br>Registrants already access their domains via their service provider (registrar or reseller)’s system, as required under the RAA. Having multiple interfaces to access the same information poses a significant risk of inappropriate data exposure; this unnecessary and unbalanced security risk is not compliant with data protection law. It also creates a confusing user experience for the registrant. For example, if a registrant uses the SSAD to review their domain data for the purpose of confirming that it is accurate, they would still need to work with their service provider to confirm that the data held in that system is also up to date. <br><br>The RrSG notes that a system used to access or disclose data is not also a system to modify that data. The EPDP team definitions of access and disclosure do not include any capability to modify the data, so this is a new addition to the requirements not grounded in any previously agreed-upon basis or definition. Modification of domains via the SSAD could easily result in synchronization issues and security risks, where the SSAD holds data that is different from what is in the registrar or reseller’s platform, or an unauthorized party could modify and even hijack a registered domain. This also represents a fundamental shift from the system in place for the past twenty years: EPP is one-directional, with data flowing from the reseller or registrar through to the registry, so any functionality for updating domain data would need to be created and implemented by thousands of service providers worldwide. <br><br>We look forward to discussing this important concern at today’s EPDP team call. Beyond these concerns about the “Registrants” group, we are also uncertain that “end users” is a valid group; this and the other groups should be discussed with the plenary team. <u></u><u></u></p><pre>-- <u></u><u></u></pre><pre>Sarah Wyld<u></u><u></u></pre><pre>Domains Product Team<u></u><u></u></pre><pre>Tucows<u></u><u></u></pre><pre>+1.416 535 0123 Ext. 1392<u></u><u></u></pre><pre><u></u> <u></u></pre><pre> <u></u><u></u></pre></div></div>_______________________________________________<br>
Gnso-epdp-team mailing list<br>
<a href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a><br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div>