Skip to main content
Resources

Approved Board Resolutions | Special Meeting of the ICANN Board

  1. Main Agenda
    1. Approval of Agreement with Australian Continuous Improvement Group Pty Ltd. for Secretariat Support to the GAC
    2. ICANN52 Meeting Location - Move the February 2015 Meeting to an Alternate Location

 

  1. Main Agenda:

    1. Approval of Agreement with Australian Continuous Improvement Group Pty Ltd. for Secretariat Support to the GAC

      Whereas, Australian Continuous Improvement Group Pty Ltd. (ACIG) is a consulting firm that has provided secretariat support to the GAC pursuant to temporary short-term interim agreements.

      Whereas, the GAC, ACIG and ICANN desire to finalize a longer-term engagement.

      Whereas, the temporary short-term agreements to date have not required Board approval; however, the longer-term engagement now under consideration would likely exceed the US$500,000.00 contracting and disbursement limits of the current Disbursement Policy and would therefore require Board approval.

      Whereas, the GAC has secured the informal commitment of certain donor country GAC members to reimburse ICANN for any disbursements ICANN makes under the proposed agreement and the donor countries have established a not-for-profit association in Switzerland, the GAC Secretariat Funding Association, to provide the funding under this agreement.

      Whereas, ICANN's acceptance of and reimbursement for these disbursements from the donor countries shall be subject to confirmation that such payments and reimbursements comply with requirements of the Office of Foreign Assets Control (OFAC), the Foreign Corrupt Practices Act (FCPA), and other applicable laws and regulations focused on compliance with anti-corruption and government imposed economic sanctions.

      Resolved (2014.10.28.01), the Board authorizes the President and CEO, or his designee(s), to take all actions to enter into the required contracts with, and make all required disbursements to Australian Continuous Improvement Group Pty Ltd. (ACIG), under the following terms: the ACIG agreement shall provide for a one-year term, with ICANN having the right to extend the term of the agreement for an additional successive one-year term, and a second successive term to expire at or around 31 July 2017, upon at least 90-days written notice prior to the expiration of the then current term, with total disbursements during any one-year period not to exceed US$900,000.

      Rationale for Resolution 2014.10.28.01

      Secretariat support services for GAC activities are important to ensure that the GAC is able to fulfill its role of providing advice to ICANN on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. The GAC and its Chair and Vice Chairs require considerable secretariat support in connection with their activities in support of ICANN. To date such support has been provided pursuant to temporary short-term interim agreements with Australian Continuous Improvement Group Pty Ltd. (ACIG).

      The GAC and ICANN wish to provide for longer-term secretariat support for the GAC.

      Because the GAC is not a legal entity with an established budget, a mechanism needs to be established for engaging a consulting group to provide such services to the GAC. ICANN's Disbursement Policy limits ICANN officers from contracting for or disbursing more than US $500,000.00 per obligation. Fees payable to ACIG could exceed the contracting and disbursement limits of the Disbursement Policy.

      Accordingly, to ensure that the GAC receives secretariat support services, the Board is therefore authorizing the President and CEO to enter into all required contracts and make all required disbursements, with ACIG, with the understanding that disbursements under the proposed contracts are anticipated to be reimbursed by one or more donor countries. The GAC has secured the informal commitment of certain donor country GAC members to reimburse ICANN for any disbursements ICANN makes under the proposed agreement and the donor countries have established a not-for-profit association in Switzerland, the GAC Secretariat Funding Association, to provide the funding under this agreement. Because that Funding Association is not otherwise staffed nor has the ability to monitor the performance of the Secretariat, it is not feasible for the ACIG to be directly engaged through there. The Board's action will have a positive impact on the community because it supports the important role that the GAC plays in providing advice to ICANN on issues of public policy.

      Although ICANN did not follow its usual Procurement Guidelines or issue RFQs or RFPs in connection with this engagement, the GAC prepared a request for proposals and selected the vendor in a competitive bidding process and finds the proposed contract to be a viable, cost-effective solution. The process for selection of this vendor does not call for public consultation, as the GAC's assessment of the suitability of the vendor is the primary consideration.

      If the donor countries reimburse ICANN in full for all expenditures under the agreement, there will be no financial impact on ICANN to enter into the agreement. If the donor countries fail to reimburse ICANN in full for all expenditures, ICANN could be responsible for payment of as much as US$900,000 per year under the agreement, but financial exposure and risk is mitigated by ICANN's having the right to terminate the agreement on ten days notice if termination is necessary to ICANN's overall business needs.

      There is no impact on the security or the stability of the DNS due to the engagement of ACIG to provide GAC secretariat support.

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

    2. ICANN52 Meeting Location - Move the February 2015 Meeting to an Alternate Location

      Whereas, on 26 June 2014 the Board previously designated Marrakech, Morocco as the February 2015 location for ICANN's 52nd Public Meeting.

      Whereas, ICANN is committed to holding three public meetings in 2015.

      Whereas, unforeseen circumstances, including increasing community concern, lead ICANN to postpone Marrakech as a host location for an ICANN Public Meeting until 2016, and identify an alternative location for ICANN52 (for 8-12 February 2015) as quickly as possible.

      Whereas, ICANN has a limited opportunity to secure the required facilities sufficient to host an ICANN Public Meeting in an alternative location for the previously announced dates.

      Resolved (2014.10.28.02), the Board approves the postponement of hosting an ICANN public meeting in Marrakech, Morocco until 2016 and authorizes the President and CEO, or his designee(s), to take all actions necessary to confirm the postponement.

      Resolved (2014.10.28.03), the Board approves the identification of an alternative location for ICANN52 from 8-12 February 2015, and authorizes the President and CEO, or his designee(s), to take all actions necessary to hold the ICANN52 Meeting in an alternative location.

      Resolved (2014.10.28.04), the Board authorizes the President and CEO, or his designee(s), to engage in and facilitate all necessary contracting and disbursements for the alternative Meeting venue for ICANN52 Public Meeting, from 8-12 February 2015 in an amount not to exceed US$2 million.

      Resolved (2014.10.28.05), the Board authorizes the President and CEO, or his designee(s), to use the Reserve Fund for additional costs associated with an alternative location for the Meeting, in an amount not to exceed US$1.0 million.

      Resolved (2014.10.28.06), the Board directs the President and CEO to continue to assess the circumstances, including travel restrictions, relating to the alternative location for ICANN 52, and periodically advise the Board.

      Resolved (2014.10.28.07), specific items within this resolution and rationale 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, as soon as reasonably possible

      Rationale for Resolutions 2014.10.28.02 – 2014.10.28.07

      As part of ICANN's public meeting schedule, three times a year ICANN hosts a meeting in a different geographic region (as defined in the ICANN Bylaws) of the world. Holding three ICANN meetings in 2015 is fundamental for the ICANN community to complete its work, particularly as the community works to develop proposals relating to the IANA Stewardship Transition and improvements to accountability mechanisms, as well as the substantial policy-related work underway across the ICANN community.

      ICANN initially identified Marrakech, Morocco as the meeting location for the February 2015 ICANN meeting. Due to recent circumstances and community concerns, there appears to be a high likelihood that there will be a curtailment of transportation facilities that could prevent a significant portion of the anticipated community and staff members from being able to attend in person.

      The risk that many ICANN participants may not be in attendance puts the work of the organization in jeopardy at a critical time.  Similarly, hosting a meeting in the African region with significant groups of Africans likely not able to attend negates the rationale behind ICANN's regional rotation of meetings.

      By postponing the meeting now to address community concerns, ICANN has the option of finding an alternative location for the February 2015 meeting, and selecting another date to hold the meeting in Morocco.

      ICANN conducted a thorough worldwide search of all available and suitable venues. Our analysis of venues to meet our requirements for a full meeting confirms that our options for a February 2015 now are limited to one alternative location.  Contract negotiations are close to finalized and must be executed, with Board approval, by 31 October 2014.  If the alternative location is not selected now, ICANN will not be able to identify any further alternatives for holding a full meeting in February 2015.

      Moving the February 2015 ICANN Meeting as-is to an alternate location makes it more likely that we will have key contributors and a balanced critical mass of community members available to discuss, among other things, the IANA Stewardship Coordination Group (ICG) report together using the consensus process.

      The Board thanks the local host for the Marrakech meeting for the extensive work that has already been done on preparing for the meeting, and for its indication that it will accept a postponement of the 8-12 February 2015 meeting. The Board affirms that ICANN is expected to host a meeting in Marrakech in 2016 and has expressed to the President and CEO that it is imperative to identify a specific date for the 2016 ICANN meeting in Marrakech as soon as possible. This decision is not taken lightly, and was reached only after substantial discussion and debate.

      ICANN will continue to monitor the evolution of circumstances including travel restrictions and to consider the continuing feasibility of hosting ICANN52 in an alternative location in February 2015. A contingency plan is also being developed to allow a distributed meeting based on remote hubs, should travel restrictions prevent a significant portion of the global community from attending a meeting in one location.

      The change to the meeting location likely will result in some financial losses to ICANN, though acting at this time (as opposed to closer to the meeting date) reduces the potential losses.

      There is no potential impact to the security, stability, or resiliency of the DNS.

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

Item 1.a and 1.b (as Confidential Resolution) published on 30 October 2014.

Item 1.b republished in full on 3 November 2014.

Published on 30 October 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""icann.org"" is not an IDN."