Skip to main content

Minutes – Board Finance Committee (BFC) Meeting

BFC Attendees: Rajasekhar Ramaraj – Chair; Gonzalo Navarro and George Sadowsky

Other Board Member Attendees: Dennis Jennings (BFC observer) and Bruce Tonkin (BFC Observer)

Staff Attendees: Doug Brent – Chief Operating Officer; Kevin Wilson – Chief Financial Officer; Samantha Eisner, Diane Schroeder, and Amy Stathos

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

  1. Reviewed the status of the strategic BFC project plan and future meeting planning.
    • Action:
      • Staff to revise work plan as identified by BFC.
      • Staff to review dashboard financials to ensure accurate reporting.
  2. Received update on FY11 budget planning and revenue strategy to prepare the budget for posting for community input. Staff identified that the draft budget maps to the strategic plan categories, and reflects a greater amount of input and feedback than in prior years.
    • Action:
      • Staff to finalize draft of budget framework for discussion at February BFC meeting.
  3. Received an update on the FY10 budget and expenditure to date, on the cost containment procedures under way to assist in managing expenditure, and on the need to access the FY10 budget contingency line item to cover additional expenditures. The BFC requested that staff make clear that any cost costing measures do not include reduction of essential ICANN services, which would require broader discussions. The BFC unanimously approved recommending that the Board approve accessing the FY10 budget contingency line item for operational expenditures in FY10.
    • Actions:
      • Staff to ensure that BFC concerns of maintaining ICANN essential services in furtherance of ICANN’s mission are reflected in FY10 cost containment budget discussions.
      • Staff to revise draft FY11 operating plan and budget framework to reflect BFC comments.
  4. Received update from staff on the drafting of Cost Accounting Framework and the Procurement Guidelines.
    • Actions:
      • Staff to address BFC comments and revise document accordingly.
      • BFC members to provide feedback on both documents.
      • Staff to facilitate receipt of comments on both documents from the Audit Committee and consolidate with comments identified by BFC members for consideration at a February BFC meeting.
  5. Received update from staff on status of the preparation of ICANN’s Form 990 filing and planning for Board member training on the Form 990 at the Nairobi meeting.

  6. Received staff update on oversight and identification of internal controls related to retirement plan.
    • Action:
      • Staff to continue to provide BFC with updates on review of internal controls.
  7. Received update from staff on budget for Nairobi meeting.
    • Action:
      • Staff to provide BFC with resolution on Nairobi budget for consideration at February BFC meeting.
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."