<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>On the website, if you dig deep enough, they have a link to a
document that defines what they mean by abuse.</p>
<p><a class="moz-txt-link-freetext" href="http://dnsabuseframework.org/media/files/2020-05-29_DNSAbuseFramework.pdf">http://dnsabuseframework.org/media/files/2020-05-29_DNSAbuseFramework.pdf</a><br>
</p>
<p>It is essentially a list of ill thing like spam, malware,
botnets, and phishing and the like. In other words the "abuse" is
not directly an aspect of DNS but rather of something that uses
DNS, among other technologies.<br>
</p>
<p>That same logic could also be used to tie the enumerated ills to
"abuse of electricity" or "abuse of computers" or "abuse of IPv6".</p>
<p>In their list of "DNS abuses" it is Pharming that is perhaps the
closest to DNS itself.</p>
<p>There is no doubt that the things are bad and deserve to be
slowed, blocked, denied, and otherwise prevented. And if that
prevention may involve some changes to the way we administer DNS
or operate it, or even how it is defined in the RFCs.<br>
</p>
<p>But to call these bad things "DNS Abuse" is, to my mind, rather a
stretch.</p>
<p>And if we are to talk about these things we should very clearly
understand whether we are talking about the name registration
machinery via registrars and registries and provisioning protocols
and whois, versus the actual machinery of resolving DNS names via
name servers.<br>
</p>
<p>I would add, however, that some of this is of our own making - my
favorite being the five minute update period between someone
changing record at a registrar and that change appearing out there
on the net. Much as that five minute period is really nice when I
am making changes I am of the opinion that convenience to those of
us who make updates should be outweighed by the public interest in
avoiding threats that are facilitated by fast (five minute)
updates to the mappings of 2nd tier names (e.g. names directly
under the TLDs - there's not much we can do about rapid updates
deeper in the hierarchy.)</p>
<p> --karl--<br>
</p>
<div class="moz-cite-prefix">On 2/18/21 1:02 PM, Matthias M.
Hudobnik wrote:<br>
</div>
<blockquote type="cite"
cite="mid:000001d70639$57fab670$07f02350$@hudobnik.at">
<pre class="moz-quote-pre" wrap="">Dear all,
What do you guys think about this initiative: <a class="moz-txt-link-freetext" href="https://dnsabuseinstitute.org/">https://dnsabuseinstitute.org/</a> :-)?
Have a nice evening!
Kindest regards,
Matthias
__________________________
Ing. Mag. Matthias M. Hudobnik, CIPP/E
<a class="moz-txt-link-abbreviated" href="mailto:matthias@hudobnik.at">matthias@hudobnik.at</a>
<a class="moz-txt-link-freetext" href="http://www.hudobnik.at">http://www.hudobnik.at</a>
@mhudobnik
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
At-Large mailing list
<a class="moz-txt-link-abbreviated" href="mailto:At-Large@atlarge-lists.icann.org">At-Large@atlarge-lists.icann.org</a>
<a class="moz-txt-link-freetext" href="https://atlarge-lists.icann.org/mailman/listinfo/at-large">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a>
At-Large Official Site: <a class="moz-txt-link-freetext" href="http://atlarge.icann.org">http://atlarge.icann.org</a>
_______________________________________________
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 class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">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.</pre>
</blockquote>
</body>
</html>