Skip to main content

Board Finance Committee (BFC) Minutes

Board Finance Committee (BFC) members present: Raimundo Beca, Steve Crocker, Dennis Jennings, Rajasekhar Ramaraj - (Chair) and Bruce Tonkin (Observer)

Staff members present: Doug Brent, Samantha Eisner, John Jeffrey, Kurt Pritz, Amy Stathos, and Kevin Wilson.

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

  • Unanimously approved previous BFC meeting minutes
  • Received update on the FY10 Operating Plan and Budget status; discussed efforts taken to cap growth while increasing travel support funding; discussed Registrar fee reductions if proposed RAA signed. Actions: CFO will provide additional information to BFC on revenue estimates as well as information on the timing of renewal due dates for registrar agreements . CFO to provide a market size estimate for the total g and cc Tld market . CFO to provide a study on asking the Registrars who are not signing the new agreement to pay 25cents instead of 20cents.
  • Received and discussed update on Cost/Expenditure Analysis; discussed need for more explanatory labeling. Action: CFO will continue to modify the Cost/Expenditure Analysis to address the BFC’s concerns.
  • COO/CFO to circulate paper regarding ccIDN finance issues prior to posting.
  • Received status report on external review of Investment Policy; report expected prior to Sydney meeting. CFO reported that investments are performing well and exceeding the composite index. Discussed need to review expenditures on and procurement of professional services. Action: Staff to review procurement issues and report to BFC. CFO to report to BFC at June meeting. Reviewed proposed budget for 2010 meeting in Africa; discussed impact of travel costs and efforts and ideas to reduce costs for meetings. In the past, BFC has suggested that the each meeting have a cap of $2million. Action: BFC unanimously recommended that the budget be presented to the Board for approval if the Board wants to have the meeting in Africa.
  • Received update on Form 990 submitted to the IRS, and discussed timeline for preparation of future tax filings. Discussed the public availability of information from the organization.
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."