Skip to main content

Minutes | Board Finance Committee (BFC) Meeting

Published 25 June 2016

BFC Attendees: Cherine Chalaby (Co-Chair), Ron da Silva, Chris Disspain, Asha Hemrajani (Co-Chair), Markus Kummer and George Sadowsky

ICANN Executive and Staff member Attendees: Xavier Calvez (Chief Financial Officer), Melissa King (VP, Board Operations), Becky Nash (VP, Finance), Taryn Presley (Sr. Manager, FP&A), Wendy Profit (Board Operations Specialist), and Amy Stathos (Deputy General Counsel)

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

  1. IANA Stewardship Transition Project Costs – The BFC discussed the actual and projected costs associated with the IANA Stewardship Transition and the work of the Project Costs Support Team (PCST). The PCST was established in March 2016 and tasked with determining a more specific estimate of costs on the IANA Stewardship Transition for the remainder of FY16 and for FY17. The PCST has been working diligently and currently estimates expenditures of US$8.8 million for FY17, which includes implementation of Workstream 1 proposal, development of Workstream 2 proposal, and Workstream 2 Bylaws drafting (noting that some or potentially all of the estimate attributable to WS2 Bylaws drafting may carry over to FY18, depending on when the drafting begins). The BFC reviewed the breakdown of the PCST's estimate of costs and agreed that US$8.8 million will be incorporated into the FY17 budget for IANA Stewardship Transition/Implementation costs. The total estimated costs for the IANA Stewardship Transition from FY15 through FY17 is approximately US$37 million. The BFC also discussed proposed communication from the PCST to the CCWG co-chairs conveying suggestions regarding the use and procurement of legal services for FY17 related to the transition.

    • Action:

      • Staff to provide further description regarding the breakdown of the PCST's estimate of IANA Stewardship Transition/Implementation costs for FY17.

  2. FY17 Operating Plan & Budget and Five-Year Operating Plan Update – The BFC discussed the status and schedule for finalizing the FY17 Operating Plan & Budget and the Five-Year Operating Plan Update. The public comment period ended on 30 April 2016, with more than 150 comments submitted. Staff and Board members held community calls with various SOs and ACs regarding the comments submitted by each. The Report of Public Comments was published on 6 June 2016. In consultation with the BFC, the FY17 Operating Plan & Budget and the Five-Year Operating Plan was updated following consideration of public comments. The BFC reviewed the finalized documents and agreed to recommend that the Board approve the updated FY17 Operating Plan & Budget and the Five-Year Operating Plan.

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