<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page WordSection1 {margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P.MsoListParagraph {
MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
LI.MsoListParagraph {
MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
DIV.MsoListParagraph {
MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
SPAN.EmailStyle18 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d
}
.MsoChpDefault {
FONT-SIZE: 10pt
}
OL {
MARGIN-BOTTOM: 0in
}
UL {
MARGIN-BOTTOM: 0in
}
</style><style id="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body lang="EN-US" link="blue" vlink="purple" fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<p>Mike:</p>
<p> </p>
<p>I'm in general agreement with points 1-3 of your letter.</p>
<p> </p>
<p>On point 4, as previously stated, I'm against the URS including a transfer option, especially if there's no additional due diligence, and most especially as there is as of yet no indication that any credible URS arbitration provider can be secured at the
$300 filing level. Assuming that a credible provider or providers can be secured, I would again propose that rather than having a transfer option, which turns URS into a bargain basement UDRP<a></a><a></a>, that suspended domains be put on a permanent do not
re-register list -- which avoids the conflict with UDRP<a></a><a></a> and also obviates the need tor TM owners<a></a> to pay defensive registration fees forever.</p>
<p> </p>
<p>On point 5, I generally<a></a> support limiting TMC<a></a><a></a> to exact<a></a> matches, especially as that has always been its purpose. If any notice is to be given in<a></a><a></a> regard to brand + keyword it must be a balanced notice that<a></a><a></a>
alerts registrants that their proposed domain name MAY OR MAY NOT be infringing, depending on use of the website, because, as pointed out in my earlier e-mail, the mere inclusion of a TM in a longer domain name is not determinative of infringement. And I'm
absolutely opposed<a></a><a></a> to inclusion of "Typos" in the TMC<a></a><a></a> database as there is no possible way to limit that vast expansion<a></a><a></a> of TM rights into the DNS space -- and, as you yourself already pointed out, every dictionary<a></a><a></a>
word is already a TM for something<a></a><a></a> so even made-up<a></a><a></a> words for Internet startups -- like Google -- would trigger warnings under such a regime.</p>
<p> </p>
<p>best, Philip </p>
<div>
<p> </p>
<div style="FONT-FAMILY: Tahoma; FONT-SIZE: 13px">
<p><strong><font color="#000080">Philip S. Corwin, Founding Principal</font></strong></p>
<p><strong><font color="#000080"><a></a><strong><font color="#000080"><a></a></font></strong><strong><font color="#000080"><strong><font color="#000080">Virtualaw</font></strong></font></strong> LLC</font></strong></p>
<p><strong><font color="#000080">1155 F Street, NW</font></strong></p>
<p><strong><font color="#000080">Suite 1050</font></strong></p>
<p><strong><font color="#000080">Washington, DC 20004</font></strong></p>
<p><strong><font color="#000080">202-559-8597/Direct</font></strong></p>
<p><strong><font color="#000080">202-559-8750/Fax</font></strong></p>
<p><strong><font color="#000080">202-255-6172/cell</font></strong></p>
<p><strong><font color="#000080"></font></strong> </p>
<p><em><strong><font color="#000080">"Luck is the residue of design" -- Branch Rickey</font></strong></em></p>
<p><font color="#000080"></font> </p>
</div>
</div>
<div style="FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px">
<hr tabindex="-1">
<div style="DIRECTION: ltr" id="divRpF914235"><font color="#000000" size="2" face="Tahoma"><b>From:</b> bc-private-bounces@icann.org [bc-private-bounces@icann.org] on behalf of icann@rodenbaugh.com [icann@rodenbaugh.com]<br>
<b>Sent:</b> Thursday, December 29, 2011 2:31 PM<br>
<b>To:</b> 'Marilyn Cade'; 'bc-private icann.org'; 'Bc GNSO list '<br>
<b>Subject:</b> Re: [Bc-private] URGENT - redrafted letter from officers to ICANN Board re improvements in the new gTLD program<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Why are our deliberations about policy positions so often pushed by a few members to the private list? I think that is contrary to the reason we have a
public list, and to our stated commitment to develop policy openly and transparently. I am moving it back to the public list where it belongs.</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I attach a redline with suggestions for improvement and accuracy in Marilyn’s redraft. It requires changes, or at least a formal policy process per our
Charter if she is going to maintain some of her stated positions.</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">The major issues I see with this, at this point:
</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p style="TEXT-INDENT: -0.25in" class="MsoListParagraph"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><span>1.<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">The BC has never discussed or recommended any sort of “block list” policy, and this would be a major policy recommendation that must go through the policy
development procedures in Section 7 of the <a href="http://www.bizconst.org/charter.htm" target="_blank">
BC Charter</a>. The implementation of such a policy across all TLDs would be unfathomable. As you state it, United can go and prevent anyone from registering United in any TLD? (Um, “which United”… one might ask.) Oh, and lucky for Siemens, they own ‘MUSIC’
as a registered trademark for hearing aids in the USA since 1997! ICANN has already given away new TLD operators’ rights to use any country name, ICANN’s trademarks, etc., for absolutely no logical reason. Now you want the BC to propose that all words that
are registered trademarks anywhere in the world can be blocked by any holder of any such registration, across every new TLD in the world?
<u>At minimum</u>, this will require more thoughtful, and formal, written policy development per our Charter. You can’t just throw this skeletal and dubious proposal into a letter to the Board, merely because you and a few other members like the idea. Particularly
while giving the membership just one holiday weekend to consider your idea?! There is no rush to get such a position developed, if that is what the membership wants to do, but I suspect the idea will die fairly quickly once people think for a moment about
the implications.</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p style="TEXT-INDENT: -0.25in" class="MsoListParagraph"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><span>2.<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Your statement about Community Priority should restate the position we have agreed upon in prior, formally developed policy positions on this issue. Specifically,
we have recommended lessening the CPE passing score from 12 to 11 points. We have never discussed giving ‘brands’ any priority over other applicants, unless somehow they can qualify as a community-based applicant. Again the practical implementation of such
a policy is unfathomable, given that almost every single word imaginable is registered somewhere as a trademark, or otherwise used as a ‘brand’ by someone, somewhere.</span></p>
<p class="MsoListParagraph"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p style="TEXT-INDENT: -0.25in" class="MsoListParagraph"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><span>3.<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">The BC has never proposed a centralized URS service, and I don’t know what you mean by this. Instead we have expected it to operate similar to the UDRP,
with several accredited providers, and we suggest ICANN have a contract with all providers. So that proposal needs to come out.</span></p>
<p class="MsoListParagraph"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p style="TEXT-INDENT: -0.25in" class="MsoListParagraph"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><span>4.<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Agreed with URS transfer option, as we have long agreed in our written policy positions, but why are we now suggesting an additional fee to trademark owners?
Again this seems like a new and unhelpful idea that has not been properly discussed, so that proposal should come out.</span></p>
<p class="MsoListParagraph"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p style="TEXT-INDENT: -0.25in" class="MsoListParagraph"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><span>5.<span style="FONT: 7pt 'Times New Roman'">
</span></span></span><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">We should reiterate our call for the TMC to include “brand + keyword” and brand typosquats, as we have previously agreed in prior written policy documents.
That would be the single biggest help to trademark owners and businesses, and could be easily achievable as there really is no downside consequence from additional notices going out to applicants for domain registration.</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I hope everyone has a happy new year, it is regretful that some in the BC leadership are so urgently pushing new proposals to us at this point in time.
I frankly don’t see the urgency, unless someone is hoping to delay the new TLD application window from opening, as scheduled for more than six months now…</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Mike Rodenbaugh</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">RODENBAUGH LAW</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">tel/fax: +1.415.738.8087</span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><a href="http://rodenbaugh.com" target="_blank">http://rodenbaugh.com</a>
</span></p>
</div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"></span> </p>
<div>
<div style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class="MsoNormal"><b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</span></b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> bc-private-bounces@icann.org [mailto:bc-private-bounces@icann.org]
<b>On Behalf Of </b>Marilyn Cade<br>
<b>Sent:</b> Thursday, December 29, 2011 8:53 AM<br>
<b>To:</b> bc-private icann.org<br>
<b>Subject:</b> [Bc-private] URGENT - redrafted letter from officers to ICANN Board re improvements in the new gTLD program</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">Dear BC members -- although it is a holiday period, I must ask that you focus on the redraft of the improvements document which has been circulating on the bc-private
list. </span></b><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"></span></p>
<div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">I have edited the earlier version of the improvements, added in accurate WHOIS at the request of a member, and a reference to not sending 'brands' or NGO or charitable gTLD
string applicants into auctions. This was called to my attention by an applicant for BC membership that has just began to learn about ICANN. </span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">The significant addition is the do not register/registry block service, which is modeled after the IFFOR .XXX service in many ways. It is challenging to consider defensive
registrations costs and UDRP costs across potentially hundreds of new gTLDs, a single
<i>cross all gTLD block </i>on a number of names associated with trademarks will at least lower the defensive registration burden somewhat. I proposed a three year period, followed by an assessment. </span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">In order to have impact, this really needs to be sent out Tuesday, January 3. The letter is silent on a delay, but does recognize that many global businesses are highly
concerned, and that the BC has consistently tried to get improvements to the program. Some are expensive to ICANN, but all are achievable improvements. </span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">I incorporated the request to express support for multi stakeholder nature of ICANN raised by a couple of members. </span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"></span> </p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>