Skip to main content

Minutes | Board Finance Committee (BFC) Meeting

BFC Attendees: Harlad Alverstrand, Becky Burr, Ron da Silva (Chair), Lito Ibarra, Danko Jevtović, Ihab Osman, and Tripti Sinha

Other Board Member Attendees: Avri Doria and León Sánchez

ICANN Org Attendees: Ted Bartles (Meeting Production Operations Senior Manager) Xavier Calvez (SVP & Chief Financial Officer), Franco Carrasco (Board Operations Specialist), Becky Nash (VP, Finance), Wendy Profit (Board Operations Senior Manager), Shani Quidwai (Director, Financial Planning & Analysis), Jennifer Scott (Senior Counsel), Amy Stathos (Deputy General Counsel), and Nick Tomasso (VP, Global Meeting Operations & Managing Director – Middle East & Africa)

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

  1. BFC Workplan – The BFC reviewed its Workplan, which is on target.

  2. Review of ICANN74 Meeting Venue and Hotel Contracting Decisions – The BFC received a presentation from ICANN org regarding the proposed June 2022 ICANN74 meeting venue and hotel contracting costs. The Board, with a recommendation from the BFC, is responsible for authorizing any costs totaling $500,000.00 and over and the ICANN74 meeting costs qualify for such authorization. ICANN org explained that it performed its due diligence on the selected venue in The Hague, Netherlands, including ensuring that the venue was selected in consideration of ICANN org's cost-savings measures for its meetings. Upon analyzing proposals for ICANN74 meeting venues to identify those that met the Meeting Location Selection Criteria, ICANN org recommended to the BFC that it recommend that the Board authorize the ICANN74 meeting venue and hotel contracting and disbursement costs. The BFC discussed ICANN org's recommendation, including comparing the ICANN74 meeting costs with the cost of other ICANN meetings. Following discussion, the BFC recommended that the Board authorize ICANN org to enter into, and make disbursements in furtherance of, contracts for the ICANN74 meeting.

    • Action: ICANN org to prepare materials for Board consideration.

Published on 31 March 2020

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"""" is not an IDN."