<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
I agree.
<div><br>
</div>
<div>I'm not really comfortable letting consumers decide. However, by attempting to make these "similarity" judgements, ICANN is introducing complexity into an already overly complex system. As an engineer (computer scientist) I see this as akin to catching
a design flaw during testing or after shipment. It's really expensive to correct an error that could have been avoided by better/different design.</div>
<div><br>
</div>
<div>In the case of the new gTLD program, a fundamental aspect of the program is choice and availability of (largely) unrestricted strings. The Community was surprised by the number of applications, perhaps by an order of magnitude. This has stressed a system/process
that would have found it difficult to handle even a few hundred new names. But here we are.</div>
<div><br>
</div>
<div>If ICANN is going to make rational, reasoned decisions regarding similarities, etc., it almost certainly will need to slow down and consider "similarity" in a broader sense. Mary Jo's list would be a good starting point but I doubt it represents a complete
list of considerations.</div>
<div><br>
</div>
<div>The new gTLD program fundamentally morphs the DNS from a taxonomy to a market. If that wasn't obvious before, it should be now. Our struggles with this new market come not from its competitive nature but rather how best to "regulate" an otherwise open
market in order to ensure the greatest good internationally.</div>
<div><br>
</div>
<div>I don't have a good answer for how to accommodate GAC advice, address similarity concerns, or any of a host of other issues that will no doubt arise in the future. If the new gTLD program follows a traditional technology curve, we may will see 25,000 or
more applications in the second round. With no limitations on what can be applied for, that's a distinct possibility in my mind.</div>
<div><br>
</div>
<div>
<div>
<div>On Aug 16, 2013, at 12:40 PM, "J. Scott Evans" <<a href="mailto:jscottevans@yahoo.com">jscottevans@yahoo.com</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td valign="top">I think Ron makes some valuable points.<br>
<br>
Sent from Yahoo! Mail for iPhone</td>
</tr>
</tbody>
</table>
<div id="_origMsg_">
<div><br>
<div>
<div style="font-size:0.9em">
<hr size="1">
<b><span style="font-weight:bold">From:</span> </b>Ron Andruff <<a href="mailto:randruff@rnapartners.com">randruff@rnapartners.com</a>>;
<br>
<b><span style="font-weight:bold">To:</span> </b>'Smith, Bill' <<a href="mailto:bill.smith@paypal-inc.com">bill.smith@paypal-inc.com</a>>; 'Mari Jo Keukelaar' <<a href="mailto:mj@johnberryhill.com">mj@johnberryhill.com</a>>;
<br>
<b><span style="font-weight:bold">Cc:</span> </b>'bc - GNSO list' <<a href="mailto:bc-gnso@icann.org">bc-gnso@icann.org</a>>;
<br>
<b><span style="font-weight:bold">Subject:</span> </b>RE: [bc-gnso] BC comment on singular plural
<br>
<b><span style="font-weight:bold">Sent:</span> </b>Fri, Aug 16, 2013 7:05:05 PM <br>
</div>
<br>
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td valign="top">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial", "sans-serif";color:#1F497D;">I appreciate Mary Jo’s analysis as well. The reality is – like or not – as much as the pundits see little dilution in .COM whether 100 or 1000 new gTLDs arrive
on the scene, one has to also realize that the English Internet is the global Internet insomuch as English is the unofficial language of business on a global scale. So the problem we are dealing with is an ‘English’ problem. Which begs the question, how do
we – as the stewards of ICANN – find an appropriate solution? I, for one, am very uncomfortable with Bill’s last comment (</span>Consumers will eventually settle the matter, at least that's the theory.<span style="font-size:11.0pt;font-family:"Arial", "sans-serif";color:#1F497D;">)
Not pushing ICANN to establish policy on this matter is tantamount to tacitly agreeing to force consumers to buy and park names that they have no interest in – or will simply point to their domain (web site) of choice. Wasn’t that a problem we were hoping
to dispense with by way of opening up the domain space?</span></p>
<div><span style="font-size:11.0pt;font-family:"Arial", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial", "sans-serif";color:#1F497D;">My two cents…</span></p>
<div><span style="font-size:11.0pt;font-family:"Arial", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial", "sans-serif";color:#1F497D;">RA</span></p>
<div><span style="font-size:11.0pt;font-family:"Arial", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#1F497D;">Ron Andruff</span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#1F497D;">RNA Partners</span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#1F497D;"><a rel="nofollow" target="_blank" href="http://www.rnapartners.com/"><span style="color:#0563C1;">www.rnapartners.com</span></a>
</span></b></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Arial", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in;">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">
<a href="mailto:owner-bc-gnso@icann.org">owner-bc-gnso@icann.org</a> [mailto:owner-<a href="mailto:bc-gnso@icann.org">bc-gnso@icann.org</a>]
<b>On Behalf Of </b>Smith, Bill<br>
<b>Sent:</b> Friday, August 16, 2013 13:50<br>
<b>To:</b> Mari Jo Keukelaar<br>
<b>Cc:</b> Smith, Bill; bc - GNSO list<br>
<b>Subject:</b> Re: [bc-gnso] BC comment on singular plural</span></p>
</div>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<p class="MsoNormal">Mari Jo, </p>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">Excellent post. No easy answers… except for ICANN to abandon what has become and will remain a hopelessly complex and expensive transition of the DNS from a taxonomy-based system to a market-based one. </p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">Where there was once order, we will now have "competition". "Dot chico" and "dot chica" can compete between themselves and with "dot child", "dot children", and a myriad of semantically similar but linguistically distinct TLDs. In a market-based
system this is goodness. It will result in an increased pool of available names. Typically an increase in supply without a commensurate increase in demand results in lower prices.</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">Over time, we may see consolidation of TLDs as competition winnows out the less fortunate in this expansion. We will then have name collisions at the second level which will bring an opportunity for yet more competition and profit making. Regretfully,
consumers (in the large) won't really benefit because as a rule they better understand simplicity, order, and stability. Change is not necessarily bad, but it can impact consumers in significant ways, not always positive.</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">For me, "doing the right thing" would have been a rather more orderly expansion of the gTLD space. Given that that train is far out of the station, we are left with how to deal with the complexity of an arbitrary expansion. Part of the
complexity in the "current new" system is the policy decision to avoid similarity. Making such decisions requires judgement and weighing a considerable number of factors in order to arrive at a "common sense" decision. ICANN (the community) works best with
a smaller number of factors and ICANN (the corp) prefers to make no judgements.</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">If we are committed to the market-based approach, perhaps the best path forward is to ignore similarity altogether and allow the market to decide. I say this only partly in jest given the time we have all invested in this discussion and
the apparent arbitrary decisions we are seeing in the English-only singular/plural cases. There seems no point in endlessly debating similarity if in the end an arbitrary decision will be rendered. Better to let the market decide and save everyone a great
deal of time.</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">Consumers will eventually settle the matter, at least that's the theory.</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">Bill</p>
</div>
<div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<div>
<p class="MsoNormal">On Aug 16, 2013, at 10:08 AM, Mari Jo Keukelaar <<a rel="nofollow" ymailto="mailto:mj@johnberryhill.com" target="_blank" href="javascript:return">mj@johnberryhill.com</a>> wrote:</p>
</div>
<p class="MsoNormal"><br>
<br>
</p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt;">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;">It is worth noting that this discussion is unfortunately referred to as "singular/plural" as a consequence of our Anglo-centrism; even there the discussion
does not take into account Germanic plural forms in English - e.g. child/children or other northern European English adoptions like wife/wives or mouse/mice, where the SWORD algorithm would likely fail to pick up enough in the line of similarity to provide
some evidence of a likelihood of confusion, let alone something impermissible. I, for one, have never been confused by whether "wife" and "wives" mean two very different things, and I hope I've managed to clearly convey this concept to my husband.</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;">As for the subject of what is "common sense," we may all have common sense but we do not have a common language. I would be curious to know what "common sense"
dictates, for example, when discussing masculine and feminine forms in Romance languages. In Spanish, chico and chica are as different as night and day. Any boy and girl would tell you the same; they all have cooties. If one doesn't know what "chico" and "chica"
mean, however, - which is likely true for the majority of internet users - is the answer, as a policy matter, different?</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;">The answer is very different if you speak Spanish, but the "majority language" of internet users is most likely not Spanish, nor is it English. If we are
seeking to make policy which is generally applicable to the global internet, does it matter whether "chico" and "chica" mean two different things to one language group, while appearing to be pretty much the same thing for everyone else? If one speaks neither
English nor Spanish, "chico" and "chica" probably appear to be more similar than, say, "thing" or "things", which are at least different string lengths.</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;">Quite frankly, to me, all of the Arabic, Hebrew and Chinese IDN TLDs look very much alike since I am unfamiliar with those scripts. Given my ignorance, and
applying the principle of “I doubt that I am alone,” shouldn't we also be asking "confusing to whom?"</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri",
"sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;">Unless we are seeking to make a limited policy on "English Nouns With Latinate Plurals" we are going to have to become very cunning linguists indeed, as the
next round will find us conjugating verbs and making adverbs out of adjectives while the entire non-English speaking world patiently waits for valuable policy attention to be paid to some issue which might be relevant to them.</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;">As with the repeated "what about us?" comments from users of pictographic writing whenever the subject of "single character domains" came up, we should be
sensitive to how the "singular/plural issue" is defined, because we are only addressing a subset of English nouns.</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;">Is the goal here to devise a general rule addressing "things which are similar across the board" or are we embarking on an exercise which will eventually
lead to a policy compendium addressing the peculiarities of every human language, guided by a "common sense" standard? If the latter, that is going to take considerable time and resources. As for “doing the right thing” I am hard pressed to know how to build
a policy or a standard around such an ill defined concept. It reminds me of obscenity being something I know when I see it.</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;">Mari Jo</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in;">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma", "sans-serif";">From:</span></b><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma", "sans-serif";"> </span></span><span style="font-size:10.0pt;font-family:"Tahoma", "sans-serif";"><a rel="nofollow" ymailto="mailto:owner-bc-gnso@icann.org" target="_blank" href="javascript:return">owner-bc-gnso@icann.org</a>
[mailto:owner-<a rel="nofollow" ymailto="mailto:bc-gnso@icann.org" target="_blank" href="javascript:return">bc-gnso@icann.org</a>]<span class="apple-converted-space"> </span><b>On Behalf Of<span class="apple-converted-space"> </span></b>Smith, Bill<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Wednesday, August 14, 2013 7:03 PM<br>
<b>To:</b><span class="apple-converted-space"> </span>Andy Abrams<br>
<b>Cc:</b><span class="apple-converted-space"> </span>Mari Jo Keukelaar; <a rel="nofollow" ymailto="mailto:jscottevans@yahoo.com" target="_blank" href="javascript:return">
jscottevans@yahoo.com</a>; bc - GNSO list<br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [bc-gnso] BC comment on singular plural</span></p>
</div>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">+1</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">I don't see this as a trademark issue. Rather it is an issue of common sense and "doing the right thing". It seems we lose on both counts.</p>
</div>
<div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<div>
<p class="MsoNormal">On Aug 14, 2013, at 1:34 PM, Andy Abrams <<a rel="nofollow" ymailto="mailto:abrams@google.com" target="_blank" href="javascript:return"><span style="color:purple;">abrams@google.com</span></a>> wrote:</p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<br>
</p>
</div>
<div>
<div>
<p class="MsoNormal">Hi Mari Jo,</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">Thank you for your input - I think we're actually opposite each other in the other pending car/cars case, so it's good to get other perspectives. You raise some very valid points, and I think the ICDR will likely agree with your legal
reasoning. But speaking only for myself, my concerns are not based on the application of trademark law at the top level. Rather, as an Internet policy matter, I respectfully believe that allowing generic singular-plural TLDs will be confusing to consumers
and bad for businesses that wish to operate websites on one of the two TLDs. Imagine a case where a legitimate business is faced with negative PR, or worse, scams/phishing, etc. because half of their prospective customers mistakenly go to used.cars instead
of used.car. Secondly, simply as a matter of process, if is literally impossible to win a string confusion objection unless ICANN had already placed the strings in contention (thereby making the need for an objection moot), it would have been nice to have
that guidance prior to everyone expending money and resources on these proceedings. I guess we'll learn very soon whether the remaining singular-plural decisions follow suit...</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">Best,</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">Andy</p>
</div>
<div>
<div style="margin-bottom: 12pt; "> <br class="webkit-block-placeholder">
</div>
<div>
<div>
<p class="MsoNormal">On Wed, Aug 14, 2013 at 12:41 PM, Mari Jo Keukelaar <<a rel="nofollow" ymailto="mailto:mj@johnberryhill.com" target="_blank" href="javascript:return"><span style="color:purple;">mj@johnberryhill.com</span></a>> wrote:</p>
</div>
<div>
<p>To be clear: the decisions reached in car/cars and hotel/hotels are actually more in keeping with present interpretation of trademark law than they are dissimilar since plurals of generic words are not "confusingly similar" to other generic words under traditional
trademark analysis. We should avoid applying terminology from trademark law out of context, in what are contests between strings that are not themselves trademarks.</p>
<div> <br class="webkit-block-placeholder">
</div>
<p>In these "generic word" disputes, the objecting parties have tended to make arguments based on trademark confusing similarity analysis. In that analysis, though, the trademark has already been determined to be distinctive. So those circumstances involve
comparing something to something else which has established distinctiveness. The point is to avoid erosion of what are already distinctive marks. That reasoning just does not apply to generic terms.</p>
<div> <br class="webkit-block-placeholder">
</div>
<p>This has been true for years under the Uniform Domain Name Dispute Policy. No confusing similarity was found between “Tire Discounter” and “Tire Discounters” despite the difference of only a single letter in Tire Discounters, Inc. v.<span class="apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://tirediscounter.com/"><span style="color:purple;">TireDiscounter.com</span></a>,
NAF Claim Number:</p>
<p>FA0604000679485 (“[b]ecause the mark is merely descriptive, small differences matter”).</p>
<div> <br class="webkit-block-placeholder">
</div>
<p>Nor was confusing similarity found between the “The Suit Warehouse” mark and a “SuitWarehouse” domain name because the presence of descriptively common words necessarily restricts the “confusingly similar” analysis very closely to exact identity. The Men's
Wearhouse Inc. v. Brian Wick d/b/a<span class="apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://defaultdata.com/"><span style="color:purple;">Defaultdata.com</span></a>, NAF Claim Number: FA0208000117861.</p>
<div> <br class="webkit-block-placeholder">
</div>
<p>The results have been no different under the Lanham Act. In a similarity analysis between “ENTREPRENEUR” and “ENTREPRENEUR PR” in two internet domain names, the 9th Circuit declined to find confusing similarity, noting, “[i]n the Internet context, consumers
are aware that domain names for different Web sites are quite often similar, because of the need for language economy, and that very small differences matter.” Entrepreneur Media, Inc. v. Smith, 279 F. 3d 1135, 1147 (9th Cir., 2002).</p>
<div> <br class="webkit-block-placeholder">
</div>
<p>Additionally, the notion that terms lacking distinctiveness are not subject to "confusing similarity" analysis is also true outside of the US, as the High Court of Australia opined in Hornsby Building Information Centre Pty Ltd v. Sydney Building Information
Centre Ltd, [1978] HCA 11:</p>
<div> <br class="webkit-block-placeholder">
</div>
<p>“There is a price to be paid for the advantages flowing from the possession of an eloquently descriptive trade name. Because it is descriptive it is equally applicable to any business of a like kind, it’s very descriptiveness ensures that it is not distinctive
of any particular business.”</p>
<div> <br class="webkit-block-placeholder">
</div>
<p>Of course if you are dealing with established distinctive marks then, yes, "Verizons" will be confusingly similar to "Verizon". But the scope of "confusing similarity" has always been delimited by the distinctiveness of the mark under analysis.</p>
<div> <br class="webkit-block-placeholder">
</div>
<p>That a panel, applying ordinary principles of application of the trademark term "confusingly similar" would decline to find such similarity between two generic words is neither surprising nor unusual. If this was an unexpected result, then one might just
as well ask how<span class="apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://lawyer.com/"><span style="color:purple;">lawyer.com</span></a><span class="apple-converted-space"> </span>and<span class="apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://lawyers.com/"><span style="color:purple;">lawyers.com</span></a><span class="apple-converted-space"> </span>manage
to exist under different ownership (along with<span class="apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://cars.com/car.com"><span style="color:purple;">cars.com/car.com</span></a>,<span class="apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://house.com/houses.com"><span style="color:purple;">house.com/houses.com</span></a><span class="apple-converted-space"> </span><a rel="nofollow" target="_blank" href="http://dog.com/dogs.com"><span style="color:purple;">dog.com/dogs.com</span></a>,
and many other generic words).</p>
<div> <br class="webkit-block-placeholder">
</div>
<p>Furthermore, and perhaps even more importantly, under the ICANN rules we are not merely looking at "confusing similarity" but rather, a higher standard of "impermissible" confusing similarity. Comparing these string objections to outcomes in trademark cases
is the proverbial mixing of apples and oranges because the generic strings involved are not, as a threshold matter, even trademarks. The lack of distinctiveness in generic words drives the result that they are not entitled to the broad swath of protection
afforded that which would be impermissibly confusing.</p>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">ICANN has done much to protect trademark interests and we can all argue as to whether they have done enough or not. Here, however, we are not even talking about trademarks; we are dealing with two generic terms. The panels did not lose
sight of that and I wonder why we sit here bashing them for applying the Policy we all approved and the law over which we’ve little control.</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">Mari Jo Keukelaar, M.A./J.D.</p>
</div>
<div>
<p class="MsoNormal">Name Administration, Inc.</p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";color:#1F497D;"> </span><br class="webkit-block-placeholder">
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in;">
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma", "sans-serif";">From:</span></b><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma", "sans-serif";"> </span></span><span style="font-size:10.0pt;font-family:"Tahoma", "sans-serif";"><a rel="nofollow" ymailto="mailto:owner-bc-gnso@icann.org" target="_blank" href="javascript:return"><span style="color:purple;">owner-bc-gnso@icann.org</span></a><span class="apple-converted-space"> </span>[mailto:<a rel="nofollow" ymailto="mailto:owner-bc-gnso@icann.org" target="_blank" href="javascript:return"><span style="color:purple;">owner-bc-gnso@icann.org</span></a>]<span class="apple-converted-space"> </span><b>On
Behalf Of<span class="apple-converted-space"> </span></b>Andy Abrams<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Tuesday, August 13, 2013 7:09 PM<br>
<b>To:</b><span class="apple-converted-space"> </span>Steve DelBianco</span></p>
</div>
<div>
<p class="MsoNormal"><br>
<b>Cc:</b><span class="apple-converted-space"> </span>bc - GNSO list</p>
</div>
<div>
<p class="MsoNormal"><b>Subject:</b><span class="apple-converted-space"> </span>Re: [bc-gnso] BC comment on singular plural</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<div>
<p class="MsoNormal">Update: the first singular-plural decisions have come in.<span style="font-size:10.0pt;font-family:"Arial", "sans-serif";"> Both singular-plural decisions have gone <i>against </i></span><span style="font-family:"Arial", "sans-serif";">a
finding of string confusion (our car/cars objection against Donuts, and a Hotel Top-Level-Domain S.a.r.l. v.<a rel="nofollow" target="_blank" href="http://booking.com/"><span style="color:purple;">Booking.com</span></a><span class="apple-converted-space"> </span>B.V. for
hotel/hotels). In the car/cars decision, the Panel stated: "It is true that </span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial", "sans-serif";">the ICANN visual similarity standards appear quite narrow, but it is not the role [of] this Panel to substitute for ICANN’s expert technical findings." In the hotel/hotels decision, the
Panel similarly stated: "I find persuasive the degrees of similarity or dissimilarity between the strings by use of the String Similarity Assessment Tool, that ICANN did not put the applications for .HOTEL and .HOTELS in the same contention set." In other
words, the early results suggest that the ICDR may give complete deference to ICANN's earlier refusal to essentially find any instances of string confusion, no matter how close the strings.</span></p>
</div>
<div><span style="font-family:"Arial", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial", "sans-serif";">Andy</span></p>
</div>
</div>
</div>
<div>
<div style="margin-bottom: 12pt; "> <br class="webkit-block-placeholder">
</div>
<div>
<div>
<p class="MsoNormal">On Thu, Apr 11, 2013 at 12:50 AM, Steve DelBianco <<a rel="nofollow" ymailto="mailto:sdelbianco@netchoice.org" target="_blank" href="javascript:return"><span style="color:purple;">sdelbianco@netchoice.org</span></a>> wrote:</p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri", "sans-serif";">Here's what we just told the Board at the Public Forum, on behalf of the BC</span></p>
</div>
<div>
<div><span style="font-family:"Calibri", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">ICANN’s String Similarity Panel was to place into contention sets any strings that create a possibility of user confusion.</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">But in late February ICANN published contention sets that did NOT include 24 pairs of singular-plural forms of the same string (English and Spanish) Sport(s) Loan(s)
Web(s) Game(s) Hotel(es)</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">Risks of allowing both singular and plural TLDs for the same word are<span class="apple-converted-space"> </span><u>well understood</u>.</span></p>
</div>
<div style="margin-left:.5in;">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">-confusion</span></p>
</div>
<div style="margin-left:.5in;">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">-precedent for the<span class="apple-converted-space"> </span><i>next</i><span class="apple-converted-space"> </span>round</span></p>
</div>
<div style="margin-left:.5in;">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">-ICANN looking pretty ridiculous</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">What’s<span class="apple-converted-space"> </span><u>not understood</u><span class="apple-converted-space"> </span>is how it happened and what we can do about it.</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">First response is to ask if the panelist follow GNSO Policy on confusingly similar.</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri",
"sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">Second response is “Chong” ( Chinese for “Do-over” )</span></p>
</div>
<div style="margin-left:.5in;">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">-Do-over on just these 24 pairs</span></p>
</div>
<div style="margin-left:.5in;">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">- WIPO Mediation Rules, Article 1 says, “Words used in the singular include the plural and vice versa, as the context may require.”</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">Guess we could correct the Guidebook (plurals<span class="apple-converted-space"> </span><u>are</u><span class="apple-converted-space"> </span>confusingly similar)</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">String Confusion Objections on 7 of these pairs are in the hands of the ICDR rightnow. If ICSR does the right thing and finds these pairs<span class="apple-converted-space"> </span><u>should</u><span class="apple-converted-space"> </span>be
contention sets, The Board can apply this rule to ALL 24 pairs</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">Failing that, there’s Formal Reconsideration. </span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">We all worry about threat from inter-governmental groups just waiting for ICANN to stumble.</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">We have enough vulnerability to stumble with so many unknowns in the new gTLD launch.</span></p>
</div>
<div><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";"> </span><br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri", "sans-serif";">No need to add to our vulnerability with this self-inflicted wound</span></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><br>
<br clear="all">
</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">--<span class="apple-converted-space"> </span><br>
<span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#333333;">Andy Abrams | Trademark Counsel<br>
</span><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#3333FF;">G</span></b><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:red;">o</span></b><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#FFCC00;">o</span></b><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#3333FF;">g</span></b><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#33CC00;">l</span></b><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:red;">e</span></b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#333333;"> |
1600 Amphitheatre Parkway, Mountain View, CA 94043</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";"><a rel="nofollow" target="_blank" href="https://www.google.com/voice#phones" title="Go to phones"><span style="color:purple;text-decoration:none;">(650) 669-8752</span></a></span></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><br>
<br clear="all">
</p>
</div>
<div> <br class="webkit-block-placeholder">
</div>
<div>
<p class="MsoNormal">--<span class="apple-converted-space"> </span><br>
<span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#333333;">Andy Abrams | Trademark Counsel<br>
</span><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#3333FF;">G</span></b><b><span style="font-size:10.0pt;font-family:"Arial",
"sans-serif";color:red;">o</span></b><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#FFCC00;">o</span></b><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#3333FF;">g</span></b><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#33CC00;">l</span></b><b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:red;">e</span></b><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#333333;"> |
1600 Amphitheatre Parkway, Mountain View, CA 94043</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial", "sans-serif";color:#333333;"><a rel="nofollow" target="_blank" href="https://www.google.com/voice#phones" title="Go to phones"><span style="color:purple;text-decoration:none;">(650) 669-8752</span></a></span></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div> <br class="webkit-block-placeholder">
</div>
</div>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>