Skip to main content
Resources

Board Finance Committee (BFC) Minutes

Committee Members Present: Rajasekhar Ramaraj – Chair, Raimundo Beca, Steve Crocker, Dennis Jennings, and Bruce Tonkin (observer)

Additional Board Member Present: Steve Goldstein

Staff Members Present: Doug Brent, Samantha Eisner, Dan Halloran, Kurt Pritz, and Kevin Wilson


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

  1. Discussed the online approval of the minutes prior to BFC meeting.
    • Action:
      • Staff to identify system for generating reminders to BFC members for online approvals to allow the minutes to be posted soon after the meeting date.
  2. Received update on the framework for reporting on ICANN financials including a review of new and revised reports and information posted on ICANN’s website.
    • Action:
      • Staff to review and consider alternatives discussed including functional costs, forecasts, variance analyses, and run rates for subsequent budget years. At meeting in Seoul, Staff to research and provide the BFC with alternatives and recommendations of how to post data in more machine processable/accessible formats.
  3. Received update on a framework for ICANN’s procurement guidelines, and discussed key points such as transparency, proper setting of levels of approvals, and principles to guide publication of and distribution of requests for proposals to allow for easier access by potential vendors, and allowing ICANN to achieve the best economic value for its expenditures. Also discussed the need for retrospective reviews and periodic re-bid requirements for incumbent vendors.
    • Actions:
      • Staff to research procurement requirements for offices outside of the United States.
      • Staff to provide data to BFC regarding historical procurements.
      • Staff to provide a draft procurement guideline for review in Seoul.
  4. Received update on drafting of the Board Member Expense Guidelines.
    • Action:
      • Staff to finalize proposed Board Member expense guidelines for review.
  5. Discussed proposed contract for meeting support vendor to help reduce costs of meetings. BFC voted to recommend the full Board approve of the contract.
    • Action:
      • Staff to clarify terms of contract and submit to Board for approval.
  6. Received update on performance under Reserve Fund including transfer of $11 million to the Reserve Fund.
  7. Received update on the educational plans for Board Members for the new IRS Form 990.
    • Action:
      • Staff to circulate summary information for BFC and Board member review.
  8. Received update on finance-related issues related to launch of New gTLD program.
  9. Discussed proposed lease agreement, and voted unanimously to recommend that the Board approve the lease from a finance perspective.
    • Action:
      • Staff to submit lease approval request to the Board.
  10. Discussed request for approving the expenditure of funds out of the contingency budget for the SSAC Retreat, and voted, with one abstention, to recommend the approval of the contingency budget expenditure to the Board.
    • Action:
      • Staff to submit request to the Board for approval.
  11. Reviewed additional outstanding items with Staff.
    • Actions:
      • Staff to provide written response to BFC member inquiry on A/R aging reports.
      • Staff to provide update in Seoul on insurance renewals.
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."