The ICA Comments on ICANN Preliminary Issue Report on IGOs and INGOs

Phil Corwin of the ICA has sent a comment to ICANN regarding the Preliminary Issue Report on Access by IGOs and INGOs to the Curative Rights Protections of the UDRP and URS.

In that report, the staff recommended the GNSO Council initiate a PDP (Policy Development Process) to see if they should modify the UDRP and URS process so that IGOs and INGOs could access these as to basically go after their acronyms at the sld level. This could subject legitimate domain owners to having to engage in a legal battle to keep a domain that is an acronym for an Intergovernmental Organization.

The ICA wrote back in December,

Yesterday ICA filed a letter that generally supported the GNSO Council’s recent and unanimously adopted Resolution on Protections for International Governmental and Non-Governmental Organizations (IGOs & INGOs). In particular, while supporting strong protections for exact matches of their full names at the top and second level of the DNS, we were pleased that the Resolution did not grant undue protections to acronyms of their names, and did not put existing acronyms at incumbent gTLDs at unreasonable risk.

But it turns out that ICA was the only organization to file a supportive comment in the initial comment round (the reply period is now open until January 8th) – and that the UN has coordinated a flood of letters (found at, all protesting that the Resolution does not go far enough to protect those acronyms. Besides the UN, such organizations as NATO, WIPO (which is a UN agency), and Interpol say it doesn’t do enough to prevent potential misuse of those acronyms, especially at new gTLDs.

ICA last weighed in on this issue in mid-October (see when we noted that some proposals would go so far as barring the registration of common acronyms such as idea, eco, imo, iso, and au, as well as adversely affecting their existing counterparts at incumbent gTLDs. We proposed a more reasonable approach that is in many ways reflected in the GNSO-adopted resolution.

But that doesn’t begin to go far enough for the UN and the IGOs and INGOs it has rallied to its cause. Indeed, their position takes a harder line than ICANN’s own Governmental Advisory Committee (GAC). The GAC’s Buenos Aires Communique ( addressed this issue by requesting a dialogue with the New gTLD program Committee (NGPC) on a final modality for permanent protection of IGO acronyms at the second level, through a notification system that would allow for timely intervention to prevent misuse and confusion through a no or nominal cost system that provided for a final binding determination by a third party. That’s fairly consistent with ICA’s position, as we have no objection to allowing IGOs and INGOs to make use of the UDRP and URS, although we have reservations about placing their exact names in the Trademark Clearinghouse (TMCH) database until changes are made in the Trademark Claims Notice generated by attempts to register matches – and we don’t support placing their acronyms in the TMCH.

Regardless of the legal or technical merits, the mass of comment filings against the GNSO Resolution has just converted this into yet another politically charged hot potato that needs to be resolved by the ICANN Board. Will the GAC now take on a tougher stance under pressure from these IGOs and INGOs? And, in an approaching year when the debate between the choice of a multistakeholder versus a multilateral model of Internet governance will take center stage at the spring Sao Paulo meeting and the fall ITU session, how will the ICANN Board balance considerations of defending the unanimous multistakeholder position of the GNSO Council versus the need to garner multilateral support for ICANN itself?

In their letter to ICANN back in October, the ICA was clear to point out that many of these acronyms are valuable domains, that the registrants have legitimate rights to the names and that there is no infringing or confusion with any IGO or INGO mark.

Here is the December letter:

Re: Protection of IGO and INGO Identifiers in All gTLDs (PDP) Recommendations for Board Consideration

 Dear ICANN:

I am writing on behalf of the members of the Internet Commerce Association (ICA). ICA is a not-for-profit trade association representing the domain name industry, including domain registrants, domain marketplaces, and direct search providers. Its membership is composed of domain name registrants who invest in domain names (DNs) and develop the associated websites, as well as the companies that serve them. Professional domain name registrants are a major source of the fees that support registrars, registries, and ICANN itself. ICA members own and operate approximately ten percent of all existing Internet domains on behalf of their own domain portfolios as well as those of thousands of customers.

This letter addresses the “Protection of IGO and INGO Identifiers in All gTLDs (PDP) Recommendations for Board Consideration”   posted for public comment on November 27th[1]. We are specifically commenting upon the Resolution[2] unanimously adopted by the GNSO Council on November 20th when it approved the consensus recommendations of the IGO-INGO PDP Working Group. Following this comment period those recommendations will be considered by the ICANN Board.

Executive Summary

The ICA is generally supportive of the Resolution adopted by the GNSO Council – with the exception of certain recommendations relating to the inclusion of exact matches and acronyms in the Trademark Clearinghouse database.

We are also gratified that the recommendations do not adopt a hostile position toward acronyms of the encompassed organizations that are registered at the second level of existing gTLDs.


The ICA filed comments[3] on October 11, 2013 in regard to the Draft Final Report on Protection of IGO and INGO Identifiers in All gTLDs.

The positions we took in that prior comment letter can be summarized follows:

  • In regard to the top level of new gTLDs, we generally favor full protection for exact matches of the full name of all the IGOs and INGOs addressed by the Report by barring their registration by third parties — but we oppose such blanket, registration-blocking  protection of exact matches of their acronyms.
  • In regard to the second level of new gTLDs, we generally favor full protection through registration blocking for exact matches of the full name of all IGOs and INGOs addressed by the Report  — but we oppose blanket protection of exact matches of their acronyms as any misuse could be addressed by existing second level dispute resolution arbitration procedures.
  • In regard to the Trademark Clearinghouse (TMCH), which is only relevant to new gTLDs — we would support inclusion in the TMCH of exact matches of the full name of all the IGOs and INGOs addressed by the Report – but only if the Trademark Notice generated by an attempt to register such a name differentiates between trademark rights and the “rights” held in such name by an IGO or INGO that has not trademarked its name.
  • We oppose inclusion in the TMCH of the exact matches of acronyms of all the IGOs and INGOs addressed by the Report. We do not oppose allowing affected organizations to utilize the curative rights of the UDRP (at new or incumbent gTLDs) or URS (only available at new gTLDs at this time) dispute resolution arbitration mechanisms if they believe that a particular domain using such exact match has been registered and used in bad faith; that is, in such a manner as to deceive and mislead the public that the particular website is being operated by or has been endorsed by the relevant IGO or INGO.

    Finally, in regard to any incumbent gTLD, while we appreciate and support the Recommendation that any currently  registered domain matching a protected IGO or INGO identifier “shall be handled like any existing registered name within the incumbent gTLD regarding renewals, transfers, sale, change of registrant, etc.”, we strongly oppose the adoption of any policy that would:

  • Define or create a mechanism against the specious and completely speculative possibility of “front-running” of domain registrations of IGO or INGO identifiers.
  • Exclude such a domain from any add/drop activities by the registrar in the event it becomes eligible for deletion, or make such deleted domains ineligible for future re-registration.
  • In any way sanction the involuntary seizure or deletion of any identifier exact match acronym domain that is registered now or may be in the future at any incumbent gTLD.

    When we compare our previously stated positions with the recommendations that were unanimously adopted by the GNSO Council, we:

  • Support the recommendation for protection of the Red Cross/Red Crescent (RCRC) at the top and second level – with the exception of including full names and acronyms in the TMCH database.
  • Support the recommendations for protection of the International Olympic Committee (IOC) at the top and second level.
  • Support the recommendations for protection of International Governmental Organizations (IGOs) at the top and second level – with the exception of including their acronyms in the TMCH database.
  • Support the recommendations for protection of International Non-Governmental Organizations (INGOs) at the top and second level – with the exception of including exact matches of their full names in the TMCH database.
  • We support the recommendation that, at the top level, acronyms of the RCRC, IOC, IGOs and INGOs shall not be considered as “Strings Ineligible for Delegation”; and at the second level, acronyms of the RCRC, IOC, IGOs and INGO under consideration in this PDP shall not be withheld from registration.
  • We do not oppose the recommendations applicable to existing gTLD registries that they shall accommodate similar protections at the second level for the exact match, full name of the RCRC, IOC, IGOs, and INGOs – and are gratified that these protections do not apply to acronyms.
  • We support the initiation of an Issue Report to consider the amendment of existing policies “so that curative rights of the UDRP and URS can be used by those organizations that are granted protections based on their identified designations” as a preceding step to a Policy Development Procedure (PDP) on this issue – so long as the Issue Report fully considers the perspective of the domain investment community.
  • We have no objection to the establishment of “an IGO-INGO Implementation Review Team (IRT) to assist ICANN staff in developing the implementation details relating to the recommendations adopted herein should they be approved by the ICANN Board” — but strongly urge that any such IRT should include qualified members or representatives of the domain investment community so that their expertise can contribute to fully informed consideration of reasonable and effective implementation steps.

    Further explaining our position in regard to the inclusion of full names and acronyms in the TMCH database, we can only support inclusion of full names of the encompassed organizations in its database if the currently flawed Trademark Claims Notice is amended to differentiate between trademark rights and the “rights” held in such name by an IGO or INGO that has not trademarked its name. We oppose the inclusion of non-trademarked acronyms as the TMCH is supposed to be a reliable database of high quality trademarks. The issue of making the UDRP and URS available for non-trademarked acronyms can be addressed in the Issue Report referenced above.


    We hope that ICANN finds our views on this matter to be useful and informative. We look forward to contributing to the Issue Report, PDP, and IRT referenced above.

In addition to the ICA, George Kirikos left a comment expressing his oppostion to the latest report. You can read his comments along with those of a few others here

The link to the ICA pdf is located on their comment for your complete review.


Comment Policy: welcomes reader comments. Please follow these simple rules:

  • Stay on topic
  • Refrain from personal attacks
  • Avoid profanity
  • Links should be related to the topic of the post
  • No spamming. Listing domains, products, or services will get the comment deleted

We reserve the right to remove comments if we deem it necessary.

Join the Discussion