How String Confusion Objections Spiraled Out of Control

The landscape of top-level domains (TLDs) is a complex and ever-evolving one, and few areas have proven as contentious and perplexing as String Confusion Objections. What appears, on the surface, to be a straightforward assessment of similarity between domain name strings has, in practice, led to a cascade of contradictory rulings, fueling uncertainty and frustration within the domain industry. This article delves into the multi-faceted reasons behind these inconsistencies, exploring the guidelines, the panels, and the real-world implications that have left many questioning the fairness and predictability of the new gTLD program.

Among the various types of objections that can be lodged against new top-level domain name applications – including Legal Rights, Community, and Limited Public Interest Objections – string confusion objections might intuitively seem the most elementary. At its core, the question is simple: does one string bear such a close resemblance to another that it could lead to user confusion?

Yet, while issues surrounding Legal Rights Objections have generally been resolved with a degree of consensus (at least among observers not directly impacted), string confusion objections have consistently highlighted deep-seated disagreements, even among the very panelists tasked with adjudicating these disputes. These divergent opinions underscore a fundamental challenge in applying objective standards to subjective perceptions of similarity, impacting crucial decisions for new gTLD applicants and the future of the internet’s naming system.

The guy in the middle got the right panelist.
The guy in the middle got the right panelist.

Consider the striking examples that have emerged from these disputes, showcasing the unpredictable nature of string similarity assessments:

  • In a widely publicized case, one panelist ruled that the proposed .cam TLD was confusingly similar to the venerable .com, while another panel, reviewing an identical or very similar comparison, reached the opposite conclusion. This direct contradiction on such a prominent comparison raises serious questions about the consistency of the adjudication process.
  • Further complicating matters, some panelists have ruled that singular and plural forms of the same word, such as .sport and .sports, are likely to cause confusion among the typical internet user. However, a majority of other panelists have not upheld such objections, indicating a split interpretation of how minor grammatical variations should be treated. The implications for brand owners seeking to protect both singular and plural forms of their trademarks are significant.
  • Perhaps the most astonishing ruling involved a panelist who determined that .通販 (pronounced “tsuhan”), a Japanese string loosely translating to “online shopping” or “mail order,” was confusingly similar to the English-language .shop. This ruling introduced a profound cross-linguistic and cross-cultural dimension to string confusion, challenging the notion of a universal “average internet user” and highlighting the difficulties in comparing strings from entirely different character sets and semantic origins.

The Unpredictable Nature of String Confusion Objections

How did such pronounced inconsistencies become the norm rather than the exception? The answer may lie precisely in the seemingly straightforward, yet ultimately subjective, nature of string confusion objections. Unlike legal rights, which often hinge on established trademark law and prior use, string confusion delves into the realm of human perception, language, and cultural context, making it inherently more difficult to define with absolute certainty.

The guidelines provided in the new top-level domain name applicant guidebook for string similarity are meant to offer a framework, but their broad language has inadvertently contributed to the unpredictability. The relevant section states:

A DRSP panel hearing a string confusion objection will consider whether the applied-for gTLD string is likely to result in string confusion. String confusion exists where a string so nearly resembles another that it is likely to deceive or cause confusion. For a likelihood of confusion to exist, it must be probable, not merely possible that confusion will arise in the mind of the average, reasonable Internet user. Mere association, in the sense that the string brings another string to mind, is insufficient to find a likelihood of confusion.

This definition, while providing some parameters, leaves an enormous amount of room for individual interpretation. Phrases like “likely to deceive or cause confusion,” “probable, not merely possible,” and “average, reasonable Internet user” are subjective benchmarks that can vary significantly from one panelist to another. Consequently, decisions in string confusion objections become more dependent on the specific panelist assigned to a case than on the intrinsic merits or clear factual evidence. This raises concerns about fairness and the consistent application of rules across different disputes.

Adding Layers of Complexity: ICANN’s Independent Similarity Check

Further exacerbating the confusion is the existence of ICANN’s own internal similarity check, conducted by an independent panel on each new top-level domain name application. Crucially, this ICANN-mandated check focuses *only* on visual similarity, whereas the String Confusion Objections process can encompass any type of similarity – visual, aural, or conceptual.

Interestingly, ICANN’s independent panel, leveraging a computer algorithm and expert review, identified only two sets of strings with a high probability of user confusion from a visual standpoint: .hotels & .hoteis and .unicorn & .unicom. Notably, this panel did not conclude that plurals of strings would be too similar to singulars based purely on visual assessment. In fact, ICANN explicitly rejected further advice from the Governmental Advisory Committee (GAC) that plurals and singulars should automatically be placed into contention sets, signaling a clear stance against automatic plural-singular confusion.

This creates a paradoxical situation: loosely written rules, open to broad interpretation, govern a dispute resolution process for a program that had never been run before. On top of this, there’s a separate, algorithm-aided visual interpretation of strings by ICANN itself, which suggested very few strings were truly in contention. The stark contrast between ICANN’s initial findings (few confusing strings) and the subsequent DRSP panel rulings (many confusing strings, often for plurals or cross-linguistic comparisons) reveals a significant disconnect within the overall system.

The “Clusterf@ck” of Contradictions and Unanswered Questions

The result of these interwoven complexities and inconsistencies is, as many in the industry have bluntly described it, a “clusterf@ck.” The fundamental questions that arise are profound and remain largely unanswered:

  • What precisely constitutes “resemblance” in the context of domain strings? Does a string need to be both visually and aurally similar, or is one sufficient? How much weight, if any, should be given to the semantic or “meaning” of two strings, particularly across different languages and cultures?
  • Can a DRSP panelist legitimately disagree with ICANN’s own string similarity panel’s decision regarding whether two strings are visually similar? The case of .pet vs. .pets, where a DRSP panel found confusion despite ICANN’s earlier stance against general plural-singular confusion, suggests that panelists believe they can and do. This undermines the consistency and authority of ICANN’s initial assessments.

Many argue that the guidebook itself inadvertently set string confusion objections up for failure. Its lack of specificity regarding the criteria for confusion, the weight of different similarity types, and the concept of the “average internet user” left too much to subjective judgment. A more robust framework might have included a requirement for multi-panelist decisions, rather than single-panelist rulings, to introduce a greater degree of checks and balances and promote consistency.

Critiques of the Dispute Resolution Mechanism: The Role of ICDR

Beyond the vague guidelines, criticism has also been leveled at the International Centre for Dispute Resolution (ICDR), the organization tasked with administering these string confusion disputes. Compared to the World Intellectual Property Organization (WIPO), which has a long-standing reputation for efficiency and expertise in handling Legal Rights Objections (particularly UDRP cases), ICDR has faced significant challenges.

Concerns have been raised about ICDR’s perceived tardiness in processing cases, and its online system for disseminating information about these disputes has been widely criticized for being cumbersome and inefficient. Furthermore, questions have been raised regarding the selection and expertise of some panelists. For instance, in the high-profile Amazon .通販 dispute, many wondered whether the panelist possessed sufficient understanding of Japanese language and culture, or a proven track record in internet-related disputes. The fact that the panelist’s name did not appear in any prior UDRP decisions further fueled these concerns, suggesting a potential lack of specialized experience in a highly technical and nuanced field.

Where Do We Go From Here? Consequences and Unresolved Issues

The current state of string confusion objections leaves the new gTLD program in a precarious position, with several complex issues still unresolved and significant implications for applicants and the broader internet community.

  • Community Review and Intervention: In some instances, particularly where panel decisions seem highly contentious or create broader systemic problems, cases may need to be elevated for community review or direct intervention by ICANN itself. However, the mechanisms for such interventions are not always clear, adding another layer of uncertainty.
  • The .cam Dilemma: Take the case of United TLD’s application for .cam. Technical rules stipulate that if an objection is successfully brought by the registry of an existing top-level domain (like Verisign for .com), the application against which the objection was lodged is essentially “dead.” Yet, with conflicting panel decisions on .cam vs. .com, how can two competing applications for .cam (or other similar strings) proceed in the application queue? This creates an absurd scenario where the fate of a TLD application hinges on which panelist heard the case, potentially leading to unfair advantages or disadvantages for applicants.
  • Amazon’s Predicament: The objection to Amazon’s application for .通販 was brought by an applicant for the potential new TLD, .shop. As a result, .通販 will be placed in a contention set with .shop. However, Amazon.com itself also holds an application for .shop. This means that, without a specific intervention from ICANN, Amazon would effectively be forced to bid against itself in the same auction to resolve this contention set, merely to secure one of its own applied-for domains. This outcome highlights the potential for procedural flaws to create unnecessary costs, strategic dilemmas, and even anti-competitive scenarios for legitimate applicants.

Conclusion: A Path Forward for Trust and Clarity

The net result of these contradictory rulings, vague guidelines, and perceived procedural shortcomings is more confusion and a pervasive sense of distrust in a process that was already fraught with complexities. The promise of an expanded, diverse, and user-friendly internet namespace through the new gTLD program is undeniably valuable. However, the current handling of string confusion objections risks undermining this vision by creating an unpredictable, inconsistent, and often unfair system.

The issues could have been largely avoided with a more meticulously crafted framework. Moving forward, it is imperative for ICANN and its partners to address these systemic flaws. This requires:

  • Developing significantly clearer and more objective guidelines for string similarity, including explicit criteria for visual, aural, and semantic confusion, and how these factors are weighed.
  • Implementing enhanced training and oversight for DRSP panelists to ensure greater consistency in rulings and a shared understanding of the “average internet user” standard.
  • Establishing robust mechanisms for addressing conflicting decisions and providing pathways for community input or higher-level review in cases of significant discrepancy.
  • Improving the efficiency, transparency, and user-friendliness of the dispute resolution administrative processes, drawing lessons from more established organizations like WIPO.

Only through such comprehensive reforms can confidence be restored in the string confusion objection process, ensuring that the expansion of the internet’s naming system proceeds on a foundation of fairness, predictability, and clarity for all stakeholders.