Skip to main content
Resources

Approved Resolutions | Meeting of the New gTLD Program Committee

  1. Main Agenda
    1. Extension of Initial Protections of IGO Names and Acronyms

 

  1. Main Agenda:

    1. Extension of Initial Protections of IGO Names and Acronyms

      Whereas, the GAC met during the ICANN 46 meeting in Beijing and issued a Communiqué on 11 April 2013 ("Beijing Communiqué").

      Whereas, the Beijing Communiqué reiterated the GAC's previous advice to the Board that "appropriate preventative initial protection for the IGO names and acronyms on the provided list be in place before any new gTLDs would launch" (the "IGO GAC Advice"). The IGO GAC Advice is identified in the GAC Register of Advice as 2013-04-11-IGO.

      Whereas, the New gTLD Program Committee (NGPC) is responsible for considering the IGO GAC Advice pursuant to the authority granted to it by the Board on 10 April 2012, to exercise the ICANN Board's authority for any and all issues that may arise relating to the New gTLD Program.

      Whereas, the NGPC has spent significant time considering the IGO GAC Advice and has had initiated dialogue with the GAC on this advice.

      Whereas, on 2 July 2013, the NGPC approved Resolutions 2013.07.02.NGPC03 – 2013.07.02.NGPC06, and the NGPC confirmed that appropriate initial protection for the IGO identifiers will continue to be provided as presented in the "IGO List dated 22/03/2013" through the first meeting following the ICANN 47 meeting in Durban while the GAC, NGPC, ICANN staff and community continue to actively work through outstanding implementation issues concerning protections for IGO names and acronyms through.

      Whereas, the GAC, NGPC, ICANN staff and community continue to actively work through outstanding implementation issues, the NGPC thinks it is prudent to further extend the initial protections for the IGO identifiers.

      Resolved (2013.07.17.NG01), the NGPC confirms that appropriate preventative initial protection for the IGO identifiers will continue to be provided as presented in the New gTLD Registry Agreement adopted on 2 July 2013 while the GAC, NGPC, ICANN staff and community continue to actively work through outstanding implementation issues.

      Resolved (2013.07.17.NG02), the NGPC determines that pursuant to Specification 5 in the New gTLD Registry Agreement adopted on 2 July 2013, registry operators will continue to implement temporary protections for the precise IGO names and acronyms on the "IGO List" posted as Annex 1 [PDF, 541 KB] to Resolution 2013.07.02NG03 – 2013.07.02.NG06 until the first meeting of the NGPC following the ICANN 48 Meeting in Buenos Aires or until the NGPC makes a further determination on the IGO GAC Advice, whichever is earlier.

      Resolved (2013.07.17.NG03), if the NGPC and GAC do not reach an agreement on outstanding implementation issues for protecting IGO names and acronyms by the first meeting of the NGPC following the ICANN 48 meeting in Buenos Aires, and subject to any matters that arise during the discussions, the NGPC determines that registry operators will be required to protect only the IGO names identified on the GAC's "IGO List" posted as Annex 1 [PDF, 541 KB] to Resolution 2013.07.02NG03–2013.07.02.NG06.

      Rationale for Resolutions 2013.07.17.NG01 – 2013.07.17.NG03

      Why the NGPC is addressing the issue?

      Article XI, Section 2.1 of the ICANN Bylaws http://www.icann.org/en/about/governance/bylaws#XI permits the GAC to "put issues to the Board directly, either by way of comment or prior advice, or by way of specifically recommending action or new policy development or revision to existing policies." The GAC issued advice to the Board on the New gTLD Program through its Beijing Communiqué dated 11 April 2013. The ICANN Bylaws require the Board to take into account the GAC's advice on public policy matters in the formulation and adoption of the polices. If the Board decides to take an action that is not consistent with the GAC advice, it must inform the GAC and state the reasons why it decided not to follow the advice. The Board and the GAC will then try in good faith to find a mutually acceptable solution. If no solution can be found, the Board will state in its final decision why the GAC advice was not followed.

      What is the proposal being considered?

      In the Beijing Communiqué, the GAC reiterated previous advice that "appropriate preventative initial protection for the IGO names and acronyms on the provided list be in place before any new gTLDs would launch ("IGO GAC Advice")." The NGPC is being asked to consider accepting this advice, while being mindful of the outstanding implementation issues. This IGO GAC Advice is identified in the GAC Register of Advice as 2013-04-11-IGO.

      The New gTLD Registry Agreement includes protections for IGOs but does not yet specify the names and acronyms to be protected.

      To address the GAC advice regarding IGO names and acronyms, on 2 July 2013, the NGPC directed that temporary protections for the IGO names and acronyms previously identified by the GAC on its "IGO List dated 22/03/2013," which was attached as Annex 1 [PDF, 541 KB] the 2 July 2013 resolutions, so that the GAC and the NGPC would have time to work out outstanding implementation issues, as noted in the Beijing Communiqué. We think it is important that those temporary protections remain in place until the first meeting of the NGPC following the ICANN Meeting in Buenos Aires, Argentina, unless the NGPC and the GAC are able to resolve the issues and the NGPC passes a resolution on the IGO GAC Advice earlier than the ICANN Meeting in Buenos Aires. If the NGPC and the GAC do not reach agreement on the issues, and subject to any matters that arise during the discussions, the NGPC would require registry operators only to protect the names, but not the acronyms, identified on the GAC's IGO List posted as Annex 1 [PDF, 541 KB] to Resolutions 2013.07.02NG03-2013.07.02.NG06. This Resolution provides temporary protections for IGOs while respecting the ongoing implementation work.

      Which stakeholders or others were consulted?

      On 29 April 2013, ICANN initiated a public comment forum to solicit input on the proposed final draft of the New gTLD Registry Agreement <http://www.icann.org/en/news/public-comment/base-agreement-29apr13-en.htm>. The public comment forum closed on 11 June 2013. The NGPC has considered the community comments on the New gTLD Registry Agreement in formulating its response to the IGO GAC Advice as it relates to the New gTLD Registry Agreement <http://forum.icann.org/lists/comments-base-agreement-29apr13/>.

      Additionally, on 14 June 2013, the GNSO Policy Development Process Working Group tasked with addressing the issue of protecting the identifiers of certain IGOs and International Non-Governmental Organizations ("INGOs") in all gTLDs published its Initial Report for public comment. The public comment period is scheduled to close 7 August 2013. <http://www.icann.org/en/news/public-comment/igo-ingo-initial-14jun13-en.htm> The Issue Report was initiated as a result of a recommendation by the GNSO Drafting Team formed to provide a GNSO Council response to the Board and GAC on the protection of IOC and RCRC names in new gTLDs. After community review, the scope of the Final GNSO Issue Report included an evaluation of whether to protect the names of both IGOs and non-government organizations at the top level and second level in all gTLDs.

      What concerns or issues were raised by the community?

      ICANN received several responses from the community during the course of the public comment forum on the proposed final draft of the New gTLD Registry Agreement; however, none of the responses specifically relates to the provisions in the New gTLD Registry Agreement to provide protections for IGO identifiers. <http://forum.icann.org/lists/comments-base-agreement-29apr13/>

      What significant materials did the NGPC review?

      As part of its deliberations, the NGPC reviewed the following significant materials and documents:

      What factors did the Board find to be significant?

      The Beijing Communiqué generated significant interest from the community and stimulated many comments. The NGPC considered the community comments, the GAC's advice transmitted in the Beijing Communiqué, the ongoing work of the GNSO PDP Working Group on the Protection of IGO and INGO Identifiers in all gTLDs and further discussion with the GAC on this topic.

      Are there positive or negative community impacts?

      The response to the GAC advice as provided in the NGPC's Resolution will assist with resolving the GAC advice in manner that permits the greatest number of new gTLD applications to continue to move forward as soon as possible, while being mindful of the ongoing efforts to work through the outstanding implementation issues.

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

      There are no foreseen fiscal impacts associated with the adoption of this resolution.

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

      Approval of the proposed resolution will not impact security, stability or resiliency issues relating to the DNS.

      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?

      On 29 April 2013, ICANN initiated a public comment forum to solicit input on the proposed final draft of the New gTLD Registry Agreement. The public comment forum closed on 11 June 2013.

      On 14 June 2013, the GNSO Policy Development Process Working Group tasked with addressing the issue of protecting the identifiers of certain IGOs and INGOs in all gTLDs published its Initial Report for public comment. The public comment period is scheduled to close 7 August 2013. <http://www.icann.org/en/news/public-comment/igo-ingo-initial-14jun13-en.htm>

Published on 18 July 2013

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