Skip to main content
Resources

Minutes | Board Finance Committee (BFC)

BFC Attendees: Sebastien Bachollet, Cherine Chalaby – Chair, Chris Disspain, and George Sadowsky, and Mike Silber

Apologies: Bruno Lanvin

Other Board member Attendee: Steve Crocker

Executive and Staff Attendees: Susanna Bennett (Chief Operating Officer), Megan Bishop (Board Support Coordinator), Xavier Calvez (Chief Financial Officer), John Jeffrey (General Counsel and Secretary), Taryn Presley (Sr. Manager, FP&A) and Amy Stathos (Deputy General Counsel)


The following is a summary of discussions and actions identified:

FY15 Budget: Staff presented various issues related to the FY15 budget. Staff reported on the process and timeline overview for the entire budgeting process, including the timeline and process for SO and AC additional budget request process, as well as the minor deviations from the process that was posted in November 2013. Staff noted that the intent this year is to minimize growth in most departments to help stabilize the organization and to optimize staff efficiency. The BFC also talked about the assumptions that have to be made in terms of revenue from transactional fees, in particular from new gTLDs, and how revenue might increase or decrease over time, depending on its source. The committee then discussed the assumptions about operating expenses for FY15, which include exceptional items from FY14 that will not be repeated, the number of Public Meetings per year goes from four to three, staffing costs, priority projects, and accounting for a higher contingency amount due to higher operating expenses. The committee also talked about the statements of activities both for FY15, and as it is compared to FY14. The committee also discussed resource utilization areas and compared the FY14 budget and the FY14 statement at activities.

  • Action:
    • Staff to schedule a further meeting to discuss the SO/AC additional budget requests, and revenue sensitivity analysis.

Published on 22 June 2014

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