Skip to main content
Resources

Minutes | Board Finance Committee (BFC) Meeting

BFC Attendees: Harald Alverstrand, Becky Burr, Ron da Silva, Danko Jevtović (Chair), Mandla Msimang, Ihab Osman and Tripti Sinha

Other Board Member Attendees: Avri Doria, Lito Ibarra, and Göran Marby

ICANN Org Attendees: Michelle Bright (Board Content Coordination Director), Xavier Calvez (SVP, Planning and Chief Financial Officer), Franco Carrasco (Board Operations Specialist), Mukesh Chulani (gTLD Accounts Senior Manager), John Jeffrey (General Counsel and Secretary), Cecibel Izaguirre (Manager, Billings Operations), Elizabeth Le (Associate General Counsel), Alex Morshed (Finance Manager), Becky Nash (VP, Planning), Shani Quidwai (Sr. Director Finance), Vivek Sengupta (Director of Procurement), Amy Stathos (Deputy General Counsel), Russ Weinstein (VP, GDD Accounts and Services), and Victoria Yang (Planning Sr. Manager)


The following is a summary of discussions, actions taken and actions identified:

  1. BFC Workplan – The BFC reviewed its Workplan for FY21, including updates on the adjustment of timing of the performance review of the Reserve Fund from January to February 2021, and the addition of the proposed Supplemental Fund for Implementation of Community Recommendations to the January 2021 BFC meeting. The BFC noted that Workplan is on target.
  2. Contracting Approval for Credit Card Processing – The BFC received a briefing on the proposed contract for credit card processing service provider because the total amount over the three-year term of the contract is expected to exceed US$500,000. ICANN org followed the procurement process, which included a formal RFP conducted by ICANN Procurement and Accounting. ICANN org evaluated the proposals received and determined that the service provider with which ICANN has engaged since September 2007, provides the best product of ICANN's needs and the lowest price. The proposed costs are in line with industry standards and were less than the proposed rates from other RFP respondents. The proposed contract represents a total costs savings to ICANN org compared to the current contract and the total costs is covered in the budget. The proposed three-year contract may be cancelled at any time with 60 days advance notice. The BFC approved a recommendation to the ICANN Board for approval of a three-year contract with the proposed vendor for credit card processing.

    • Actions: ICANN org to prepare materials for Board consideration.
  3. Draft FY22-26 Operating & Financial Plans (FY22-26 O&FP) and Draft FY22 Operating Plan & Budget (FY22 OP&B) – The ICANN President and CEO provided a summary of the draft FY22-26 O&FP and draft FY22 OP&B. He expressed his thanks to ICANN org staff for the amount of work that was needed to prepare the draft FY22-26 O&FP and draft FY22 OP&B. ICANN org briefed the BFC on the draft FY22-26 O&FP and draft FY22 OP&B, which will be published from mid-December 2020 to February 2021 for public comment. The ICANN Strategic Outlook: 2020 Trends Report and Funding Forecast Assumptions for Fiscal Years 2022-2026 will be published alongside the Planning documents as supporting documentation. With respect to the draft FY22-26 O&FP, based on the Strategic Outlook trends assessment, the Board Strategic Planning Committee recommended no changes at this time to the Strategic Objectives. Although there is still uncertainty, for planning purposes the FY22 plans assume business travel and three face-to-face meetings ICANN meetings and other engagement activity will resume. The WS2 Implementation work is prioritized in the FY22 plans. Other Board-approved recommendations will be subject to prioritization process. Progression towards the achievement of the Operating Initiatives is included in FY22 plans. The BFC reviewed the 15 Operating Initiatives for FY22, including examples of key milestones. ICANN org also briefed the BFC on the five year (FY22-26) financial funding projections approach, and the funding and expense assumptions. The BFC expressed its support to publish the documents for public comment. The BFC also discussed preparations for future work and asked ICANN org to prepare a resourcing plan.

    • Actions:

      • ICANN org to publish materials for public comment.
      • ICANN org to prepare a resourcing plan for future work.
  4. AOB

    1. Process for Approval of Legal Invoice Disbursement – The BFC discussed the revised process for approval of legal invoice payments, which includes a step for the Board Accountability Mechanism Committee (BAMC) to consider the proposed payment before it is submitted to the Board for approval. As part of this revised process, the BFC will be notified of any BAMC recommendation for such approvals before the approvals are submitted to the Board. The BFC will also receive a regular spending report.
    2. Sponsoring Committee for the Board Caucus on Auction Proceeds – The BFC considered and agreed with the Board Governance Committee's proposal that the BFC shall act as the Sponsoring Committee for the Board Caucus on Auction Proceeds.

Published on 21 January 2021

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."