<div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif">Hi Bruna,</div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">Here are some preliminary comments. We can work on them if you want to send something on behalf of NCSG:</div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">1. Thank you for focussing on protecting registrants when fighting with DNS abuse. They are most of the time neglected.</div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">2. They mention that the registrars are contributing to DNS abuse "community mechanisms".We should be clear that we are not sure how NCSG and noncommercials are included in these efforts. If they mean by community effort you as being a part of DNS abuse institute advisory council or Stephanie Perrin as the rep on the advisory council of PIR then I think they should be clear about that. If they mean "community efforts" at ICANN then I am not sure what they mean. </div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">3. Under the Evidentiary section, this is not an appeals mechanism or a pre-appeal mechanism. What they are describing is the evidence that the DNS abuse complaints should include and is a part of the due process they need to provide for the registrants. That section needs to be much more detailed with a process on how the abuse reports are treated, what sort of evidence they need from the complainant etc.</div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">4. I have not heard the term "ombud". It is either Ombuds or Ombuds Person or Ombuds Office. It's a good idea but they need to look into what they mean by "binding" outcomes because usually Ombuds outcomes are not legally binding - So the registrar binds itself by it? </div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">5. Fundamental problem with this white paper is that it bases the protection of registrants from fraudulent and frivolous DNS abuse complaints (or just simply mistaken ones) by just considering ex post dispute resolution and appeals mechanism. It is a good step forward but that is not enough. Measures should be taken to reduce the number of unfairly impacted domains before they actually happen. People have businesses and websites and they rely on their domain name. A shut-down can cost them a lot and affects them financially as well as operationally and their activism and whatever service is time-sensitive. </div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div><div dir="ltr" data-smartmail="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 Mon, Jun 28, 2021 at 10:28 AM Bruna Martins dos Santos <<a href="mailto:bruna.mrtns@gmail.com" target="_blank">bruna.mrtns@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">Hey all, <div><br></div><div>Hope this email finds you well. </div><div><br></div><div>RrSG just issued a white paper on DNS abuse mitigation that Ashley Heineman kindly sent to NCUC in order to gather any input from the Constituency. Given that this is a policy discussion that is more often discussed at the SG level and by the PC, I am also sharing the paper on our list in order to check whether anyone would like us to offer additional input to this initiative. </div><div><br></div><div>The deadline Raphael set for NCUC is Thursday (01.07), so I believe we can adopt the same one. <br><br>Best, </div><div>Bruna </div><div><br></div><div><br></div><div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">Raphael Beauregard-Lacroix</strong> <span dir="auto"><<a href="mailto:rbeauregardlacroix@gmail.com" target="_blank">rbeauregardlacroix@gmail.com</a>></span><br>Date: Mon, Jun 28, 2021 at 11:04 AM<br>Subject: [NCUC-DISCUSS] Fwd: RrSG Draft White Paper: Registrant Protections in DNS Abuse Mitigation<br>To: NCUC Discuss <<a href="mailto:ncuc-discuss@lists.ncuc.org" target="_blank">ncuc-discuss@lists.ncuc.org</a>><br></div><br><br><div dir="ltr">Dear all, <div><br></div><div>The Registrar SG has drafted a white paper on DNS abuse mitigation and would like to know if we (NCUC) have any input to provide. See below for more info and attachment. </div><div><br></div><div>Feel free to discuss in this thread by Thursday COB UTC. </div><div><br></div><div>Thank you and have a nice day, <br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto"><a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a></strong> <span dir="auto"><<a href="mailto:aheineman@godaddy.com" target="_blank">aheineman@godaddy.com</a>></span><br>Date: Fri, Jun 4, 2021 at 8:08 PM<br>Subject: RrSG Draft White Paper: Registrant Protections in DNS Abuse Mitigation<br>To: <a href="mailto:rbeauregardlacroix@gmail.com" target="_blank">rbeauregardlacroix@gmail.com</a> <<a href="mailto:rbeauregardlacroix@gmail.com" target="_blank">rbeauregardlacroix@gmail.com</a>><br>Cc: Zoe Bonython <<a href="mailto:secretariat@icannregistrars.org" target="_blank">secretariat@icannregistrars.org</a>>, Reg Levy <<a href="mailto:rlevy@tucows.com" target="_blank">rlevy@tucows.com</a>>, Luc SEUFER <<a href="mailto:lseufer@namespace.com" target="_blank">lseufer@namespace.com</a>><br></div><br><br>
<div lang="EN-US">
<div>
<p class="MsoNormal">Dear Raphaël Beauregard-Lacroix,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The RrSG DNS Abuse Subgroup drafted the attached White Paper discussing Registrant Protections in DNS Abuse Mitigation, centering on the issue of innocent registrants whose domains are impacted by DNS Abuse mitigation by a registrar (or registry,
as the case may be). The RrSG is looking to publish the paper around the time of ICANN 71, but wanted to give the NCUC the opportunity to provide comments in advance as we know this is an issue of interest to your members. This paper is not time sensitive,
so if you would like additional time, please let us know. As additional background, the RrSG periodically drafts and publishes white papers for informational purposes, and this is our first attempt to better socialize our work with interested community members.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Kindest regards,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Ashley Heineman<u></u><u></u></p>
<p class="MsoNormal">Chair, RrSG<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div></div></div>
_______________________________________________<br>
Ncuc-discuss mailing list<br>
<a href="mailto:Ncuc-discuss@lists.ncuc.org" target="_blank">Ncuc-discuss@lists.ncuc.org</a><br>
<a href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss" rel="noreferrer" target="_blank">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a><br>
</div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b><i>Bruna Martins dos Santos <br></i></b><div dir="ltr" style="color:rgb(34,34,34)"><br></div><p style="color:rgb(34,34,34);margin:0cm 0cm 0.0001pt"><span style="font-family:arial,sans-serif"><font color="#000000"><span style="font-size:11px"></span></font></span></p><p style="color:rgb(34,34,34);margin:0cm 0cm 0.0001pt"><font size="2"><span style="font-family:arial,sans-serif"><font color="#000000">Advocacy Coordinator | <a href="https://www.dataprivacybr.org/en/" target="_blank">Data Privacy Brazil Research</a></font></span></font></p><p style="color:rgb(34,34,34);margin:0cm 0cm 0.0001pt"><font size="2"><span style="font-family:arial,sans-serif"><font color="#000000">Member | <a href="https://direitosnarede.org.br/" target="_blank">Coalizão Direitos na Rede</a> <br>Chair</font></span></font><span style="color:rgb(0,0,0);font-family:arial,sans-serif"> | <a href="https://gnso.icann.org/en/about/stakeholders-constituencies/ncsg" target="_blank">Non-Commercial Stakeholder Group at ICANN</a><br></span><font size="2"><span style="font-family:arial,sans-serif"><font color="#000000">Co-Coordinator</font></span></font><span style="color:rgb(0,0,0);font-family:arial,sans-serif"> | <a href="https://igcaucus.org/" target="_blank">Internet Governance Caucus </a><br></span><font size="2"><span style="font-family:arial,sans-serif"><font color="#000000"><br></font></span></font></p><div style="color:rgb(34,34,34)"><span style="font-family:arial,sans-serif"><font size="1" color="#000000"><font size="2">Twitter: <a href="https://twitter.com/boomartins" target="_blank"><font color="#1155cc">@</font>boomartins</a> // </font></font></span><span style="color:rgb(32,33,36)">Skype: bruna.martinsantos</span></div></div><div><font size="1"><a href="mailto:bruna@dataprivacybr.org" target="_blank">bruna@dataprivacybr.org</a> and <a href="mailto:bruna.mrtns@gmail.com" target="_blank">bruna.mrtns@gmail.com</a></font></div></div></div></div></div></div></div></div></div>
</blockquote></div>