NetBeacon Institute: Difference between revisions

Line 41:

==NetBeacon and ICANN==

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]]" 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>

Line 51:

On [[ICANN 73]], the Institute’s president, [[Graeme Bunton]], moderated a plenary session named “Evolving the DNS Abuse Conversation”, explored the distinction between compromised and maliciously registered domain names and discussed the evolving industry response to Domain Name System (DNS) abuse. Participants had the opportunity to interact with industry representatives and community members to discuss mitigation strategies <ref>https://meetings.icann.org/en/meetings/icann73/icann73-policy-outcome-report-29mar22-en.pdf</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, 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>.

@@ Line 41: / Line 41: @@
 ==NetBeacon and ICANN==
-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]]" 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>
@@ Line 51: / Line 51: @@
 On [[ICANN 73]], the Institute’s president, [[Graeme Bunton]], moderated a plenary session named “Evolving the DNS Abuse Conversation”, explored the distinction between compromised and maliciously registered domain names and discussed the evolving industry response to Domain Name System (DNS) abuse. Participants had the opportunity to interact with industry representatives and community members to discuss mitigation strategies <ref>https://meetings.icann.org/en/meetings/icann73/icann73-policy-outcome-report-29mar22-en.pdf</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, 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>.