| Comment Close Date | Statement Name | Status | Assignee(s) and | Call for Comments | Call for Comments Close | Vote Announcement | Vote Open | Vote Reminder | Vote Close | Date of Submission | Staff Contact and Email | Statement Number |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| n/a | Confusingly Similar gTLDs | Drafting | Unlicensed user (NARALO) | TBC | TBC | TBC | TBC | TBC | TBC | TBC | n/a | TBC |
The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote.
On 24 June 2013, as requested by the GAC, the Board New gTLD Program Committee (NGPC) considered the issue of singular and plural stings being confusingly similar and decided to let the original process stand (subject to individual objections).
Events and findings which have occurred since then indicate that the transparent, predictable and objective criteria called for by the GNSO New gTLD Policy recommendations 1 and 9 have not been met, ultimately resulting in Internet end-user confusion.
As examples, recent string similarity objection decisions have ruled:
The ALAC is particularly concerned with the issue of singular vs plural strings. A central issue is that the "confusingly similar" test relies purely on visual similarity. Based on the initial evaluation adding an "S" makes it a recognizably different string. The recent NGPC decision (http://www.icann.org/en/groups/board/documents/minutes-new-gtld-25jun13-en.htm#2.d), re-affirms this position, although several NGPC members expressed regret that the wording of the Applicant Guidebook effectively forced this outcome.
The Applicant Guidebook section 2.2.1.1 describes the string similarity review:
This review involves a preliminary comparison of each applied-for gTLD string against existing TLDs, Reserved Names (see subsection 2.2.1.2), and other applied-for strings. The objective of this review is to prevent user confusion and loss of confidence in the DNS resulting from delegation of many similar strings.
Note: In this Applicant Guidebook, “similar” means strings so similar that they create a probability of user confusion if more than one of the strings is delegated into the root zone.
The visual similarity check that occurs during Initial Evaluation is intended to augment the objection and dispute resolution process (see Module 3, Dispute Resolution Procedures) that addresses all types of similarity.
The ALAC disagrees with the NGPC decision. The problem is the belief that "visual similarity" relies purely on what, in computer terminology, would be called "pattern matching". Pattern matching is certainly part of human perception, but it is not limited to that. At issue is whether two strings will be PERCEIVED as being equivalent, and perception is a far more complex (and less understood) issue.
Consider strings pairs such as:
Will these be memorably equivalent or different to typical Internet users (the ones who have no knowledge of terms such as ICANN, domain name, TLD and second level)? The ALAC strongly doubts that most Internet users will note the subtle differences.
If both singular and plural TLDs are delegated:
The ALAC is also concerned with the lack of predictability and consistency in objection decisions. Certainly allowing identical strings to be individually evaluated (based on different arguments and by different panelists) does not appear to have been a wise move. Moreover the clear lack of consistency among the evaluations of different panelists implies that overall, we will put either some TLDs in contention sets where it is not justified, or delegate strings that will cause user confusion.
It is not clear how this can be fixed at this time, but proceeding with no change is either going to unfairly disadvantage some applicants and their target markets or cause certain user confusion.
On 24 June 2013, as requested by the GAC, the Board New gTLD Program Committee (NGPC) considered the issue of singular and plural stings being confusingly similar and decided to let the original process stand (subject to individual objections).
Events and findings which have occurred since then indicate that the transparent, predictable and objective criteria called for by the GNSO New gTLD Policy recommendations 1 and 9 have not been met, ultimately resulting in Internet end-user confusion.
As examples, recent string similarity objection decisions have ruled:
The ALAC is particularly concerned with the issue of singular vs plural strings. A central issue is that the "confusingly similar" test relies purely on visual similarity. Based on the initial evaluation adding an "S" makes it a recognizably different string. The recent NGPC decision (http://www.icann.org/en/groups/board/documents/minutes-new-gtld-25jun13-en.htm#2.d), re-affirms this position, although several NGPC members expressed regret that the wording of the Applicant Guidebook effectively forced this outcome.
The Applicant Guidebook section 2.2.1.1 describes the string similarity review:
This review involves a preliminary comparison of each applied-for gTLD string against existing TLDs, Reserved Names (see subsection 2.2.1.2), and other applied-for strings. The objective of this review is to prevent user confusion and loss of confidence in the DNS resulting from delegation of many similar strings.
Note: In this Applicant Guidebook, “similar” means strings so similar that they create a probability of user confusion if more than one of the strings is delegated into the root zone.
The visual similarity check that occurs during Initial Evaluation is intended to augment the objection and dispute resolution process (see Module 3, Dispute Resolution Procedures) that addresses all types of similarity.
The ALAC disagrees with the NGPC decision. The problem is the belief that "visual similarity" relies purely on what, in computer terminology, would be called "pattern matching". Pattern matching is certainly part of human perception, but it is not limited to that. At issue is whether two strings will be PERCEIVED as being equivalent, and perception is a far more complex (and less understood) issue.
Consider strings pairs such as:
Will these be memorably equivalent or different to typical Internet users (the ones who have no knowledge of terms such as ICANN, domain name, TLD and second level)? The ALAC strongly doubts that most Internet users will note the subtle differences.
If both singular and plural TLDs are delegated:
The ALAC is also concerned with the lack of predictability and consistency in objection decisions. Certainly allowing identical strings to be individually evaluated (based on different arguments and by different panelists) does not appear to have been a wise move. Moreover the clear lack of consistency among the evaluations of different panelists implies that overall, we will put either some TLDs in contention sets where it is not justified, or delegate strings that will cause user confusion.
It is not clear how this can be fixed at this time, but proceeding with no change is either going to unfairly disadvantage some applicants and their target markets or cause certain user confusion.