Skip to main content
Resources

Approved Board Resolutions | Regular Meeting of the ICANN Board

  1. Consent Agenda:
    1. Approval of Board Meeting Minutes
    2. Acknowledgment of Receipt and Thank You for SAC056 Advisory on Impacts of Content Blocking via the Domain Name System to the ICANN Board.
      1. Rationale for Resolution 2012.10.13.02
    3. Revisions to Board Governance Committee Charter
      1. Rationale for Resolution 2012.10.13.03
  2. Main Agenda:
    1. Approval of Proposed .Name Renewal Registry Agreement
      1. Rationale for Resolution 2012.10.13.04
    2. Confidential Resolution
      1. Rationale for Resolutions 2012.10.13.05 – 2012.10.13.06

 

  1. Consent Agenda:

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

    1. Approval of Board Meeting Minutes

      Resolved (2012.10.13.01), the Board approves the minutes of the 3 October 2012 ICANN Board Meeting.

    2. Acknowledgment of Receipt and Thank You for SAC056 Advisory on Impacts of Content Blocking via the Domain Name System to the ICANN Board.

      Whereas, on 9 October 2012, the Security & Stability Advisory Committee forward the SSAC Advisory: SAC056: SSAC Advisory on Impacts of Content Blocking via the Domain Name System to the ICANN Board.

      Whereas, the ICANN Board acknowledges that blocking using the DNS can cause collateral damage or unintended consequences with limited or no remedies available to affected parties.

      Resolved (2012.10.13.02), the ICANN Board acknowledges receipt of SAC056 and thanks the SSAC for their work in preparing this Advisory for the ICANN community.

      Rationale for Resolution 2012.10.13.02

      To remain accountable to the ICANN community, the Board considers it important to acknowledge the reports prepared by its Advisory Committee.  This action does not have any impact on the resources of ICANN, and acknowledging the report is not expected to have any impact on the security, stability or resiliency of the DNS.

      This is an ICANN Organizational Administrative Function not requiring public comment.

    3. Revisions to Board Governance Committee Charter

      Whereas, the Charter of the Board Governance Committee required changes to remain factually accurate and the BGC recommends the Board to approve the changes.

      Resolved (2012.10.13.03), the Board approves the revised Board Governance Committee Charter.

      Rationale for Resolution 2012.10.13.03

      As part of its annual work, the Board Governance Committee performs a review of its Charter to assure that the work of the BGC is in alignment with its Charter.  The change approved today does not have any impact on the resources of ICANN or the community.  This action does not have any impact on the security, stability or resiliency of the DNS.

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

  2. Main Agenda:

    1. Approval of Proposed .Name Renewal Registry Agreement

      Whereas, on 3 July 2012 ICANN commenced a public comment period <http://www.icann.org/en/news/public-comment/name-renewal-2012-03jul12-en.htm> on a proposed agreement for renewal of the 2007 .name Registry Agreement <http://www.icann.org/en/about/agreements/registries/name/agreement-15aug07-en.htm>.

      Whereas, the proposed .name renewal Registry Agreement includes modified provisions to bring the .name Registry Agreement into line with other comparable agreements.

      Whereas, the public comment forum on the proposed agreement closed on 23 August 2012, with ICANN receiving three comments; a summary and analysis of the comments was provided to the Board.

      The Board has determined that no revisions to the proposed .name renewal Registry Agreement are needed after taking the comments into account.

      Whereas, the proposed .name renewal Registry Agreement includes significant improvements as compared to the current .name Registry Agreement.

      Resolved (2012.10.13.04), the proposed .name renewal Registry Agreement is approved, and the President and CEO and the General Counsel are authorized to take such actions as appropriate to implement the agreement.

      Rationale for Resolution 2012.10.13.04

      Why the Board is addressing the issue now?

      The prior .name Registry Agreement expired on 15 August 2012. Verisign is continuing to operate under the terms of the prior agreement during ICANN's consideration of the proposed new form of agreement. The proposed renewal agreement was posted for public comment on 3 July 2012. The comment period closed on 23 August 2012.

      What is the proposal being considered?

      The changes to the .name Agreement and the Appendices fall within several broad categories: (i) changes to promote consistency across registries; (ii) changes to update the agreement to reflect changes that have occurred since the current .name Registry Agreement was signed (including updating references, technical changes and other updates); and (iii) changes to allow Verisign to better serve the internet community (including to allow Verisign to more quickly address certain imminent threats to the security and stability of the TLD or the Internet).

      Which stakeholders or others were consulted?

      ICANN conducted a public comment period on the proposed .name renewal Registry Agreement from 3 July 2012 through 23 August 2012, following which time the comments were summarized and analyzed.

      What concerns or issues were raised by the community?

      Three members of the community participated in the public comment, however, only one comment substantively addressed the proposed Agreement. That comment addressed competitive contract bidding.

      What significant materials did the Board review?

      The Board reviewed the proposed .name renewal Registry Agreement and its Appendices, as well as the public comment summary and analysis.

      What factors the Board found to be significant?

      The Board carefully considered the public comments and the Staff recommendation with respect to those comments. The Board considered ICANN's contractual obligations with respect to the .name Registry Agreement currently in operation in reaching this decision, specifically that the Agreement must be renewed absent certain uncured breaches by the registry operator and that certain terms of the renewal are required to conform to existing comparable gTLD registry agreements.

      Are there positive or negative community impacts?

      As part of the renewal process, ICANN conducted a review of Verisign's recent performance under the currently operated .name Registry Agreement. The contractual compliance review covered areas including: (i) SRS Outage Restrictions; (ii) equal Registrar access to the SRS; (iii) bulk zone file access; (iv) payment of required fees; and (v) submission of monthly reports. Verisign was found to have met its contractual requirements (see http://www.icann.org/en/resources/compliance/reports/operator-verisign-name-06apr12-en.pdf [PDF, 104 KB]). Evidence indicates that the community can expect that good performance to continue.

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

      There is no significant fiscal impact expected if ICANN approves the proposed .name renewal Registry Agreement. The provisions regarding registry-level fees and pricing constraints are for the most part consistent with the new gTLD base agreement and the current major gTLDs.

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

      There are no expected security, stability, or resiliency issues related to the DNS if ICANN approves the proposed .name renewal Registry Agreement. The proposed agreement in fact includes terms intended to allow for swifter action in the event of certain threats to the security or stability of the DNS.

      This is an ICANN Organizational Administrative Function requiring public comment.

    2. Confidential Resolution

      [Resolution redacted]

      Resolved (2012.10.13.07), the Board approves maintaining the confidentiality of all or a portion of this Resolution 2012.10.13.05 and 2012.10.13.06, the corresponding rationale and related materials.

      Rationale for Resolutions 2012.10.13.05 – 2012.10.13.06

      [Rationale redacted]

Posted on 16 October 2012.

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