Skip to main content
Resources

Board Finance Committee (BFC) Meeting Minutes

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

Apologies: Bruno Lanvin

Other Board member Attendees: Steve Crocker and Fadi Chehadé

ICANN Executive and Staff Member Attendees: Susanna Bennett (Chief Operating Officer), Megan Bishop (Board Support Coordinator), Michelle Bright (Board Support Content Manager), Xavier Calvez (Chief Financial Officer), Allen Grogan (Chief Contracting Counsel), John Jeffrey (General Counsel and Secretary), David Olive (Vice President, Policy Development Support), Amy Stathos (Deputy General Counsel) and Nick Tomasso (VP, Meetings & Int'l Real Estate Operations)


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

  1. Minutes – The BFC approved the minutes from the last BFC meeting.

  2. GAC Secretariat Support – Staff presented the background and overview of a potential long-term contract for the GAC Secretariat. The item has come to the BFC and is then meant for Board approval because the proposed contract exceeds $500,000, which requires Board approval pursuant to ICANN's Contracting and Disbursement Policy. The BFC raised and discussed some questions about the nature and structure of the agreement and agreed that staff should gather some additional information before proceeding.

    • Action – Staff to reach out to the appropriate parties to gather additional information and then decide how to proceed.
  3. Istanbul Office Lease – Staff presented an overview and the BFC discussed various matters relating to a more long-term lease in Istanbul, including the location, the lease costs, the size and quality of staff being hired for the office, and the current space we are using. The BFC recommended that the Board authorize the President and CEO, or his designee(s), to take all actions necessary to enter into a lease for the Istanbul office.

    • Action – Staff to prepare necessary materials for Board consideration at the next Board meeting scheduled for 30 July 2014.
  4. October 2015 Public Meeting Venue – Staff presented a proposal for the October 2015 Public Meeting venue. Staff explained that the proposal for this meeting was being presented before the proposal for the mid-year 2015 meeting because of the availability of the proposed venue. The BFC discussed various aspects of the proposal and recommended that the Board approve the proposal and authorize the President and CEO, or his designee(s) to take all steps necessary to negotiate, contract and make all necessary disbursements relating to the October 2015 meeting venue.

    • Action – Staff to prepare necessary materials for Board consideration at the next Board meeting scheduled for 30 July 2014.

Published on 24 July 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."