Kevin McGillivray*


The Internet Corporation for Assigned Names and Numbers (“ICANN”) has implemented an ambitious programme to expand the domain name system. The programme will make available new generic-Top-Level-Domain names (“gTLDs”). New gTLDs, the letters after the last dot in a web address (i.e. <.org>), will be available to applicants able to meet ICANN’s demanding application requirements. As part of the expansion, ICANN has drafted a guidebook (“AGB”) providing the rules and standards for obtaining a new gTLD. The AGB includes dispute resolution measures aimed at protecting parties with existing legal rights in the expansion process. The following paper considers the dispute resolution systems in the AGB for objecting to or blocking new gTLDs. The AGB contains systems for resolving disputes prior to the launch of a gTLD, and after a gTLD has been issued. The focus of this article is largely on the rights of parties to challenge new gTLDs during the application process, prior to delegation or “launch” of a new gTLD.

Cite as: K McGillivray, “Anticipating Conflict—An Evaluation of the New gTLD Dispute Resolution System”, (2012) 9:2 SCRIPTed 195

Download  options Description: pdficon

DOI: 10.2966/scrip.090212.195

© Kevin McGillivray 2012.

Creative Commons License

This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 2.5 UK: Scotland License.

1. Introduction

After much discussion, planning, and conflict, the Internet Corporation for Assigned Names and Numbers (“ICANN”) has implemented a programme with the potential to greatly expand domain name offerings on the Internet. Expansion of generic-Top-Level-Domain names (“gTLDs”), the letters after the last dot in a web address (i.e. <.com>), has been a long-term plan of ICANN. ICANN’s goals of increasing competition, fostering innovation, and providing users with greater choice are some of the central reasons for making available new gTLDs.[1] The expansion of gTLD offerings is interesting to brand owners, communities, and trade associations, among others. The new gTLD expansion has also been a source of concern for trademark owners and other rights holders.

Securing a new gTLD will require an extensive application process and considerable capital.[2] The requirements for obtaining a new gTLD are provided for in the Applicant Guidebook (“AGB”), which has been drafted by ICANN to provide the “rules of the road” for the upcoming launch.[3] The rules provided in the AGB include guidelines for applicants, costs, and clarification of much of the new gTLD delegation process.[4] Among other systems designed to protect parties and limit risks to users, the AGB provides a system for resolving disputes. In an attempt at effective dispute resolution, the AGB provides for both ex ante and ex post dispute resolution procedures for new gTLDs.

In this paper, the focus is largely on the rights of parties to challenge new gTLDs during the application process, prior to delegation or “launch” of a new gTLD. Specifically, the paper provides analysis of “Module 3” of the AGB, which contains the AGB’s objection-based system for dispute resolution. The paper considers the present launch in the context of past expansions, concerns and tensions in the current expansion, and provides some comparison to systems of online dispute resolution currently being used. The paper further evaluates the standards and procedures provided for in the dispute resolution procedure contained in Module 3 of the AGB. This evaluation considers practical aspects of the available objections and attempts to predict the challenges they may present in expanding domain names.

2. Background: The Domain Name System

On the Internet, computers find each other using a string of numbers known as an Internet Protocol (“IP”) address.[5] IP addresses are essential to routing packets of data over the Internet.[6] The Domain Name System (“DNS”) operates based on a hierarchy of names and acts as a central system for routing traffic on the Internet.[7] The well-worn, but useful analogy is that the DNS system operates as the Internet’s phonebook. Internet users can find the IP address they need by locating the corresponding domain name.

By typing a domain name into a browser, an Internet user is able to locate websites with words or phrases instead of numbers. Although domain names are not essential for finding locations on the Internet, they do provide for a more user-friendly method of navigation.[8] For example, to access the search engine Yahoo® an Internet user has the option of entering either <> or <>.[9] A top-level domain (“TLD”) refers to part of a web address making up the two or more letters after the last dot.[10] For example, in the address <>, <.com> is the TLD. A second-level domain (“SLD”) name is directly to the left of the TLD, for example <>.[11] Traditionally, the second level has been the section of a domain name where a trademark such as Nike® is displayed (i.e. <>). However, a trademark may also be placed at the Third Level Domain (“thLD”) (i.e. <>).

Currently, available open gTLDs, among others, include <.com>, <.net>, and <.org>.[12] Not all gTLDs are open. For example, <.gov> is limited to the US government.[13] Specialised or “sponsored” top-level domain names like <.pro> or <.jobs> represent a specific community and are only available to qualifying applicants.[14] In addition to gTLDs, country code Top Level Domains (“ccTLDs”) are also available. There are currently 250 ccTLDs while there are only twenty-two gTLDs.[15] Unlike gTLDs, the use and terms of ccTLDs are controlled, to a certain extent, by agencies in individual countries.[16] Countries with catchy abbreviations, like <.co> (Columbia) and <.tv> (Tuvalu) have made their ccTLDs available for registration by private parties located outside of their boarders.[17]

Like the IP numbers they represent, domain names must also be unique. The more memorable or well known a domain name is, the more valuable it generally becomes.[18] Domain names may also have significance outside of their commercial application for culture, language rights, and multilingualism on the Internet.[19] New gTLDs, along with Internationalized Domain Names (“IDNs”), could provide new avenues for cultural and linguistic expression.[20]

Domain names corresponding with well-known or famous trademarks are highly sought after by both trademark owners and parties wishing to profit from the notoriety or recognition of the trademark.[21] As many facets of the modern economy continue to move online, a company’s domain name, which is often at the core of its online image, has become an increasingly important asset.[22] Although domain names are still available in existing gTLD registries, much of the beachfront property is occupied.[23] Therefore, ICANN has decided it is time to create a bigger beach.

3. ICANN and the Domain Name System

ICANN is a private, not-for-profit entity.[24] Much of ICANN’s authority over the Internet is derived from contracts or other agreements with the United States Government (“USG”).[25] In addition to other functions, ICANN plays a central role in the coordination and management of the Domain Name System.[26] In its role as coordinator of the DNS, ICANN has expanded domain names in the past. In the following section, I consider past gTLD expansions and discuss the focus in the current round.

Although ICANN does not distribute domain names directly to users, it does determine the TLDs that will ultimately be made available for distribution.[27] ICANN makes its decisions based on the input of a wide community consisting of private Internet users, businesses, governments, and an array of commercial and non-commercial interests.[28] ICANN’s bottom-up, Multi-Stakeholder Model is a core principle of governance and is acknowledged in important USG/ICANN agreements like the Affirmation of Commitments (“AOC”).[29] Consistent with the Multi-Stakeholder model, ICANN has incorporated advice and comments from its broad base of stakeholders into the gTLD programme.

As a result of ICANN’s ability to determine available gTLDs, it plays an essential role in the evolution of the Internet.[30] By determining the TLDs available, ICANN controls, to a large extent, what the Internet will ultimately look like to users. There are currently over 200 million domain names.[31] What the next 200 million look like may be significantly affected by the current expansion.

3.1 Expansion of gTLD Names

ICANN has expanded gTLD offerings on two prior occasions.[32] The first gTLD expansion occurred in 2000 and included the gTLDs <.biz> and <.info>, in addition to others.[33] There was excitement regarding some of the proposed gTLDs, particularly <.biz>.[34] The new gTLD <.biz> was seen as a possible rival to <.com>.

In the 2000 round, the ICANN board considered forty-four applications for gTLDs, ultimately accepting seven of them.[35] The process was described as “complex, expensive, and somewhat mysterious.”[36] In one article, the authors described the 2000 process as “no way to make law, sausage or domain name policy.”[37] Among other criticisms of the process, gTLD applicants had very little time to review staff recommendations and it was claimed that “the Board’s discussion was based on trivial factors, such as whether a gTLD string was ‘pronounceable.”[38] ICANN’s failure to provide a more systematic approach, which would have included rules that were clear and available to gTLD applicants, created problems in the 2000 round. Thus it was necessary to take a more measured and orderly approach in future expansions.

A second gTLD expansion took place in 2004. The 2004 expansion was largely aimed at sponsored gTLDs, that is, domain names with restrictive eligibility requirements.[39] The new gTLDs were targeted at specific groups by using gTLDs such as <.travel> or <.pro>.[40] Although the 2004 round certainly added some choice, new gTLD names like <.museum> never quite took off.[41] There was also considerable discussion and protest over the gTLD <.xxx>, which was aimed at adult themed websites.[42] Although <.xxx> was not accepted during the 2004 round, the name was ultimately cleared for use in 2011.[43]

As early as 2005, the Generic Names Supporting Organization (“GNSO”) began discussing an open round of gTLD expansion. In October 2007, the GNSO completed its policy development work on new gTLDs.[44] On 16 June 2008, ICANN formally announced that it would allow new gTLDs and began preparations for the expansion.[45] The first version of the AGB was published for public comment in October 2008.[46] In the following three years, ICANN continued to release various drafts of the AGB. The most recent version of the AGB was released on 4 June 2012.[47]

A clear divergence from earlier rounds is the scope of the current procedure. Unlike the 2000 and 2004 rounds, it is expected that hundreds of new gTLDs may be created. As noted by one author, it “has been one of the most contentious and longest running disputes at ICANN.”[48] Unlike the 2000 and 2004 rounds, with pre-determined offerings, the current “wide-open” expansion has brought with it a measure of concern, particularly for trademark holders and brand owners.[49]

Based on the comprehensive AGB, the current round provides increased structure compared to the 2000 round. Moving from a system of pre-defined offerings to wide-open gTLDs should also allow for increased opportunity compared to the 2004 expansion. However, this is not guaranteed. Even with a high level of applicants, the number of new gTLDs that are able to survive the application process may be substantially restricted, depending on how broadly objections to new gTLDs are applied.

For businesses and individuals that missed out on the domain name of their choice, the expansion may also provide something of a second chance for a stronger online presence.[50] Applicants may also be interested in entering registry or registrar markets. Parties able to secure a popular gTLD will have an opportunity for increased SLD name sales.[51] Companies that secure their own TLD domain will no longer have to fight to obtain their domain name of choice for advertising campaigns. In short, new gTLDs have the potential to provide the right applicants with substantial benefits.

4. Application of the gTLD Dispute Resolution Procedure (DRP)

4.1 Introduction

Minimising conflict by design has been a central theme in the creation of the new gTLD application process. This section considers the new dispute resolution procedure provided for in the AGB. Based on its experiences during the gTLD expansions of 2000[52] and 2004,[53] ICANN gained insight into the legal, technical, and political conflicts inherent in creating new gTLDs. As a result, ICANN is arguably in a better position to implement an effective dispute resolution system in the current round. In the following section I provide an overview of the new gTLD application process, with a particular focus on the dispute resolution aspects provided for in Module 3. In evaluating the Module 3 systems, some comparison to the ex post approach taken by the Universal Dispute Resolution Policy (“UDRP”) is valuable.[54] Discussion of some of the similarities (and differences) between the UDRP and the Module 3 dispute resolution system is included in this section.

4.2 Overview of the New gTLD Procedure

The new gTLD programme will allow applicants to apply for a gTLD during specified time periods or rounds. The first round of applications opened on 12 January 2012 and closed on 30 May 2012, receiving over 1900 applications.[55] Applicants seeking a gTLD had the option to apply with either a “standard” or a “community based” application.[56]

In order to obtain a new gTLD there are several hurdles that must be cleared. Many of the challenges are common to both gTLD application types. First, applications for new gTLDs must pass a rigorous administrative check. Applicants must also pay an $185,000 application fee.[57] Applications that pass the administrative check will then be posted on the ICANN website for public comment.[58] The comment period allows members of the Internet community, without any specific interest, to raise concerns regarding new gTLDs. In addition to general comments, applications may receive an “Early Warning notice” from ICANN’s Governmental Advisory Committee (“GAC”).[59] ICANN will also consider factors like general business diligence and criminal history.[60] Following the comment period and background screening, ICANN will conduct its Initial Evaluation (“IE”) of gTLD applications.[61] In conducting the IE of new gTLDs, the reviewing body will consider a variety of issues surrounding the application including similarity to existing applications, DNS stability, and use of geographic names.

After the results of the IE are announced, parties have approximately seven months to make formal objections.[62] In addition to paying required fees, there are two basic procedural requirements for making a formal objection.[63] First, the objection must be timely. Second, the objecting party must have standing.[64] The standing requirements perform three functions which are determining general eligibility to make an objection, the objections available to a party, and the dispute resolution service provider that will consider the objection.[65] The four grounds for an objection include: String Confusion, Legal Rights, Limited Public Interest, and a Community Objection.[66] In addition to objections based on specific rights, ICANN has added a “GAC Advice on New gTLDs” procedure to Module 3. The GAC objection provides GAC members the opportunity to make a formal (or equivalent) objection, even though they would not meet general standing requirements set out in Module 3.[67] In addition to the objections generated by private parties or organisations, ICANN will select an Independent Objector (“IO”) to make objections based on “the best interests of the public who use the global Internet.”[68]

During objection proceedings, the objecting party bears the burden of proof.[69] Claims available to a third-party are dependent on the legal rights of the objecting party. If a third-party has a sufficient basis for an objection on more than one ground, they may include a combination of objections, or even make multiple objections arising from the same circumstances. However, the objections must be made to the appropriate provider. Although the policy has been developed by ICANN, private dispute resolution service providers (“DRSPs”) will carry out proceedings based on formal complaints.[70]

If an objection is successful, the new gTLD will be ineligible for further review and will not be issued.[71] For the party applying for a new gTLD, this determination is dispositive. There is no appeal at this step of the process. The party seeking a new gTLD may apply again in future rounds. For the party making the objection, the dispute resolution is only one of several available measures to protect their rights. If the objector does not succeed with their opposition to a new gTLD at the application stage, affected parties will still have UDRP and other Rights Protection Measures (“RPMs”) available.[72] However, after the gTLD is issued, absent abuse of the gTLD, there is no clear avenue for the objecting party to stop or “block” the new gTLD from proceeding.[73]

4.3 UDRP and the New gTLD Dispute Resolution Procedure

In 1999, ICANN drafted the UDRP as a means of combating cybersquatting and quickly resolving disputes over domain names.[74] Although the UDRP and the new gTLD dispute resolution process have procedural and substantive differences, the UDRP provides a useful comparison when evaluating aspects of the new gTLD system. The UDRP has been widely used to adjudicate domain name disputes and uses standards that are similar to those in the new gTLD programme.[75] All new gTLD applications are subject to the objection-based dispute resolution procedure in Module 3 of the AGB.[76] ICANN’s authority to require both the UDRP and the new gTLD dispute resolution procedure is derived from its monopoly over the DNS.[77] ICANN’s “jurisdiction” over UDRP domain name determinations and new gTLD resolutions is essentially contractual.[78]

Both systems provide a form of online arbitration among other common factors.[79] For example, both procedures are drafted in a concise manner and provide a specific and limited remedy.[80] Under the UDRP, the remedy is limited to cancellation or transfer of the domain name.[81] Pursuant to the new gTLD procedure, the remedy is limited to blocking a new gTLD.[82] Additionally, both systems have a simple substantive structure. As designed, the new gTLD system, like the UDRP, is intended to allow access to unsophisticated parties or those without legal representation.[83] Both systems use private dispute resolution service providers instead of court systems. Both processes are relatively condensed and provide the parties with rather short timeframes to respond to complaints. In the case of the Module 3 policy, the respondent’s time frame is thirty days, while the UDRP only provides the respondent with twenty days to answer.[84]

The UDRP policy also significantly differs from the Module 3 policy provided for in the AGB. One such difference is the time the objections are made available. Unlike the UDRP, the new gTLD proceedings in Module 3 take place prior to the domain name being issued. At the point the Module 3 proceedings may be utilised, the applicant has not been granted use of, or any rights to a new gTLD. The UDRP policy considers complaints under a different distribution system. Unlike the Module 3 process, the UDRP does not consider domain names that are subject to a pre-approval. Stated differently, the second-level domain name being challenged pursuant to the UDRP has already been issued, on a first-come-first-served-basis.[85]

The cost of obtaining a new gTLD is significantly higher than that of a SLD name under an existing gTLD.[86] As a group, those able to afford a new gTLD are likely to have greater financial and legal resources available. Under the UDRP, if a party does not agree with the decision rendered by a dispute resolution provider, they have the option of pursuing the matter in court on a de novo basis.[87] The Module 3 process does not allow for de novo review. In that regard, the decision from the DRSP is final.

The Module 3 gTLD process and the UDRP are not mutually exclusive or separate processes in the life of a new gTLD. In the case of new gTLDs, the UDRP will also be applicable. However, by allowing objections early in the process, ICANN has provided interested parties with the means to protect intellectual property interests prior to infringement. Although drawing on some of the properties of the UDRP, the Module 3 process remains distinct. In the following sections I consider the individual objections themselves as provided for in the new gTLD process. Where appropriate, comparisons to and analysis of the UDRP takes place.

5. Objection Based on Confusion between Potential gTLD “String” and an Existing or Applied-for gTLD

Of the four objections provided for in the Module 3 procedure, there are two that are particularly relevant for trademark holders.[88] The first of these is the “string confusion objection.” The objection will allow certain right holders to contest an applied for gTLD string. In this section I consider the role of the objection, the legal standard used, and the impact it may have on the overall availability of new gTLDs.


During the initial background screening, ICANN will check gTLD applications for string similarity.[89] The string similarity review will use an algorithm that is designed to help ICANN flag applications for removal that fail to meet minimum gTLD requirements.[90] For example, gTLDs that compromise DNS stability or use geographic names without proper authorisation will not move forward for further consideration.[91] Although the review may limit obvious problematic applications, background screening will not weed out all confusing potential gTLDs. For example, clever spellings or code words may escape the string similarity review. In anticipation of this shortcoming, ICANN has developed a system for interested parties to object to confusing applications based on their similarity to existing or applied for gTLDs.[92]


Standing to object to gTLDs that are confusingly similar is limited to current gTLD operators and applicants applying for a gTLD in the same round of applications.[93] A string confusion objection may be based on confusion between an applied-for gTLD and a currently operating gTLD.[94] If an existing gTLD operator is successful with their objection, the application will be rejected.[95] If, on the other hand, the complainant is another gTLD applicant, the application will be placed in a “contention set” and will be subject to procedures covered in Module 4 of the AGB.[96] If a new gTLD enters a contention set, the four possible outcomes are: (1) the withdrawal of the application, (2) contenders conduct private dispute resolution including mediation, (3) a determination based on community priority is made, or (4) an auction provides the name to the highest bidder.[97]


Both the procedural and substantive rules governing string confusion objections can be found in Module 3 of the AGB. In an attachment to Module 3, the AGB provides the procedure to be applied by dispute resolution service providers (“DRSPs”).[98] In the case of a string confusion objection, the International Centre for Dispute Resolution will adjudicate complaints.[99] Pursuant to Module 3 of the AGB, the grounds for a string confusion objection are where “[t]he applied-for gTLD string is confusingly similar to an existing gTLD or to another applied for gTLD string in the same round of applications.”[100] The standard for prevailing on a string confusion objection is where “a string so nearly resembles another that it is likely to deceive or cause confusion.”[101] The AGB further requires that it is “probable, not merely possible that confusion will arise in the mind of the average, reasonable Internet user.”[102]


Mere association with another string will not be sufficient to support a finding of string confusion by a dispute resolution service provider.[103] This is for two main reasons. First, the AGB requires that in addition to being “confusingly similar,” the confusion must be “likely.”[104] Second, the AGB provides an objective measure, “the reasonable Internet user,” to determine whether the likelihood of confusion is great enough that it is “probable” rather than simply “possible” that confusion will take place.[105] Likely confusion, in the eyes of “the reasonable Internet user” to an existing or applied for gTLD is sufficient for the objecting party to prevail.


The “confusingly similar” standard is widely applied in trademark law and domain name disputes. The US Anti-cybersquatting Consumer Protection Act creates a cause of action for “bad faith” registrations that are “confusingly similar” to a trademark.[106] The UDRP uses a similar standard and allows transfer of a domain name that is “identical or confusingly similar to a trademark or service mark….”[107] However, for a complainant to prevail under the UDRP; the objector must also show the registrant has no legitimate interest in the domain name and that the name is registered in “bad faith.”[108] The adoption of a simplified “confusion test” for evaluating domain names, particularly in the UDRP, has not been without criticism. As stated by one author:

This rule [the confusion test] is ‘borrowed’ and is in conformity with the language used in traditional trade mark law statutes; however, the way it is interpreted and applied departs significantly from the way it is used by courts and tribunals. A combination of lack of direction on behalf of ICANN—as the administrator of the Policy—and of the World Intellectual Property Organization (WIPO)—as the mastermind behind its inception and an accredited dispute resolution provider— have twisted the ‘confusion test’ to its core.[109]

Whether adoption of a similar test for evaluating new gTLD applications, and application of the test by the DRSP will result in similar inconsistencies or problems is an important point for consideration.[110] This is particularly so if the standard is taken out of context or applied in an oversimplified manner.[111] In the US, infringement of a trademark is based on “whether trademark is such ‘as to be likely, when used on or in connection with the goods of such other person, to cause confusion, or to cause mistake, or to deceive.’”[112] Thus, the “likelihood of confusion” standard also considers how a mark is used, not just its similarity to other marks, before finding a basis for infringement.[113] Some UDRP providers, following the US approach, have applied a similar test when determining whether a domain name is confusingly similar pursuant to UDRP Art. 4(a)(i).[114] In the current AGB, the legal standards are combined. The AGB standard blends the “likelihood of confusion” standard with the “confusingly similar” standard.[115] It is unclear whether the blending of the legal standards will have any effect on the procedural or substantive rights of the parties seeking dispute resolution.


The “confusingly similar” standard and the “likely to deceive or cause confusion” set forth in the AGB are not the same legal standard.[116] Lack of clarity regarding the standard to be applied could be a potential barrier to releasing new gTLDs.[117] Under a broad reading of “confusingly similar” it will be difficult for new gTLDs to overcome objections, even if the services or products they offer are different from those offered by the objecting TLD operator.[118] However, requiring that the confusion is likely should allow a greater widow for obtaining new gTLDs.


The AGB provides some additional guidance for dispute resolution providers in determining names that are “likely to deceive or cause confusion.”  By including an objective “average, reasonable Internet user” standard for determining “probable confusion,” ICANN has provided an avenue for DRSPs to avoid removing applications based solely on their similarity with existing gTLDs.[119] What an “average, reasonable Internet user” is, on an objective basis, is not abundantly clear. The Internet is accessible the world over, extremely international, and its users vary considerably. Effectively creating and applying a standard that objectively defines the “average, reasonable Internet user” is therefore challenging. Like other objective “reasonable person” standards, it may be difficult to assign characteristics that adequately define what is “reasonable” or expected of an Internet user.


It has been noted that during UDRP proceedings, a “significant minority of panels assume that the meaning of the phrase ‘confusingly similar’ is identical with the traditional, ‘likelihood of confusion’ analysis in trademark law.”[120] Although the confusingly similar standard applied in the UDRP considers misuse of trademarks and the present objection evaluates confusion between applied for and existing gTLDs, the experience of new gTLDs could very well be similar. That is to say, even if the underlying basis of objection diverges, the experience of the UDRP may be a strong predictor of the experience with new gTLDs. Like the UDRP, the AGB has also borrowed legal concepts and terms commonly found in trademark law. Even with the blending of legal standards in application of the UDRP, based on the limited studies available, parties have not regularly sought a de novo review in a court following the decision of a dispute resolution provider.[121] Notwithstanding the UDRP confusion test, SLDs have still been obtainable. It is therefore unlikely that the blending of legal standards in the AGB will stem the flow of available words or phrases suitable for new gTLDs.


If an existing gTLD operator is successful with their objection, the application for the confusingly similar gTLD will be denied. However, if the party objecting is another applicant for a new gTLD, both applications will “be placed in a contention set,” and will be subject to the contention set resolution procedure.[122] The situation where a party has the potential to make overlapping objections, based on their legal rights, could also occur.[123] In the context of trademarks, the legal rights objection considered in the next section may provide for an additional objection.

6. Legal rights objection

6.1 Introduction

Like previous rounds of gTLD expansion, not all groups with an interest in the Internet have welcomed the proposition of expanded offerings.[124] Advocates from the business community, trademark holders, and governments via the Governmental Advisory Committee (“GAC”) have voiced concerns regarding the potential negative impact of new gTLDs.[125] Many trademark holders assume that the expansion of domain name offerings will equal a greater number of infringements.[126] After expending a great deal of resources to secure their domain names and online identities, trademark and brand owners are concerned that new gTLDs will bring with them new expenses including those involved tackling increased levels of cybersquatting.[127]

In the following section I consider the legal rights objection, which has been designed to protect legal rights prior to the issuance of a new gTLD. The boundaries of what should be considered a legal right are not entirely clear. Much of the discussion has been focused on traditionally protected groups, like trademark holders. However, Module 3 also will also consider objections for an “[intergovernmental organisation] name or acronym.”[128]

6.2 Input on Protecting Trademarks

Protecting the legal rights of trademark holders was a clear goal in creating a system for gTLD expansion. However, the policy objectives of trademark owners had to be considered in the context of other competing policy interests. Groups representing trademark holders were active in aspects of planning the dispute resolution procedures and Rights Protection Measures (“RPMs”).[129] The Implementation Recommendation Team (“IRT”), a group largely representing trademark interests, provided significant input and helped to design systems for protecting trademark holders on both a pre- and post-launch basis.[130] In addition to the information provided by the IRT, input from those not representing trademark interests was also considered. The Special Trademarks Issues Working Team (“STI”) evaluated the report created by the IRT and accepted many of the IRTs recommendations, with some alterations.[131] Although both sides had input in the drafting process, there was discontent with the result from both constituencies.[132]

In the present gTLD expansion, the protection of trademarks at both gTLD and SLD levels has been a central goal. At the gTLD level, infringement could occur if a new gTLD uses a trademarked word or phrase like <.coke>, resulting in an infringing gTLD. At the second-level, trademark owners are concerned that infringing SLD names will be registered under the new gTLDs. This would occur where a new gTLD was approved under the application process, but an infringing second-level domain name was subsequently awarded (i.e. <>).

Businesses have also argued that in addition to the increased policing of improper registrations, they will be required to undertake an unprecedented number of “defensive registrations” to protect their trademarks and online image.[133] Those opposed to the new gTLD programme argue that new gTLDs will bring with them significant operating costs, which will ultimately be carried by consumers.[134] In testimony before a US congressional committee, Mei-lan Stark, of Fox News Corporation, stated that as a result of the new gTLDs, protection of their brand might cost as much as “$12 million in the initial stages alone.”[135] Even if the protections are effective, a position that is not universally accepted, they will be expensive to utilise.[136]

Potential expenses for protecting trademark holders are often difficult to ascertain. Although business representatives assert that the cost will be substantial, actual estimates vary widely. For example, one study projects the costs resulting from new cases of cybersquatting to trademark owners will be as low as $.10 per trademark, per year, for trademarks registered on a worldwide basis.[137] ICANN’s studies on the economic impact of new gTLDs have thus far been inconclusive. In one such report, ICANN simply stated that “[n]one of the studies were able to specifically quantify projected net benefits, stating, among other things, that innovation was difficult or impossible to predict, as was the effectiveness of the many cost mitigation tools being implemented along with the program.”[138] This is, at least in part, due to the difficulty in determining how consumers will react to the expansion. The threat of new gTLDs to existing domain names largely depends on the success of new gTLDs. The prime gTLD space may well remain at <.com>.[139] If the new gTLDs are not used, any threat they pose to trademark holders will likely to be reduced.[140]

6.3 Applying the Legal Rights Objection

The AGB provides trademark holders and others with the ability to object to new gTLDs that may infringe their existing legal rights.[141] To establish standing under the objection, the objecting party must have a legal right that will be infringed by the new gTLD.[142] Trademark holders, for example, will have the opportunity to object to an applied for gTLD that infringes on their trademark.[143] The objecting party may be the holder of a registered or unregistered trademark, or a service mark.[144] If the objector is successful, the new gTLD will not be issued. Unlike the “string confusion objection,” the legal rights objection does not include contention set proceedings.


The Module 3 standard states that new gTLDs “must not infringe the existing legal rights of others that are recognised or enforceable under generally accepted and internationally recognized principles of law.”[145] In particular, the rules require that the applied for gTLD must not take unfair advantage of the “distinctive character” or “reputation of” the objector’s trademark or other legal rights.[146] If an objection is based on a trademark right, the DRSP must consider a list of non-exclusive factors in reaching its determination.[147] The Arbitration and Mediation Centre of the World Intellectual Property Organization (“WIPO”) will handle all legal rights objections.[148]


The factors the DRSP will consider include general indicators such as likeness in appearance, sound, or meaning to the objector’s mark.[149] In addition to more traditional characteristics associated with trademark infringement (i.e. use of the mark), a dispute resolution provider must also evaluate additional more subjective or abstract factors, including the intention of the applicant. For example, the dispute resolution provider may also consider “whether the applicant, at the time of application for the gTLD, had knowledge of the objector’s mark, or could not have reasonably been unaware of that mark….”[150] As the gTLD applicant will not have had the opportunity to use the gTLD in commerce prior to the evaluation, factors indicating intent may be of increased importance. The DRSP will also consider whether use of the proposed gTLDs “would create a likelihood of confusion with the objector’s mark.”[151] Additional factors such as the applicant’s interest in the name and preparations made to use the gTLD, if granted, will also be taken into account.[152] Additionally, any IP rights which correspond to the applied for gTLD will also be assessed.[153]


Drafting protections for trademark owners and other right holders was a contentious aspect in creating new gTLDs. Trademark owners criticised the rights protection measures as being inadequate.[154] Many outside the trademark lobby argued that the legal rights objection is overly-broad and provides greater protection to rights holders, particularly trademark holders, than exists in the offline world.[155] Criticising an earlier draft of the AGB, one author provided: “under this rule, the Cherokee Nation would be unable to use Cherokee as a gTLD because some automobile company is said to have prior rights under this policy.”[156]


Although trademark holders received much of what they requested in the form of protection, they did not get everything they wanted. The process maintains room for legal rights holders to successfully obtain new gTLDs, despite the potential for broad objections. For example, if an association of heavy equipment manufacturers were seeking a new gTLD like <.diesel>, it would not necessarily be disqualified as a result of the trademarked use of the word “diesel” by Diesel S.p.A, a clothing and fashion company.[157] Use of the word “diesel” in a gTLD would arguably infringe on the existing legal rights of Diesel S.p.A. However, when considering the non-exclusive factors in the AGB, a DRSP would have to consider whether the gTLD <.diesel> would create “a likelihood of confusion” with the Diesel S.p.A.’s trademark.[158] Based on the required factors, it is unlikely that consumers visiting the website would confuse high fashion jeans and shoes with heavy trucks or other types of construction equipment. However, if the construction company began selling construction clothing, Diesel S.p.A, would have a better argument. If the hypothetical gTLD <.diesel> was granted and then began selling second level domain names in a manner inconsistent with its application, such as <www.jeans.DIESEL>, the trademark owner would have the opportunity to seek relief under the other Rights Protection Measures (RPMs) provided for in the AGB. Specifically, the Post Delegation Dispute Resolution Procedure (PDDRP) would be pertinent.[159]


It has been argued that confusion occurring with new gTLDs will be less problematic than it has been under the popular gTLD <.com>. Assuming the application would be approved; typosquatting with gTLDs like <.nkie> or a <.macdonalds> would be less attractive as the misspellings are less likely to be inadvertently visited by consumers.[160] Considering the cost of a new gTLD, the prospect of this practice becomes even more unlikely. Even at the second level domain space, typosquatting is unlikely to be as effective, unless the name is widely used.

The “existing legal rights objection,” on its face, is a strong protection, particularly for trademark holders. The policy, if applied broadly, could significantly curtail options available to applicants. This begs the question of whether owners of trademark rights are being provided with a monopoly on language in the expansion of the Internet or whether a more balanced approach could have been taken.

As a DRSP under the UDRP system, the WIPO dispute resolution panel has handled a high number of cases.[161] The WIPO track record also shows that panellists have decided for complainants in a high proportion of cases.[162] In one period, cases before a sole WIPO panellist were in favour of the complaining party 83% of the time.[163] However, the complaint success rate was much lower at 58% when a three-member panel was used.[164] The high rate of wins for complainants is not, in and of itself, indicative of bias.[165] However, several factors, including the large amount of panellists also acting as practising trademark lawyers, actively representing right holders, has raised some question of systemic bias.[166] The role of WIPO as a DRSP for the Module 3 legal rights objection has raised some concerns that trademark owners will receive more favourable treatment. Unlike the UDRP process which allows for a choice of DRSPs, WIPO is the only DRSP available.

7. GAC Advice on New gTLDs

After the dispute resolution procedures in the AGB were substantially complete, ICANN added a new avenue for governments, through the Governmental Advisory Committee (“GAC”), to oppose or provide “advice” on new gTLD applications.[167] The GAC advice procedure allows governments to address applications they identify “to be problematic.”[168] The GAC procedure was added following an on-going debate between members of the GAC and the ICANN board regarding the role of governments in the new gTLD process.[169] Although not included in early AGB drafts, the procedure was likely an important step in procuring final approval of the AGB.[170] In the following section, I evaluate the GAC advice procedure. Background information on the GAC and its role in the AGB processes is also presented.

The GAC’s central responsibility is to provide advice to ICANN on issues where ICANN’s programmes have an impact on “national laws or international agreements.”[171] The GAC has played an increasingly important role in gTLD policy since 2002.[172] For example, in conjunction with the US government and other groups, the GAC was central in blocking the <.xxx> domain name after its initial ICANN approval in 2005.[173] Regarding the new gTLD programme, the GAC has requested considerable authority in determining acceptable or allowable domain names.[174]

In the AGB drafting process, the GAC received support for its request for a greater or expanded role regarding the protection of trademarks, violation of national laws, and the use of sensitive gTLDs. For example, the USG suggested that the drafters remove the Limited Public Interest Objection and provide for a GAC review in its place. In a letter to ICANN, the US government argued that allowing a private expert to make determinations of morality and legal norms was “contrary to the sovereign right of governments to interpret and apply principles of international law on a country-by-country basis.”[175]

Following discussion with the GAC, the Module 3 device or objection mechanism was adopted. The purpose of the GAC advice procedure is to allow governments to object to new gTLDs “that potentially violate national law or raise sensitivities.”[176] From a procedural point of view, the GAC advice period functions much like the other objections or challenges provided in Module 3. Any advice presented by the GAC to ICANN must take place within the objection filing time period.[177] If the GAC objects to a gTLD, the applicant will have twenty-one days to respond to ICANN after it receives notice of the objection.[178] A major procedural difference compared to other objections is how the complaint will be administered. Unlike other objections in this section, a private DRSP will not consider GAC objections.[179] Rather, the ICANN board will play the role of DRSP.[180] The ICANN board has the option to consult with independent experts, but such consultation is not required.[181]

From a substantive point of view, the new procedure provides very little guidance as to its application. What constitutes “national law” is not defined in the GAC advice procedure. As the scope is not limited, it may also cover violations of national trademark laws. Weight or deference given to the GAC advice will take different forms, depending on whether there is “consensus” advice from the GAC stating that an application should not proceed.[182] In the current AGB, what constitutes GAC “consensus” remains undefined.[183] The policy provides that “[t]he GAC as a whole will consider concerns raised by GAC members, and agree on GAC advice to forward to the ICANN Board of Directors.”[184] If the GAC advises ICANN that a given application should not proceed, it will create “a strong presumption for ICANN that the application should not be approved….”[185] However, the presumption is not irrefutable.[186] If there is no “consensus” that an application should not proceed, but “concerns” about an application, the “ICANN Board is expected to enter into dialogue with the GAC to understand the scope of concerns.”[187] The concern by the governments will be taken seriously; however, no presumption will be formed.[188] In the case of GAC concerns regarding an application, ICANN is expected to provide a rational for its decision.[189] Applicants will have an opportunity to address the GAC advice by filing a response in the same manner as an applicant would respond to a formal objection.[190]

The GAC may also advise ICANN that an application should not proceed unless remediated.[191] It is unclear what sort of agreement must be reached by the GAC members before they may “advise” remediation.[192] In any event, if remediation is advised, a strong presumption that remediation is necessary will arise before the application is accepted.[193] Remediation may include securing approval “of one or more governments” for the use of the gTLD.[194] If no clear method for remediation exists, such as securing government approval for use of the name of a capital city, it is unlikely that the application will be able to proceed.[195] The effect of GAC suggested remediation could become a difficult barrier to overcome for gTLD applicants.

The GAC objection has been criticised as being vague and providing one group with too much influence in the gTLD process. Critics maintain that providing governments with too much power, via a government veto or other procedural mechanism, could have negative consequences for open discourse and freedom on the Internet. For one, it could also lead to much broader censorship on the Internet. As stated by Milton Mueller, “[t]he ICANN process has spent years trying to ensure that only applications that involve words contrary to general principles of international law will be vetoed.”[196] In Mueller’s post discussing the GAC veto, he uses the example of the potential domain name <.gay> as a gTLD that is important to a community, but may be vulnerable under the new objection.[197] Mueller maintains that based on conversations with conservative governments within the GAC; there is objection to a <.gay> domain name.[198] Under the proposed GAC objection, does the domain name <.gay> potentially “raise sensitivities” to an extent that it may be blocked? The disjunctive use of “or” indicates that the domain name does not have to be in violation of national law in a jurisdiction, but must only be “sensitive.” What constitutes sensitive information is unclear.[199]

Although gTLDs like <.jesus> or <.mohammed> may be likely candidates for raising sensitivities, it is unclear whether they could be blocked under this objection. Will there emerge a system where votes for trademark protection are traded for votes to block sensitive names? Although the GAC advice procedure may have been a politically necessary step for the adoption of the AGB, it has also raised concerns regarding the freedom of speech associated with new gTLDs.[200] Allowing the advice procedure to be applied broadly could have an effect on the gTLDs available. In addition to <.gay>, will names like <.wine> or <.beer> be limited by the more conservative members of the constituency?

The counter argument to complaints about the breadth of the new GAC objection is that the policy also contains checks and balances. If consensus is not reached, the presumption will not apply. It is unlikely that a handful of conservative countries with strict religious codes or blasphemy laws will have the ability to block a significant number of new gTLDs. Even if an application is objected to, with GAC consensus, the ICANN board will have the opportunity to accept or reject the advice.[201] As a result, ICANN will remain in a position to rebut a presumption based on GAC advice.

8. Conclusion

Despite improvements in the expansion process from earlier rounds, there are issues with the dispute resolution procedure in Module 3 that will make it difficult for new gTLD applicants to succeed. Unlike earlier expansions, it will no longer be possible to deny applications based on whether the proposed gTLD is easily pronounced by members of the ICANN board. However, broad application of the objections in Module 3, particularly, the legal rights objection, have the potential to limit new gTLDs. In addition to the vast number of existing trademarks, there are many other interests that may qualify as “legal rights” under the objection. If WIPO, as the DRSP, errs overwhelmingly on the side of protecting rights holders, there are very few gTLDs outside of the “dot brand” (i.e. <.coke>) applicants that will make it to launch. If the only gTLDs able to survive Module 3 are the 2012 equivalent of <.museum>, the goals of creating competition in the domain name system will not be reached.

The GAC advice objection, added very late in the game, may also limit the success of the programme. Although including governments and protecting national laws are important goals, providing such a powerful and loosely defined objection at the eleventh hour may prove to be problematic. If the GAC advice objection is broadly applied, or allows conservative governments to widely limit the availability of new gTLDs, the programme may become less inclusive than was intended by ICANN and the majority of its stakeholders.

The current gTLD expansion has been a long time coming. In the months leading up to approval, there were many last minute attempts to rewrite and even derail the programme. Opponents of gTLD expansion maintained that he programme was rushed and failed to take into consideration the interests of all relevant stakeholders. Misinformation about the scope of the programme was also prevalent. Based on some accounts, new gTLDs would be made easily available and would be destructive to the security and stability of the Internet. The reality of the new gTLD programme is very different. The programme took years of planning, meetings with governments, and over a thousand comments before the AGB was finally approved. As the programme stands, obtaining a new gTLD will not be an easy task.

* Research Assistant, Norwegian Research Center for Computers and Law (NRCCL), University of Oslo, Department of Private Law, Igov2 Project. Thanks are due to Lee Bygrave, Emily Weitzenboeck, and Tobias Mahler, who have provided valuable comments on several drafts. However, any errors or omissions are entirely mine.

[1] Z Efroni, “Names as Domains, Names as Marks: Issues Concerning the Interface between Internet Domain Names and Trademark Rights” in P Yu (ed), Intellectual Property and Information Wealth: Issues and Practices in the Digital Age (Praeger Publishers, 2007), at 375.

[2] The application window will last for 90 days while it may take between 9 to 20 months to obtain a new gTLD. AGB, at 1.1.3.

[3] ICANN, “gTLD Applicant Guidebook, Version 2012-06-04” (2012) available at, (accessed 6 Jun 2012).

[4] Steps to delegation include an administrative check, initial evaluation, possible extended evaluation, string contention check, and potential dispute resolution proceedings. ICANN, “New gTLDs FAQs, v. 2.7.” available at, (accessed 24 May 2012).

[5] L Bygrave and J Bing, Internet Governance: Infrastructure and Institutions (Oxford: OUP, 2009), at 150.

[6] Ibid, 147-48.

[7] S Alikhan and R Mashelkar, Intellectual Property and Competitive Strategies in the 21st Century 2nd ed (Alphen aan den Rijn: Wolters Kluwer, 2009), at 194; B Borchert, “Imminent Domain Name: The Technological Land-Grab and ICANN’s Lifting of Domain Name Restrictions” (2011) 45 Valparaiso University Law Review 505-549, at 508 available at (accessed 28 Sept 2011) (stating that the DNS is not a singular file, but is made up multiple networks).

[8] L Bygrave and J Bing, Internet Governance: Infrastructure and Institutions (Oxford: OUP, 2009), at 47. See also J Kesan and S Rajiv, “Fool Us Once Shame on You – Fool Us Twice Shame on Us: What We Can Learn from the Privatizations of the Internet Backbone Network and the Domain Name System” (2001) 79 Washington University Law Quarterly 89-220, at 89.

[9] Yahoo! Inc., “Company Information” available at (accessed 11 Nov 2011).

[10] E Schierman, “Make Room for Trademark: What You Should Know About the New Global Domain Names” (2010) 53-Feb Advocate 25-29, at 25.

[11] L Bygrave and J Bing, Internet Governance: Infrastructure and Institutions (Oxford: OUP, 2009), at 148.

[12] ICANN, “Top-Level Domains (gTLDs)” available at (accessed 11 Nov 2012) (stating that “[d]omain names may be registered in…<.com, .net, and .org> without restriction”).

[13] Both .gov and .mil predate ICANN.

[14] ICANN “Information Page for Sponsored Top-Level Domains” available at (accessed 22 Sept 2011).

[15] Ibid.

[16] J Swinson, “Domain Directors PTY Ltd v .AU Domain Administration LTD” (2010) 16 Computer Law Review 147-148, at 147. The actual management of the ccTLD may be carried out on a private basis.

[17] Pfanner, Eric, “For Countries That Own Shorter Web Site Suffixes, Extra Cash from Abroad,” N.Y. Times, (6 Feb 2011) available at (accessed 25 Mar 2011).

[18] K Manheim and L Solum, “The Case for gTLD Auctions: A Framework for Evaluating Domain Name Policy” (23 Mar 2003) available at, at 27. See also J Lipton, Internet Domain Names, Trademarks and Free Speech (Edward Elgar, 2010) 1-325, at 293.

[19] D Mac Sithigh, “More than Words: The Introduction of Internationalized Domain Names and the Reform of Generic Top-Level Domains at ICANN” (2010) 18 International Journal of Law and Information Technology, 274-300.

[20] Ibid.

[21]K Manheim and L Solum, “An Economic Analysis of Domain Name Policy” (2004) Vol. 25 Hastings Communications and Entertainment Law Journal Vol. 25 317-452,

, 325. See also J Lipton, Internet Domain Names, Trademarks and Free Speech (Edward Elgar, 2010) 1-325, at 305 (arguing that domain names are the closest thing to real property available on the Internet).

[22] J Thomas, “Fifteen Years of Fame: The Declining Relevance of Domain Names in the Enduring Conflict between Trademark and Free Speech” (2011) 11 John Marshall Review of Intellectual Property Law 1-58, at 43 available at (accessed 5 Jun 2012).

[23] N Brown, “Six Degrees of Disputation New DRPs for New gTLDs on the Internet” (2012) 66 Dispute Resolution Journal 46- 54, at 48.

[24] J Weinberg, “Governments, Privatization and ‘Privatization’: ICANN and the GAC” (2011) 18 Michigan Telecommunications and Technology Law Review 189-218.

[25] In 2009, the USG and ICANN entered into the Affirmation of Commitments (“AOC”) available at (accessed 1 May 2012). See M Froomkin, “Almost Free: An Analysis of ICANN’s ‘Affirmation of Commitments’” (2011) 9 Journal of Telecommunications and High Technology Law, 187-233, at 190-198.

[26] Ibid. See also L Bygrave and J Bing, Internet Governance: Infrastructure and Institutions (Oxford: OUP, 2009), at 150.

[27] Excluding “legacy” names pre-dating ICANN.

[28] ICANN, “Groups” available at (accessed 5 Jun 2012).

[29] ICANN, “Affirmation of Commitments by the United States Department of Commerce and the Internet Corporation for Assigned Names and Numbers” available at (accessed 9 Sept 2011).

[30] See e.g. ICANN, “About ICANN” available at (accessed 7 Mar 2011).

[31] VeriSign, “Domain Name Industry Brief” (2010) available at (accessed 11 Nov 2011).

[32] W Kleinwachter, “High Noon in Singapore? ICANN’s new gTLD program at a crossroads” (2011) available at (accessed 17 Aug 2011) (stating that gTLDs predating ICANN are: <.com .edu .gov .int .mil .net .org .arpa>). Prior to ICANN’s existence, Jon Postel planned to introduce 150 gTLDs.

[33] Including gTLDs: <.aero .biz .coop .info .museum .name .pro>. ICANN, “List of gTLDs” available at (accessed 11 Feb 2011).

[34] M Wang, “Regulating the Domain Name System: Is the ‘.Biz’ Domain Name Distribution Scheme an Illegal Lottery?” (2003) 1 University of Illinois Law Review 245-288, at 263. See also P Michael, “ICANN’s Implementation Recommendation Team for New gTLDs: Safeguards Needed” (2009) 16.10 Progress & Freedom Foundation Progress on Point, at 2.

[35] ICANN, “Criteria for Assessing TLD Proposals” (15 Aug 2000) available at (accessed 5 May 2012).

[36] See Manheim and Solum (2004), at 410.

[37] Ibid.

[38] Ibid.

[39] Ibid, 26.

[40] Including gTLDs: <.asia .cat .jobs .mobil .tel .travel>. ICANN, “Information Page for Sponsored Top-Level Domains” available at (accessed 11 Feb 2011).

[41] J Levine, “What are TLDs Good For?”  (3 Jul 2009) available at (accessed 30 Sept 2011) (maintaining that “<.museum> is a noble failure, with only about 200 registrants, a lot of dead links, and negligible visibility”).

[42] ICANN, “XXX Comments,” available at (accessed 28 Sept 2011). During consideration of the gTLD, ICANN received over 90000 email messages concerning the <.xxx> proposal.

[43] M Helft, “Pornography Sites Will Be Allowed to Use .XXX Addresses,” N.Y. Times, Mar 18, 2011 available at (accessed 27 Sept 2011). See also R Richards and C Calvert, “Adult Websites and the Top-Level Domain Debate: ICANN’s Adoption of .XXX Draws Adult-Industry Ire” (2011) 29 Cardozo Arts and Entertainment Law Journal 527-556.

[44] ICANN GNSO, “Final Report – Introduction of New Generic Top-Level Domains” (8 Aug 2007) available at (accessed 16 Aug 2011). See also ICANN, “Factsheet” available at (accessed 16 Aug 2011).

[45] ICANN, “About the New gTLD Program” available at (accessed 11 May 2011).

[46] K Rosette, “ICANN and Trademark Protection in New GTLDs” (2010) 223 Trademark World 39-43; ICANN, “New gTLD Program: Draft Applicant Guidebook (Draft RFP)” (24 Oct 2008) available at (accessed 11 May 2011).

 [47] ICANN, “gTLD Applicant Guidebook Version 2012-06-04” available at, (accessed 6 Jun 2012).

[48] M Froomkin, “Almost Free: An Analysis of ICANN’s ‘Affirmation of Commitments’” (2011) 9 Journal of Telecommunications and High Technology Law, 187-233, at 225.

[49] CH Farley, “Convergence and Incongruence: Trademark Law and ICANN’s Introduction of New Generic Top-Level Domains” (2009) 25 John Marshall Journal of Computer & Information Law 625-633.

[50] B Borchert, “Imminent Domain Name: The Technological Land-Grab and ICANN’s Lifting of Domain Name Restrictions” (2011) 45 Valparaiso University Law Review 505-549, at 506.

[51] Ibid.

[52] Information including applications and guidebooks from the 2000 round available at (accessed 11 May 2011).

[53] Information including applications and guidebooks from the 2004 round available at (accessed 11 May 2011).

[54] ICANN, “Uniform Domain-Name Dispute-Resolution Policy” available at (accessed 11 May 2011).

[55] A Atallah, “New gTLD Update (30 May 2012)” ICANN, available at (accessed 31 May 2012). Further rounds have not yet been scheduled.

[56] AGB, at

[57] AGB, at 1.5.1. See AGB at 1.5.2 (providing additional fees for community application).

[58] AGB, at

[59] AGB, at The warning provides the applicant with notice that their application is seen as “sensitive or problematic by one or more governments.”

[60] AGB, at 2.1.1.

[61] AGB, at 2.2.

[62] AGB, at See also ICANN, “Fact Sheet” (2011) available at (accessed 4 Jun 2012).

[63] AGB, at 1.5.2.

[64] Dispute Resolution Procedures (hereinafter “DRP”), at Art. 1(d).

[65] AGB, at 3.0-3.1. See also AGB, at. 3.2.1, 3.2.2.

[66] AGB, at 3.2.1.

[67] AGB, at 3.2.2.

[68] AGB, at 3.2.5. The IO is limited to filing objections on the grounds of Limited Public Interest and Community.

[69] AGB, at 3.5.

[70] AGB, at 3.2.3.

[71] In the case of a string contention objection, the result may also include string contention proceedings. See AGB, at 4.1.

[72] AGB, at 5.4.1.

[73] See AGB, at Module 5 (providing additional rights protection measures).

[74] J Hörnle, Cross-border Internet Dispute Resolution (Cambridge: CUP, 2009), at 187.

[75] ICANN, “GNSO Final Issue Report: the Current State of the UDRP” (3 Oct 2011) available at (accessed 5 Jun 2012).

[76] AGB, at 3.2.1.

[77] T Bettinger et al (eds), Domain Name Law and Practice: An International Handbook (Oxford: Oxford University Press, 2005), at 947.

[78] T Shahan, “The World Summit on the Information Society & the Future of Internet Governance” (2006) 10 Computer Law Review & Technology Journal 325-355, at 334-35.

[79] G Kaufmann-Kohler and T Schultz, Online Dispute Resolution: Challenges for Contemporary Justice (Kluwer Law International 2004), at 6 (discussing the extensive use of the process and the low number of UDRP appeals). But see K Komaitis, The Current State of Domain Name Regulation: Domain Names As Second Class Citizens In A Mark-Dominated World, (Abingdon: Routledge, 2010), at 89-91 (arguing that referring to the UDRP as arbitration proceedings is a “common mistake” as “the UDRP is confusingly similar to arbitration as it resembles its nature, but neither serves justice nor facilitates the parties’ needs”).

[80] ICANN, “UDRP Procedure” available at (accessed 23 Mar 2011).

[81] Ibid, at point 3 (“Cancellations, Transfers, and Changes.”).

[82] Ibid, at 4(i) (“The remedies available to a complainant pursuant to any proceeding before an Administrative Panel shall be limited to requiring the cancellation of your domain name or the transfer of your domain name registration to the complainant.”).

[83] R Owens, “Domain-Name Resolution after Sallen v. Corinthians Licenciamentos &, Inc. v. Excelentisimo Ayuntameiento de Barcelona” (2003) 18 Berkeley Technology Law Journal 257-274, at 265.

[84] See Attachment to Module 3 Article 11(b) and UDRP Rule 5(a) available at (accessed 25 May 2012).

[85] See S Reed, “Sensible Agnosticism: An Updated Approach to Domain-Name Trademark Infringement” (2011) 61 Duke Law Journal 212-250, at 222-25 (discussing the ease of the registration process on a first-come-first-served basis).

[86] For example the new gTLD application fee is $185,000, plus an annual ICANN fee $25,000. AGB at 1.5.1. Other costs including registry back end and consulting fees will vary widely depending on the applicant and use of the gTLD. New gTLD Site, “New gTLD Cost” (8 Aug 2011) available at (accessed 21 May 2012).

[87] D Sorkin, “Judicial Review of ICANN Domain Name Dispute Decisions” (2001) 18 Santa Clara Computer and High Technology Law Journal 35-55, at 46. See also, Incorporated v Excelentisimo Ayuntamiento De Barcelona, (2003) 330 F.3d 617 (US 4th Cir Ct App), at 626.

[88] D Prahl and E Null, “The New Generic Top-Level Domain Program: a New Era of Risk for Trademark Owners and the Internet” (2011) 101 Trademark Reporter 1757-1800, at 1772.

[89] AGB, at 3.4. See also Attachment to Module 3 new gTLD DRP (hereinafter “new gTLD DRP”) Art.2(e)(i).

[90] See ICANN, “String Similarity Assessment Tool” available at (accessed Sept 2011).

[91] AGB, at

[92] AGB, at

[93] Ibid.

[94] AGB, at 3.2.1.

[95] AGB, at 3.

[96] AGB, at Module 4.

[97] Ibid.

[98] AGB, at new gTLD DRP, P1-P11.

[99] AGB, at 3.2.3.

[100] AGB, at 3.5.1 (emphasis added). See also ICANN GNSO, “Introduction of New Generic Top-Level Domains Final Report” (8 Aug 2007) available at (accessed 25 May 2012), at Recommendation 3.

[101] AGB, at 3.5.1 (emphasis added).

[102] Ibid (emphasis added).

[103] AGB, at 3.5.1. See also AGB at. See Schierman (2010), at 25.

[104] AGB, at 3.5.

[105] Ibid.

[106] 15 U.S.C. § 1125 (d)(1)(c)(2006). See The Utah E-Commerce Integrity Act, Utah Code Ann. § 13-40-101 (2010).

[107] UDRP Art. 4(a)(i). During UDRP proceedings it is considered whether: “(i) your domain name is identical or confusingly similar to a trademark or service mark in which the complainant has rights; and (ii) you have no rights or legitimate interests in respect of the domain name; and (iii) your domain name has been registered and is being used in bad faith.” ICANN, “Uniform Dispute Resolution Policy” (24 Oct 1999) available at (accessed 20 Sept 2011).

[108] Ibid; UDRP, at 4(a)(iii). See also UDRP at, 4(b)(i-iv).

[109] K Komaitis, “Trademark Law’s Increment through the Uniform Domain Name Dispute Resolution Policy” (2011) 6 Oxford Intellectual Property Law and Practice, 553-567, at 560.

[110] Ibid (discussing the lengthy evaluation taken under US law for a finding of infringement based on confusion—an evaluation that considers the following factors: “(i) the similarity or dissimilarity of the marks in their entireties as to appearance, sound, connotation and commercial impression; (ii) the similarity or dissimilarity and nature of the goods described in an application or registration or in connection with which a prior mark is in use; (iii) the similarity or dissimilarity of established, likely-to-continue trade-channels; (iv) the conditions under which and buyers under whom sales are made; (v) the fame of the prior mark; (vi) the number and nature of similar marks in use on similar products; (vii) the nature and extent of any actual confusion; (viii) the length of time during and the conditions under which there has been concurrent use without evidence of actual confusion; (ix) the variety of goods on which a mark is or is not used; (x) the market interface between the applicant and the owner of the prior mark; (xi) the extent to which the applicant has a right to exclude others from use of its mark on its goods; (xii) the extent of potential confusion; and (xiii) any other established fact probative of the effect of use”).

[111] Ibid.

[112] CH Farley, “Convergence and Incongruence: Trademark Law and ICANN’s Introduction of New Generic Top-Level Domains” (2009) 25 John Marshall Journal of Computer & Information Law 625-633, at 627.

[113] Ibid, 629.

[114] See Interpace Corp v Lapp, Inc (1983) 721 F.2d 460, 463 (US 3rd Cir. Ct. App.). See also Northland Ins. Companies v. Blaylock, (2000) 115 F. Supp. 2d 1108 (US D Ct Minn).

[115] CH Farley, “Convergence and Incongruence: Trademark Law and ICANN’s Introduction of New Generic Top-Level Domains” (2009) 25 John Marshall Journal of Computer & Information Law 625-633, at 627.

[116] Ibid.

[117] Ibid, 628.

[118] Ibid.

[119] AGB, at 3.5.1.

[120] T Bettinger et al (eds), Domain Name Law and Practice: An International Handbook (Oxford: Oxford University Press, 2005), at 1030.

[121] D Sorkin, “Judicial Review of ICANN Domain Name Dispute Decisions” (2001) 18 Santa Clara Computer and High Technology Law Journal 35-55.

[122] AGB, at See also AGB, at Module 4.

[123] See AGB, at 3.5.2.

[124] M Palage, “ICANN’s ‘Go/No-Go’ Decision Concerning New gTLDs” (2009) 16.3 Progress & Freedom Foundation Progress on Point (2009), at 1.

[125] The role of the GAC is to provide ICANN input from governments on issues of public policy and the potential impacts of ICANN’s policies on national laws or international agreements. GAC, “Governmental Advisory Committee” available at (accessed 24 May 2012). See GAC, “ICANN Board Notes on the GAC New gTLDs Scorecard” available at (accessed 10 Mar 2011).

[126] D Prahl and E Null, “The New Generic Top-Level Domain Program: a New Era of Risk for Trademark Owners and the Internet” (2011) 101 Trademark Reporter 1757-1800, at 1771 (stating that “[t]he new gTLD program will exacerbate infringement problems…”).

[127] M Palage, “ICANN’s Implementation Recommendation Team for New gTLDs: Safeguards Needed” (2009)  Vol. 16 Progress & Freedom Foundation Progress on Point Paper No. 10., at 1. See also Y Zhao, Dispute Resolution in Electronic Commerce, (Leiden: Martinus Nijhoff, 2005), at 178.

[128] AGB, at 3.52.

[129] Implementation Recommendation Team (“IRT”), “Final Report” (2009) available at (accessed 21 May 2011), 1-69, at 1 (stating “[t]he views of the IRT reflect the views of business and trademark interests in general”).

[130] Ibid. See also J Lipton and M Wong, “Trademarks and Freedom of Expression in ICANN’s New GTLD Process” (2012) available at (accessed 27 May 2011), 1-39, at 19.

[131] Special Trademarks Issues Working Team (“STI”), “Final Report” (2009) available at (accessed 21 May 2011), 1-47.

[132] K McCarthy, “Trademark Lawyers to ICANN: Close, But No Cigar” (2011) available at (accessed 27 May 2011).

[133] ICANN, “Defensive Applications for New gTLDs” (2012) available at (accessed 4 Jun 2012). See also Palage (2009).

[134] Ibid.

[135] E Pfanner, “An Explosion in Universe of Web Names” (2011) available at (accessed 20 Jun 2011).

[136] See Association of National Advertisers (“ANA”), “Major Assns. and Businesses Join with ANA to Form Coalition to Oppose ICANN’s TLD Expansion Program” (2011) available at (accessed 11 Nov 2011).

[137] F Krueger and A Van Couvering, “Quantitative Analysis of Trademark Infringement and Cost to Trademark Holders in New gTLDs” (10 Feb 2010) available at (accessed 15 Aug 2011), at 1.

[138] ICANN, “New gTLD Program Explanatory Memorandum –Discussion Draft: Market & Economic Impacts” (15 Apr 2011) available at  (accessed 15 May 2011).

[139] J Lipton, Internet Domain Names, Trademarks and Free Speech (Edward Elgar, 2010) 1-325, at 79 (arguing that based on past releases of new gTLDs, <.com> will likely remain the most sought after gTLD).

[140] Ibid.

[141] AGB, at

[142] Ibid.

[143] Ibid. IGOs and specialised agencies including the UN may also meet the criteria.

[144] Ibid.

[145] AGB, at 3.52 (emphasis added).

[146] Ibid.

[147] AGB, at 3.52.

[148] AGB, at 3.1.3. During dispute resolution proceedings, the WIPO Rules for New gTLD dispute resolution are applicable. See New gTLD DRP Art.2(e)(ii); WIPO, “Legal Rights Objections under ICANN’s New gTLD Program” available at (accessed 21 May 2012). See also WIPO, “Schedule of Fees and Costs” (11 Jan 2012) available at (accessed 4 Jun 2012).

[149] AGB, at 3.52(1).

[150] Ibid, at 3.52. (4).

[151] Ibid, at 3.52.(6) (emphasis added). See also AGB, 2.4; K Komaitis, “Trademark Law’s Increment through the Uniform Domain Name Dispute Resolution Policy” (2011) 6 Oxford Intellectual Property Law and Practice, 553-567, at 560.

[152] AGB, at 3.52. (5).

[153] Ibid, at 3.52 (5-6).

[154] See e.g. J Lipton and M Wong, “Trademarks and Freedom of Expression in ICANN’s New GTLD Process” (2012) available at (accessed 2 August 2012), 1-39, at 23.

[155] K Komaitis, The Current State of Domain Name Regulation: Domain Names As Second Class Citizens In A Mark-Dominated World, (Abingdon: Routledge, 2010), at 49.

[156] CH Farley, “Convergence and Incongruence: Trademark Law and ICANN’s Introduction of New Generic Top-Level Domains” (2009) 25 John Marshall Journal of Computer & Information Law 625-633, at 630.

[157] Wikipedia, “Diesel (brand)” available at (accessed 27 May 2011).

[158] AGB, at 3.52(6).

[159] AGB, at “Trademark Post-Delegation Dispute Resolution Procedure (Trademark PDDRP)”.

[160] J Lipton, Internet Domain Names, Trademarks and Free Speech (Edward Elgar, 2010) 1-325, at 263; C Clark, “The Truth in Domain Names Act of 2003 and a Preventative Measure to Combat Typosquatting” (2004) 89 Cornell Law Review 1476-1518, at 1476.

[161] M Mueller, “Rough Justice, An Analysis of ICANN’s Uniform Dispute Resolution Policy” available at (accessed 23 Sept 2011). See also N Branthover, “UDRP-A Success Story: A Rebuttal to the Analysis and Conclusions of Professor Milton Mueller in Rough Justice” (6 May 2002) available at

[162] G Kaufmann-Kohler and T Schultz, Online Dispute Resolution: Challenges for Contemporary Justice (Kluwer Law International 2004), at 193.

[163] Ibid.

[164] M Geist, “ An Examination of the Allegations of Systemic Unfairness in the ICANN UDRP (2001) available at (accessed 27 May 2011). See also S Bechtold, “Governance in Namespaces” (2003) 36 Loyola of Los Angeles Law Review 1239-1320, at 1261.

[165] Y Zhao, Dispute Resolution in Electronic Commerce, (Leiden: Martinus Nijhoff, 2005), at 178.

[166] G Kaufmann-Kohler and T Schultz, Online Dispute Resolution: Challenges for Contemporary Justice (Kluwer Law International 2004), at 193.

[167] AGB, at 3.1.

[168] Ibid.

[169] For documents including scorecards: (accessed 18 May 2011). See also ICANN Board of Directors / GAC Joint Working Group (“JWG”), “Review of the Role of the GAC” (2011) available at (accessed 27 Sept 2011); GAC, “GAC Principles Regarding New gTLDs” (28 Mar 2007) available at (accessed 27 May 2011), at 1-4.

[170] K Papac, “ICANN Successfully Tiptoes through Political Minefield with New TLD Applicant Guidebook” (12 May 2011) available at (accessed 10 Nov 2011).

[171] GAC, “About the GAC” available at, (accessed 5 Jun 2012).

[172] J Weinberg, “Governments, Privatization and ‘Privatization’: ICANN and the GAC” (2011) 18 Michigan Telecommunications and Technology Law Review 189-218, at 200-202.

[173] Ibid.

[174] Ibid (citing GAC, “Principles Regarding New gTLDs” (28 Mar 2007) available at (accessed 14 May 2011), at §§ 2.1, 2.2, 2.7) (discussing a GAC request for a procedure for blocking new domain names, at no cost, which would be “on demand for governments.”).

[175] USG, “Submission to the GAC Scorecard re New gTLDs” (31 Jan 2011) available at See also M Mueller, “The US Commerce Dept Position Paper for the ICANN Board Negotiations” (2011) available at (accessed 6 Jun 2012).

[176] AGB, at 3.1.

[177] Ibid.

[178] AGB, at 3.1.

[179] Ibid.

[180] Ibid.

[181] AGB, at 3.1.

[182] AGB, at 3.1.

[183] Ibid.

[184] Ibid.

[185] Ibid. at 3.1.(III).

[186] Ibid.

[187] AGB, at 3.1(II).

[188] Ibid.

[189] Ibid.

[190] AGB, at 3.1.

[191] Ibid.

[192] Ibid.

[193] AGB, at 3.1(III).

[194] Ibid.

[195] Ibid.

[196] M Mueller, “The US Commerce Dept Position Paper for the ICANN Board Negotiations” (2011) available at (accessed 6 Jun 2012).

[197] Ibid.

[198] Ibid.

[199] ICANN, “New gTLD Program Explanatory Memorandum—GAC and Government Objections; Handling of Sensitive Strings; Early Warning” (15 Apr. 2011) available at (accessed 5 Jun 2012).

[200] J Lipton and M Wong, “Trademarks and Freedom of Expression in ICANN’s New GTLD Process” (2012) available at (accessed 27 May 2011), 1-39, at 23-24 (citing statements made by USG officials on the GAG advice system, available at (accessed 5 Jun 2012)).

[201] AGB, at 3.1.

Anticipating Conflict—An Evaluation of the New gTLD Dispute Resolution System

2 thoughts on “Anticipating Conflict—An Evaluation of the New gTLD Dispute Resolution System

  • August 12, 2016 at 1:56 am

    The link to the PDF version of this article is mistakenly to BOOK REVIEW
    Graeme Hodge, Diana Bowman and Andrew Maynard (eds)
    Cheltenham: Edward Elgar, 2010, 640 pp, £175.00, ISBN 978-1-84844-673-1 (hbk).

    Do please correct it.

    Thank you.

    • August 12, 2016 at 8:58 am

      Thanks for bringing this to our attention — we’ve now fixed the link.

      – SCRIPTed


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.