<div dir="ltr"> Dear Farzaneh,<div>Thank you for providing context and putting this letter together.</div><div>I support the letter.</div><div><br></div><div>Kind regards,</div><div>Benjamin </div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Nov 27, 2025 at 1:50 AM gopal <<a href="mailto:gopal@annauniv.edu">gopal@annauniv.edu</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 class="msg-6515110080984437775">
<div dir="ltr">
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Thank you Farzaneh.</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
How does this take into account GDPR Right to Erasure / to be Forgotten" @ <a href="https://gdpr.eu/right-to-be-forgotten/#:~:text=In%20Article%2017%2C%20the%20GDPR,that%20individual%20withdraws%20their%20consent." target="_blank">
https://gdpr.eu/right-to-be-forgotten/#:~:text=In%20Article%2017%2C%20the%20GDPR,that%20individual%20withdraws%20their%20consent.</a></div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Gopal T V</div>
<div id="m_2677928198555056659Signature">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<span style="font-size:14.6667px;color:rgb(32,31,30);background-color:rgb(255,255,255)">0 9840121302</span><br>
<span style="font-size:14.6667px;background-color:rgb(255,255,255)"><a style="margin:0px;background-color:rgb(255,255,255);text-align:left" rel="noopener noreferrer" id="m_2677928198555056659OWA4ee9f1ba-14b8-b3fd-da94-a2c8f03ff483" href="https://vidwan.inflibnet.ac.in/profile/57545" target="_blank">https://vidwan.inflibnet.ac.in/profile/57545</a></span><br>
<span style="font-size:14.6667px;background-color:rgb(255,255,255)"><a style="margin:0px;background-color:rgb(255,255,255);text-align:left" rel="noopener noreferrer" id="m_2677928198555056659OWA7a16808f-b128-216f-331c-47c4acc1b7a7" href="https://www.facebook.com/gopal.tadepalli" target="_blank">https://www.facebook.com/gopal.tadepalli</a></span><br>
<span style="font-size:14.6667px;color:rgb(32,31,30);background-color:rgb(255,255,255)">++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++</span><br>
<span style="font-size:14.6667px;color:rgb(32,31,30);background-color:rgb(255,255,255)">Dr. T V Gopal</span><br>
<span style="font-size:14.6667px;color:rgb(32,31,30);background-color:rgb(255,255,255)">Retired Professor</span><br>
<span style="font-size:14.6667px;color:rgb(32,31,30);background-color:rgb(255,255,255)">Department of Computer
Science and Engineering &</span></div>
<div><span style="font-size:14.6667px;color:rgb(32,31,30)">Retired Director, Centre for Applied Research in Indic Technologies [CARIT]<br>
</span><span style="font-size:14.6667px;color:rgb(32,31,30);background-color:rgb(255,255,255)">College of
Engineering, Guindy Campus</span><br>
<span style="font-size:14.6667px;color:rgb(32,31,30);background-color:rgb(255,255,255)">Anna University</span><br>
<span style="font-size:14.6667px;color:rgb(32,31,30);background-color:rgb(255,255,255)">Chennai - 600 025,
INDIA</span><br>
<span style="font-size:14.6667px;color:rgb(32,31,30);background-color:rgb(255,255,255)">Ph : (Off) 22351723
Extn. 3340</span><br>
<span style="font-size:14.6667px;color:rgb(32,31,30);background-color:rgb(255,255,255)"> (Res) 24454753</span><br>
<span style="font-size:14.6667px;color:rgb(32,31,30);background-color:rgb(255,255,255)">++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++</span></div>
</div>
<div id="m_2677928198555056659appendonsend"></div>
<hr style="display:inline-block;width:98%">
<div id="m_2677928198555056659divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> NCSG-Discuss <<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank">NCSG-DISCUSS@LISTSERV.SYR.EDU</a>> on behalf of farzaneh badii <<a href="mailto:farzaneh.badii@GMAIL.COM" target="_blank">farzaneh.badii@GMAIL.COM</a>><br>
<b>Sent:</b> 23 November 2025 22:33<br>
<b>To:</b> <a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank">NCSG-DISCUSS@LISTSERV.SYR.EDU</a> <<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank">NCSG-DISCUSS@LISTSERV.SYR.EDU</a>><br>
<b>Subject:</b> Important Law Enforcement Agencies, Authentication, Accountability and Safeguards</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div>
<p>Dear all,</p>
<p>I want to provide an update on where things currently stand regarding law-enforcement (LEA) authentication, the work of the practitioner group, and the implications of the ICANN Board’s October 2025 resolution. </p>
<p>Given recent developments, I believe NCSG should consider a coordinated response. Several months ago, when PSWG<span style="font-family:arial,sans-serif"> (public Safety Working Group)</span> Gabriel briefed us on their intention
to work with ICANN Org to validate LEA domain names, NCSG agreed that LEA could submit domain names<span style="font-family:arial,sans-serif"> of Law Enforcement Agencies</span> to the RDRS, but only if specific safeguards and conditions
were met. </p>
<p>We conveyed these conditions clearly at the time, yet we have not received any indication that these concerns are being incorporated into<span style="font-family:arial,sans-serif"> PSWG's planning</span>. To remind everyone of what
NCSG agreed to:<span style="font-family:arial,sans-serif">1) </span> a verified LEA domain can serve only as a supplementary signal and not as a standalone authentication mechanism.
<span style="font-family:arial,sans-serif">2) </span>Disclosure decisions must still be grounded in rights-balancing, necessity, and a clear legal basis.
<span style="font-family:arial,sans-serif">3) </span>We stressed that domain validation does not prove identity; spoofing remains a serious risk, and both registrars and ICANN must be equipped to handle that.
<span style="font-family:arial,sans-serif">4) </span>We also emphasized that any “verified LEA domain list” must include renewal, periodic review, and removal processes to prevent stale or misused entries—especially for agencies that
operate multiple domains. In addition, we were explicit that domain-based checks can only be a temporary measure while a more robust, accountable authentication system is being developed.<span style="font-family:arial,sans-serif"> 5)</span>
We recommended a six-month review period to evaluate registrar confidence, safeguard effectiveness, and progress toward a long-term solution. </p>
<p>Importantly, we made clear that any authentication mechanism must incorporate safeguards, transparency, oversight, and avenues for redress for registrants whose data may be accessed.</p>
<p>The Board’s <a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-30-10-2025-en" target="_blank">
October 2025 resolution intersects</a> with this work by encouraging expanded LEA authentication efforts and urging alignment of SSAD-related policies with disclosure mechanisms. However, the Board’s rationale focuses almost exclusively on RDRS continuity,
registrar/requestor satisfaction, voluntary participation, and ICANN’s operational resources. What is missing is any acknowledgment of the safeguards, accountability requirements, or user-impact considerations that NCSG has raised repeatedly in meetings, letters,
and contributions to the RDRS Standing Committee report. Registrants and end users—who are directly affected—are absent from the Board’s “community impact” framing.</p>
<p>Given this gap between what NCSG has consistently recommended and what the Board has recognized, I suggest that NCSG take two steps. </p>
<p>First, send a short letter to the ICANN Board reaffirming that we support LEA authentication only if safeguards, transparency, oversight, and renewal mechanisms are integral to the system, and noting that the resolution omits the impact on registrants and
end users. </p>
<p>Second, develop a concise Human Rights Impact Assessment (HRIA) of the Board resolution and the related RDRS/SSAD work, mapping risks to privacy, due process, non-discrimination, and access to remedy, particularly around cross-border LEA requests. </p>
<p>I can prepare a first draft of the Board letter and a short HRIA scoping note for review.</p>
<p>Best regards,<br>
<br>
</p>
</div>
<div>
<div dir="ltr">
<div dir="ltr">
<div><font face="verdana, sans-serif">Farzaneh </font></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div></blockquote></div>