Skip to main content
Resources

Minutes | Board Finance Committee (BFC) Meeting

BFC Attendees: Maarten Botterman, Ron da Silva (Chair), Chris Disspain, and Khaled Koubaa, George Sadowsky

Other Board Member Attendees: Cherine Chalaby and Lousewies van der Laan

Invited Observers: Merike Kaeo

ICANN Org Attendees: Susanna Bennett (SVP, Chief Operating Oficer), Michelle Bright (Board Content Coordination Director), Xavier Calvez (SVP, Chief Financial Officer), Franco Carrasco (Board Operations Specialist), Aaron Jimenez (Board Operations Sr. Coordinator), Vinciane Koenigsfeld (Director, Board Operations), Elizabeth Le (Associate General Counsel), Becky Nash (VP Finance), Wendy Profit (Manager, Board Operations), and Amy Stathos (Deputy General Counsel)


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

  1. Reserve Fund Replenishment Strategy– The BFC continued its discussion on the Reserve Fund Replenishment Strategy. The BFC discussed the components that were proposed and that were put out for the public comment, including contribution from excess operating expenses, auction proceeds and remaining new gTLD funds. The Committee also reviewed the principles under which the Reserve Fund should be replenished. The Committee discussed the importance of operational efficiency as fundamental with respect to the contribution from excess operating expenses, and what is a reasonable amount while ensuring that ICANN will be able to fulfill its Mission to provide the community with the strongest support from the organization. The Committee also debated numerous aspects of utilizing auction proceeds and remaining New gTLD Program funds to replenish the reserve Fund, and agreed to recommend some options for the Board's consideration.
    • Action:
      • ICANN org to prepare materials for Board consideration.

Published on 26 November 2018

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