<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Dear Fazaneh,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
thanks for sharing can i join the small team to work in this topic please ?</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks in advance, </div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>De :</b> NCSG-Discuss <NCSG-DISCUSS@LISTSERV.SYR.EDU> de la part de farzaneh badii <farzaneh.badii@GMAIL.COM><br>
<b>Envoyé :</b> vendredi 20 juin 2025 16:35<br>
<b>À :</b> NCSG-DISCUSS@LISTSERV.SYR.EDU <NCSG-DISCUSS@LISTSERV.SYR.EDU><br>
<b>Objet :</b> Important: DNS Abuse Small Group</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div>
<div class="x_gmail_default" style="font-family:arial,sans-serif">Dear Members, </div>
<div class="x_gmail_default" style="font-family:arial,sans-serif"><br>
</div>
<div class="x_gmail_default" style="font-family:arial,sans-serif">As I mentioned before the Council has a small team on DNS abuse and we need to write up an issue report. At the moment we are working on the gaps here: <a href="https://docs.google.com/spreadsheets/d/1TRyUYb4Dr1VqxJ1H9n983ClbGx968QK0/edit?gid=1836517289#gid=1836517289">https://docs.google.com/spreadsheets/d/1TRyUYb4Dr1VqxJ1H9n983ClbGx968QK0/edit?gid=1836517289#gid=1836517289</a></div>
<div class="x_gmail_default" style="font-family:arial,sans-serif">The small team members should consult with their stakeholder groups. So I am consulting with you, here are the concerns I see in the solutions and going to send a few of the concerns to the small
team after your consideration. Please weigh in by next week: </div>
<div class="x_gmail_default" style="font-family:arial,sans-serif"><br>
</div>
<div class="x_gmail_default" style="font-family:arial,sans-serif">
<div class="x_gmail-markdown x_gmail-markdown-main-panel x_gmail-stronger x_enable-updated-hr-color" id="x_gmail-model-response-message-contentr_c1674cd55a488b80" dir="ltr" style="background:none 0% 0%/auto repeat scroll padding-box border-box rgba(0,0,0,0); border:0px none rgb(27,28,29); clear:none; color:rgb(27,28,29); columns:auto; direction:ltr; float:none; isolation:auto; margin:0px; opacity:1; outline:rgb(27,28,29) none 0px; padding:0px; quotes:auto; speak:normal; zoom:1; font-family:"Google Sans Text",sans-serif; line-height:1.15">
<p style="background:none 0% 0%/auto repeat scroll padding-box border-box rgba(0,0,0,0); border:0px none rgb(27,28,29); clear:none; columns:auto; direction:ltr; float:none; isolation:auto; margin:0px 0px 16px; opacity:1; outline:rgb(27,28,29) none 0px; padding:0px; quotes:auto; speak:normal; zoom:1; line-height:1.15">
<br>
</p>
<h3><font size="2" style="">Principles for Rights-Respecting DNS Abuse Mitigation</font></h3>
<h3 style="background:none 0% 0%/auto repeat scroll padding-box border-box rgba(0,0,0,0); border:0px none rgb(27,28,29); clear:none; columns:auto; direction:ltr; float:none; isolation:auto; margin:0px 0px 8px; opacity:1; outline:rgb(27,28,29) none 0px; padding:0px; quotes:auto; speak:normal; zoom:1; font-family:"Google Sans",sans-serif; line-height:1.15">
<p><span style="font-weight:normal"><font size="2">Associated Domains & Surveillance<br>
When investigating actionable DNS abuse, registrars may need to examine other domains associated with the same registrant data to disrupt broader abuse networks. However, such inspections must be conducted with strict safeguards to avoid undue surveillance
of legitimate registrants. Investigations must be grounded in clear, specific evidence of abuse linked to the registrant—never on speculative or broad profiling. The focus must remain on the abusive activity, not on surveilling the registrant’s broader online
presence.</font></span></p>
<p><span style="font-weight:normal"><font size="2">Domain Pricing & Access<br>
Affordable or free domain names are essential for digital inclusion. They allow individuals, small businesses, and civil society groups to establish a presence online.</font></span></p>
<ul>
<li>
<p><span style="font-weight:normal"><font size="2">Pricing should not be used as a blunt tool for abuse mitigation. Doing so risks disproportionately harming legitimate users and undermining efforts to expand equitable access to the Internet.</font></span></p>
</li><li>
<p><span style="font-weight:normal"><font size="2">Abuse mitigation by registrars offering low-cost domains should instead rely on rights-respecting measures: clear abuse reporting channels, prompt investigation, proportionate response, and strong due process—not
financial barriers.</font></span></p>
</li></ul>
<p><span style="font-weight:normal"><font size="2">Reactive vs. Proactive Measures<br>
Well-implemented reactive measures can be as effective as proactive strategies in addressing abuse.</font></span></p>
<ul>
<li>
<p><span style="font-weight:normal"><font size="2">However, overly broad or premature proactive interventions (e.g., preemptive takedowns, automated flagging) can generate false positives, unjust suspensions, and chilling effects on lawful expression.</font></span></p>
</li><li>
<p><span style="font-weight:normal"><font size="2">Any proactive measure must be subject to rigorous human rights risk assessment, implemented with narrowly tailored scope, transparency, and meaningful recourse options to ensure proportionality and accountability.</font></span></p>
</li></ul>
<p><span style="font-weight:normal"><font size="2">Pre-Mitigation Due Diligence<br>
Before taking any mitigation action, registrars must carry out thorough and proportionate due diligence based on specific, actionable evidence. This helps prevent false positives and ensures that mitigation measures are appropriate to the verified abuse. Where
possible, less restrictive alternatives should be considered before resorting to domain suspension.</font></span></p>
<p><span style="font-weight:normal"><font size="2">During Mitigation Transparency<br>
When action is taken against a domain, the registrant must be promptly notified. This notice should include:</font></span></p>
<ul>
<li>
<p><span style="font-weight:normal"><font size="2">The reason for the action;</font></span></p>
</li><li>
<p><span style="font-weight:normal"><font size="2">The type of action taken;</font></span></p>
</li><li>
<p><span style="font-weight:normal"><font size="2">The initiator of the action (e.g., registrar, third-party request);</font></span></p>
</li><li>
<p><span style="font-weight:normal"><font size="2">A clear explanation in accessible language.</font></span></p>
</li></ul>
<p><span style="font-weight:normal"><font size="2">Post-Mitigation Remedy & Recourse<br>
Registrars must maintain accessible and transparent mechanisms for registrants to seek remedy or challenge decisions. This includes:</font></span></p>
<p></p>
<ul>
<li>
<p><span style="font-weight:normal"><font size="2">Restoration Process: A pathway for legitimate registrants to demonstrate that abuse has been resolved—or that the action was mistaken—and regain control of their domain in a timely manner.</font></span></p>
</li><li>
<p><span style="font-weight:normal"><font size="2">Complaints & Appeals: A clear and fair process through which registrants can file complaints or appeal mitigation actions, reinforcing procedural fairness and accountability.</font></span></p>
</li></ul>
</h3>
</div>
</div>
<br clear="all">
</div>
<div>
<div dir="ltr" class="x_gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div><font face="verdana, sans-serif">Farzaneh </font></div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>