Changes

As the first "hybrid" event since the beginning of the COVID pandemic, '''ICANN 74''' marked a return to in-person meetings, with a limited number of vaccinated participants attending sessions in the Netherlands. The Policy Forum ran from June 13 to June 16, 2022. The Prep Week for the event ran from May 31 to June 2, 2022.<ref name="hub">[https://74.schedule.icann.org/ ICANN 74 Archive]</ref>

As the first "hybrid" event since the beginning of the COVID pandemic, '''ICANN 74''' marked a return to in-person meetings, with a limited number of vaccinated participants attending sessions in the Netherlands. The Policy Forum ran from June 13 to June 16, 2022. The Prep Week for the event ran from May 31 to June 2, 2022.<ref name="hub">[https://74.schedule.icann.org/ ICANN 74 Archive]</ref>

The meeting was the first to feature an in-person gathering since the initiation of safety measures in response to COVID. Attendees noted that registration for some sessions was quickly fully booked.<ref name="hub" /> the overbooking appeared to be primarily related to room size and limitations on attendance. ICANN CIO [[Ashwin Rangan]] noted that the lessons of the pandemic would improve the experience for both in-person and remote attendees:

The meeting was the first to feature an in-person gathering since the initiation of safety measures in response to COVID. Attendees noted that registration for some sessions was quickly fully booked.<ref name="hub" /> the overbooking appeared to be primarily related to room size and limitations on attendance. ICANN CIO [[Ashwin Rangan]] noted that the lessons of the pandemic would improve the experience for both in-person and remote attendees:

<blockquote>The switch to virtual meetings more than two years ago presented us with the opportunity to further innovate and advance the way we get together as a global community. Since then, we have significantly enhanced the meeting experience for participants from around the world. We look forward to blending the knowledge gained through the virtual meetings with the option of in-person participation to make ICANN74 more inclusive and equitable for all who attend.<ref>[https://www.icann.org/en/blogs/details/update-on-the-technical-preparations-for-icann74-19-05-2022-en ICANN.org Blog - Update on the Technical Preparations for ICANN 74], May 19, 2022</ref></blockquote>

<blockquote>The switch to virtual meetings more than two years ago presented us with the opportunity to further innovate and advance the way we get together as a global community. Since then, we have significantly enhanced the meeting experience for participants from around the world. We look forward to blending the knowledge gained through the virtual meetings with the option of in-person participation to make ICANN74 more inclusive and equitable for all who attend.<ref>[https://www.icann.org/en/blogs/details/update-on-the-technical-preparations-for-icann74-19-05-2022-en ICANN.org Blog - Update on the Technical Preparations for ICANN 74], May 19, 2022</ref></blockquote>

==Elections and Rotation of Appointments==

==Elections and Rotation of Appointments==

** [[Leon Sanchez]] opened the discussion by stressing the need for a consensus definition of [[DNS Abuse]], as well as improving understanding of the approaches to and interests in DNS Abuse responses from different stakeholders. [[Graeme Bunton]] intervened later in the meeting, noting that there was no need to gain consensus on a definition in order to move forward. Stating that it would be very easy to spend endless hours defining the edges of the term, Bunton urged participants to focus on solutions.

** [[Leon Sanchez]] opened the discussion by stressing the need for a consensus definition of [[DNS Abuse]], as well as improving understanding of the approaches to and interests in DNS Abuse responses from different stakeholders. [[Graeme Bunton]] intervened later in the meeting, noting that there was no need to gain consensus on a definition in order to move forward. Stating that it would be very easy to spend endless hours defining the edges of the term, Bunton urged participants to focus on solutions.

** [[Joanna Kulesza]], acting as moderator noted that there is no current policy development platform within ICANN for addressing DNS Abuse, although it is a topic in numerous other policy processes;

** [[Joanna Kulesza]], acting as moderator noted that there is no current policy development platform within ICANN for addressing DNS Abuse, although it is a topic in numerous other policy processes;

** [[Seun Ojedeji]], representing [[AFRALO]], emphasized the importance within the AFRALO region of educating the continent's end user population, who have a strong expectation that the Internet will reliably deliver the information or goods they are searching for. AFRALO's efforts have focused on virtual and in-person opportunities to raise awareness and build capacity among end users;

** [[Seun Ojedeji]], representing [[AFRALO]], emphasized the importance within the AFRALO region of educating the continent's end user population, who have a strong expectation that the Internet will reliably deliver the information or goods they are searching for. AFRALO's efforts have focused on virtual and in-person opportunities to raise awareness and build capacity among end-users;

** [[Satish Babu]] of [[APRALO]] repeated the call for education and capacity building within the region, and added that both policy advocacy and the development of tools, technologies, or institutional knowledge were other opportunities for RALO involvement. He pointed out efforts such as [[NetBeacon]], as well as mooting the possibility of an inter-RALO abuse watchdog, which might be particularly effective at noting trends or new targets (such as the rise in fraudulent charities in the wake of a natural disaster). Babu agreed with Graeme Bunton that a precise, consensus definition had very little benefit, and wasted time that could be spent combating abuse;

** [[Satish Babu]] of [[APRALO]] repeated the call for education and capacity building within the region, and added that both policy advocacy and the development of tools, technologies, or institutional knowledge were other opportunities for RALO involvement. He pointed out efforts such as [[NetBeacon]], as well as mooting the possibility of an inter-RALO abuse watchdog, which might be particularly effective at noting trends or new targets (such as the rise in fraudulent charities in the wake of a natural disaster). Babu agreed with Graeme Bunton that a precise, consensus definition had very little benefit, and wasted time that could be spent combating abuse;

** [[Olivier Crepin-Leblond]] spoke on behalf of [[EURALO]], and also emphasized the value of focusing on concrete tools to combat abuse. He highlighted [[ISOC Belgium]]'s [[ISTrust.org]] tool, which provides a plugin for all major browsers that provides information about the owner, age, security protocols, and other aspects of a website;

** [[Olivier Crepin-Leblond]] spoke on behalf of [[EURALO]], and also emphasized the value of focusing on concrete tools to combat abuse. He highlighted [[ISOC Belgium]]'s [[ISTrust.org]] tool, which provides a plugin for all major browsers that provides information about the owner, age, security protocols, and other aspects of a website;

** [[Keith Drazek]] then facilitated a discussion around DNS Abuse and what the CPH can do to address SG and AC concerns and needs.

** [[Keith Drazek]] then facilitated a discussion around DNS Abuse and what the CPH can do to address SG and AC concerns and needs.

* The [[GNSO]] Council DNS Abuse Small Team held a session to identify opportunities and next steps.<ref>[https://74.schedule.icann.org/meetings/pQCgaeXGXGnd2MAmw ICANN 74 Archive - GNSO Council DNS Abuse Small Team Meeting], June 16, 2022</ref>  

* The [[GNSO]] Council DNS Abuse Small Team held a session to identify opportunities and next steps.<ref>[https://74.schedule.icann.org/meetings/pQCgaeXGXGnd2MAmw ICANN 74 Archive - GNSO Council DNS Abuse Small Team Meeting], June 16, 2022</ref>  

** The presentation and subsequent discussion emphasized prioritizing action against known abuse, as opposed to precisely defining DNS abuse.

** The presentation and subsequent discussion emphasized prioritizing action against known abuse instead of precisely defining DNS abuse.

** Commenters noted that [[Contractual Compliance]] was not necessarily calling for more tools to combat abuse through the [[Registrar Accreditation Agreement]] or [[Registry Agreement]].

** Commenters noted that [[Contractual Compliance]] was not necessarily calling for more tools to combat abuse through the [[Registrar Accreditation Agreement]] or [[Registry Agreement]].

** The second half of the session was devoted to the continued work of the small team on specific issues or recommendations. In particular, the small team focused on the conversation that began at [[ICANN 73]] regarding malicious registration versus compromised websites.

** The second half of the session was devoted to the continued work of the small team on specific issues or recommendations. In particular, the small team focused on the conversation that began at [[ICANN 73]] regarding malicious registration versus compromised websites.

{{reflist}}

{{reflist}}

__NOTOC__

__NOTOC__