Difference between revisions of "ICANN 74 - The Hague"

From ICANNWiki
Jump to navigation Jump to search
 
(34 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{ICANNMeetings|
 +
| logo            =ICANN_74_logo.png|200px
 +
| dates          =13-16 June 2022
 +
Policy Forum
 +
| location        = The Hague, NL
 +
| host            =
 +
| venue        =  World Forum The Hague
 +
| website      = https://74.schedule.icann.org/
 +
| totalregistrants = 1,817
 +
| registration    =
 +
| keyappointments      =
 +
| historicalimport  = First hybrid ICANN Meeting
 +
}}
 
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>
  
 
==Return to In-Person==
 
==Return to In-Person==
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 mostly 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>
 +
 +
ICANN74 had 1,817 attendees, of which 917 people participated in person and 900 attended virtually.<ref>[https://www.icann.org/en/blogs/details/icann75-health-and-safety-04-08-2022-en ICANN75 Health and Safety, ICANN Blogs]</ref>
 +
 +
==Elections and Rotation of Appointments==
 +
* At the [[GAC]] opening plenary, [[Manal Ismail]] noted that there were nearly 150 new GAC representatives since the last in-person meeting at [[ICANN 66]].<ref>[https://74.schedule.icann.org/meetings/PgCqfrE4SCi65HZXX ICANN 74 Archive - GAC Opening Plenary], June 13, 2022</ref>
  
 
==Topics==
 
==Topics==
 
===Prep Week===
 
===Prep Week===
 
# The Phase 1a Initial Report of the [[Policy Development Process to Review the Transfer Policy]] Working Group was presented at [[Prep Week]], <ref>[https://74.schedule.icann.org/meetings/R6mxL9aTrm6NNWj3f ICANN 74 Archive - Initial Report of the GNSO Transfer Policy Review Phase 1a], June 2, 2022</ref> with an expectation that the public comment period for the report would open on or around ICANN 74.  
 
# The Phase 1a Initial Report of the [[Policy Development Process to Review the Transfer Policy]] Working Group was presented at [[Prep Week]], <ref>[https://74.schedule.icann.org/meetings/R6mxL9aTrm6NNWj3f ICANN 74 Archive - Initial Report of the GNSO Transfer Policy Review Phase 1a], June 2, 2022</ref> with an expectation that the public comment period for the report would open on or around ICANN 74.  
#* The initial report concerning inter-transfers (changes in registrars) to be published Q2 of 2022; at ICANN 74, the focus will focus on intra-transfers: change of registrants.
+
#* The initial report concerning inter-transfers (changes in registrars) was published Q2 of 2022; at ICANN 74, the focus was on intra-transfers: change of registrants.
 
# The [[Prioritization Framework]] pilot was also a topic during Prep Week in the Planning & Finance Update Session.<ref name="preppf">[https://74.schedule.icann.org/meetings/eoKAM7x4Rh2bf9z34 ICANN 74 Archive - Planning & Finance Update], June 1, 2022</ref> Participants in the pilot process praised the efficiency and work product of the pilot.<ref name="preppf" /> [[Xavier Calvez]] clarified that, in principle, recommendations and policy objectives would only go through the prioritization framework one time.<ref name="preppf" />
 
# The [[Prioritization Framework]] pilot was also a topic during Prep Week in the Planning & Finance Update Session.<ref name="preppf">[https://74.schedule.icann.org/meetings/eoKAM7x4Rh2bf9z34 ICANN 74 Archive - Planning & Finance Update], June 1, 2022</ref> Participants in the pilot process praised the efficiency and work product of the pilot.<ref name="preppf" /> [[Xavier Calvez]] clarified that, in principle, recommendations and policy objectives would only go through the prioritization framework one time.<ref name="preppf" />
 
# Updates and details from the [[SUBPRO]] Operational Design Phase were also shared and discussed during Prep Week.<ref>[https://74.schedule.icann.org/meetings/ZwGFKyDZpR69khesm ICANN 74 Archive - New gTLD Subsequent Procedures ODP Update], May 31, 2022</ref>
 
# Updates and details from the [[SUBPRO]] Operational Design Phase were also shared and discussed during Prep Week.<ref>[https://74.schedule.icann.org/meetings/ZwGFKyDZpR69khesm ICANN 74 Archive - New gTLD Subsequent Procedures ODP Update], May 31, 2022</ref>
Line 16: Line 34:
  
 
===Policy Forum===
 
===Policy Forum===
# DNS Abuse:
+
====DNS Abuse====
#* The [[ALAC]] held a session on DNS abuse from the end user's perspective. The session focused on what the [[RALO]]s can do to curtail abuse.  
+
* The [[ALAC]] identified DNS Abuse as a top priority during its leadership session on the first day of the meeting.<ref>[https://74.schedule.icann.org/meetings/gFkaacMWpYM2696yt ICANN 74 Archive - At-Large Leadership Session: Welcome to ICANN 74], June 13, 2022</ref>. ALAC members also held a session on DNS abuse from the end user's perspective. The session focused on what the [[RALO]]s were doing to address abuse.  
#** [[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;
+
** [[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.
#*[[ccNSO]] have sessions from each organization's perspective.<ref>[https://74.schedule.icann.org/meetings/tnf2SWwmySJmJJqdk ICANN 74 Archive - At-Large Policy: An End User's Perspective on the Role of At-Large in DNS Abuse], June 13, 2022</ref> <ref>[https://74.schedule.icann.org/meetings/NL93AXLzxeQE7bwgd ICANN 74 Archive - ccNSO: ccTLD Role in DNS Abuse Policies], June 16, 2022</ref>
+
** [[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;
# Prioritization:
+
** [[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;
#* The [[Prioritization Framework]] is featured in a broader plenary session on priority-setting.<ref>[https://74.schedule.icann.org/meetings/ZP3ZHC242wXKnWRdP ICANN 74 Archive - Plenary Session: Who Sets ICANN's Priorities?], June 14, 2022</ref>
+
** [[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;
# The [[SSAC]] is presenting on the progress of the [[Name Collision Analysis Project]].<ref>[https://74.schedule.icann.org/meetings/wcin8eB2MQNNRwWP6 ICANN 74 Archive - NCAP Status Update]</ref> Due to a small meeting room, seats for the presentation were fully reserved before the commencement of the meeting. NCAP project members also held working group meetings during the conference.
+
** [[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;
# Subsequent Procedures for new gTLDs:
+
** [[Augusto Ho]], representing [[LACRALO]], suggested that entrepreneurship and work within the private sector might assist and inform RALO efforts to develop tools and solutions;
#* The ICANN team presented on the [[SUBPRO]] operational design phase and the process, and discussed with board and IRT members the scope and focus of the SPRT.<ref>[https://74.schedule.icann.org/meetings/Q5k7NyhhFhLwmbkgY ICANN 74 Archive - New gTLD Subsequent Procedures: Working Together], June 13, 2022</ref>
+
** [[Eduardo Diaz]] spoke for [[NARALO]].<ref>[https://74.schedule.icann.org/meetings/tnf2SWwmySJmJJqdk ICANN 74 Archive - At-Large Policy: An End User's Perspective on the Role of At-Large in DNS Abuse], June 13, 2022</ref>  
#* The [[GAC]] held a discussion session on SUBPRO, focusing on the open topic of closed generics, and had an opportunity to speak with ICANN org staff regarding developments and advances in the ODP. The session also provided background on the intended facilitated dialogue between the GAC and the [[GNSO]] regarding closed generics and other topics relevant to the GAC.<ref>[https://74.schedule.icann.org/meetings/Gni9k2LjdDePHJsAm ICANN 74 Archive - GAC Discussion on Subsequent Rounds of new gTLDs], June 13, 2022</ref>
+
* The [[ccNSO]] held a session from the perspective of ccTLD managers.<ref>[https://74.schedule.icann.org/meetings/NL93AXLzxeQE7bwgd ICANN 74 Archive - ccNSO: ccTLD Role in DNS Abuse Policies], June 16, 2022</ref>
# [[Policy Development Process to Review the Transfer Policy|Transfer Policy Review]]:
+
** Managers from [[.bw]], [[.hk]], [[.si]], [[.pa]], and [[.us]] spoke about their abuse mitigation practices and challenges each ccTLD faces.
#* The working group initiated work on Phase 1(b) of the Transfer Policy Review PDP.<ref>[https://74.schedule.icann.org/meetings/exSok5N3N9WTCM4LH ICANN 74 Archive - GNSO Transfer Policy Review PDP Working Group], June 13, 2022</ref>
+
** An overriding theme was the varying level and extent of ccTLD managers' regulatory authority based on national mandates.
 +
* The [[GAC]] was briefed on [[NetBeacon]] and also received information from ICANN staff in their discussion on DNS Abuse.<ref>[https://74.schedule.icann.org/meetings/QqjSKJnn38qcv5Zv5 ICANN 74 Archive - GAC Discussion: DNS Abuse], June 14, 2022</ref>
 +
* The [[Contracted Parties House]] held a session on community outreach regarding DNS Abuse.<ref name="cphabuse">[https://74.schedule.icann.org/meetings/ivvqzxPAdu8GCWEK5 ICANN 74 Archive - GNSO: CPH DNS Abuse Community Outreach], June 15, 2022</ref>
 +
** [[Brian Cimbolic]] reminded the CPH of the definition of DNS Abuse: malware, botnets, phishing, pharming, and spam when it is a delivery mechanism for one of the prior methods of abuse.
 +
** [[Samaneh Tajalizadehkhoob]] from ICANN org presented on ICANN findings regarding trends in the data from domain abuse reporting.<ref>See [https://www.icann.org/en/blogs/details/icann-publishes-dns-abuse-trends-22-03-2022-en ICANN.org blog - ICANN Publishes DNS Abuse Trends], March 22, 2022</ref>
 +
** [[Graeme Bunton]] reminded the audience of the plenary session held at [[ICANN 73]] regarding responses to intentional abuse and hijacked or co-opted URLs. He reported that the outcomes of that plenary session and subsequent work would be presented at [[ICANN 75]]. He subsequently presented on [[NetBeacon]] as well.
 +
** [[Reg Levy]] discussed [[abusetool.org]], a CPH-created tool to identify the web host and email hosting company for a given domain.
 +
** [[Alan Woods]] presented on Specification 11(3)(b) of the [[Registry Agreement]] and CPH advances toward a proposal for gathering and reporting statistics around abuse as required under that specification.
 +
** [[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 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]].
 +
** 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.
 +
 
 +
====External Forces: Governments, International Agreements, & Emergencies====
 +
* [[EURALO]] hosted a session on legislative and regulatory developments in the EU and how they impact the DNS.<ref>[https://74.schedule.icann.org/meetings/javiEh2kZqtc995vo ICANN 74 Archive - At-Large EURALO: Laws and Regulations in the European Union], June 14, 2022</ref>
 +
** [[Pari Esfandiari]] set the stage for the discussion, noting the critical EU initiatives that were announced in December 2020:
 +
*** Communication on the EU's Cybersecurity Strategy for the Digital Decade, including the [[DNS4EU]] initiative and developing resilience of critical entities, including a contingency plan for the root;
 +
*** [[Revision of the Directive on the Security of Network and Information Systems]] (NIS 2); and
 +
** Esfandiari noted that "the devil is in the details" on all of these objectives and initiatives, noting particularly that revisions to Article 23 under NIS 2 were critical to the ICANN community.
 +
** [[Elena Plexida]] described ICANN's view on the EU's efforts described above:
 +
*** Related to DNS4EU, Plexida noted that the EU was concerned about the market consolidation of public resolvers. However, ICANN's study on the existing public resolvers within the EU revealed that roughly 96% of the Internet queries within the Eu are reliant on an in-country ISP resolver. Google and Cloudflare, the particular points of concern for the EU, represented only about 2% of the resolver usage. ICANN's conclusion was that there was no indication that the market was contracting.
 +
*** On NIS 2, Plexida stated that ICANN org's attention was focused on the scope of application of the regulations on the DNS, and the registration data provisions of Article 23.
 +
* [[EURALO]] also hosted a policy session on issues facing ICANN and other Internet Governance bodies in time of emergency.<ref>[https://74.schedule.icann.org/meetings/khmnpDKfTLdvkpCCm ICANN 74 Archive - At-Large EURALO Policy: Internet Governance and Multistakeholderism in Times of Emergency], June 16, 2022</ref>
 +
 
 +
====Name Collision====
 +
* The [[SSAC]] presented on the progress of the [[Name Collision Analysis Project]].<ref name="ncap">[https://74.schedule.icann.org/meetings/wcin8eB2MQNNRwWP6 ICANN 74 Archive - NCAP Status Update], June 14, 2022</ref> Due to a small meeting room, seats for the presentation were fully reserved before the commencement of the meeting. The discussion group presented on the workflow for name collision analysis and evaluation, as well as the current state of the project. NCAP project members also held working group meetings during the conference, which were also open to the public.<ref>[https://74.schedule.icann.org/meetings/th2nNfvvn5mGPoj3e ICANN 74 Archive - NCAP Discussion Group], June 14, 2022</ref>
 +
 
 +
====Prioritization====
 +
* The [[Prioritization Framework]] was featured in a broader plenary session on priority-setting.<ref>[https://74.schedule.icann.org/meetings/ZP3ZHC242wXKnWRdP ICANN 74 Archive - Plenary Session: Who Sets ICANN's Priorities?], June 14, 2022</ref> The briefing paper for the session provided some background on the ongoing struggles with ICANN board, org, and community workloads, and the enduring call for prioritization.<ref name="prbrief">[https://cdn.filestackcontent.com/content=t:attachment,f:%22Who%20Sets%20ICANN's%20Priorities_ICANN74%20Plenary%20Session%20Briefing%20Paper.pdf%22/v9Y65TZSCqr7ydRGjf0o ICANN 74 Archive - Briefing Paper: Who Sets ICANN's Priorities?], June 2022</ref> The paper noted that a similar plenary session was held at [[ICANN 59]]:
 +
<blockquote>While ICANN community discussions with the ICANN Board and ICANN org were ongoing, there was a perceived risk that various ICANN community groups were asserting different priorities with different interpretations.<br /> The ICANN Strategic and Operating Planning Framework provided an initial shared understanding of prioritization, but further work was needed on how to prioritize projects related to the strategic plan and how to meet evolving needs. The plenary session explored the likely benefits from future discussions about how to set priorities.<ref name="prbrief" /></blockquote>
 +
 
 +
====Subsequent Procedures for new gTLDs====
 +
* The ICANN team presented on the [[SUBPRO]] operational design phase and the process, and discussed with board and IRT members the scope and focus of the SPRT.<ref>[https://74.schedule.icann.org/meetings/Q5k7NyhhFhLwmbkgY ICANN 74 Archive - New gTLD Subsequent Procedures: Working Together], June 13, 2022</ref>
 +
* The [[GAC]] held a discussion session on SUBPRO, focusing on the open topic of [[Policy Development Process for New gTLD Subsequent Procedures#Closed Generics|closed generics]], and had an opportunity to speak with ICANN org staff regarding developments and advances in the ODP. The session also provided background on the intended facilitated dialogue between the GAC and the [[GNSO]] regarding closed generics.<ref>[https://74.schedule.icann.org/meetings/Gni9k2LjdDePHJsAm ICANN 74 Archive - GAC Discussion on Subsequent Rounds of new gTLDs], June 13, 2022</ref>  
 +
* The plans and structure of the facilitated dialogue were also the main topics in the GAC's meeting with the GNSO.<ref>[https://74.schedule.icann.org/meetings/6Rk6WAeG5iaeFHsCS ICANN 74 Archive - Joint Meeting: GAC and GNSO], June 13, 2022</ref>
 +
* [[Jonathan Zuck]] facilitated a session on closed generics for the [[ALAC]], and made an effort to identify At-Large's consensus position on the analysis and response to applications for closed gTLDs.<ref>[https://74.schedule.icann.org/meetings/BJnY77v7evQLZgkg3 ICANN 74 Archive - At-Large Policy: Closed Generics - Finding a Balance], June 15, 2022</ref>
 +
====[[Policy Development Process to Review the Transfer Policy|Transfer Policy Review]]====
 +
* The working group initiated work on Phase 1(b) of the Transfer Policy Review PDP.<ref>[https://74.schedule.icann.org/meetings/exSok5N3N9WTCM4LH ICANN 74 Archive - GNSO Transfer Policy Review PDP Working Group], June 13, 2022</ref>
 +
 
 +
====SSAD and Alternative Tool Options====
 +
* The [[GNSO]] held a session on [[Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data#EPDP Phase 2|Phase 2]] of the EPDP on the Temporary Specification for gTLD Registration Data, whose recommendations focused on creating a Standardized System of Access/Disclosure of registration data ([[SSAD]]).<ref name="ssad">[https://74.schedule.icann.org/meetings/EsEMmLrkif6b52rJB ICANN 74 Archive - GNSO: EPDP Phase 2 (SSAD)], June 13, 2022</ref> Correspondence and analysis before ICANN 74 had resulted in the opinion of GNSO Council that a "[[SSAD#Simple Ticketing System (aka SSAD Light)|SSAD Light]]" option might be more feasible and cost-effective. The session, therefore, focused on options and tools for SSAD Light.<ref name="ssad" /> [[Goran Marby]] introduced [[Ashwin Rangan]]'s presentation on a "WHOIS Disclosure System," a technical solution for the reporting of registration data. Rangan then proceeded to describe how ICANN org might be able to leverage existing technologies to create a solution for the needs of accurate access and disclosure of registration data.<ref name="ssad" /> The proposal was to utilize the ICANN Account authorization system to allow users to request registration information through ICANN's [[Naming Services Portal]], which is built with SalesForce. This would create a ticket capture method and would allow each request to be handled in a pre-existing service system. The WHOIS Disclosure System would then be an application that would allow the retrieval of encrypted registration data. The proposal would balance the need to access registration data with the requirements of GDPR and other data privacy regulations. It would also sidestep the requester authentication process that rendered SSAD too expensive in the eyes of ICANN org.<ref name="ssad" /> During Q &A, Marby emphasized that the technical aspects of the proposal were designed to avoid complications with GDPR.
 +
* At the same session, [[Steve Crocker]] was given an opportunity to present on another software tool that might fit the bill for SSAD Light.<ref name="ssad" /> The project is a collaboration between [[Donuts]] and Crocker's [[Edgemoor Research Institute]]. Crocker noted that there would be "quite a bit of similarity and some differences" between the Donuts/ERI tool and ICANN org's proposal. He stated that the systems could coexist and augment each other.<ref name="ssad" />
 +
* During the GNSO Council session, as well as earlier in the week at GNSO stakeholder gatherings, [[Sebastien Ducos]] reported that the "SSAD Light" scoping and implementation of the proposed ICANN tool could impact the timeline of the [[SUBPRO]] Operational Design Phase.<ref>[https://74.schedule.icann.org/meetings/H2wGoiw8J8Lv7u6z8 ICANN 74 Archive - GNSO Council Meeting], June 15, 2022</ref>
 +
* The [[GAC]] received a briefing on the SSAD ODP and the next steps for registration data policymaking.<ref>[https://74.schedule.icann.org/meetings/HbvLAFb7CaqLgQnCt ICANN 74 Archive - GAC Discussion: WHOIS and Data Protection], June 14, 2022</ref>
  
 
==Dates==
 
==Dates==
Line 36: Line 98:
 
{{reflist}}
 
{{reflist}}
 
__NOTOC__
 
__NOTOC__
 +
 +
[[Category:ICANN Meetings]]

Latest revision as of 14:51, 8 August 2022

ICANN 74 logo.png
Dates: 13-16 June 2022

Policy Forum

Location: The Hague, NL
Venue: World Forum The Hague
Website: https://74.schedule.icann.org/
Total Registrants: 1,817
Historical Significance
First hybrid ICANN Meeting

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.[1]

Return to In-Person

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.[1] 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 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.[2]

ICANN74 had 1,817 attendees, of which 917 people participated in person and 900 attended virtually.[3]

Elections and Rotation of Appointments

  • At the GAC opening plenary, Manal Ismail noted that there were nearly 150 new GAC representatives since the last in-person meeting at ICANN 66.[4]

Topics

Prep Week

  1. The Phase 1a Initial Report of the Policy Development Process to Review the Transfer Policy Working Group was presented at Prep Week, [5] with an expectation that the public comment period for the report would open on or around ICANN 74.
    • The initial report concerning inter-transfers (changes in registrars) was published Q2 of 2022; at ICANN 74, the focus was on intra-transfers: change of registrants.
  2. The Prioritization Framework pilot was also a topic during Prep Week in the Planning & Finance Update Session.[6] Participants in the pilot process praised the efficiency and work product of the pilot.[6] Xavier Calvez clarified that, in principle, recommendations and policy objectives would only go through the prioritization framework one time.[6]
  3. Updates and details from the SUBPRO Operational Design Phase were also shared and discussed during Prep Week.[7]
    • special focus on possibly updating the rules on Application Change Requests (ACRs) to resolve contention sets, lengthening the objection period, determining the interest/potential volume of applications, and outlining how long the ODP process may take (10 months), followed with a 3-month allowance for the ICANN Board to consider the ODA
  4. DNS Abuse persisted as a salient topic; the GNSO's small team on DNS Abuse was optimistic about its work and said that it had received a lot of input from across the community and generated many fresh ideas on tackling the issue
  5. The session on ICANN's Evolution of the Multistakeholder Model involved several participant polls, which reflected an interest in ICANN improving inclusivity, accountability, and the culture (moving away from silos)

Policy Forum

DNS Abuse

  • The ALAC identified DNS Abuse as a top priority during its leadership session on the first day of the meeting.[8]. ALAC members also held a session on DNS abuse from the end user's perspective. The session focused on what the RALOs were doing to address abuse.
    • 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;
    • 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;
    • 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;
    • Augusto Ho, representing LACRALO, suggested that entrepreneurship and work within the private sector might assist and inform RALO efforts to develop tools and solutions;
    • Eduardo Diaz spoke for NARALO.[9]
  • The ccNSO held a session from the perspective of ccTLD managers.[10]
    • Managers from .bw, .hk, .si, .pa, and .us spoke about their abuse mitigation practices and challenges each ccTLD faces.
    • An overriding theme was the varying level and extent of ccTLD managers' regulatory authority based on national mandates.
  • The GAC was briefed on NetBeacon and also received information from ICANN staff in their discussion on DNS Abuse.[11]
  • The Contracted Parties House held a session on community outreach regarding DNS Abuse.[12]
    • Brian Cimbolic reminded the CPH of the definition of DNS Abuse: malware, botnets, phishing, pharming, and spam when it is a delivery mechanism for one of the prior methods of abuse.
    • Samaneh Tajalizadehkhoob from ICANN org presented on ICANN findings regarding trends in the data from domain abuse reporting.[13]
    • Graeme Bunton reminded the audience of the plenary session held at ICANN 73 regarding responses to intentional abuse and hijacked or co-opted URLs. He reported that the outcomes of that plenary session and subsequent work would be presented at ICANN 75. He subsequently presented on NetBeacon as well.
    • Reg Levy discussed abusetool.org, a CPH-created tool to identify the web host and email hosting company for a given domain.
    • Alan Woods presented on Specification 11(3)(b) of the Registry Agreement and CPH advances toward a proposal for gathering and reporting statistics around abuse as required under that specification.
    • 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.[14]
    • 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.
    • 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.

External Forces: Governments, International Agreements, & Emergencies

  • EURALO hosted a session on legislative and regulatory developments in the EU and how they impact the DNS.[15]
    • Pari Esfandiari set the stage for the discussion, noting the critical EU initiatives that were announced in December 2020:
    • Esfandiari noted that "the devil is in the details" on all of these objectives and initiatives, noting particularly that revisions to Article 23 under NIS 2 were critical to the ICANN community.
    • Elena Plexida described ICANN's view on the EU's efforts described above:
      • Related to DNS4EU, Plexida noted that the EU was concerned about the market consolidation of public resolvers. However, ICANN's study on the existing public resolvers within the EU revealed that roughly 96% of the Internet queries within the Eu are reliant on an in-country ISP resolver. Google and Cloudflare, the particular points of concern for the EU, represented only about 2% of the resolver usage. ICANN's conclusion was that there was no indication that the market was contracting.
      • On NIS 2, Plexida stated that ICANN org's attention was focused on the scope of application of the regulations on the DNS, and the registration data provisions of Article 23.
  • EURALO also hosted a policy session on issues facing ICANN and other Internet Governance bodies in time of emergency.[16]

Name Collision

  • The SSAC presented on the progress of the Name Collision Analysis Project.[17] Due to a small meeting room, seats for the presentation were fully reserved before the commencement of the meeting. The discussion group presented on the workflow for name collision analysis and evaluation, as well as the current state of the project. NCAP project members also held working group meetings during the conference, which were also open to the public.[18]

Prioritization

  • The Prioritization Framework was featured in a broader plenary session on priority-setting.[19] The briefing paper for the session provided some background on the ongoing struggles with ICANN board, org, and community workloads, and the enduring call for prioritization.[20] The paper noted that a similar plenary session was held at ICANN 59:

While ICANN community discussions with the ICANN Board and ICANN org were ongoing, there was a perceived risk that various ICANN community groups were asserting different priorities with different interpretations.
The ICANN Strategic and Operating Planning Framework provided an initial shared understanding of prioritization, but further work was needed on how to prioritize projects related to the strategic plan and how to meet evolving needs. The plenary session explored the likely benefits from future discussions about how to set priorities.[20]

Subsequent Procedures for new gTLDs

  • The ICANN team presented on the SUBPRO operational design phase and the process, and discussed with board and IRT members the scope and focus of the SPRT.[21]
  • The GAC held a discussion session on SUBPRO, focusing on the open topic of closed generics, and had an opportunity to speak with ICANN org staff regarding developments and advances in the ODP. The session also provided background on the intended facilitated dialogue between the GAC and the GNSO regarding closed generics.[22]
  • The plans and structure of the facilitated dialogue were also the main topics in the GAC's meeting with the GNSO.[23]
  • Jonathan Zuck facilitated a session on closed generics for the ALAC, and made an effort to identify At-Large's consensus position on the analysis and response to applications for closed gTLDs.[24]

Transfer Policy Review

  • The working group initiated work on Phase 1(b) of the Transfer Policy Review PDP.[25]

SSAD and Alternative Tool Options

  • The GNSO held a session on Phase 2 of the EPDP on the Temporary Specification for gTLD Registration Data, whose recommendations focused on creating a Standardized System of Access/Disclosure of registration data (SSAD).[26] Correspondence and analysis before ICANN 74 had resulted in the opinion of GNSO Council that a "SSAD Light" option might be more feasible and cost-effective. The session, therefore, focused on options and tools for SSAD Light.[26] Goran Marby introduced Ashwin Rangan's presentation on a "WHOIS Disclosure System," a technical solution for the reporting of registration data. Rangan then proceeded to describe how ICANN org might be able to leverage existing technologies to create a solution for the needs of accurate access and disclosure of registration data.[26] The proposal was to utilize the ICANN Account authorization system to allow users to request registration information through ICANN's Naming Services Portal, which is built with SalesForce. This would create a ticket capture method and would allow each request to be handled in a pre-existing service system. The WHOIS Disclosure System would then be an application that would allow the retrieval of encrypted registration data. The proposal would balance the need to access registration data with the requirements of GDPR and other data privacy regulations. It would also sidestep the requester authentication process that rendered SSAD too expensive in the eyes of ICANN org.[26] During Q &A, Marby emphasized that the technical aspects of the proposal were designed to avoid complications with GDPR.
  • At the same session, Steve Crocker was given an opportunity to present on another software tool that might fit the bill for SSAD Light.[26] The project is a collaboration between Donuts and Crocker's Edgemoor Research Institute. Crocker noted that there would be "quite a bit of similarity and some differences" between the Donuts/ERI tool and ICANN org's proposal. He stated that the systems could coexist and augment each other.[26]
  • During the GNSO Council session, as well as earlier in the week at GNSO stakeholder gatherings, Sebastien Ducos reported that the "SSAD Light" scoping and implementation of the proposed ICANN tool could impact the timeline of the SUBPRO Operational Design Phase.[27]
  • The GAC received a briefing on the SSAD ODP and the next steps for registration data policymaking.[28]

Dates

  • Prep Week: May 31 - June 2, 2022
  • ICANN 74: June 13 - 16, 2022

References

  1. 1.0 1.1 ICANN 74 Archive
  2. ICANN.org Blog - Update on the Technical Preparations for ICANN 74, May 19, 2022
  3. ICANN75 Health and Safety, ICANN Blogs
  4. ICANN 74 Archive - GAC Opening Plenary, June 13, 2022
  5. ICANN 74 Archive - Initial Report of the GNSO Transfer Policy Review Phase 1a, June 2, 2022
  6. 6.0 6.1 6.2 ICANN 74 Archive - Planning & Finance Update, June 1, 2022
  7. ICANN 74 Archive - New gTLD Subsequent Procedures ODP Update, May 31, 2022
  8. ICANN 74 Archive - At-Large Leadership Session: Welcome to ICANN 74, June 13, 2022
  9. ICANN 74 Archive - At-Large Policy: An End User's Perspective on the Role of At-Large in DNS Abuse, June 13, 2022
  10. ICANN 74 Archive - ccNSO: ccTLD Role in DNS Abuse Policies, June 16, 2022
  11. ICANN 74 Archive - GAC Discussion: DNS Abuse, June 14, 2022
  12. ICANN 74 Archive - GNSO: CPH DNS Abuse Community Outreach, June 15, 2022
  13. See ICANN.org blog - ICANN Publishes DNS Abuse Trends, March 22, 2022
  14. ICANN 74 Archive - GNSO Council DNS Abuse Small Team Meeting, June 16, 2022
  15. ICANN 74 Archive - At-Large EURALO: Laws and Regulations in the European Union, June 14, 2022
  16. ICANN 74 Archive - At-Large EURALO Policy: Internet Governance and Multistakeholderism in Times of Emergency, June 16, 2022
  17. ICANN 74 Archive - NCAP Status Update, June 14, 2022
  18. ICANN 74 Archive - NCAP Discussion Group, June 14, 2022
  19. ICANN 74 Archive - Plenary Session: Who Sets ICANN's Priorities?, June 14, 2022
  20. 20.0 20.1 ICANN 74 Archive - Briefing Paper: Who Sets ICANN's Priorities?, June 2022
  21. ICANN 74 Archive - New gTLD Subsequent Procedures: Working Together, June 13, 2022
  22. ICANN 74 Archive - GAC Discussion on Subsequent Rounds of new gTLDs, June 13, 2022
  23. ICANN 74 Archive - Joint Meeting: GAC and GNSO, June 13, 2022
  24. ICANN 74 Archive - At-Large Policy: Closed Generics - Finding a Balance, June 15, 2022
  25. ICANN 74 Archive - GNSO Transfer Policy Review PDP Working Group, June 13, 2022
  26. 26.0 26.1 26.2 26.3 26.4 26.5 ICANN 74 Archive - GNSO: EPDP Phase 2 (SSAD), June 13, 2022
  27. ICANN 74 Archive - GNSO Council Meeting, June 15, 2022
  28. ICANN 74 Archive - GAC Discussion: WHOIS and Data Protection, June 14, 2022