<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks MJ, I had similar thoughts but hadn’t got to draft them yet.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I believe the BC has previously proposed (at least in the STI if not also elsewhere) that TM owners could self-select the brand/keyword combinations that they wish to register in the TMC, so long as the keyword is present in a national trademark registration somewhere. This approach seemed to work well with the dotAsia launch. If there is some slight incremental cost to registering each combination, that would provide some disincentive for TM owners to overreach. Perhaps the BC could coalesce around a proposal like this again now?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Also, putting this back to the public BC list where it belongs.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Mike<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Mike Rodenbaugh<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>RODENBAUGH LAW<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>tel/fax: +1.415.738.8087<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://rodenbaugh.com"><span style='color:blue'>http://rodenbaugh.com</span></a> <o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><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 style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> bc-private-bounces@icann.org [mailto:bc-private-bounces@icann.org] <b>On Behalf Of </b>Mari Jo Keukelaar<br><b>Sent:</b> Friday, September 14, 2012 11:25 AM<br><b>To:</b> 'bc-private icann.org'<br><b>Subject:</b> Re: [Bc-private] [bc-gnso] For expedited review by 17-Sep-2012: proposed expansion/clarification of BC's position on TM Claims Notices<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><br>After reading and considering the proposal made here, we find it difficult to understand how this would work as a practical matter. First, particularly in the EU, goods and services descriptions can go on for hundreds of words; and second, how do you define the "a generic term from the description of goods and services?"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Just taking the example provided, and applying reality, the G&S description for one of the PAYPAL registrations is:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-----<o:p></o:p></p><p class=MsoPlainText>"PAYPAL"<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Clearing and reconciling financial transactions via a global computer network; Providing a wide variety of banking services and providing <o:p></o:p></p><p class=MsoPlainText>financial services, namely, credit card services, processing and transmission of bills and payments thereof, and insurance for financial <o:p></o:p></p><p class=MsoPlainText>transactions conducted via global computer network<o:p></o:p></p><p class=MsoPlainText>----<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>From this we get such strings as:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>paypaland<o:p></o:p></p><p class=MsoPlainText>paypalvia<o:p></o:p></p><p class=MsoPlainText>paypalwide<o:p></o:p></p><p class=MsoPlainText>paypala<o:p></o:p></p><p class=MsoPlainText>paypalnamely<o:p></o:p></p><p class=MsoPlainText>paypalthereof<o:p></o:p></p><p class=MsoPlainText>paypalconducted<o:p></o:p></p><p class=MsoPlainText>paypalcomputer<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>And other senseless things. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Of course, "PAYPAL" is a fanciful mark and other marks come with a different set of problems. When you consider the fact that there are trademarks for things like "O", claimed by Oprah Winfrey, Oakley sunglasses, and Overstock.com, then every time someone registers a domain name beginning with the letter O, there will be hundreds of queries and notifications required.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Now, you could, and most likely will, say "we only mean the words in the G&S which actually relate to the goods and services." In that instance, the answer presumes that someone is going to go through all of the G&S descriptions and flag those which duly relate. That cannot be done on an automated basis.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Furthermore, which language are we looking at for the G&S for EU registrations? If the proposal intends all languages, then the problem <o:p></o:p></p><p class=MsoPlainText>of large EU G&S descriptions is again multiplied.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Then there is an implementation issue:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The TCH is thus far envisioned as a blackbox which matches "inputstring" to "mark". If someone is registering "paypaland" what is the input query to the TCH? If the query is "paypaland", it comes back "no match".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The question is, in querying the TCH, how is the software at either end supposed to know which part of the input string is a mark?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Finally, the TCH is envisioned to enable identification of trademark strings. I may own five different trademark registrations for "EXAMPLE" encompassing five different sets of goods and services. There are, of course, a number of "PAYPAL" trademark registrations.<o:p></o:p></p><p class=MsoPlainText>Whereas before I believed I would only have to submit one of my trademark registrations to the TCH in order to enter the mark into the <o:p></o:p></p><p class=MsoPlainText>TCH, under this scheme I am being told I should submit five different registrations of the same mark (since I now wish to protect all of my listed goods and services)?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Name Administration agrees that the TCH should be a more flexible database capable of implementing a variety of operations. There is <o:p></o:p></p><p class=MsoPlainText>significant pushback on the possibility of it becoming a source of public trademark registration data in competition with commercial <o:p></o:p></p><p class=MsoPlainText>providers of such information. We believe that is the primary tension which prevents any number of innovative solutions to be implemented.<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Mari Jo Keukelaar, M.A./J.D.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>On behalf of Name Administration, Inc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><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 style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:owner-bc-gnso@icann.org">owner-bc-gnso@icann.org</a> <a href="mailto:[mailto:owner-bc-gnso@icann.org]">[mailto:owner-bc-gnso@icann.org]</a> <b>On Behalf Of </b>Steve DelBianco<br><b>Sent:</b> Thursday, September 13, 2012 1:08 PM<br><b>To:</b> <a href="mailto:bc-gnso@icann.org">bc-gnso@icann.org</a><br><b>Subject:</b> [bc-gnso] For expedited review by 17-Sep-2012: proposed expansion/clarification of BC's position on TM Claims Notices<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>To all BC members:<o:p></o:p></span></p></div></div></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><div><div><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>Your executive committee is seeking member review and approval of an incremental change to the BC's present position on rights protection mechanism (RPMs) for new gTLDs. We have authorized an expedited review since this is a small change and it would be useful to know the BC position during new gTLD discussions in Washington DC on Tuesday 18-Sep. <o:p></o:p></span></p></div></div></div></div></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><div><div><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>The proposed change would allow TM owners to specify variants on their TM that would generate TM Claims notices to registrants. This change was suggested at the Brand Summit participants in their letter to the US Govt (<a href="http://www.aipla.org/advocacy/intl/Documents/JointLetter-BrandOwners-SecondLevelRights-gTLDProgram.pdf">link</a>). The proposed change is to: <o:p></o:p></span></p></div></div></div></div></div><blockquote style='margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div></blockquote><div><div><div><div><blockquote style='margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal><b><span style='font-family:"Calibri","sans-serif";color:black'>Require the TM Cl</span></b><span class=apple-style-span><b><span style='font-size:13.5pt;font-family:"Calibri","sans-serif";color:black'>aims Service to issue warnings for any registration that consists of the mark and a generic term from the description of goods and services in the registration deposited with the Trademark Clearinghouse.</span></b></span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div></blockquote><blockquote style='margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>For example, Paypal is a registered TM that includes "payments" in its description of goods and services, so TM Claims notices would be issued to anyone that registered paypalpayments.tld. Same would apply to verizon-phones.tld, yahoomail.tld, etc.<o:p></o:p></span></p></div></blockquote><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>You may ask, How does this proposal differ from the existing BC position? Here's how:<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>In Jan-2012 the BC approved the attached ballot of RPMs, which was then summarized in our <a href="http://www.bizconst.org/Positions-Statements/BC%20request%20for%20implementation%20improvements.pdf">letter</a> to ICANN leadership in Feb-2012. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>The BC voted to require that any domain name recovered in URS/UDRP be added to TM Clearinghouse, which would therefore automatically generate TM Claim Notices to subsequent registration attempts of those strings. See item 3.4 on page 2:<o:p></o:p></span></p></div><div><div><div><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><blockquote style='margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt;border-width:initial;border-color:initial'><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>(3.4) Successful URS complainants should have option to transfer or suspend the name, and such names should generate TM Claims Notice for subsequent registrations. <o:p></o:p></span></p></div></blockquote><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>The BC also went well beyond exact matches for allowing TM owners to acquire Domain Blocks. See item 8 on page 4:<o:p></o:p></span></p></div><div><div><blockquote style='margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt;border-width:initial;border-color:initial'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span class=apple-style-span><span style='font-family:"Calibri","sans-serif";color:black'>(8) Add a “do not register/registry block” service to the Trademark Clearinghouse, allowing any trademark holder to pay a one time fee to permanently prevent registration of names that are an identical match <b>or include the identical match trademark name</b>.</span></span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></blockquote></div></div></div></div></div></div></div></div><div><div><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>So please reply to me (or reply all) to indicate whether you approve or oppose the change by 17-Sep-2012. <o:p></o:p></span></p></div></div></div></div></div></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div><div><div><div><div><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>If by that date 10% of BC members oppose the change, we will follow the process described in our charter:<o:p></o:p></span></p></div><div><div><blockquote style='margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt;border-width:initial;border-color:initial'><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#009800'>7.3. Approval where there is initial significant disagreement. </span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#009800'>If there are at least 10% of members who oppose a position a mechanism to discuss the issue will be provided by the Vice Chair for policy coordination. This may be an e-mail discussion, a conference call or discussion at a physical meeting. </span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div></blockquote></div></div></div></div></div></div></div><div><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>-- <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>Steve DelBianco<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>Executive Director<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>NetChoice<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><a href="http://www.NetChoice.org">http://www.NetChoice.org</a> and <a href="http://blog.netchoice.org">http://blog.netchoice.org</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>+1.202.420.7482 <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div></div></div><div><div><div><div><div><div><div><blockquote style='margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div></blockquote></div></div></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><div><div><div><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div></div></div></div></div></div></div></div></div></div></div></body></html>