<div dir="auto"><div>Hi all,</div><div dir="auto"><br></div><div dir="auto">Since there are no further inputs or comments, I will proceed to submit what I have here to the council as NCSG response, since today is the deadline for submission.</div><div dir="auto"><br></div><div dir="auto">Thanks again Farzi for your contribution to this.</div><div><br></div><div data-smartmail="gmail_signature">Warmly, <br>Tomslin</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, 29 Jan 2025, 07:30 Tomslin Samme-Nlar, <<a href="mailto:mesumbeslin@gmail.com">mesumbeslin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Farzi,</div><div><br></div><div>Thanks for the contribution. It is timely! <br></div><div><br></div><div>@everyone, are there any other suggested contributions to these questions?</div><div><br></div><div>I am also re-attaching the ICANN Org response here since it appears the previous link is now broken.<br clear="all"></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>Warmly,<br></div>Tomslin<div><span style="color:rgb(0,0,0);font-size:12.8px"><br></span></div></div></div></div></div></div></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 28 Jan 2025 at 15:17, farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com" target="_blank" rel="noreferrer">farzaneh.badii@gmail.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 dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div class="gmail_default" style="font-family:arial,sans-serif">Thanks Tomslin. Please see my responses below: </div><br clear="all"></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 7, 2025 at 8:58 PM Tomslin Samme-Nlar <<a href="mailto:mesumbeslin@gmail.com" target="_blank" rel="noreferrer">mesumbeslin@gmail.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 dir="ltr"><div>Hi all,</div><div><br></div><div>If you recall, Registration data accuracy has been a topic of contention in the community now for a while. Those who follow the the topic know that the Accuracy Scoping team was paused by the council due to challenges of pursuing further work on accuracy, including that <br></div><div><ol><li>It is unclear whether [the scenarios] would provide useful data to inform the Accuracy Scoping Team’s efforts;</li><li>The scenarios are not expected to provide data as it relates to identity verification of the registrant or veracity of the contact information (i.e., the data belongs to the data subject);</li><li>The costs associated with a full-scale registrar audit [Scoping Team Recommendation #2] may be prohibitive when taking into account the relatively low level of insight the audit may yield;</li><li>ICANN does not have the authority to mandate collection of nonpublic registration data necessary to conduct reviews outside of auditing current contractual requirements; and</li><li>ICANN may not be able to demonstrate the purpose of some of the data processing outweighs the rights of the impacted data subject.</li></ol></div><div>As a result, deliberations on this topic on the council was deferred till February and an assignment to ask ICANN Org some clarifying legal questions, and thereafter ask each SG/C to respond to a set of threshold questions that will help guide the way forward on this topic was agreed by the council. ICANN Org came back with their <a href="https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/d3fd2bca-021f-494b-957c-0c800d63f333__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1a2SSvlTw$" target="_blank" rel="noreferrer">response</a> just before the December holidays. </div><div><br></div><div>Now therefore, each SG/C is required to respond to the <a href="https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-proposal-accuracy-12sep24.pdf" target="_blank" rel="noreferrer">threshold questions</a> by Friday 31 January 2025. We forgot to include it for discussion in our Policy meeting earlier this week. However, I request that members provide their input via this email thread. Once agreed, we'll forward our response to the Council. The questions we have to answer are in the link above but for convenience, I'll list them here below:</div><div><ol><li><b>What are concrete and articulable examples of what inaccurate data DOES prevent or inhibit, and how does it do so?</b></li></ol></div></div></blockquote><div>Inaccurate domain name registrant data should be defined based on the purpose of accuracy within the scope of ICANN's mandate: ensuring that the registrant is 'contactable.' If the registrant cannot be reached due to undeliverable messages caused by errors in the provided contact details, the data should be deemed inaccurate.<span class="gmail_default" style="font-family:arial,sans-serif"> </span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><ol><li><b>What are concrete and articulable examples of what inaccurate data does NOT prevent?</b></li></ol></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><ol><li><b>Are there specific stakeholders, industries, or sectors particularly vulnerable to the effects of inaccurate registration data? If so, what are they and why?</b></li></ol></div></div></blockquote><div><div class="gmail_default" style="font-family:arial,sans-serif">Domain name registrants can be affected by insisting on having even more "accuracy" requirements. In order to ensure accuracy suggestions could be made to "identify" domain name registrants which goes against the principle of respecting anonymity should the domain name registrant want to remain anonymous and identification of registrants can have an adverse impact on data protection and access to domain names globally. </div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><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 dir="ltr"><div><ol><li><b>Given the examples provided in response to the three questions above (if any), please articulate a short problem statement for accuracy. The problem statement should consider:</b></li><ul><li><b>What is the current problem or challenge?</b></li><li><b>What are the consequences of this problem or challenge?</b></li><li><b>What is the ultimate objective of working on this problem or challenge?</b></li><li><b>Considering the limitations of data processing, how do you propose to address this problem?</b></li></ul></ol></div></div></blockquote><div><span class="gmail_default" style="font-family:arial,sans-serif">We don't believe there are many challenges facing data accuracy. There are already requirements in place for domain name registrants to keep their data accurate, and there is an ultimate punishment for that: losing their domain name if they don't do so. Please refer to registrants obligation here: <a href="https://www.icann.org/resources/pages/registration-data-accurate-2023-11-02-en?utm_source=chatgpt.com" target="_blank" rel="noreferrer">https://www.icann.org/resources/pages/registration-data-accurate-2023-11-02-en?utm_source=chatgpt.com</a></span> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><ol><li><b>Is now the appropriate time to address the problem? For example, some stakeholders have mentioned the implementation of NIS2 as an important precursor to understanding new accuracy requirements. Should this or other examples be considered prior to engaging in potential policy work?</b></li></ol></div></div></blockquote><div><div style="color:rgb(31,31,31);font-family:Roboto,Helvetica,Arial,sans-serif;font-size:14px;letter-spacing:0.2px">it's crucial to remember that NIS2 is a directive, not a regulation. Its implementation will vary across European jurisdictions, and it shouldn't set the accuracy standard for ICANN. This is due to two key reasons:</div><div style="color:rgb(31,31,31);font-family:Roboto,Helvetica,Arial,sans-serif;font-size:14px;letter-spacing:0.2px"><br></div><div style="color:rgb(31,31,31);font-family:Roboto,Helvetica,Arial,sans-serif;font-size:14px;letter-spacing:0.2px">1. NIS2's provisions concerning domain names were influenced by specific stakeholder groups, not by multistakeholder consensus.</div><div style="color:rgb(31,31,31);font-family:Roboto,Helvetica,Arial,sans-serif;font-size:14px;letter-spacing:0.2px">2. Some transposing laws (e.g., Germany) aim to identify registrants through data accuracy to prevent fraud. However, we believe that accuracy at ICANN should not necessitate registrant identification.</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><ol><li><b>Are the ICANN org alternatives proposals worth exploring, such as:</b></li><ul><li><b>Provision of historical audit data that measures registrars’ compliance with accuracy-related provisions in the RAA.</b></li><li><b>Engagement with contracted parties and ccTLD operators on developments in European policymaking regarding registration data accuracy.</b></li></ul><li><b>What are the limitations of the ICANN proposals? Why should or should they not be pursued?</b></li><li><b>What other possibilities can be explored to move our work on Accuracy forward?</b></li></ol></div><div>I look forward to your contribution to these questions.<br></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>Warmly,<br></div>Tomslin<div><span style="color:rgb(0,0,0);font-size:12.8px"></span></div><div><span style="color:rgb(0,0,0);font-size:12.8px"><br></span></div></div></div></div></div></div></div></div></div></div></div></div></div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">Feodora Hamza via council</b> <span dir="auto"><<a href="mailto:council@icann.org" target="_blank" rel="noreferrer">council@icann.org</a>></span><br>Date: Thu, 12 Dec 2024 at 23:11<br>Subject: [council] Re: Follow-up GNSO Council Accuracy Assignment<br>To: DiBiase, Gregory <<a href="mailto:dibiase@amazon.com" target="_blank" rel="noreferrer">dibiase@amazon.com</a>>, <a href="mailto:council@gnso.icann.org" target="_blank" rel="noreferrer">council@gnso.icann.org</a> <<a href="mailto:council@gnso.icann.org" target="_blank" rel="noreferrer">council@gnso.icann.org</a>><br></div><br><br><div>
<div lang="en-NL">
<div>
<p class="MsoNormal"><span lang="DE-CH" style="font-family:Aptos,sans-serif">Dear Councilors,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="DE-CH" style="font-family:Aptos,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:Aptos,sans-serif">due to technical issues, please see accuracy assignment attached and linked below.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:Aptos,sans-serif">Accuracy Assignment:
<a href="https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-proposal-accuracy-12sep24.pdf" target="_blank" rel="noreferrer">
https://gnso.icann.org/sites/default/files/policy/2024/draft/draft-concept-proposal-accuracy-12sep24.pdf</a>
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:Aptos,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:Aptos,sans-serif">Kind regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-family:Aptos,sans-serif">Feodora Hamza<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Aptos,sans-serif"><u></u> <u></u></span></p>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentcolor currentcolor;padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:12pt;color:black">From:
</span></b><span lang="EN-US" style="font-size:12pt;color:black">"DiBiase, Gregory via council" <<a href="mailto:council@icann.org" target="_blank" rel="noreferrer">council@icann.org</a>><br>
<b>Reply to: </b>"DiBiase, Gregory" <<a href="mailto:dibiase@amazon.com" target="_blank" rel="noreferrer">dibiase@amazon.com</a>><br>
<b>Date: </b>Thursday, 12 December 2024 at 20:57<br>
<b>To: </b>"<a href="mailto:council@gnso.icann.org" target="_blank" rel="noreferrer">council@gnso.icann.org</a>" <<a href="mailto:council@gnso.icann.org" target="_blank" rel="noreferrer">council@gnso.icann.org</a>><br>
<b>Subject: </b>[council] Follow-up GNSO Council Accuracy Assignment<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12pt;font-family:Aptos,sans-serif"><u></u> <u></u></span></p>
</div>
<div style="border:1pt solid rgb(170,183,184);padding:9pt 15pt;margin-bottom:15pt;border-radius:2px;box-sizing:border-box" id="m_-2838618194215911936m_-3374897119280912567m_-3676270597125658733m_-7332355707455580457m_-7747752021881977879m_-536660239216140031m_5544954348878318178m_-31504803274369481370d892d34-3e72-4293-a311-64ec2c2bf8eb">
<div style="margin-bottom:6pt">
<ul style="margin-top:0cm" type="disc">
<li style="margin-top:0cm;margin-bottom:0cm">
<b><span lang="EN-US" style="font-size:10.5pt;font-family:Arial,sans-serif">Attachments protected by Amazon:
</span></b><span lang="EN-US"><u></u><u></u></span></li><li style="color:rgb(0,115,187);margin-top:0cm;margin-bottom:0cm;display:inline-block">
<span lang="EN-US"><a href="https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/d3fd2bca-021f-494b-957c-0c800d63f333__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1a2SSvlTw$" title="Answer to the GNSO questions on accuracy.pdf" target="_blank" rel="noreferrer"><span style="font-size:10.5pt;font-family:Arial,sans-serif;color:rgb(0,115,187);text-decoration:none">Answer
to the GNSO questions on accuracy.pdf [us-east-1.secure-attach.amazon.com]</span></a>
</span><span><span lang="EN-US" style="color:rgb(104,112,120)">|
</span></span><span lang="EN-US"><u></u><u></u></span></li><li style="color:rgb(0,115,187);margin-top:0cm;margin-bottom:0cm;display:inline-block">
<span lang="EN-US"><a href="https://urldefense.com/v3/__https:/us-east-1.secure-attach.amazon.com/da78dbeb-dd4d-4f3f-96c2-1d5abfe7810b/94d6cb3e-3ab2-446c-a385-9c201a9cffc9__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1ZAKmAJaA$" title="ATT00001.txt" target="_blank" rel="noreferrer"><span style="font-size:10.5pt;font-family:Arial,sans-serif;color:rgb(0,115,187);text-decoration:none">ATT00001.txt
[us-east-1.secure-attach.amazon.com]</span></a> </span><span><span lang="EN-US" style="color:rgb(104,112,120)">|
</span></span><span lang="EN-US"><u></u><u></u></span></li></ul>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12pt;font-family:Aptos,sans-serif">Amazon has replaced the attachments in this email with download links. Downloads will be available until January 11, 2025, 19:56 (UTC+00:00).
<a href="https://urldefense.com/v3/__https:/amazonexteu.qualtrics.com/jfe/form/SV_ehuz6zGo8YnsRKK__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1Zzdd6ztA$" target="_blank" rel="noreferrer">
<span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(0,115,187)">Tell us what you think [amazonexteu.qualtrics.com]</span></a>
<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:12pt;font-family:Aptos,sans-serif">For more information click
<a href="https://urldefense.com/v3/__https:/docs.secure-attach.amazon.com/guide__;!!PtGJab4!5ebsdR0WRUrjpIzUO8HekPbjqckThf0GWEiIM_7eVuzWwd4NAuc_-nt2-GqtwpE87UIulB_KPGxmS00M_1ZzNkqBbQ$" target="_blank" rel="noreferrer">
<span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(0,115,187)">here [docs.secure-attach.amazon.com]</span></a>
<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US">Dear Councilors,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">I am following up on the attached email from ICANN Org in which they provided their input on the accuracy assignment. On 25 October, we shared the proposed accuracy assignment, which included questions for ICANN org
and the community. <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Now that ICANN org has provided responses to the Council’s questions, we are now sending the remaining questions in the attached proposal to interested SG/C/ACs for their input. Given the proximity to the holidays, we
propose giving groups until Friday, 31 January 2025 to provide their input to the Council.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">As noted during the Council’s previous discussions on the topic of accuracy, the Council recognizes the importance of accuracy and is committed to making progress on this issue. Your group’s responses to these questions
are very important for the Council’s future discussion, and we strongly encourage your groups to think about these questions and provide candid responses.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Thank you in advance for your input.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Greg<u></u><u></u></span></p>
</div>
</div>
_______________________________________________<br>
council mailing list -- <a href="mailto:council@icann.org" target="_blank" rel="noreferrer">council@icann.org</a><br>
To unsubscribe send an email to <a href="mailto:council-leave@icann.org" target="_blank" rel="noreferrer">council-leave@icann.org</a><br>
<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 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 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.</div></div></div>
</blockquote></div></div>
</div>
</div>
</div>
</div>
</blockquote></div>
</blockquote></div>