Skip to main content

Board Finance Committee (BFC) Minutes

Committee Members Present: Raimundo Beca, Steve Crocker, Dennis Jennings, and Rajasekhar Ramaraj – Chair

Committee Member not present and sending apologies: Bruce Tonkin

Staff Members Present: Samantha Eisner, John Jeffrey, and Kevin Wilson

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

  • Unanimously approved minutes from previous meeting.
  • Discussed the BFC meeting schedule and revised upcoming dates. The next BFC meeting will take place in September.
  • Received update on Investment Policy review and final report, and discussed recommended revisions to Investment Policy arising from the review. Reviewed recommended amount for transfer to reserve fund after the revised Investment Policy is approved by the Board, and the future need to determine a cap on the reserve fund. Unanimously approved a resolution 1) informing the Board of the results of the Investment Policy review and recommending the Board adopt the policy as revised; 2) recommending the Board approve a transfer of US $11 million to the reserve fund; and 3) requiring monthly reporting on compliance with Investment Policy and performance.
  • Discussed timeline for drafting and formation of procurement policy to address all contracts entered into by ICANN. Action: Staff to prepare first draft of procurement policy for committee review and discussion at BFC meeting in September, with a plan for further review prior to the Seoul meeting.
  • Received update on financial reporting developments and the additional reports provided as a result of BFC and community input. Action: Staff to include Expense Area Group reporting in public dashboard after review of public comments, and staff to provide BFC projected forecasts for functional reporting.
  • Reviewed the BFC project list and work plan created by staff. Discussed need for creation of a calendar of events and activities for all regular work of the BFC. Action: Staff to create a calendar of basic BFC activities.
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."