Skip to main content
Resources

Minutes | Special Meeting of the ICANN Board

A Special Meeting of the ICANN Board of Directors was held telephonically on 28 July 2015 at 22:00 UTC.

Steve Crocker, Chair, promptly called the meeting to order.

In addition to the Chair, the following Directors participated in all or part of the meeting: Rinalia Abdul Rahim, Fadi Chehadé (President and CEO), Chris Disspain, Asha Hemrajani, Markus Kummer, Bruno Lanvin, Gonzalo Navarro, Ray Plzak, George Sadowsky, Mike Silber, and Bruce Tonkin (Vice Chair).

The following Board Liaisons participated in all or part of the meeting: Ram Mohan (SSAC Liaison), Jonne Soininen (IETF Liaison), and Suzanne Woolf (RSSAC Liaison).

Cherine Chalaby, Wolfgang Kleinwächter, Erika Mann, Thomas Schneider (GAC Liaison), and Kuo-Wei Wu sent apologies.

Board Member Elect: Ron da Silva (observing).

Secretary: John Jeffrey (General Counsel and Secretary).

ICANN Executives and Staff in attendance for all or part of the meeting: Megan Bishop (Board Support Coordinator); Michelle Bright (Board Support Content Manager); Samantha Eisner (Associate General Counsel); Allen Grogan (Chief Contract Compliance Officer); Larisa Gurnick (Director, Strategic Initiatives); Vinciane Koenigsfeld (Board Support Content Manager); Denise Michel (VP, Strategic Initiatives & Advisor to President); Olof Nordling (Senior Director, GAC Relations); Erika Randall (Senior Counsel); Ashwin Rangan (Chief Innovation & Information Officer); Amy Stathos (Deputy General Counsel); and Theresa Swinehart (Sr. Advisor to the President on Strategy).

  1. Consent Agenda:
    1. Structural Improvements Committee Charter Revisions
    2. Board IDN Working Group
    3. GNSO Policy & Implementation Recommendations – Proposed Changes to ICANN Bylaws
    4. Composition and Scope of the Board Working Group on Registration Data Directory Services (BWG-RDS)
    5. Update to Contracting and Disbursement Policy
  2. Main Agenda:
    1. Approval of Board Meeting Minutes
    2. Reconsideration Request 15-7
    3. Proposed Schedule and Process / Operational Improvements for AoC and Organizational Reviews
    4. Process for Requesting GAC Advice
  3. Confidential Session:
    1. President and CEO FY15 SR2 At-Risk Compensation
    2. Ombudsman FY15 At-Risk Compensation
    3. Officer Compensation

 

  1. Consent Agenda:

    The Chair introduced the items on the consent agenda and called for a vote. The Board then took the following action:

    Resolved, the following resolutions in this Consent Agenda are approved:

    1. Structural Improvements Committee Charter Revisions

      Whereas, the Structural Improvements Committee is responsible for review and oversight of policies relating to ICANN's ongoing organizational review process mandated by Article IV, Section 4 of ICANN's Bylaws.

      Whereas, the Structural Improvements Committee has proposed revisions to its name and current charter, with which the Board Governance Committee agrees.

      Resolved (2015.07.28.01), that the Board approves the proposed revisions to the charter of the Structural Improvements Committee, including the change in the name to Organizational Effectiveness Committee.

      Rationale for Resolution 2015.07.28.01

      Why the Board is addressing the issue?

      The Board is addressing this issue because of the requirement that the Board approve revisions to charters of Board Committees.

      What is the proposal being considered?

      The Structural Improvements Committee is proposing the following changes:

      1. Change of the name to "Organizational Effectiveness Committee" – The proposed change is intended to provide ICANN community with more clarity about the purpose and focus of organizational reviews and how the reviews will be conducted.
      2. Clarification of the purpose of the Committee and of reviews – This proposed revision incorporates into the charter an important aspect of reviews – the assessment of how effectively the organization follows its policies, procedures and implements means of continuous improvement.
      3. Adding concept of Review Framework – The documentation of a policy and procedures Framework will facilitate conducting reviews in a predictable, consistent and efficient manner, based on lessons learned from recent reviews and the applicable portions of ATRT2 recommendations on improving effectiveness of such reviews. The anticipated implementation of a Review Framework is designed to align all reviews to have consistently applied and efficiency-focused processes and oversight. The proposed changes are in alignment with process and operational improvements posted for public comment in response to community's workload concerns.
      4. Clarification of the Committee's oversight responsibility – This change to clarify the Committee's oversight responsibility for the work of independent consultants and the implementation of review recommendations, including regular reporting to the Board on implementation status and Committee activities. Specifically, the appointment of independent consultants should follow the recent practice whereby staff conduct the competitive bidding process and recommend a finalist based on specific criteria and scoring. The Committee then confirms the staff recommendation (or discusses with staff an alternative). While the language in the 2009 Charter suggested that the Committee should recommend independent reviewer engagements for Board approval, this has instead been handled as a routine engagement that does not require full Board action. The recommended change of aligning the Charter with the recent practice of Committee's confirmation of the independent reviewer selection will result in a more efficient process, in line with focusing the Board's work on strategic rather than operational and routine matters.
      5. Composition of the Committee and other procedural matters – Proposals include increasing maximum number of members, and well as adding more clarity in relation to conduct of meetings.

      Which stakeholders or others were consulted?

      Based on the requirements of the Charter of the Board Governance Committee the Structural Improvements Committee consulted with the Board Governance Committee. A formal public comment process is not required for this action.

      What significant materials did the Board review?

      The Board reviewed the proposed revisions to the 2009 Structural Improvements Committee charter. See Reference Materials, Exhibit A.

      Are there positive or negative community impacts?

      The proposed revisions are intended to provide further clarity and align all reviews to have consistently applied and efficiency-focused processes and oversight. These developments are expected to have a positive impact on the community.

      Are there fiscal impacts or ramifications on ICANN (strategic plan, operating plan, and budget); the community; and/or the public?

      There will be no fiscal impact or adverse ramifications on ICANN's strategic and operating plans from the proposed changes. The name change will not have a significant impact on governance documents, with most changes impacting web pages and documents currently being updated.

      Are there any security, stability or resiliency issues relating to the DNS?

      There are no security, stability or resiliency issues relating to the DNS as the result of this action.

    2. Board IDN Working Group

      Whereas, the Board IDN Variants Working Group noted that the working group needs to be able to address IDN-related issues that are beyond those limited to variants, and has proposed that the scope of the working group be expanded to include all IDN-related issues.

      Whereas, the BGC considered the issues raised by the Board IDN Variants Working Group (BV-WG) and the proposed charter reflecting the expanded scope of the working group and recommended that: (a) the name of the BV-WG be changed to the Board IDN Working Group; (b) the scope of the working group be expanded to include other IDN issues; and (c) the proposed charter be approved.

      Resolved (2015.07.28.02), the Board hereby approves changing the name of the Board IDN Variants Working Group to the Board IDN Working Group, expands the scope of the Board IDN Working Group to include other IDN-related issues (as reflected in the Charter), approves the proposed Charter of the Board IDN Working Group, and identifies the following members of the Board IDN Working Group: Rinalia Abdul Rahim, Ram Mohan (Chair), Jonne Soininen, Kuo-Wei Wu, and Suzanne Woolf.

      Rationale for Resolution 2015.07.28.02

      The Board IDN Variants Working Group (BV-WG) was initially created by the Board in December 2010 (see https://www.icann.org/resources/board-material/resolutions-2010-12-10-en#7), and the initial membership was established in March 2011 (See https://www.icann.org/resources/board-material/resolutions-2011-03-18-en#1.5). At that time, the purpose of the BV-WG was to oversee and track the IDN Variant Issues Project. Since that time, it has become clear that there are numerous issues related to IDNs that are beyond those specific to variants and should be addressed by a working group. This has become especially applicable given the continued registrations of new gTLD IDNs. In its recent meetings, the BV-WG has noted the frequency and need to address various IDN-related issues beyond those limited to variants. As a result, the BV-WG is proposing that the scope of this working group be expanded to include other IDN-related issues. Specifically, the BV-WG proposed that the name of the working group be changed to the Board IDN Working Group and provided the following proposed charter language regarding the purpose and scope of the Board IDN Working Group:

      To provide oversight on efforts related to work on the planning, design, development and implementation of Internationalized Domain Names (IDNs) in the context of both generic top-level domains (gTLDs) and country code TLDs (ccTLDs), including but not limited to the analysis of feasibility and introduction of IDN TLDs in a manner that ensures the continued security and stability of the Internet.

      The working group will also provide oversight on aspects of Universal Acceptance specifically related to IDN TLDs.

      The BGC reviewed the proposal and proposed charter language, and considered the importance of having Board involvement in various IDN-related issues in order to capitalize on the technical expertise and varied skill sets of those on the Board. As a result, the BGC recommended that the working group be re-named the Board IDN Working Group, the scope of the working group be expanded to include other IDN issues, and the proposed Charter be accepted.

      Adopting the BGC's recommendation has no direct financial impact on ICANN and is likely to positively impact the systemic security, stability and resiliency of the domain name system.

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

    3. GNSO Policy & Implementation Recommendations – Proposed Changes to ICANN Bylaws

      Whereas, On 17 July 2013, the GNSO Council approved the charter for a GNSO non-PDP Policy and Implementation Working Group (http://gnso.icann.org/en/council/resolutions#201307) tasked to provide the GNSO Council with a set of recommendations on:

      1. A set of principles that would underpin any GNSO policy and implementation related discussions, taking into account existing GNSO Operating Procedures.
      2. A process for developing gTLD policy, perhaps in the form of "Policy Guidance", including criteria for when it would be appropriate to use such a process (for developing policy other than "Consensus Policy") instead of a GNSO Policy Development Process.
      3. A framework for implementation related discussions associated with GNSO Policy Recommendations.
      4. Criteria to be used to determine when an action should be addressed by a policy process and when it should be considered implementation.
      5. Further guidance on how GNSO Implementation Review Teams, as defined in the PDP Manual, are expected to function and operate.

      Whereas, the GNSO Policy and Implementation Working Group published its Initial Recommendations Report for public comment on 19 January 2015 (see https://www.icann.org/public-comments/policy-implementation-2015-01-19-en).

      Whereas, the GNSO Policy and Implementation Working Group reviewed the input received (see public comment review tool [DOC, 267 KB]) and updated the report accordingly.

      Whereas, the Final Recommendations Report (see http://gnso.icann.org/en/drafts/policy-implementation-recommendations-01jun15-en.pdf [PDF, 1.53 MB]), which contains a number of recommendations that will require changes to the ICANN Bylaws, has obtained the full consensus support of the GNSO Policy and Implementation Working. The Final Recommendations Report was submitted to the GNSO Council for its consideration on 2 June 2015.

      Whereas, the GNSO Council unanimously adopted the recommendations during its meeting on 24 June 2015 (see http://gnso.icann.org/en/council/resolutions#20150624-2).

      Whereas, any changes to the ICANN Bylaws may be adopted only upon action by a two-thirds (2/3) vote of all members of the Board.

      Resolved (2015.07.28.03), the President and CEO, or his designee(s), is directed to post for public comment for a period of at least 40 days revised Bylaws reflecting the addition of a GNSO Guidance Process and a GNSO Expedited Policy Development Process. After taking public comments into account, the Board will consider the proposed changes for adoption.

      Rationale for Resolution 2015.07.28.03

      The action being approved today is to direct the ICANN President and CEO, or his designee, to initiate a public comment period on potential changes to the ICANN Bylaws to implement certain recommendations resulting from the GNSO's non-PDP Policy and Implementation Working Group. The Board's action is a first step to consider the unanimous approval by the GNSO Council of the recommendations of the Policy & Implementation Working Group.

      There is no anticipated fiscal impact from this decision, which would initiate the opening of public comments, but the fiscal impacts of implementing the GNSO Council's recommendations from the non-PDP Policy and Implementation Working Group will be further analyzed if adopted. Approval of the resolution will not impact the security, stability and resiliency of the domain name. The posting of the proposed Bylaws for public comment is an Organizational Administrative Action not requiring public comment.

    4. Composition and Scope of the Board Working Group on Registration Data Directory Services (BWG-RDS)

      Whereas, under the Affirmation of Commitments (AoC), ICANN is committed to conducting periodic reviews of the effectiveness of the WHOIS policy and its implementation.

      Whereas, in 2012, the Board adopted a two-pronged approach to address the recommendations of the first WHOIS Review Team, calling for ICANN to (i) continue to fully enforce existing consensus policy and contractual conditions relating to WHOIS, and (ii) create an expert working group to determine the fundamental purpose and objectives of collecting, maintaining and providing access to gTLD registration data, to serve as a foundation for a Board-initiated GNSO policy development process (PDP).

      Whereas, upon publication of the EWG's Final Report [PDF, 5.12 MB] in June 2014, an informal group of Generic Names Supporting Organization (GNSO) Councilors and ICANN Board members collaborated to propose a Process Framework [PDF, 829 KB] for structuring a GNSO Policy Development Process (PDP) to successfully address this challenging issue.

      On 26 April 2015, the Board adopted that Process Framework [PDF, 829 KB] and reaffirmed its 2012 request for a Board-initiated PDP to define the purpose of collecting, maintaining and providing access to gTLD registration data, and to consider safeguards for protecting data, using the recommendations in the EWG's Final Report as an input to, and, if appropriate as, the foundation for a new gTLD policy.

      Whereas, the Board also approved the formation of a group of Board members that will (i) liaise with the GNSO on the policy development process to examine the EWG's recommended model and propose policies to support the creation of the next generation registration directory services, and (ii) oversee the implementation of the remaining projects arising from the Action Plan [PDF, 119 KB] adopted by the Board in response to the first WHOIS Review Team's recommendations.

      Whereas, the Board Governance Committee proposed a Charter for the Board Working Group on Registration Data Directory Services (BWG-RDS) and identified a recommended slate of Board members to do this work.

      Whereas, the BGC has recommended that the following Board members be appointed as members of the BWG-RDS: Steve Crocker, Bruce Tonkin, Erika Mann, Rinalia Abdul Rahim, Markus Kummer, Cherine Chalaby, and Chris Disspain, and the ICANN CEO as an ex-officio member. Given that the current ICANN CEO has announced his resignation from ICANN, the BGC also recommended that the CEO role on the BWG-RDS not be filled until the next CEO takes office.

      Resolved (2015.07.28.04), the Board hereby adopts the Charter of the Board Working Group on Registration Data Directory Services.

      Resolved (2015.07.28.05), the Board hereby names the following Board members to serve on the BWG-RDS: Steve Crocker, Bruce Tonkin, Erika Mann, Rinalia Abdul Rahim, Markus Kummer, Cherine Chalaby, and Chris Disspain. The Board also names an ex-officio role on the BWG-RDS for ICANN's CEO, however that role will not become operative until the next ICANN CEO takes office.

      Rationale for Resolutions 2015.07.28.04 – 2015.07.28.05

      Why is the Board addressing the issue?

      This resolution continues the Board's attention to the implementation of the Action Plan [PDF, 119 KB] adopted by the Board in response to the WHOIS Review Team's recommendations [PDF, 5.12 MB]. It also is a continuation of the Board's 26 April 2015 resolution establishing a Board group to address specific issues related to registration data directory services (BWG-RDS). That resolution indicated that the membership of the Board Working Group would be addressed by the Board Governance Committee (BGC). As contemplated by the Board's 26 April 2015 resolution, the BGC considered the membership of the BWG-RDS and made a recommendation to the Board. The Board's action today adopts the recommendation of the BGC concerning the composition of the BWG-RDS. In addition, the Board is adopting the Charter recommended by the BGC to clarify the scope of the work to be undertaken by the BWG-RDS.

      What is the proposal being considered?

      Under the Affirmation of Commitments (AoC), ICANN is committed to enforcing its existing policy relating to WHOIS (subject to applicable laws), which "requires that ICANN implement measures to maintain timely, unrestricted and public access to accurate and complete WHOIS information…." The AoC obligates ICANN to organize no less frequently than every three years a community review of WHOIS policy and its implementation to assess the extent to which WHOIS policy is effective and its implementation meets the legitimate needs of law enforcement and promotes consumer trust. Under this timeline, the second WHOIS Review Team is to be convened in late 2015.

      In 2012, the first WHOIS Review Team recommended in its Final Report that the Board create a committee to support WHOIS as a strategic priority and ensure the implementation of its recommendations to improve the effectiveness of the WHOIS policy. In response, the Board adopted a two-prong approach that simultaneously directed ICANN to (1) implement improvements to the current WHOIS system based on the Action Plan [PDF, 119 KB] that was based on the recommendations of the WHOIS Review Team, and (2) launch a new effort, achieved through the creation of the Expert Working Group, to focus on the purpose and provision of gTLD directory services, to serve as the foundation of a Board-initiated GNSO policy development process (PDP).

      The effect of the Board's action today, establishing the composition of the BWG-RDS and adopting its Charter, will allow the BWG-RDS to commence: (1) liaising with the GNSO as it conducts the Board-directed GNSO policy development process to examine the EWG's recommended model for the next generation registration directory services, and (2) oversee the implementation of the remaining projects arising from the AoC WHOIS Review Team recommendations Action Plan [PDF, 119 KB], and provide oversight and guidance related to the activities of the second WHOIS Review Team when convened.

      What factors did the Board find to be significant?

      The Board believes that the importance of the WHOIS issue, along with the breadth and scope of the many WHOIS activities currently under way, support the need for a designated group of Board members dedicated to overseeing the entire WHOIS Program, including working with the community on the GNSO PDP, and any future transition to a next generation registration directory services that may emerge following the GNSO PDP. Community members participating in the informal Board-GNSO Council effort to develop the Board-approved framework [PDF, 612 KB] for the PDP also requested the Board's continued involvement in this effort.

      What significant materials did the Board review?

      The Board reviewed the Charter proposed by the BGC, and the Briefing Papers submitted by Staff.

      Are there fiscal impacts or ramifications on ICANN (strategic plan, operating plan, or budget)?

      The creation of the BWC-RDS and conduct of its activities is not expected to require additional resources beyond those included in the Board-approved FY16 Operating Plan and Budget.

      Are there any security, stability or resiliency issues relating to the DNS?

      This action is not expected to have an immediate impact on the security, stability or resiliency of the DNS, though the outcomes of this work may result in positive impacts.

      Is public comment required prior to Board action?

      As this is a continuation of prior Board actions, this is an Organizational Administrative Action for which public comment is not necessary prior to adoption.

    5. Update to Contracting and Disbursement Policy

      Whereas, the Board Finance Committee has reviewed the current Contracting and Disbursement Policy and recommended that it be revised to define the signature authority for bank transaction purposes, in addition to the approval authority already defined in the current document.

      Whereas, the Board agrees with Board Finance Committee.

      Resolved (2015.07.28.06), the Board adopts the ICANN Contracting and Disbursement Policy as reflected at <http://www.icann.org/en/about/financials/signing-authority>, which replaces the ICANN Contracting and Disbursement Policy last revised on 16 March 2012.

      Rationale for Resolution 2015.07.28.06

      The Contracting and Disbursement policy defines the approval authority granted to the officers of the company. The previous version of the policy did not specify, in addition to the approval authority, the signature authority for bank transactions. In an effort to ensure adequate documentation for operational purposes, defining the signature authority facilitates the processing of the transactions by financial institutions. The suggested language additions include an added level of control by requiring that bank transactions in excess of $1 million be authorized by two officers, in addition to the approval authority requirements already in place of approval by two or three officers, or by the Board for transactions in excess of $50,000, $100,000 or $500,000 respectively.

      This decision that does not have any impact on the Strategic and Operating plans, or on the budget of ICANN, other than increasing the control over signature authority. This decision will have no impact on the security, stability and resiliency of the domain name system.

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

      All members of the Board present voted in favor of Resolutions 2015.07.28.01, 2015.07.28.02, 2015.07.28.03, 2015.07.28.04, 2015.07.28.05, and 2015.07.28.06. Cherine Chalaby, Wolfgang Kleinwächter, Erika Mann, Thomas Schneider, and Kuo-Wei Wu were unavailable to vote on the Resolutions. The Resolutions carried.

  2. Main Agenda:

    1. Approval of Board Meeting Minutes

      The Chair introduced the agenda item, and a member of the Board suggested additional language to be included in the 25 June 2015 Minutes concerning the Approval of Payment of Certain CWG-Stewardship Related Legal Costs. The Minutes were updated to take note of the mechanism put in place by the chairs of both the CWG and the CCWG to certify or vet questions before they are sent to legal counsel.

      The Board took the following action:

      Resolved (2015.07.28.07), the Board approves the minutes of the 21 June and 25 June 2015 Meetings of the ICANN Board.

      All members of the Board present voted in favor of Resolution 2015.07.28.07. Cherine Chalaby, Wolfgang Kleinwächter, Erika Mann, Thomas Schneider, and Kuo-Wei Wu were unavailable to vote on the Resolution. The Resolution carried.

    2. Reconsideration Request 15-7

      Ram Mohan recused himself from the discussion, citing potential or perceived conflicts of interest on the matter. The Chair provided some background on the underlying facts of Reconsideration Request 15-7 ("Request"). The Request involved the Board's adoption of the findings contained in the IRP Panel's Final Declaration in Booking.com v. ICANN. Staff provided a summary to the Board regarding the matters that were presented to the IRP Panel and the Board's previous consideration in April 2015 of the IRP Panel's Final Declaration.

      The Board discussed the recommendation of the Board Governance Committee (BGC) concerning the Request, which was to deny the Request because the requesters did not state proper grounds for reconsideration. Board members expressed varying views about whether to accept or reject the BGC's recommendation, and discussed the potential outcomes of taking a particular action.

      Some Board members noted that the matters in the Request had been before the Board, NGPC, and BGC through various accountability measures on various occasions, and there was not material new information for the Board to consider to support the grounds for Reconsideration.

      Other members of the Board commented that although the BGC's recommendation is reasonable given the current Reconsideration Request process, they did not intend to support the proposed Board resolution in order to highlight a concern about the limited focus of the Reconsideration Request process. These Board members suggested that the existing Reconsideration Request process does not deal with situations where an accepted process leads to unreasonable results. George Sadowsky noted that the hotes/hoteis expert determination should be used to as an example of the deficiency in the Reconsideration Request process.

      The Board also discussed the New gTLD Program string similarity review process, which was an underlying matter in the IRP and the Request. The Board noted that the IRP Panel suggested that string similarity process be reviewed for the next round, which ICANN has agreed to do as part of the New gTLD review process. A member of the Board noted that the issue of string similarity review would be considered as part of the review process of the current round of the New gTLD Program, and would also be part of community discussions about subsequent rounds of the New gTLD Program.

      Some Board members discussed the IRP Panel's suggestion that ICANN, ". . . in the exercise of its authority under Section 5.1 (Module 5-4) of the Guidebook (which it may choose to exercise at any time, in its discretion) to consider whether, notwithstanding the result of the string similarity review of .hotels and .hoteis, approval of both of Booking.com's and Despegar's proposed strings would be in the best interest of the Internet community." (IRP Final Declaration [PDF, 4.76 MB] at paragraph 154.) Chris Disspain clarified that consideration of the IRP Panel's suggestion is beyond the scope of the reconsideration request before the Board. The President and CEO further pointed out that the issue currently before the Board is whether the Board violated its Bylaws or Articles of Incorporation by accepting the Booking.com Final Declaration.

      After discussion, the Board took the following action:

      Whereas, Booking.com B.V and Travel Reservations SRL (formerly Despegar Online SRL) (collectively, "Requesters") filed Reconsideration Request 15-7 seeking reconsideration of the ICANN Board's passing of Resolutions 2015.4.04.26.14, 2015.4.04.26.15, and 2015.04.26.16, in which the Board adopted the findings contained in the IRP Panel's Final Declaration in Booking.com v. ICANN, ICDR Case No. 50-20-1400-0247, and directed the President and CEO to move forward with processing the .hotels/.hoteis contention set.

      Whereas, the BGC thoroughly considered the issues raised in Reconsideration Request 15-7.

      Whereas, the BGC recommended that Reconsideration Request 15-7 be denied because the Requesters have not stated proper grounds for reconsideration, and the Board agrees.

      Resolved (2015.07.28.08), the Board adopts the BGC Recommendation on Reconsideration Request 15-7, which can be found at https://www.icann.org/resources/pages/reconsideration-15-7-booking-bv-travel-reservations-srl-2015-05-15-en.

      Nine members of the Board present voted in favor of Resolution 2015.07.28.08. Asha Hemrajani abstained from voting. Ray Plzak and George Sadowsky voted against Resolution 2015.07.28.08. Cherine Chalaby, Wolfgang Kleinwächter, Erika Mann, Thomas Schneider, and Kuo-Wei Wu were unavailable to vote on the Resolution. The Resolution carried.

      Rationale for Resolution 2015.07.28.08

      1. Brief Summary

        Requester Booking.com B.V. ("Booking.com") submitted a standard application for .hotels, and Requester Travel Reservations SRL ("TRS") submitted a standard application for .hoteis (collectively, the "Applications"). On 26 February 2013, pursuant to a process called string similarity review ("SSR"), an expert string similarity review panel ("SSR Panel") determined that the .hotels and .hoteis strings were visually confusingly similar. Pursuant to applicable procedure, the Applications were then placed into a contention set.

        Requester Booking.com challenged the establishment of the contention set in a prior reconsideration request (Reconsideration Request 13-5), which was denied on 10 September 2013. Booking.com then initiated an Independent Review Process ("IRP") on 18 March 2014, challenging the denial of Reconsideration Request 13-5 and ICANN's adoption of the SSR Panel's determination that the .hotels and .hoteis strings were visually confusingly similar. In its Final Declaration, the Booking.com IRP Panel unanimously rejected Booking.com's claims, determining that Booking.com's challenge to the decision of an independent evaluator did not challenge Board action and, moreover, that the ICANN Board had no obligation to review or otherwise intervene in the conclusions reached by third-party expert evaluators. At its 26 April 2015 meeting, the ICANN Board approved Resolutions 2015.4.04.26.14, 2015.4.04.26.15, and 2015.04.26.16 ("Resolutions"), thereby adopting the findings contained in the Booking.com v. ICANN, ICDR Case No. 50-20-1400-0247, Final Declaration and directing the President and CEO, or his designee(s), to move forward with processing the contention set.

        On 13 May 2015, the Requesters filed the instant Reconsideration Request 15-7, seeking reconsideration of ICANN's approval of the Resolutions. The Requesters argue that reconsideration is warranted because, in approving the Resolutions, the Board: (a) contravened certain of ICANN's "goals" or core values; (b) failed to consider material information; (c) relied on inaccurate information; and (d) violated unspecified provisions of ICANN's Articles of Incorporation, Bylaws, and Affirmation of Commitments.

        At its core, Request 15-7 is an attempt to appeal (only) those portions of the Booking.com Final Declaration with which the Requesters disagree. The Requesters' claims do not support reconsideration because they do not establish that the Board failed to consider material information, or considered false or inaccurate material information, in approving the Resolutions. Moreover, the Requester has not demonstrated that it has been materially adversely affected by the adoption of the Resolutions. Accordingly, the BGC recommends that Request 15-7 be denied.

      2. Facts

        The BGC Recommendation on Reconsideration Request 15-7, which sets forth in detail the Facts relevant to this matter, is hereby incorporated by reference and shall be deemed a part of this Rationale. The BGC Recommendation on Reconsideration Request 15-7 is available at https://www.icann.org/resources/pages/reconsideration-15-7-booking-bv-travel-reservations-srl-2015-05-15-en, and is attached as Exhibit B to the Reference Materials.

      3. Issues

        In view of the claims set forth in Request 15-7, the issues for reconsideration seem to be:

        1. Whether reconsideration is warranted because:

          1. The approval of the Resolutions purportedly contravened what the Requesters contend are ICANN's "goals of increasing competition" and "making the domain name system more global and understandable through the use of local languages" (Request § 7, Pg. 3);

          2. The Board failed to consider material information in approving the Resolutions;

          3. The Board relied on false or inaccurate information in approving the Resolutions; or

          4. The Resolutions violate unspecified provisions of ICANN's Articles of Incorporation, Bylaws, and Affirmation of Commitments; and

        2. Whether the Requesters have demonstrated that they have suffered material adverse harm due to the approval of the Resolutions.

      4. The Relevant Standards for Evaluating Reconsideration Requests

        The BGC Recommendation on Reconsideration Request 15-7, which sets forth the Relevant Standards for Evaluating Reconsideration Requests, is hereby incorporated by reference and shall be deemed a part of this Rationale. The BGC Recommendation on Reconsideration Request 15-7 is available at https://www.icann.org/resources/pages/reconsideration-15-7-booking-bv-travel-reservations-srl-2015-05-15-en, and is attached as Exhibit B to the Reference Materials.

      5. Analysis and Rationale

        Request 15-7 again challenges the merits of the SSR Panel's determination that the .hotels and .hoteis strings are visually confusingly similar, which resulted in the formation of the .hotels/.hoteis contention set. Booking.com sought to challenge the SSR Panel's decision in Reconsideration Request 13-5 and was unsuccessful. Booking.com tried again in its IRP and was unsuccessful. Now having banded together with contention-set mate and fellow Requester TRS, Booking.com seeks to use the instant Reconsideration Request 15-7 to appeal the Booking.com Final Declaration. Here too, the effort to undermine the SSR Panel's determination is unsuccessful. There is no appeals mechanism to challenge the substance of an expert SSR Panel determination in ICANN's Articles of Incorporation ("Articles"), Bylaws or the Applicant Guidebook.

        The Board notes that the IRP Panel encouraged ICANN, ". . . in the exercise of its authority under Section 5.1 (Module 5-4) of the Guidebook (which it may choose to exercise at any time, in its discretion) to consider whether, notwithstanding the result of the string similarity review of .hotels and .hoteis, approval of both of Booking.com's and Despegar's proposed strings would be in the best interest of the Internet community." (See https://www.icann.org/en/system/files/files/final-declaration-03mar15-en.pdf [PDF, 4.76 MB] at paragraph 154.) The Board specifically chose to exercise its discretion, considered the IRP Panel's suggestion above, and chose to rely on the experts who determined these two strings should not co-exist in the domain name system. Specifically, in adopting the Guidebook, the Board put the SSR process in place so the experts could decide, in the best interest of the Internet community, what strings should not co-exist in the domain name system because they could cause user confusion. The Board relied on the experts to make the determination that it was in the best interest of the Internet community that .hotels and .hoteis should not co-exist in the domain name system; The Board chose not to second guess the experts.

        Reconsideration of a Board action, the process that Requesters have invoked here, is warranted only where the Board took action without consideration of material information or with reliance upon false or inaccurate information. Here, as the BGC explains in detail in its Recommendation, the Board did not fail to consider material information and did not consider false or inaccurate information in approving the Resolutions. Moreover, the only material adverse harm alleged by either Requester stems from the creation of the contention set, not any Board failure to consider material information or reliance upon false information related to the Resolutions. As a result, the BGC concluded and the Board agrees that reconsideration is not appropriate.

        In short, the Requesters made several claims, none of which support reconsideration. First, the Requesters seem to suggest that the Board somehow failed to consider ICANN's core values in adopting the Resolutions. The Requesters, however, have not presented any facts to support such a suggestion. To the contrary, in passing the Resolutions the Board acted in a manner that was fully consistent with ICANN's core values, including those relating to the promotion of competition where "[f]easible and appropriate," and when "beneficial to the public interest." (Bylaws, Art. IV, §§ 2.5 and 2.6.)

        Second, the Requesters challenge the SSR process in general, which itself is not a Board decision subject to reconsideration. Further, any challenge to inclusion of the SSR process in the Guidebook is long since time-barred.

        Third, the Requesters claim that the Board failed in the following four ways to consider material information in passing the Resolutions: (i) the Board disregarded its discretion to improve the New gTLD Program; (ii) ICANN ignored their requests to discuss their issue; (iii) the Board should have first considered the Requesters' expert report; and (iv) the Board did not consider that it had previously intervened in other decisions. None of these claims withstand scrutiny. As to the first point, the Requesters concede that the Board had discretion to take action. Discretion means that the Board is not required to intervene. In fact, they used their discretion to specifically not intervene and this in no way constitutes a failure to consider material information. As to the second point, among other reasons set forth by the BGC, the staff's decision not to engage in unspecified informal talks with the Requesters does not relate to what information the Board did or did not consider in passing the Resolutions. The Board considered the entirety of the IRP Panel's Declaration, and took the actions specified in the Resolutions. As to the third point, the Requesters' claim that the Board should have considered evidence that Booking.com presented to the IRP Panel shows that Reconsideration Request 15-7 is just an attempt to appeal the merits of the IRP Panel's decision and another of several attempts to appeal the SSR Panel's determination. Finally, as the Booking.com IRP Panel explained, "the fact that the ICANN Board enjoys [the] discretion [to individually consider an application for a New gTLD] and may choose to exercise it at any time does not mean that it is bound to exercise it, let alone at the time and in the manner demanded by [claimant]. (See Booking.com Final Determination ¶ 138.) Furthermore, the fact that the Board may have done that in the past is not material information relevant to the Requesters' circumstances.

        Fourth, the Requesters argue that because the Booking.com IRP Panel was "wrong" in finding that Booking.com's challenges to the SSR process as a whole were time-barred, the Board therefore relied upon false or inaccurate information in approving the Resolutions insofar as they accepted that finding. However, the Requesters' claim is nothing more than an attempt to re-argue the question of whether its IRP claim was time-barred, and does not present any grounds for reconsideration. Simply because the Requesters do not agree with the IRP Panel's Declaration, does not make it false or inaccurate.

        In addition to the above claims, the only material adverse harm alleged by either Requester stems from the creation of the contention set, not any Board failure to consider material information or reliance upon false information related to the Resolutions. Accordingly, reconsideration is not appropriate.

        The full BGC Recommendation on Reconsideration Request 15-7, which sets forth the Analysis and Rationale in detail and with which the Board agrees, is hereby incorporated by reference and shall be deemed a part of this Rationale. The BGC Recommendation on Reconsideration Request 15-7 is available at https://www.icann.org/resources/pages/reconsideration-15-7-booking-bv-travel-reservations-srl-2015-05-15-en, and is attached as Exhibit B to the Reference Materials.

      6. Decision

        The Board had the opportunity to consider all of the materials submitted by or on behalf of the Requesters or that otherwise relate to Reconsideration Request 15-7, including the Requesters' letter date 16 July 2015, after the BGC made its recommendation. Following consideration of all relevant information provided, the Board reviewed and has adopted the BGC's Recommendation on Reconsideration Request 15-7 (https://www.icann.org/en/system/files/files/recommendation-15-7-booking-bv-travel-reservations-srl-20jun15-en.pdf [PDF, 191 KB]), which shall be deemed a part of this Rationale and is attached as Exhibit B to the Reference Materials to the Board Paper on this matter.

        Adopting the BGC's recommendation has no direct financial impact on ICANN and will not negatively impact the systemic security, stability and resiliency of the domain name system.

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

    3. Proposed Schedule and Process / Operational Improvements for AoC and Organizational Reviews

      The Board engaged in a discussion regarding the proposed schedule and process changes for the AoC reviews and organizational reviews required by the Bylaws. The Board discussed the proposed improvements to increase the efficiency and effectiveness of reviews, and some members asked whether the proposed changes would potentially impact the ongoing work of the CCWG on enhancing ICANN's accountability framework recommendations. The Board also discussed the need to engage with NTIA on proposed changes to the AoC review schedule.

      Bruce Tonkin moved and George Sadowsky seconded and the Board then took the following action:

      Whereas, under the Affirmation of Commitments (AoC) and ICANN Bylaws, seven reviews are scheduled to take place in FY2016, in addition to the finalization of the GNSO Review.

      Whereas, the ICANN community expressed concern regarding volunteer workload, its ability to effectively participate in these important accountability mechanisms, and the need to change the Review schedule, and the Accountability & Transparency Review Team (ATRT2) recommendations adopted by the Board called for improvements to the Review process.

      Whereas, the Board desires to meet ICANN's accountability commitments and provide the community relief from the proposed schedule by delaying several of the Organizational Reviews mandated by the Bylaws, delaying and staggering some of the Reviews required under the AoC, and by adopting process and operational improvements to Reviews.

      Whereas, based on public feedback, a proposed revised Reviews schedule and process and operational improvements were posted for public comment and discussed at ICANN53.

      Whereas, in the CCWG on Enhancing ICANN Accountability process, some recommendations are under discussion that are interdependent with the AoC Reviews.

      Resolved (2015.07.28.09), the Board endorses the following schedule for the conduct of upcoming AoC Reviews on or about the following dates: CCT Review to continue as scheduled, with a call for volunteers—October 2015; the second Security, Stability and Resiliency Review—June 2016; the second WHOIS Review—October 2016; and the third Accountability and Transparency Review—July 2017.

      Resolved (2015.07.28.10), the CEO is directed to engage in a dialogue with the NTIA, a signatory to the AoC, regarding the changes to the AoC Review schedule endorsed by the Board.

      Resolved (2015.07.28.11), the Board adopts the following schedule for the conduct of upcoming Bylaws mandated Organizational Reviews on or about the following dates: the second At-Large Review—April 2016; the second review of the Nominating Committee—February 2017; the second review of the Root Server System Advisory Committee – April 2017; and the second review of Security & Stability Advisory Committee—June 2017.

      Resolved (2015.07.28.12), the Board acknowledges that the work of the CCWG on Enhancing Accountability may impact ICANN Reviews, and that adopted Accountability Framework recommendations will be factored into the Reviews timeline and processes.

      Resolved (2015.07.28.13), the Board Governance Committee is requested to determine which committee or subgroup of the Board should be responsible for oversight of AoC Reviews, in parallel to Structural Improvements Committee's responsibility for overseeing Organizational Reviews.

      Resolved (2015.07.28.14), the Board endorses the proposed process and operational improvements that were posted for public comment and are designed to simplify and increase the effectiveness of Reviews, and the Board acknowledges that the Structural Improvements Committee is finalizing "Organizational Reviews Policies, Procedures and Guidelines," following appropriate public consultation.

      All members of the Board present voted in favor of Resolutions 2015.07.28.09 – 2015.07.28.14. Cherine Chalaby, Wolfgang Kleinwächter, Erika Mann, Thomas Schneider, and Kuo-Wei Wu were unavailable to vote on the Resolutions. The Resolutions carried.

      Rationale for Resolutions 2015.07.28.09 – 2015.07.28.14

      A Secretary's Note [PDF, 133 KB] was added to the Rationale to provide greater clarity on the AOC and Organization Reviews Schedule and Process/Operational Improvements.

      Why is the Board addressing this issue?

      The Board is addressing this issue because of the significant impact seven reviews in FY2016 would have on ICANN stakeholders' capacity and ICANN resources. In response to public requests to delay some or all Reviews, a proposal was posted for public comment that called for four Reviews to take place in FY2016 and introduced several improvements to increase the efficiency and effectiveness of Reviews. Widespread concerns were received regarding the community's and ICANN's ability to conduct this large number of simultaneous Reviews, in addition to the already heavy workload, such as the IANA stewardship transition and the many policy initiatives underway and anticipated to start in FY2016. As a result, today's action provides relief to the community by proposing an updated schedule of reviews, and operational and process improvements to enable the community to more effectively participate in these key accountability mechanisms.

      What is the proposal being considered?

      The resolution endorses a proposed schedule for AoC and Organizational Reviews:

      • AoC Reviews - CCT Review to continue as scheduled, with a call for volunteers targeted for October 2015; SSR2 to be deferred by nine months (with the call for volunteers targeted for June 2016); WHOIS2 to be deferred by one year (with the call for volunteers targeted for October 2016); ATRT3 targeted for July 2017, based on the trigger of three years from the time that the Board took action on the recommendations of the prior Review Team;

      • Organizational Reviews - prepare for and begin the At-Large2 Review under a slower schedule, targeting an independent examiner to be engaged in March 2016 and conduct the Review between April and December 2016; and planning for NomCom2, SSAC2 and RSSAC2 will occur late in FY2016 and the Reviews will be conducted in FY2017.

      The resolution also endorses the proposed process and operational improvements that were posted for public comment and are designed to simplify review processes and increase their effectiveness.

      The resolution acknowledges that the work of the CCWG on Enhancing ICANN Accountability may impact ICANN Reviews, and that adopted Accountability Framework recommendations will be factored into the Reviews timeline.

      Noting that the U.S. Department of Commerce's NTIA is a signatory to the Affirmation of Commitments that details ICANN's AoC Review obligations, the resolution also instructs ICANN's CEO to engage with NTIA on the AoC Review schedule change endorsed by the Board.

      Related to process and operational improvements, the resolution tasks the Board Governance Committee with determining which Board committee or group should have the responsibility for oversight of AoC Reviews, in parallel to the SIC's responsibility for overseeing Organizational Reviews. The resolution also acknowledges that the Structural Improvements Committee (SIC) will be finalizing "Organizational Reviews Policies, Procedures and Guidelines," following appropriate public consultation.

      This supports the development of a comprehensive Review Framework. The improved documentation will facilitate clarity and shared understanding by all parties and will help streamline the operation of reviews.

      Which stakeholders or others were consulted?

      Written comments were submitted by seven organizations/groups and six individuals, in addition to discussions with community leaders and a public session held at ICANN53. Forum commenters represented one GNSO constituency and stakeholder group, and the At-Large Community, as well as a global not-for-profit association and several consultancy firms.

      What significant materials did the Board review?

      The Board reviewed public comments, participated in the public session on Reviews held at ICANN53, and considered Community views and comments discussed during ICANN53.

      In addition to considering volunteer resources, the Board considered the financial and human resources necessary to support the operations of Reviews during the review and approval of ICANN's FY2016 Operating Plan and Budget. Reflecting on the community's views on prioritization of Reviews and Review recommendations, the Board believes that the implementation of "Organizational Reviews Policies, Procedures and Guidelines" will facilitate a clear and focused Review scope, consistent budgeting and cost tracking, and a streamlined Review process and duration.

      Furthermore, the Board has periodically reviewed ICANN's plans and progress toward implementing the ATRT2 recommendations aimed at improving the effectiveness of Reviews.

      What factors did the Board find to be significant?

      As noted, the Board is sympathetic to the community's concerns about volunteer burnout and the community's and ICANN's ability to conduct the unusually large number of Reviews in one year. Community feedback also indicates a growing concern about the pace and effectiveness of implementation of prior Review recommendations and the need to improve clarity and consistency of reporting on the progress of implementation work. The Board considered this factor to be significant and in alignment with previous discussions held by the Board. To that end, the Board has assigned to the Board Governance Committee the task of determining which committee should bear the responsibility for oversight of AoC Reviews, in parallel to the Structural Improvements Committee's responsibility for oversight of Organizational Reviews.

      Are there positive or negative Community impacts?

      Based on Community feedback, the Board determined that maintaining the originally proposed schedule of four Reviews in FY2016 would have significant negative impact on the volunteers, Staff and ICANN's ability to accomplish the critical work laid out in the Strategic Plan and Operating Plan for FY2016.

      At the same time, the Board is keenly aware of the importance of conducting independent and effective Reviews and thanks the community for offering valuable feedback and suggestions for an improved Review process and result. This effort is expected to have a significant and lasting positive impact on the community and the ongoing effectiveness of AoC and Organizational Reviews.

      Are there any security, stability, or resiliency issues relating to the DNS?

      While there are not expected to be any security, stability or resiliency issues relating to the DNS as the result of actions being considered, there may be a perception that the deferral in the conduct of the next SSR Review could have a negative impact on the DNS. However, the Board notes that implementation of, and periodic reporting on, the last SSR Review continues, along with the range of ICANN SSR-related activities. In addition, the upcoming review of the New gTLD Program's effect on competition, consumer choice and trust (which is not deferred under today's resolution) is expected to include an assessment of safeguards put in place to mitigate issues involved in gTLD introduction or expansion.

      This is an Organizational Administrative Function for which public comment was received.

    4. Process for Requesting GAC Advice

      This item was removed from agenda. The Board decided to discuss this matter at a subsequent meeting.

  3. Confidential Session:

    The Board entered a confidential session. The Board undertook the following actions during its confidential session:

    1. President and CEO FY15 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 FY15 SR2 at-risk compensation payment.

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

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

      Rationale for Resolution 2015.07.28.15

      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, which the President and CEO has set in coordination with the Compensation Committee.

      Following FY15 SR2, which is a scoring period that ran from 16 November 2014 through 15 May 2015, the President and CEO provided to the Compensation Committee his self-assessment of his achievements towards his goals for FY15 SR2 the measurement period. After seeking input from other Board members, the Compensation Committee reviewed with the President and CEO his FY15 SR2 goals and discussed his achievements against those goals. Following that discussion, the Compensation Committee recommended that the Board approve the President and CEO's at-risk compensation for the second scoring period of FY15 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 FY15 budget. This decision will not have an impact on the security, stability or resiliency of the domain name system.

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

    2. Ombudsman FY15 At-Risk Compensation

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

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

      Rationale for Resolution 2015.07.28.16

      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. The score provides the Ombudsman with an understanding of areas in which he has done well and where he may need to improve or increase certain activities.

      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.

    3. Officer Compensation

      Whereas, the retention of high caliber staff is essential to ICANN's operations and ICANN desires to ensure competitive compensation for staff.

      Whereas, independent market data provided by outside expert compensation consultants indicates that current compensation for the Chief Operating Officer, (COO) and Chief Innovation and Innovation Officer (CIIO) is within ICANN's target of the 50th to 75th percentile for total cash compensation based on comparable market data for the respective positions.

      Whereas, the compensation for the two ICANN Officers identified above has not been adjusted since they started working for ICANN.

      Whereas, the Board has confirmed that they are not conflicted with respect to compensation packages for any of ICANN's Officers.

      Resolved (2015.07.28.17), at the President and CEO's request, the Board grants the President and CEO the discretion to adjust the compensation, effective 1 July 2015, of: (i) Susanna Bennett, COO; and (ii) Ashwin Rangan, CIIO, in accordance with the independent study on comparable compensation, subject to a limitation that their annual base salaries shall not increase by more than 4% per annum from their current rates.

      Resolved (2015.07.28.18), specific items within this resolution shall remain confidential pursuant to Article III, section 5.2 of the ICANN Bylaws until the President and CEO determines that the confidential information may be released.

      Rationale for Resolutions 2015.07.28.17 – 2015.07.28.18

      Attracting and retaining high caliber staff by providing a competitive compensation package is crucial to the organization. An improving job market will make more opportunities available for high caliber performers outside of ICANN.

      ICANN's President and CEO has requested that he be granted the discretion to increase these Officers' base salaries by up to 4% of their current base salaries. The President and CEO has also informed the Board that he intends to seek the same discretion for other Officers as and when appropriate, and that he intends to also exercise the same discretion with respect to ICANN's global leaders that are not Officers (which do not require Board approval).

      ICANN is in a critical phase that calls for continuity of certain skill and expertise, particularly with ongoing key projects including the New gTLD Program, Affirmation of Commitments reviews, the U.S. Governments' IANA stewardship transition, ICANN Accountability review underway, expanding contractual compliance, and enhanced globalization efforts, among many others. Each of these projects requires knowledgeable and skilled executives to ensure ICANN's operational goals and objectives are met while ensuring that risk is mitigated to the greatest extent possible. Adhering to ICANN's employment philosophy, and providing competitive compensation, will help ensure these goals are achieved.

      It should be noted, however, that previously, it had been discussed that the plan was to only seek authorization to increase relevant Officers' salaries every two years. Last year the Board authorized the President and CEO to use his discretion to adjust the base salary of the four Officers who had not had an increase in two years or more. Those adjustments were made effective 1 July 2014, which is the same date on which all other staff realizes their salary adjustments. The two Officers for whom no authorization was sought in 2014 because they had not yet been with ICANN for two years or more are the COO and the CIIO. In trying to better align the timing of increases so requests for authorization to adjust Officers' base salaries need only happen once a year, it is being recommended that this year include the CIIO's salary, who has only been with ICANN since March 2014, but that the President and CEO will "pro-rate" the CIIO's adjustment such that the first compensation adjustment aligns to 1 July 2015, but that he is still treated similarly to other Officers. Note that the COO's two-year employment anniversary with ICANN falls directly on 1 July 2015.

      Continuity and retention of key personnel during key organization phases is beneficial to all aspects of the organization. Thus, salary adjustments provided under this resolution likely will have a positive impact on the organization and its effort to fulfill its mission, as well as on the transparency and accountability of the organization. There will be some fiscal impact to the organization, but that impact will not have an effect on the overall current fiscal year budget. This resolution will not have any direct impact on the security, stability and resiliency of the domain name system.

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

The Chair called the meeting to a close.

Published on 29 September 2015

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