Skip to main content
Resources

Approved Board Resolutions | Special Meeting of the ICANN Board

  1. Consent Agenda:
    1. Thank you from the Security and Stability Advisory Committee (SSAC) to Departing Members
    2. SSAC Member Reappointments
    3. Appointment of A/J-, F-I-, L-Root Server Operator Representatives to the RSSAC
    4. Geographic Regions Review Working Group Final Report Submission
  2. Main Agenda:
    1. Consideration of Re-evaluation of the Vistaprint Limited String Confusion Objection Expert Determination
    2. Los Angeles Hub Office Lease
    3. IT Roadmap for 2016
    4. AOB
      1. Recognition of Dr. Robert Blokzijl – In Memoriam

 

  1. Consent Agenda:

    1. Thank you from the Security and Stability Advisory Committee (SSAC) to Departing Members

      Whereas, on 17 May 2002 the ICANN Board approved the appointment of Alain Aina and Rick Wesson to the SSAC.

      Whereas, on 26 June 2009 the ICANN Board approved the appointments of Roy Arends and Doug Maughan to the SSAC.

      Whereas, on 5 August 2010 Alain Aina, Doug Maughan, and Rick Wesson were reappointed to terms beginning 1 January 2011 and ending on 31 December 2012 and Roy Arends, to a term ending 31 December 2013.

      Whereas, on 03 October 2012 the ICANN Board approved the appointment of Narayan Gangalaramsamy to the SSAC.

      Whereas, on 20 December 2012 the ICANN Board reappointed Alain Aina, Doug Maughan, and Rick Wesson to the SSAC, with terms ending on 31 December 2015.

      Whereas, on 21 November 2013 the ICANN Board reappointed Roy Arends to a 3-year term beginning 1 January 2014 and ending 31 December 2016.

      Whereas, on 14 July 2015 Roy Arends joined ICANN as an employee, and resigned from the SSAC.

      Resolved (2015.12.02.01), that Alain Aina, Roy Arends, Narayan Gangalaramsamy, Doug Maughan and Rick Wesson have earned the deep appreciation of the Board for their service to ICANN by their membership on the Security and Stability Advisory Committee, and that the Board wishes them well in all future endeavors.

      Rationale for Resolution 2015.12.02.01

      It is the practice of the SSAC to seek Board recognition of the service of Committee members upon their departure.

    2. SSAC Member Reappointments

      Whereas, Article XI, Section 2, Subsection 2 of the Bylaws governs the Security and Stability Advisory Committee (SSAC).

      Whereas, the Board, at Resolution 2010.08.05.07 approved Bylaws revisions that create three-year terms for SSAC members, require staggering of terms, and obligate the SSAC chair to recommend the reappointment of all current SSAC members to full or partial terms to implement the Bylaws revisions.

      Whereas, the Board, at Resolution 2010.08.05.08 appointed SSAC members to terms of one, two, and three years beginning on 1 January 2011 and ending on 31 December 2011, 31 December 2012, and 31 December 2013.

      Whereas, in June 2015 the SSAC Membership Committee initiated an annual review of SSAC members whose terms are ending 31 December 2015 and submitted to the SSAC its recommendations for reappointments.

      Whereas, on 16 September 2015, the SSAC members approved the reappointments.

      Whereas, the SSAC recommends that the Board reappoint the following SSAC members to three-year terms: Jaap Akkerhuis, Patrik Fältström, Ondrej Filip, Jim Galvin, Robert Guerra, Julie Hammer, Ram Mohan, Doron Shikmoni, and Suzanne Woolf.

      Resolved (2015.12.02.02) the Board accepts the recommendation of the SSAC and reappoints the following SSAC members to three-year terms beginning 1 January 2016 and ending 31 December 2018: Jaap Akkerhuis, Patrik Fältström, Ondrej Filip, Jim Galvin, Robert Guerra, Julie Hammer, Ram Mohan, Doron Shikmoni, and Suzanne Woolf.

      Rationale for Resolution 2015.12.02.02

      The SSAC is a diverse group of individuals whose expertise in specific subject matters enables the SSAC to fulfill its charter and execute its mission. Since its inception, the SSAC has invited individuals with deep knowledge and experience in technical and security areas that are critical to the security and stability of the Internet's naming and address allocation systems. The above-mentioned individuals provide the SSAC with the expertise and experience required for the Committee to fulfill its charter and execute its mission.

    3. Appointment of A/J-, F-I-, L-Root Server Operator Representatives to the RSSAC

      Whereas, the ICANN Bylaws call for the establishment of a Root Server System Advisory Committee (RSSAC) with the role to advise the ICANN community and Board on matters relating to the operation, administration, security, and integrity of the Internet's Root Server System.

      Whereas, the ICANN Bylaws call for Board of Directors appointment of RSSAC members based on recommendations from the RSSAC Co-Chairs.

      Whereas, the RSSAC Co-Chairs recommended for Board of Directors consideration the appointments of representatives from the A/J-, F-,

      I-, and L-root server operators to the RSSAC.

      Resolved (2015.12.02.03), the Board of Directors appoints the representatives from the A/J-, F-, I-, and L-root server operators, Brad Verd, Jim Martin, Lars-Johan Liman, and John Crain, respectively, through 31 December 2018.

      Rationale for Resolution 2015.12.02.03

      In May 2013, the root server operators (RSO) agreed to an initial membership of RSO representatives for RSSAC, and each RSO nominated an individual. The Board of Directors approved the initial membership of RSSAC in July 2013 with staggered terms.

      The representatives from the A/J-, F-, I-, and L-root server operators were appointed to an initial two-year term, which expires on 31 December 2015. Their re-appointment is for a full, three-year term.

      The appointment of these RSSAC members is not anticipated to have any fiscal impact on ICANN, though there are budgeted resources necessary for ongoing support of the RSSAC.

      This resolution is an organizational administrative function for which no public comment is required. The appointment of RSSAC members contributes to ICANN's commitment to strengthening the security, stability, and resiliency of the DNS.

    4. Geographic Regions Review Working Group Final Report Submission

      Whereas, the cross-community Geographic Regions Review Working Group has produced its Final Report in which it proposes a series of recommendations regarding the ongoing application of the organization's geographic regions framework.

      Whereas, the ICANN Board is interested in further community reaction to those recommendations.

      Whereas, the Working Group has recommended that the Board direct staff to manage a public comment period of at least 120 days to give the community an opportunity to thoroughly review the proposals and provide any additional comments on its recommendations.

      Resolved (2015.12.02.04), that the Board directs the President and CEO, or his designee(s), to initiate and manage a public comment period of at least 120 days on the Geographic Regions Review Working Group Final Report to give the community an opportunity to review the recommendations of the Working Group, and to provide any additional comments on those recommendations.

      Rationale for Resolution 2015.12.02.04

      Why is the Board addressing this issue now?

      The Board-chartered cross-community Geographic Regions Review Working Group submitted its Final Report recommendations to the Chairman of the ICANN Board on November 4, 2015. At the recommendation of the Working Group, the Board taking action to seek community review and further comment on the Working Group recommendations.

      What are the proposals being considered?

      1. The Working Group concludes that the general principle of geographic diversity is valuable and should be preserved.
      2. Application of the geographic diversity principles must be more rigorous, clear and consistent.
      3. Adjusting the number of ICANN geographic regions is not currently practical.
      4. No other International Regional Structures offer useful options for ICANN.
      5. ICANN must formally adopt and maintain its own unique Geographic Regions Framework.
      6. The Community wants to minimize any changes to the current structure.
      7. ICANN must acknowledge the sovereignty and right of self-determination of states to let them choose their region of allocation.
      8. ICANN communities have flexibly applied geographic diversity principles over the years. While the Board should remain strictly subject to the current framework, flexibility should be preserved for other structures.
      9. "Special Interest Groups" or "Cross-Regional Sub-Groups" offer new diversity opportunities.
      10. Implementation mechanisms and processes must be developed by Staff.
      11. The Board must preserve its oversight and future review opportunities.

      After the close of the public comment period, the Board will consider the recommendations of the Working Group taking into account the input from the community.

      What stakeholders or others were consulted?

      All ICANN Supporting Organizations and Advisory Committees were invited to provide representatives to the Working Group. At various times throughout the working group effort the ALAC, ASO, ccNSO and GNSO had representatives serving on the group.  The GAC Chair also participated early in the process. Prior to submission of the Working Group's Final Report, comments were provided by the ALAC, ccNSO, GNSO and the GAC Chair. The formal ALAC, ccNSO and GNSO comments accompanied the Final Report submission.

      What significant materials did the Board review?

      The Board received a copy of the Working Group's Final Report including formal written statements from the ALAC, ccNSO and GNSO.

      What factors did the Board find to be significant?

      For purposes of directing the initiation of a public comment forum, the Board reviewed the recommendation of the Working Group to establish a public comment period of at least 120 days.

      Are there Positive or Negative Community Impacts?

      Opening an extensive public comment period on this matter can be viewed as a positive development for the community.

      Are there fiscal impacts/ramifications on ICANN (Strategic Plan, Operating Plan, Budget); the community; and/or the public?

      The initiation of a public comment period regarding this matter presents no fiscal impacts/ramifications on the organization, the community or the public.

      Are there any Security, Stability or Resiliency issues relating to the DNS?

      The initiation of a public comment period regarding this matter will have no anticipated impact on the security, stability and resiliency of the domain name system.

      Is this either a defined policy process within ICANN's Supporting Organizations or ICANN's Organizational Administrative Function decision requiring public comment or not requiring public comment?

      Public comment opportunities regarding this matter have been numerous and extensive so no further comment opportunities are required. However, the Board has decided to provide an additional opportunity for public comment as it is interested in receiving additional feedback from the community before it deliberates on the recommendations of the Working Group.

  2. Main Agenda:

    1. Consideration of Re-evaluation of the Vistaprint Limited String Confusion Objection Expert Determination

      Whereas, on 9 October 2015, an Independent Review Process (IRP) Panel (Panel) issued its Final Declaration in the IRP filed by Vistaprint Limited (Vistaprint) against ICANN (Final Declaration). Vistaprint specifically challenged the String Confusion Objection Expert Determination (Expert Determination) finding Vistaprint's applications for .WEBS to be confusingly similar to Web.com's application for .WEB (Vistaprint SCO).

      Whereas, while the IRP Panel found that ICANN did not discriminate against Vistaprint in not directing a re-evaluation of the Expert Determination, the Panel recommended that the Board exercise its judgment on the question of whether an additional review is appropriate to re-evaluate the Expert Determination. (See id. at ¶ 196.)

      Resolved (2015.12.02.05), the Board defers to a subsequent meeting its consideration of the Panel recommendation in the Final Declaration that the Board exercise its judgment on the question of whether an additional review is appropriate to re-evaluate the Expert Determination.

    2. Los Angeles Hub Office Lease

      Whereas, ICANN has stated its objective to secure a lease for long-term office space, conducive to efficient operations, at affordable costs.

      Whereas, staff has identified ideally located space available for lease until the expiration of ICANN's main lease in June 2022, allowing ICANN to accommodate the current and planned office needs and consolidate its operations onto two connected floors.

      Whereas, the staff and Board Finance Committee recommend that the Board authorize the President and CEO, or his designee(s), to enter into, and make all necessary disbursements for additional space in the ICANN Los Angeles hub office, in an amount not to exceed [AMOUNT REDACTED].

      Resolved (2015.12.02.06), the Board authorizes the President and CEO, or his designee(s), to enter into, and make all necessary disbursements for, an amendment to ICANN's lease for the Los Angeles hub office in an amount not to exceed [AMOUNT REDACTED].

      Resolved (2015.12.02.07), specific items within this resolution shall remain confidential for negotiation purposes 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.12.02.06 – 2015.12.02.07

      The ICANN Los Angeles office at 12025 Waterfront Drive currently consists of the entire third floor, a portion of the fourth floor (both terms expiring in June 2022) and space on the second floor of the building, which ICANN has been subleasing on a month-to-month basis, which will end December 2015.

      The key drivers for this lease amendment are as follows:

      1. provision of space for existing staff and contractors, as current space for current staff is not sufficient;
      2. provision of space for future additional staff as per FY16 Operating Plan and Budget;
      3. Conversion of month to month lease to consolidated long term lease;
      4. Added benefit of improving of operational efficiency as we consolidate operations onto 2 floors, connected through the staircase private to ICANN 3rd/4th floors (2nd floor is only accessible by elevator).

      The adopted FY16 Operating Plan and Budget suggests a staff growth of 38 headcount in FY16 (https://www.icann.org/en/system/files/files/adopted-opplan-budget-fy16-25jun15-en.pdf [PDF, 1.74 MB], page 27), on a worldwide basis, of which 23 employees will be in the Los Angeles office. This expected growth required ICANN to plan for additional space in the Los Angeles office during FY16.

      Based on this plan, ICANN has been researching options to expand its Los Angeles office. The landlord for the second floor space, that ICANN currently subleases month-to-month, has requested ICANN to vacate it shortly. Separately, the tenant occupying the remainder of the fourth floor is moving, thereby providing ICANN the opportunity to consolidate its operations on the entire third and fourth floors, through an amendment to its current long-term lease (until June 2022), instead of expanding the 2nd floor month-to-month arrangement.

      As a result, ICANN intends to enter into a lease amendment for the portion of the fourth floor that is being vacated, and release the second floor space as requested. The net space addition is 5,732 square feet.

      The decision offers the opportunity to resolve the lack of space ICANN is currently already facing in terms of accommodating existing staff and contractors and to accommodate the growth planned for in the FY16 Operating Plan and Budget.

      The term of the lease amendment under consideration in this resolution would match ICANN's existing lease through June 2022. The new long-term lease amendment (which would replace the month to month lease for the second floor) would amount to a total of [AMOUNT REDACTED] for the remaining 67 months for the 12,819 square feet on the 4th floor.

      This amount exceeds the ICANN Officers' contracting and disbursement authority and must be approved by the Board.

      Local real estate market surveys have been reviewed, and there is presently no other rental space available in the immediate area at comparable prices. Other less desirable available space outside of the current building is more expensive.

      This decision will have a financial impact on ICANN. The financial impact for FY16 has been for FY16 has been catered for in the FY16 budget. Annual cost will be budgeted for in subsequent years and is expected to be affordable.

      This decision is not anticipated to have any impact on the security, stability and resiliency of the domain name system.

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

    3. IT Roadmap for 2016

      No resolution taken.

    4. AOB

      1. Recognition of Dr. Robert Blokzijl – In Memoriam

        Whereas, Dr. Robert "Rob" Blokzijl passed away on 1 December 2015. He was a gentle man who radiated warmth and optimism, while working constructively in the Netherlands, in Europe and, indeed, throughout the world to foster the development of the Internet.

        Whereas, Dr. Blokzijl served on the ICANN Board in our early days (1999-2002), and is best remembered as the chair of RIPE for an astonishing 25 years.

        Whereas, Dr. Blokzijl has earned the deep appreciation of the Board and the Internet community contributions and service.

        Resolved (2015.12.02.08), the Board notes the passing of Internet pioneer Dr. Rob Blokzijl who was among other things a former ICANN Board member. The ICANN Board, management, and staff send their deepest condolences to his family and friends. Our dear friend and colleague Rob will be deeply missed by all who knew him.

Published on 4 December 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."