Skip to main content
Resources

Minutes | Board Finance Committee (BFC) Meeting

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

Other Board Member Attendees: Maarten Botterman, Avri Doria, Manal Ismail, and León Sánchez

ICANN Org Attendees: Susanna Bennett (SVP & Chief Operating Officer), Xavier Calvez (SVP & Chief Financial Officer), David Conrad (SVP & Chief Technology Officer) John Jeffery (General Counsel & Secretary), Becky Nash (VP, Finance), Wendy Profit (Board Operations Senior Manager), Shani Quidwai (Director, Financial Planning & Analysis), Jennifer Scott (Senior Counsel), Vivek Sengupta (Director, Procurement), Amy Stathos (Deputy General Counsel), and Victoria Yang (Operations Sr. Program Manager)

Invited Guests: Representatives from State Street Global Advisors


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. Proposed Approval of FY21 IANA Budget – The BFC received an update from ICANN org about the FY21 IANA budget and approval process. The BFC also reviewed and discussed proposed approval of the FY21 IANA budget. The BFC provides oversight on the budgeting process for the IANA and full ICANN budget. ICANN org noted that the IANA budget is driven by its proposed expenses, includes a contingency amount for unforeseen operational expenses, and takes into account inflation. The IANA budget cycle occurs in advance of the full ICANN budget because it needs to be integrated into the full ICANN budget. ICANN org reported that to date, ICANN received input from PTI on the IANA budget; the IANA budget was published for public comment on 14 October 2019; a report of public comments was published on 19 December 2019; and the PTI Board adopted the operating plan and budget on 8 January 2020. The BFC discussed that during the public comment period, 32 comments were received and noted that no substantive changes were required to the IANA budget as a result of the comments. ICANN org recommended the BFC recommend that the Board approve the IANA budget. The committee noted that following ICANN Board approval, an empowered community process will begin and, if no petitions are raised, the FY21 IANA budget will be adopted and in effect for FY21. After discussion, the BFC voted to recommend that the Board approve the FY21 IANA budget.

    • Action: Board to consider the BFC's recommendation that it approve the FY21 IANA budget.
  3. Reserve Fund Performance Review – The BFC received its annual update on the reserve fund performance by representatives from State Street Global Advisors (SSGA), including how the reserve fund is invested and how the investments are performing. The performance of the reserve fund investments over 2019 was favorable, both in terms of contributions and market returns. The fund is maintaining a moderately conservative risk profile and growing its value beyond inflation. The BFC raised the question of whether the strategy of the reserve fund portfolio investments should change after it reaches the desired amount of reserve funding. ICANN org intends to continue discussion on that topic with the SSGA representatives and provide analysis and feedback to the BFC.

  4. Review of BFC Charter – The BFC Chair indicated the BFC needs to do a number of things regarding the charter. However, the BFC deferred review and discussion of the BFC's charter until its next meeting.

Published on 20 February 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""icann.org"" is not an IDN."