Update on GNSO Council DNS abuse small team

[Tomslin Samme-Nlar]

Dear Wisdom,

Thanks so much for the update.

With regards to the questions asked, I don't see any DNS abuse as it
relates to phishing, bots, malware and pharming that is not already
addressed by ICANN's DNS Security Threat Mitigation program.

I would also like to ask you to keep an eye on how the small group's
leadership, especially Mark, steers the group. Based on his updates during
ICANN73,  he seem to presume that a policy development effort will be an
outcome of the group's effort. The group should not be sending such signals
to the community. The guidance the assignment form gives is clear that the
Council is on the side of the assumption that it is not aware of any other
DNS abuse problem that can be resolved through a GNSO policy, however would
like to hear from the community before the Council closes the curtains on
this subject.

Best regards
Tomslin


On Wed, 16 Mar 2022, 23:37 Wisdom Donkor, <wisdom.dk at gmail.com> wrote:

> Dear NCSG Leadership / Members
>
> As some of you may recall, the GNSO Council agreed at the end of the ICANN
> 72 to establish a small team to consider the next step for DNS
> abuse.  Acknowledging the time taken to get this group kicked off, I would
> note that the remit and expected outputs of the group were not established.
> As such, Council leadership and staff have developed the *proposed
> attached Assignment Form* to help provide some pertinent background
> information (mostly focusing on recent items), as well as to try and
> articulate what this small group could focus on. The GNSO small team
> members on the DNS abuse are: Greg, Mark, Maxim, Sebastien, Thomas, Wisdom,
>
> The team first met on February 9, 2022 and took the opportunity to discuss the
> small team assignment (here
> <https://community.icann.org/download/attachments/178587048/Small%20Team%20Assignment%20-%20DNS%20abuse_26Jan2022.docx?version=1&modificationDate=1643230285000&api=v2>)
> and also GNSO focused resources on the subject of DNS abuse (here
> <https://urldefense.com/v3/__https:/docs.google.com/document/d/1VTkKU-VqysorzuPlSO-E0_HR6PvWO3Es/edit__;!!PtGJab4!sC-69GIEu5NqfSdYS0--GHuzOa6R9Ym_3DE3J33sRtkYxC9ZwCIC-J-XxjKjq9OFYj8xn4s$>
> ) but it was done without a great deal of elaboration. As such, the small
> team discussed and quickly agreed that its central question should be to
> consider what DNS abuse issues are best mitigated via policy development
> specifically, if any, as a mechanism to help determine the Council’s next
> steps on DNS abuse. The small team also agree that a good first step in
> helping to answer that question is to reach out to community groups that
> have expressed a keen interest in DNS abuse and seek their input. You can
> see the draft communications here:
> https://docs.google.com/document/d/1rpmBJZ5EwbztuoNH8r36lCxVo_VD4mEDwloFyEr8aqs/edit?usp=sharing
> [docs.google.com] [docs.google.com]. The group also quickly agreed that
> these letters should be sent via Council leadership rather than the small
> team.
>
> The initial set of outreach targets includes these four:* ALAC, GAC, SSAC*,
> and the *DNS* Abuse Institute. There was a suggestion to also reach out
> to eco’s topDNS initiative and the Internet & Jurisdiction’s Domains &
> Jurisdiction Program, but there is a concern that with all of the community
> work on DNS abuse, the Council is bound to miss a group in its formal
> outreach. Therefore, it was decided to leave it up to small team members to
> reach out to additional groups as they deem helpful.
>
> I must also note that the letters to the * ALAC, GAC, SSAC*, and the DNS
> Abuse Institute were sent out  as agreed by the DNS small team, it was also
> agreed that if any of the small team members want to perform additional
> outreach should feel free to do so  (presumably informing each other of
> that outreach, to avoid overlap!).  Marika and Steve Chan suggested that it
> would be a useful exercise for the small team to try and answer the same
> questions that it is asking others in the community via the letters. To
> that end google doc was prepared to help collect inputs.
>
> The team is set to meet later today 16 March 2022 at Time: 20:00 UTC and
> the following agenda is expected to be discussed:
>
>    1. Identification of any additional outreach already done or planned
>    2. Small team thoughts on the questions posed to the community as
>    listed below:
>
>
>    - What specific problem(s) would policy development in particular be
>    expected to address and why do you believe that policy development is the
>    right mechanism to solve those problems?
>    - What do you believe are the expected outcomes if policy development
>    would be undertaken, taking into account the remit of ICANN and more
>    specifically GNSO policy development in this context?
>    - Do you (or your community group) have any expectations with regards
>    to possible next steps the GNSO Council could or should undertake in the
>    context of policy development?
>
>  The team is set to meet later today 16 March 2022 at 20:00 UTC and the
> following two important agenda is expected to be discussed:
>
>    1. Identification of any additional outreach already done or planned
>    2. Small team thoughts on the questions posed to the community as
>    listed below:
>       1. What specific problem(s) would policy development in particular
>       be expected to address and why do you believe that policy development is
>       the right mechanism to solve those problems?
>       2. What do you believe are the expected outcomes if policy
>       development would be undertaken, taking into account the remit of ICANN and
>       more specifically GNSO policy development in this context?
>       3. Do you (or your community group) have any expectations with
>       regards to possible next steps the GNSO Council could or should undertake
>       in the context of policy development?
>
>
>  On this note, I think of bringing this to the attention of NCSG and what
> leadership will think will be the policy direction with regards to the
> questions above.
>
> With apologies for the short notice. The agenda was circulated on the
> small team list yesterday night.
>
> I look forward to your feedback.
>
>
> *Wisdom Donkor* (CASP+,  CISM, CEH Certified,)
> President & CEO
> Africa Open Data and Internet Research Foundation (AODIRF) | Africa
> Geospatial Data and Internet Conference (AGDIC)
> P.O. Box CT 2439, Cantonments, Accra | www.aodirf.org  /
> www.afrigeocon.org
> Tel: +233 20 812 8851
> Skype: wisdom_dk | Facebook: kwasi wisdom |  Twitter: @wisdom_dk
>
> _______________________________________________________________________________________________________________________
> ICANN GNSO Council Member | ICANN transfer policy review working group
> Member  | Council Committee for Overseeing and Implementing Continuous
> Improvement (CCOICI) | UN IGF MAG Member | IGF Support Fund Association
> Executive Committee Member, World Bank Independent Consultant | AU AFIGF
> Member |  Ghana OGP Advisory Committee member | GSS SDGs Advisory Committee
> Member
>
> ____________________________________________________________________________________________
> Specialization:
> E-government Network Infrastructure and E-application, Internet
> Governance,  Open Data policies platforms & Community Development, Cyber
> Security, Geospatial Technologies, Open Source Technologies, Domain Name
> Systems, Human Resource Planning and Development, Software Engineering,
> Event Planning & Management,
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20220317/aa6329e3/attachment.htm>