Skip to main content
Resources

Approved Executive Committee Resolutions | Meeting of the Board Executive Committee

  1. Main Agenda:
    1. Officer Compensation
    2. President and CEO FY17 SR2 At-Risk Compensation
    3. Ombudsman FY17 At-Risk Compensation

 

  1. Main Agenda:

    1. Officer Compensation

      [CONFIDENTIAL – PERSONNEL EMPLOYMENT MATTER]

    2. President and CEO FY17 SR2 At-Risk Compensation

      Whereas, each Board member has confirmed that he/she does not have a conflict of interest with respect to establishing the amount of payment for the President and CEO's FY17 SR2 at-risk compensation payment.

      Whereas, the Compensation Committee recommended that the Board approve payment to the President and CEO for his FY17 SR2 at-risk compensation component.

      Resolved (2017.06.29.05), the Board hereby approves a payment to the President and CEO for his FY17 SR2 at-risk compensation component.

      Rationale for Resolution 2017.06.29.05

      When the President and CEO was hired, he was offered a base salary, plus an at-risk component of his compensation package. This same structure exists today. Consistent with all ICANN staff members, the President and CEO is to be evaluated against specific goals.

      After the conclusion of FY17 SR2, the President and CEO provided to the Compensation Committee his self-assessment of his performance for FY17 SR2. After they reviewed and considered that self-assessment, the Compensation Committee recommended that the Board approve the President and CEO's at-risk compensation for the second scoring period of FY17 (16 November 2016 through 15 May 2017), and the Board agrees with that recommendation.

      While this will have a fiscal impact on ICANN, it is an impact that was contemplated in the FY17 budget. This decision will not have an impact on the security, stability or resiliency of the domain name system.

      This is an Organizational Administrative Function that does not require public comment.

    3. Ombudsman FY17 At-Risk Compensation

      Whereas, the Compensation Committee recommended that the Board approve payment to the Ombudsman of his FY17 at-risk compensation.

      Resolved (2017.06.29.06), the Board hereby approves a payment to the Ombudsman of his FY17 at-risk compensation component.

      Rationale for Resolution 2017.06.29.06

      Annually the Ombudsman has an opportunity to earn a portion of his compensation based on specific performance goals set by the Board, through the Compensation Committee. This not only provides incentive for the Ombudsman to perform above and beyond his regular duties, but also leads to regular touch points between the Ombudsman and Board members during the year to help ensure that the Ombudsman is achieving his goals and serving the needs of the ICANN community.

      Scoring of the Ombudsman's objectives results from both the Ombudsman self-assessment, as well as review by the Compensation Committee, with a recommendation to the Board.

      Scoring the Ombudsman's annual performance objectives is in furtherance of the goals of ICANN and helps increase the Ombudsman's service to the ICANN community. While there is a fiscal impact from the results of the scoring, that impact is already accounted for in the annual budget. This action will have no impact on the security, stability or resiliency of the domain name system.

      This is an Organizational Administrative Function that does not require public comment.

Published on 3 July 2017

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