Skip to main content

Minutes | Board Finance Committee (BFC)

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

Apologies: Bruno Lanvin and Mike Silber

Other Board member Attendees: Steve Crocker

Staff Attendees: Susanna Bennett (Chief Operating Officer), Megan Bishop (Board Support Coordinator), Xavier Calvez (Chief Financial Officer), John Jeffrey (General Counsel and Secretary), and Amy Stathos (Deputy General Counsel)

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

  1. SO/AC Additional Budget Request: Staff presented a list of all of the SO/AC additional budget requests and the results of the Steering committee recommendation in response to those requests. Staff explained that the executives on the Steering Committee who review, evaluate and make recommendations on the additional requests are executives covering the areas where the requests are focused, in particular policy and outreach. Staff further explained that some of the recommendations on certain requests are addressed by indicating that the request should be presented through the Community Regional Outreach Pilot Program (CROPP), which was initiated last year, was well received and will be in place again this year. Staff noted that because SOs and ACs were not sure if the CROPP was going to be conducted again this year, they made the requests through the additional request process. Since the CROPP is in place, it is likely that the groups will recognize that many of the requests belong within the CROPP process, although it was mentioned that the CROPP may not be appropriately used for some of the requests.
    • Actions:
      • Staff to follow up on a few of the requests to gather additional information and report to the BFC on 28 April 2014, to the extent possible.
      • Staff to obtain BFC's suggestions on evaluation criteria for SSAC and RSSAC support funding requests.
  2. Revenue Sensitivity Analysis: Staff presented a report showing the various scenarios that were evaluated and considered in estimating revenue on transactional fees for FY15.
    • Action: Staff to continue to monitor over time.

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"""" is not an IDN."