DNS Abuse Session

[Poncelet Ileleji]

Concur definitely very good, best wishes on the panel

Poncelet

On Wednesday, 6 November 2019, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> wrote:

> Sounds good, best of luck on the panel!
>
> Stephanie
> On 2019-11-06 09:28, farzaneh badii wrote:
>
> Hi everyone
>
> We will have a DNS Abuse session in Montreal at 10.30 AM today (in an
> hour). Stephanie asked me to be on the panel providing the non-commercial
> perspective.
>
> As far as I know and as they informed me during the planning meeting for
> this, Bruce Tonkin has formatted it roughly as such:
>
> 1. What is DNS abuse.
> I don't think our problem rests in the definition of DNS abuse but we have
> been struggling with not having a thorough governance mechanism for
> fighting with abuse. We need to have policies, an implementation plan and
> dispute resolution. We only have patches of solutions but not a governance
> mechanism.
>
> Here I want to emphasize the solely technical aspect of DNS abuse. DNS is
> a tool that can be used to carry out crimes and to a much greater extent,
> it can be used to facilitate our communications, global interconnectedness,
> e-commerce and many more human life activities that can lead to
> prosperity.   We need to refrain from re-opening the issue of DNS abuse
> definition every time. DNS abuse has a limited technical meaning, it is in
> the RAAs and by no means, it relates to the content.  Re-opening the
> discussion on definition only has merits if there are novel criminal
> activities that are directly and solely related to the usage of the DNS.
>
>
> 2. What is the role of ICANN: Just because the usage of DNS can be
> detected in a grand criminal scheme does not mean we have to and can combat
> that crime through ICANN. ICANN becomes a convenient policy forum to go to
> because its mission is related to the DNS but that doesn't mean that we can
> and need to resolve all the  crimes that are somehow related to DNS or have
> used the DNS among other things through ICANN. Wanting to resolve all
> crimes that someone had DNS involved can hamper the distributed and open
> nature of the Internet. ICANN should not become the cetralized go to place
> for combatting with all sorts of crimes. sometimes DNS is used but the
> crime committed through a wide variety of other technical deceptions, for
> example through insecure protocols or social engineering. These subtlities
> have to be considered when we want to discuss them at  ICANN.
>
> 3. Registries registrars: incentives, sharing best practices  etc.
>
> There has to be a clear line between what registries and registrars want
> to do with regards to DNS abuse and what ICANN should tell them to do. I
> personally don't like ICANN be used as a venue to share practices about
> content regulation even if it's not binding it reflects a wrong image about
> ICANN's mission to the public.
>
>
> 4. How should registries and registrars combat egregious content: I
> believe if registries and registrars want to do something about egregious
> content they need to have again a governance mechanism. They need to have
> transparent policies, policies on implementation and dispute resolution.
> The legitimacy of decisionmaking and their authority will be hampered
> should they make arbitrary decision. They will be more prone to government
> pressure as well if they don't have a thorough governance mechanism.
>
> I am sorry, sending this in late but I just managed to put them all
> together.
>
>
> Farzaneh
>
>

-- 
Poncelet O. Ileleji MBCS
Coordinator
The Gambia YMCAs Computer Training Centre & Digital Studio
MDI Road Kanifing South
P. O. Box 421 Banjul
The Gambia, West Africa
Tel: (220) 4370240
Fax:(220) 4390793
Cell:(220) 9912508
Skype: pons_utd


*www.ymca.gm <http://www.ymca.gm>http://jokkolabs.net/en/
<http://jokkolabs.net/en/>*

*https://www.netfreedompioneers.org/
<https://www.netfreedompioneers.org/>   *



*www.waigf.org <http://www.waigf.org>www,insistglobal.com
<http://www.itag.gm>www.npoc.org <http://www.npoc.org>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20191106/0dde9ced/attachment.htm>