Bureaucrats, steward, Administrators, translator
2,307
edits
Changes
Improved writing
On the [[GAC]] Communiqué from [[ICANN 70]], dated March, 2021, on the [[DNS Abuse]] session, we have that “DNS Abuse should be addressed in collaboration with the ICANN community and ICANN org prior to the launch of a second round of New gTLDs”, and that “The GAC welcomes the recently-launched DNS Abuse Institute and encourages community efforts to cooperatively tackle DNS Abuse in a holistic manner” <ref>https://gac.icann.org/advice/communiques/public/ICANN70%20GAC%20Communique-ar1.pdf?language_id=1</ref>. GAC cites the Institute again in the Communiqué from [[ICANN 72]], on November, 2021, saying the GAC follows developments in the area of voluntary measures against DNS Abuse with interest; an example being the work of the then called DNS Abuse Institute <ref>https://gac.icann.org/file-asset/public/icann72-gac-communique-en.pdf?language_id=1</ref>.
On the [[GAC]] Communiqué from [[ICANN 70]], dated March, 2021, on the [[DNS Abuse]] session, we have that “DNS Abuse should be addressed in collaboration with the ICANN community and ICANN org prior to the launch of a second round of New gTLDs”, and that “The GAC welcomes the recently-launched DNS Abuse Institute and encourages community efforts to cooperatively tackle DNS Abuse in a holistic manner” <ref>https://gac.icann.org/advice/communiques/public/ICANN70%20GAC%20Communique-ar1.pdf?language_id=1</ref>. GAC cites the Institute again in the Communiqué from [[ICANN 72]], on November, 2021, saying the GAC follows developments in the area of voluntary measures against DNS Abuse with interest; an example being the work of the then called DNS Abuse Institute <ref>https://gac.icann.org/file-asset/public/icann72-gac-communique-en.pdf?language_id=1</ref>.
In February 2022, the [[GNSO Council]] tasked a small team consisting of Council members to consider what policy efforts, if any, the GNSO Council should consider undertaking to support the efforts already underway in the different parts of the community to tackle DNS abuse <ref>https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2022-11-17</ref>. As part of its deliberations, the small team, named "[[Small Team on DNS Abuse|Small Team on Domain Name System (DNS) Abuse]]", performed outreach to interested community groups to better understand what DNS abuse related issues need to be addressed specifically via [[gTLD]] policy development, including the DNS Abuse Institute, asking for input on what problems <ref>https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2022-10-20_</ref> policy development specifically is needed to mitigate, if any, as well as the expected outcomes if policy development would be undertaken <ref>https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2022-11-17</ref>
In February 2022, the [[GNSO Council]] tasked a small team consisting of Council members to consider what policy efforts, if any, the GNSO Council should consider undertaking to support the efforts already underway in the different parts of the community to tackle DNS abuse <ref>https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2022-11-17</ref>. As part of its deliberations, the small team, named "[[Small Team on DNS Abuse|Small Team on Domain Name System (DNS) Abuse]]" and chaired by [[Mark Datysgeld]] and [[Paul McGrady]], performed outreach to interested community groups to better understand what DNS abuse related issues need to be addressed specifically via [[gTLD]] policy development, including the DNS Abuse Institute, asking for input on what problems <ref>https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2022-10-20_</ref> policy development specifically is needed to mitigate, if any, as well as the expected outcomes if policy development would be undertaken <ref>https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2022-11-17</ref>
The Institute responded with a letter on April, 2022, which, in summary, suggested that the GNSO Council could significantly influence policy development in this area. They recommended adopting a series of focused, sequential Policy Development Processes (PDPs) targeting specific aspects of clear-cut DNS Abuse, which they believe could lead to incremental but substantial changes in addressing such issues. The Institute emphasized the need for a deep understanding of DNS Abuse symptoms, causes, and potential remedies before policy-making and advocates for starting with widely agreed upon forms of DNS Abuse to avoid the complexities and delays associated with broad definitional disagreements. They propose practical, narrow-scoped PDPs on malicious registrations related to malware, phishing, and botnets, emphasizing that these should align with ICANN’s remit and avoid broader issues of content regulation. The goal would be to effectively reduce DNS Abuse while minimizing the impact on legitimate domain registrants, leveraging gained expertise for potentially more complex future issues <ref>https://netbeacon.org/dnsai-response-gnso-small-team-dns-abuse/</ref>.
The Institute responded with a letter on April, 2022, which, in summary, suggested that the GNSO Council could significantly influence policy development in this area. They recommended adopting a series of focused, sequential Policy Development Processes (PDPs) targeting specific aspects of clear-cut DNS Abuse, which was believed could lead to incremental but substantial changes in addressing such issues. The Institute emphasized the need for a deep understanding of DNS Abuse symptoms, causes, and potential remedies before policy-making and advocates for starting with widely agreed upon forms of DNS Abuse to avoid the complexities and delays associated with broad definitional disagreements. They proposed practical, narrow-scoped PDPs on malicious registrations related to malware, phishing, and botnets, emphasizing that these should align with ICANN’s remit and avoid broader issues of content regulation. The goal would be to effectively reduce DNS Abuse while minimizing the impact on legitimate domain registrants, leveraging gained expertise for potentially more complex future issues <ref>https://netbeacon.org/dnsai-response-gnso-small-team-dns-abuse/</ref>.
The small team on DNS Abuse delivered their report in October, 2022, <ref>https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2022-10-20</ref> and it was later accepted by the GNSO Council <ref>https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2022-11-17</ref>.
The small team on DNS Abuse delivered their report in October, 2022, <ref>https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2022-10-20</ref> and it was later accepted by the GNSO Council <ref>https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2022-11-17</ref>.
The Institute commented that shortly after ICANN 73, [[ICANN]] produced a retrospective on the last four years of DNS Abuse trends named [[Domain Abuse Activity Reporting]] (DAAR) and that, drawing on its data, it paints an interesting picture of DNS Abuse over time, and one that they haven’t seen clearly before, and that this sort of work that would enable the Institute and the ICANN community to focus its work on where it’s most needed <ref>https://netbeacon.org/dnsai-newsletter-april-2022/</ref>.
The Institute commented that shortly after ICANN 73, [[ICANN]] produced a retrospective on the last four years of DNS Abuse trends named [[Domain Abuse Activity Reporting]] (DAAR) and that, drawing on its data, it paints an interesting picture of DNS Abuse over time, and one that they haven’t seen clearly before, and that this sort of work that would enable the Institute and the ICANN community to focus its work on where it’s most needed <ref>https://netbeacon.org/dnsai-newsletter-april-2022/</ref>.
On July, 2023, Institute expressed support for the proposed amendments to ICANN’s Base gTLD [[Registry Agreement]] (RA) and [[Registrar Accreditation Agreement]] (RAA) regarding DNS Abuse. They commend ICANN and the contracted parties for their quick action and shared commitment to addressing DNS Abuse. The amendments introduce a clear requirement to mitigate malicious domain registrations, which the DNS Abuse Institute viewed as significant progress <ref>https://www.icann.org/es/public-comment/proceeding/amendments-base-gtld-ra-raa-modify-dns-abuse-contract-obligations-29-05-2023/submissions/dns-abuse-institute-20-07-2023</ref>.
On July, 2023, the Institute expressed support for the proposed amendments to ICANN’s Base gTLD [[Registry Agreement]] (RA) and [[Registrar Accreditation Agreement]] (RAA) regarding DNS Abuse. They commended ICANN and the contracted parties for their quick action and shared commitment to addressing DNS Abuse. The amendments introduced a clear requirement to mitigate malicious domain registrations, which the DNS Abuse Institute viewed as significant progress <ref>https://www.icann.org/es/public-comment/proceeding/amendments-base-gtld-ra-raa-modify-dns-abuse-contract-obligations-29-05-2023/submissions/dns-abuse-institute-20-07-2023</ref>.
ICANN hosted "A Day of Domain Name System Abuse Discussions" in Da Nang, Vietnam, on 4 September 2023. The hybrid event was part of several technical workshops that included the ICANN DNS Symposium and OARC 41. The sessions, developed in collaboration with the DNS Abuse Institute, were designed to explain the proposed amendments and then highlight different aspects of combating DNS abuse. The event's goal was for participants to gain a solid understanding of the proposed obligations and new tools to give them the confidence to support the pending contractual amendments and better combat DNS abuse. There were more than 125 in-person participants <ref>https://www.icann.org/en/blogs/details/icanns-day-of-dns-abuse-discussions-draws-more-than-125-participants-27-09-2023-en</ref>.
ICANN hosted "A Day of Domain Name System Abuse Discussions" in Da Nang, Vietnam, on 4 September 2023. The hybrid event was part of several technical workshops that included the ICANN DNS Symposium and OARC 41. The sessions, developed in collaboration with the DNS Abuse Institute, were designed to explain the proposed amendments and then highlight different aspects of combating DNS abuse. The event's goal was for participants to gain a solid understanding of the proposed obligations and new tools to give them the confidence to support the pending contractual amendments and better combat DNS abuse <ref>https://www.icann.org/en/blogs/details/icanns-day-of-dns-abuse-discussions-draws-more-than-125-participants-27-09-2023-en</ref>.
On January 21, 2024, the [[ICANN Board]] approved new contractual obligations for registries and registrars related to DNS Abuse. The Institute is, as of 2024, considering their role in this development, as there has been discussion about how the community of people interested in DNS Abuse can assess their effectiveness. The Institute, with their partner KOR Labs, has been collecting important data since May 2022 that they believe will be crucial to measuring the impact of the amendments. Over time, they have the goal of helping answer a number of key questions compared to our pre-amendment baseline data:
On January 21, 2024, the [[ICANN Board]] approved new contractual obligations for registries and registrars related to DNS Abuse. The Institute is, as of 2024, considering their role in this development, as there has been discussion about how the community of people interested in DNS Abuse can assess their effectiveness. The Institute, with their partner [[KOR Labs]], has been collecting data since May 2022, that they believe will be crucial to measuring the impact of the amendments. Over time, they have the goal of helping answer a number of key questions compared to their pre-amendment baseline data:
* How are rates of DNS Abuse changing, and are they different from before the amendment?
* How are rates of DNS Abuse changing, and are they different from before the amendment?
==Leadership==
==Leadership==
The Institure is driven by Graeme Bunton and [[Rowena Schoo]]. The Advisory Council counts with expert representation from interested stakeholders related to DNS Abuse, such as gTLD registries, ccTLD registries, registrars, security researchers, and academics on issues related to DNS Abuse. Current Advisory Council members include:
The Institute is driven by Graeme Bunton and [[Rowena Schoo]]. The Advisory Council counts with expert representation from interested stakeholders related to DNS Abuse, such as gTLD registries, ccTLD registries, registrars, security researchers, and academics on issues related to DNS Abuse. Current Advisory Council members include:
* Alissa Starzak
* Alissa Starzak