Skip to main content
Resources

Board Finance Committee (BFC) Minutes

BFC Attendees: Sébastien Bachollet, Cherine Chalaby (Chair), Chris Disspain, and George Sadowsky

Other Board attendees: Steve Crocker

Staff Members Present: Akram Atallah – Chief Operating Officer, Xavier Calvez – Chief Financial Officer; Megan Bishop, Michelle Bright, Samantha Eisner, Taryn Presley, Ken Redhead, and Amy Stathos


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

  1. Minutes: The BFC approved the minutes of its previous meeting.

  2. FY14 Budget: The BFC reviewed the draft FY14 budget prior to the budget being posted for public comment. The staff reported on the change in the budget process that was used for the development of this budget, including community input from working groups. The budget includes the fast track budget requests that were approved at the Beijing meeting. The BFC began a discussion on how to revise the fast track process to remove the exceptional nature of those approvals and streamline them more as part of a regular approval process. The staff then presented a detailed review of the draft budget, and discussed changes and improvements to the presentation prior to posting for comment. The BFC discussed some of the community support requests, and agreed to have a further discussion on how those requests are analyzed, with a particular focus on the SSAC budget requests. The BFC agreed that, pending changes to the document, staff should move forward with the posting of the FY14 Budget for public comment.

    • Actions:

      • Discussion on the fast track approval to be continued at the next meeting of the BFC.

      • Paper to be produced for BFC comparing FY13 budget to FY14 budget.

      • Staff to revise FY14 in line with BFC comments prior to posting.

      • BFC to continue discussions regarding the status of community fast track budget requests at the next meeting of the BFC, including the SSAC fast track budget request for additional travel funding for the Durban meeting.

      • BFC to discuss timing of approval of budget at the next meeting of the BFC.

      • BFC members to submit additional proposed topics for discussion at the next meeting of the BFC.

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."