Board Activities and Meetings

View records of actions and decisions made by the ICANN Board from recent activities and meetings.

Minutes | Special Meeting of the ICANN Board | 24 October 2024

A Special Meeting of the ICANN Board of Directors was held telephonically on 24 October 2024, at 20:00 UTC.

Tripti Sinha, Chair, promptly called the meeting to order.

In addition to the Chair, the following Directors participated in all or part of the meeting: Catherine Adeya, Alan Barrett, Maarten Botterman, Chris Buckridge, Becky Burr, Edmon Chung, Sally Costerton (Sr. Advisor to President and SVP, Global Stakeholder Engagement & Interim President and CEO), Christian Kaufmann, Patricio Poblete, and León Sánchez.

The following Directors sent their apologies: Chris Chapman, Sarah Deutsch, Danko Jevtović (Vice-Chair), and Sajid Rahman.

The following Board Liaisons participated in all or part of the meeting: Harald Alvestrand (IETF Liaison), Nico Caballero (GAC Liaison), James Galvin (SSAC Liaison), and Wes Hardaker (RSSAC Liaison).

Secretary: John Jeffrey (General Counsel and Secretary).

The following ICANN org Executives and Staff participated in all or part of the meeting: Michelle Bright (Board Operations Content Coordination Director), Xavier Calvez (SVP, Planning and Chief Financial Officer), Sally Newell Cohen (SVP, Global Communications and Language Services), Samantha Eisner (Deputy General Counsel), Aaron Jimenez (Senior Board Operations Specialist), Vinciane Koenigsfeld (VP-Board Operations), Elizabeth Le (Deputy General Counsel), and Theresa Swinehart (SVP, Global Domains & Strategy).

1. Consent Agenda

The Chair opened the meeting and introduced the Consent Agenda. Becky Burr provided an overview of the agenda item, noting that the Board Governance Committee has recommended the appointment of León Sánchez to serve as a Board liaison and a member of the Pilot Holistic Review Team. Becky moved. The Board Chair called for a vote and the Board took the following action:

a. Appointment of Board member to Pilot Holistic Review Team

Whereas, on 29 April 2024, the Board directed that "preparations shall begin immediately to initiate the Pilot Holistic Review as soon as possible, by no later than September 2024. The Pilot Holistic Review shall be carried out based on the Pilot Holistic Review ToR and follow the Operating Standards for Specific Reviews, modified to be applicable to the Pilot Holistic Review."

Whereas, in Resolution 2024.04.29.02, the Board stated its intent to designate a Board member to serve as a liaison on the Pilot Holistic Review. The selected Board member will also serve on the Pilot Holistic Review Team as a full member as well as reporting to the Board progress of the review and facilitating Board consultation on the recommendations being considered by the Review Team.

Whereas, the Board Governance Committee (BGC) has recommended the Board designate León Sánchez as the Board liaison and a member of the Pilot Holistic Review Team.

Resolved (2024.10.24.01), the Board hereby appoints León Sánchez to serve as a Board liaison and a member of the Pilot Holistic Review Team.

Rationale for Resolution 2024.10.24.01

The Board is addressing this issue as part of its commitment to implement Board-approved community-issued Specific Review recommendations. As part of the initiation of the Pilot Holistic Review, the Board noted its intent to appoint a Board member to serve as a liaison on the Pilot Holistic Review Team. The selected Board member will also serve on the Pilot Holistic Review Team as a full member as well as reporting to the Board progress of the review and facilitating Board consultation on the recommendations being considered by the Review Team.

This action is in the public interest and within ICANN's mission as the Holistic Review would be focused on improving how the ICANN community contributes to the overall effectiveness of ICANN. Proceeding with the Board mandated Pilot Holistic Review to develop community supported guidelines for how the Holistic Review would be run is both in the public interest and within ICANN's mission.

There are no direct security, stability or resiliency issues relating to the DNS.

This is an Organizational Administrative Function that does not require public comment.

The Consent Agenda was approved by general consent. The Resolution passed.

2. Main Agenda

The Chair introduced the Main Agenda.

a. Updates to ICANN Delegation of Authority Guidelines

A member of the Board Governance Committee (BGC) introduced the agenda item and explained the BGC has been evaluating the Delegation of the Authority Guidelines (Guidelines), which was previously adopted in November 2016 and subsequently updated in 2017, to align with current practices and provide greater clarity of the roles between the Board and the CEO. Following substantive discussions at the BGC and Board level, the BGC has recommended that the Board approve the proposed updates to the Guidelines.

Following discussion, the Chair called for a vote and the Board took the following action:

Whereas, ICANN Bylaws Article 2 establishes that with certain exceptions, the powers of ICANN shall be exercised by, and its property controlled and its business and affairs conducted by or under the direction of, the Board.

Whereas, ICANN Bylaws Article 15 establishes officers of ICANN, and designates the President to be the Chief Executive Officer (CEO) of ICANN in charge of all of its activities and business. All other officers and staff shall report to the President or his or her delegate, unless stated otherwise in the Bylaws.

Whereas, on 8 November 2016, the ICANN Board adopted Delegation of Authority Guidelines (Guidelines) to set out a clear line of delegation of authority between the role of the Board and the roles of CEO and management. The Board noted therein that "the Guidelines shall be reviewed regularly and amended from time to time by resolution of the Board." The Board subsequently revised the Guidelines on 16 March 2017.

Whereas, the Board Governance Committee has reviewed the Guidelines and has recommended updates to the Guidelines to align with current areas of authority and responsibilities between the ICANN Board and the ICANN CEO.

Resolved (2024.10.24.02), the Board hereby adopts the updated ICANN Delegation of Authority Guidelines to provide clear guidance and clarification of roles between the ICANN Board and the ICANN CEO.

All members of the Board present voted in favor of Resolution 2024.10.24.02. Four Directors were unavailable to vote. The Resolution carried.

Rationale for Resolution 2024.10.24.02

The Board is taking action at this time in furtherance of its adoption of the ICANN Delegation of Authority Guidelines (Guidelines) to provide greater clarity of roles between the Board and CEO. As resolved on 8 November 2016, the Guidelines were anticipated to need updating and modification, and the process for such modification includes resolution of the Board. The updated Guidelines align with current practices and provide greater clarity of the roles between the Board and the CEO, and the key interdependencies in those relationships. By adopting these updated Guidelines, the Board intends to ensure that the Board and CEO continue to operate within the scope of its mission.

This decision is within the public interest and consistent with ICANN's mission as it is expected to positively impact the ICANN community as it provides additional transparency and clarity about the roles and responsibilities of key members in the ICANN organization. Additionally, it provides additional accountability to the community by clearly defining the roles and responsibilities.

The action is not expected to have a fiscal impact on ICANN organization.

There are no direct security, stability or resiliency issues relating to the DNS.

This is an Organizational Administrative Function that does not require Public Comment.

b. GAC Advice: ICANN80 Kigali Communiqué (June 2024)

Becky Burr introduced the agenda item. Becky explained that following receipt of the GAC's ICANN80 Kigali Communiqué setting forth advice concerning the Applicant Support Program (ASP), the Board initiated the Board-GAC consultation process in accordance with Bylaws requirements. Becky explained that the Board and GAC engaged in productive dialogue during this consultation process, and that it is recommended that the Board accept the comprise reached between the parties on this issue, as set forth in the scorecard titled GAC Advice – ICANN80 Kigali Communiqué: Actions and Updates (24 October 2024).

Harald Alvestrand, Edmon Chung, James Galvin, and Patricio Poblete recused themselves from consideration due to potential, actual, or perceived conflicts of interest. The recusing Board members noted that they have recused themselves from all discussions of this matter to date.

León Sánchez moved and Becky seconded. The Chair called for a vote and the Board took the following action:

Whereas, the Governmental Advisory Committee (GAC) met during the ICANN80 meeting in Kigali, Rwanda and issued advice to the ICANN Board in a communiqué on 17 June 2024 ("ICANN80 Kigali Communiqué").

Whereas, the ICANN80 Kigali Communiqué was the subject of an exchange between the Board and the GAC on 15 July 2024.

Whereas, in a 12 July 2024 letter, the GNSO Council provided its feedback to the Board concerning advice in the ICANN80 Kigali Communiqué relevant to Applicant Support Program and Auctions: Mechanisms of Last Resort/Private Resolution of Contention Sets in New gTLDs.

Whereas, the Board developed a scorecard to respond to the GAC's advice in the ICANN80 Kigali Communiqué, taking into account the dialogue between the Board and the GAC and the information provided by the GNSO Council.

Whereas, on 29 July 2024, the Board initiated the Board-GAC consultation process in accordance with Bylaws 12.2(a)(x) on ICANN80 Kigali Communiqué GAC Consensus Advice items §1.a.i and §1.a.ii.

Whereas, on 16 September 2024, the Board met with the GAC to "try, in good faith and in a timely and efficient manner, to find a mutually acceptable solution" for the two GAC advice items regarding the Applicant Support Program in the ICANN80 Kigali Communiqué.

Whereas, on 3 October 2024, the Board sent correspondence to the GAC outlining the Board's understanding of the Consultation meeting compromise and conclusion on advice items 1.a.i and 1.a.ii.

Whereas, on 16 October 2024, the GAC sent correspondence to the Board affirming its understanding of the Consultation meeting compromise and conclusions on advice items 1.a.i and 1.a.ii.

Resolved (2024.10.24.03), the Board adopts the scorecard titled "GAC Advice – ICANN80 Kigali Communiqué: Actions and Updates (24 October 2024)" in response to some of the open GAC advice items in the ICANN80 Kigali Communiqué.

Nine Board Directors voted in favor of Resolution 2024.10.24.03.  Chris Chapman, Sarah Deutsch, Danko Jevtović, and Sajid Rahman were unavailable to vote. Edmon Chung and Patricio Poblete abstained. The Resolution carried.

Rationale for Resolution 2024.10.24.03

Article 12, Section 12.2(a)(ix) of the ICANN Bylaws permits the GAC to "put issues to the Board directly, either by way of comment or prior advice, or by way of specifically recommending action or new policy development or revision to existing policies." In its ICANN80 Kigali Communiqué (17 June 2024), the GAC issued advice to the Board regarding the Applicant Support Program and Auctions: Mechanisms of Last Resort/Private Resolution of Contention Sets in New gTLDs. The GAC also provided a follow-up to previous advice regarding the Applicant Support Program and Urgent Requests for Disclosure of Registration Data. Article 12, Section 12.2(a)(x) of the ICANN Bylaws states that the "advice of the Governmental Advisory Committee on public policy matters shall be duly taken into account, both in the formulation and adoption of policies. In the event that the Board determines to take an action that is not consistent with Governmental Advisory Committee advice, it shall so inform the Governmental Advisory Committee and state the reasons why it decided not to follow that advice. Any Governmental Advisory Committee advice approved by a full Governmental Advisory Committee consensus, understood to mean the practice of adopting decisions by general agreement in the absence of any formal objection ("GAC Consensus Advice"), may only be rejected by a vote of no less than 60% of the Board, and the Governmental Advisory Committee and the Board will then try, in good faith and in a timely and efficient manner, to find a mutually acceptable solution. The Governmental Advisory Committee will state whether any advice it gives to the Board is GAC Consensus Advice."

The ICANN Bylaws require the Board to take into account the GAC's advice on public policy matters in the formulation and adoption of policies. The Board is taking action today on two GAC Consensus Advice items regarding the Applicant Support Program to the ICANN Board in the ICANN80 Kigali Communiqué in the scorecard dated 24 October 2024. This decision is in the public interest and within ICANN's mission, as it is consistent with ICANN's Bylaws for considering and acting on advice issued by the GAC.

In adopting its response to accept the compromise on GAC advice item 1.a.i and to reject GAC advice item 1.a.ii in the ICANN80 Kigali Communiqué, the Board reviewed various materials, including, but not limited to, the following materials and documents:

The adoption of the GAC scorecard will have a positive impact on the community because it will assist with resolving the advice from the GAC concerning gTLDs and other matters. There are no foreseen fiscal impacts associated with the adoption of this resolution. Approval of the resolution will not impact security, stability or resiliency issues relating to the DNS. This is an Organizational Administrative function that does not require public comment.

c. Board adoption of the Applicant Support Program (ASP) Handbook

Becky Burr, the Co-Chair of the Next Round Board Caucus introduced the agenda item, noting that the Board is being asked to adopt the Applicant Support Program (ASP) Handbook. She explained the Handbook has been reviewed by the Implementation Review Team and put out for public comment. She also noted that there was another public comment proceeding held for the ASP terms and conditions.

Harald Alvestrand, Edmon Chung, James Galvin, and Patricio Poblete recused themselves from consideration of the matter due actual or potential conflicts of interest. The recusing Board members noted that they have recused themselves from all discussions of this matter to date.

Becky moved and Maarten Botterman seconded. The Chair called for a vote and the Board took the following action:

Whereas, the ICANN Board directed ICANN org to make preparations for the New gTLD Program: Next Round at the ICANN76 Community Forum.

Whereas, the ICANN Board acknowledged receipt of the plan for preparations of New gTLD Program: Next Round and directed ICANN org to provide the Board with periodic updates on its progress of implementation of this program.

Whereas, the Subsequent Procedures Implementation Review Team (SubPro IRT) was formed to assist ICANN org in the implementation of Final Report in the new gTLD Subsequent Procedures Policy Development Process.

Whereas, the Applicant Support Program (ASP) is an implementation of Topic 17 of the Subsequent Procedures Policy.

Whereas, ICANN org affirms that the ASP Handbook describes the Applicant Support Program criteria, indicators, and evaluation process.

Whereas, the SubPro ASP-IRT has reviewed the ASP Handbook.

Whereas, a public comment proceeding was held between 12 February 2024 to 2 April 2024 for the express purpose of soliciting feedback on the ASP Handbook, and all feedback received was subsequently addressed by ICANN org in consultation with the ASP-IRT.

Whereas, a public comment proceeding on the draft ASP Terms and Conditions was held between 24 July and 23 August 2024 and ICANN org addressed feedback in consultation with the full IRT.

Resolved (2024.10.24.04), the ICANN Board approves the implementation of the Applicant Support Program as described by the ASP Handbook.

Resolved (2024.10.24.05), the ICANN Board approves the ASP Handbook, and directs the Interim President and CEO, or her designee(s), to publish the ASP Handbook and update it as appropriate.

Nine Board Directors voted in favor of Resolutions 2024.10.24.04 and 2024.10.24.05. Chris Chapman, Sarah Deutsch, Danko Jevtović, and Sajid Rahman were unavailable to vote. Edmon Chung and Patricio Poblete abstained. The Resolutions carried.

Rationale for Resolutions 2024.10.24.04 – 2024.10.24.05

Why is the Board addressing this issue?

The Applicant Guidebook for the 2012 round of new gTLDs was explicitly approved by the ICANN Board. Unlike the 2012 round, the New gTLD Program: Next Round has ancillary programs, each requiring a separate document for applicants. The Board is approving the ASP Handbook to acknowledge the community review it has received similar to the Applicant Guidebook of the 2012 round.

What is the proposal being considered?

The proposal being considered is the affirmation of the ASP Handbook following the review by the ICANN community through consultation with the ASP Subsequent Procedures Implementation Review Team (SubPro ASP-IRT), a public comment proceeding, and further consultation with the ASP-IRT.

What concerns or issues were raised by the community?

Overall, the community provided constructive feedback regarding the ASP Handbook. Many suggestions from both the SubPro ASP-IRT and the public comments were incorporated into the ASP Handbook.

Some in the community raised concerns regarding the accessibility of the ASP eligibility criteria and the ASP Handbook, especially in light of global diversification aims.

These concerns had two areas of focus:

  1. The ASP eligibility criteria do not include geographic restrictions or prioritization for ASP applicants from lesser developed economies or regions, and that the ASP Handbook should include more focus on underserved regions.
  2. The ASP Handbook is not accessible to diverse, non-English speaking audiences.

Per recommendation 17.1 of the GNSO Final Report on the new gTLD Subsequent Procedures Policy Development Procedure, the ASP should be open to applicants regardless of their location as long as they meet other program criteria. Following the public comment period, ICANN staff updated the ASP Handbook structurally and accessibility-wise.

Following the public comment period on the draft ASP Handbook, the Governmental Advisory Committee (GAC) issued advice on the Applicant Support Program in its ICANN80 Kigali Communiqué. The GAC expressed concerns with the first-come, first-served approach of evaluating ASP applications on an ongoing basis. The GAC also expressed a desire for ICANN community members with relevant expertise to participate in the ASP application evaluation process. The Board and the GAC entered into a Bylaws consultation on these advice items and the Board took action on the ASP-related ICANN80 GAC advice items 1.a.i and 1.a.ii on 24 October 2024.

What other factors did the Board consider?

The ASP application submission period is anticipated to open on 19 November 2024. Material changes to the ASP Handbook and/or the ASP Evaluation may require a delay in the opening of this period, which could in turn impact the opening of the gTLD application period. Additionally, material changes may require some re-implementation to systems that have been developed for the ASP Evaluation, increasing the cost of the program.

What materials did the Board review?

Are there positive or negative community impacts?

Approval of the ASP Handbook will allow the ASP to launch to receive applications for support, in line with the Board-approved policy recommendations on Topic 17 from the Final Report of the Subsequent Procedures Policy Development Process. As evidenced by the community attention and participation on the topic of Applicant Support, there is a great deal of community anticipation about the implementation of the Applicant Support Program.

Are there fiscal impacts or ramifications on ICANN (strategic plan, operating plan, budget); the community; and/or the public?

The fiscal impacts of the ASP are part of the gTLD Program: Next Round budget and funding. The Board previously resolved (2024.09.07.03) on funding for the Applicant Support Program.

Are there any security, stability or resiliency issues relating to the DNS?

Applicants that qualify for support under the Applicant Support Program are still required to apply for and successfully complete all aspects of the gTLD Program evaluation in order to be eligible for delegation of a new gTLD. Security, stability and resiliency issues relating to the DNS are addressed as part of the New gTLD Program.

Is this decision in the public interest and within ICANN's mission?

Approving the ASP Handbook will allow the ASP to launch the application submission period, anticipated on 19 November, to receive applications for support. As part of the New gTLD Program: Next Round, the ASP is designed to be in line with Affirmation 1.3 of the Final Report on the new gTLD Subsequent Procedures Policy Development Process: "The Working Group affirms that the primary purposes of new gTLDs are to foster diversity, encourage competition, and enhance the utility of the DNS."

Is this either a defined policy process within ICANN's Supporting Organizations or ICANN's Organizational Administrative Function decision requiring public comment or not requiring public comment?

The ASP Handbook already completed a public comment period from 12 February 2024 to 2 April 2024.

d. Fundamental Bylaws Amendment regarding Grant Program

León Sánchez, the Chair of the Board Accountability Mechanisms Committee, introduced the agenda item, noting that the Board has had extensive discussions regarding the proposed Fundamental Bylaws amendment related the ICANN Grant Program. The Board engaged in a discussion regarding Board member conflicts of interests related to the ICANN Grant Program. Harald Alvestrand, Maarten Botterman, Chris Buckridge, Nicolas Caballero, Edmon Chung, James Galvin, Wes Hardaker, Christian Kaufmann and Patricio Poblete recused themselves from consideration of the matter out of an abundance of caution for conflicts of interest. It was noted that while the Board intends to approve the Fundamental Bylaws amendment as posted for public comment, there were not sufficient non-conflicted Board attendance to achieve the required voting threshold for a Fundamental Bylaws amendment.

León moved and Catherine Adeya seconded. The Chair called for a vote and the Board took the following action:

Whereas, the ICANN community, through the Cross Community Working Group on New gTLD Auction Proceeds (CCWG-AP), made a recommendation that utilization of ICANN's Reconsideration and Independent Review processes (collectively, "ICANN Accountability Mechanisms") should be limited in certain circumstances (Recommendation 7). During ICANN organization's (ICANN org) work to implement the ICANN Grant Program aligned with the CCWG-AP's full set of recommendations, Recommendation 7 posed a unique challenge, as the CCWG-AP's language was too narrow based on the implementation design.

Whereas, the ICANN Board has taken a series of actions and communications to move forward with the ICANN Grant Program while trying to address the issues presented by the original language of Recommendation 7, including:

  • 26 October 2023 resolutions revisiting the Board's prior approval of Recommendation 7 and directing the development of a more general process for the ICANN community to indicate when ICANN's Accountability Mechanisms should not be available;
  • 21 January 2024 initiation of a Fundamental Bylaws amendment process setting forth the general process for the ICANN community to limit access to ICANN's Accountability Mechanisms.
  • 2 March 2024 letter to the CCWG-AP's Chartering Organizations specifying a proposed change to Recommendation 7 to remove a reference to the "Independent Application Assessment Panel" so that Recommendation 7 could better achieve its goal of preserving auction proceeds for grants instead of funding challenges to decisions on grant applications; and the

Whereas, in response to Public Comment on the proposal for a general process on limitation of access to ICANN Accountability Mechanisms, the ICANN community was not supportive. The ICANN Board therefore, on 29 July 2024, reinitiated a Fundamental Bylaws Amendment Process with a more narrow scope, which proposed to amend the ICANN Reconsideration process (at ICANN Bylaws, Article 4, Section 4.2) and the Independent Review process (at ICANN Bylaws, Article 4, Section 4.3) to specifically exclude claims or disputes "relating to decisions to approve or not approve an application to the ICANN Grant Program" from each of the relevant mechanisms. As part of this action, the Board clarified "that it is no longer pursuing the previously posted amendment to Article 4, Section 4.1 of the Bylaws."

Whereas, on 7 August 2024, ICANN opened a Public Comment Forum on the updated Fundamental Bylaws Proposal. Nine submissions were received (including one late), and all commenters were supportive of the proposal as posted for Public Comment. Commenters noted that the updated proposal was better aligned to the intention of Recommendation 7 and was a more appropriate means of implementation than the prior proposal. The Governmental Advisory Committee (GAC) specifically noted that the new proposal amendment to the Fundamental Bylaws narrows the impact on ICANN's Accountability Mechanisms about which the GAC raised a concern in May 2024.

Whereas, at or before the forthcoming ICANN81 Public Meeting, ICANN will take the opportunity to finalize confirmation with the Chartering Organizations of the CCWG-AP their support or non-objection to the proposed update Recommendation 7, including confirmation with the GAC that it too is in a position to support or not object to the updating of Recommendation 7, in light of the Board's acceptance of this alternate path. The Board will, prior to the approval of a slate of successful applications to the first cycle of the ICANN Grant Program, formally confirm its adoption of the updated Recommendation 7.

Resolved (2024.10.24.06), the ICANN Board hereby indicates that it intends to take an action to approve the amendment of the Fundamental Bylaws at Article 4, Section 4.2(d) and Section 4.3(c), as posted for public comment when it has sufficient attendance to achieve the required voting threshold for a Fundamental Bylaws amendment.

Six Board Directors voted in favor of Resolution 2024.10.24.06 to signal the Board's intent to approve the relevant Fundamental Bylaws amendment when it has sufficient attendance to achieve the required voting threshold. Chris Chapman, Sarah Deutsch, Danko Jevtović, and Sajid Rahman were unavailable to vote. Maarten Botterman, Chris Buckridge, Edmon Chung, Christian Kaufmann, and Patricio Poblete abstained. The Resolution carried.

Rationale for Resolution 2024.10.24.06

Today's Board action is to express the Board's intent to approve an amendment to the Fundamental Bylaws set out at Article 4, Sections 4.2(d) and 4.3(c), which would represent a path to closure of the conversation about the Cross-Community Working Group on New gTLD Auction Proceeds (CCWG-AP) Recommendation 7. This action signals the Board's intent to move forward with the Grant Program consistent with the series of actions and the communications taken to date. The Board's intended action to approve the Fundamental Bylaws amendment would support the Board's duty and interest in remaining accountable for the use of the auction proceeds funds that support the ICANN Grant Program.

Today's action is in the public interest, and is aligned with ICANN's Bylaws and mission, in preserving accountability for funds under the ICANN Grant Program and faithfully implementing the recommendations of the community.

This action is not anticipated to result in any impact to the security, stability or resiliency of the Internet's DNS. Nor is this action anticipated to result in any budgetary or financial implications.

This is an Organizational Administrative Function decision requiring public comment, which has already been undertaken.

The Chair called the meeting to a close.

Published on 15 November 2024