<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css">BODY {
BACKGROUND-COLOR: #ffffff; MARGIN: 5px
}
HR {
COLOR: #000000
}
BODY {
FONT-STYLE: normal; FONT-FAMILY: 'Courier New'; COLOR: #000000; FONT-SIZE: 9pt; FONT-WEIGHT: normal; TEXT-DECORATION: none
}
TABLE {
FONT-STYLE: normal; FONT-FAMILY: 'Courier New'; COLOR: #000000; FONT-SIZE: 9pt; FONT-WEIGHT: normal; TEXT-DECORATION: none
}
SPAN.rvts1 {
FONT-FAMILY: 'Arial'; COLOR: #0000ff; FONT-SIZE: 10pt; FONT-WEIGHT: bold
}
SPAN.rvts2 {
FONT-FAMILY: 'Arial'; COLOR: #000080; FONT-SIZE: 10pt; FONT-WEIGHT: bold
}
SPAN.rvts3 {
FONT-STYLE: italic; FONT-FAMILY: 'Arial'; COLOR: #800000; FONT-SIZE: 10pt
}
A.rvts4 {
FONT-FAMILY: 'Arial'; COLOR: #008000; FONT-SIZE: 10pt; TEXT-DECORATION: underline
}
SPAN.rvts4 {
FONT-FAMILY: 'Arial'; COLOR: #008000; FONT-SIZE: 10pt; TEXT-DECORATION: underline
}
A.rvts5 {
FONT-FAMILY: 'Arial'; COLOR: #008000; FONT-SIZE: 10pt; TEXT-DECORATION: underline
}
SPAN.rvts5 {
FONT-FAMILY: 'Arial'; COLOR: #008000; FONT-SIZE: 10pt; TEXT-DECORATION: underline
}
A.rvts6 {
COLOR: #0000ff; TEXT-DECORATION: underline
}
SPAN.rvts6 {
COLOR: #0000ff; TEXT-DECORATION: underline
}
SPAN.rvts7 {
FONT-FAMILY: 'arial'; COLOR: #000080
}
SPAN.rvts8 {
FONT-FAMILY: 'tahoma'; FONT-WEIGHT: bold
}
SPAN.rvts9 {
FONT-FAMILY: 'tahoma'
}
SPAN.rvts11 {
BACKGROUND-COLOR: #ffffff; FONT-FAMILY: 'calibri'; COLOR: #1f497d; FONT-SIZE: 11pt
}
SPAN.rvts12 {
FONT-FAMILY: 'segoe ui'; FONT-SIZE: 8pt
}
SPAN.rvts13 {
FONT-FAMILY: 'arial black'; COLOR: #000080
}
SPAN.rvts14 {
FONT-STYLE: italic; FONT-FAMILY: 'arial black'; COLOR: #000080
}
A.rvts15 {
FONT-FAMILY: 'tahoma'; COLOR: #0000ff; TEXT-DECORATION: underline
}
SPAN.rvts15 {
FONT-FAMILY: 'tahoma'; COLOR: #0000ff; TEXT-DECORATION: underline
}
SPAN.rvts16 {
FONT-FAMILY: 'calibri'; COLOR: #1f497d; FONT-SIZE: 11pt
}
SPAN.rvts17 {
FONT-FAMILY: 'arial'; COLOR: #0000ff; FONT-SIZE: 12pt
}
SPAN.rvts18 {
FONT-FAMILY: 'arial'; COLOR: #0000ff
}
SPAN.rvts19 {
FONT-FAMILY: 'calibri'; FONT-SIZE: 11pt
}
A.rvts20 {
FONT-FAMILY: 'calibri'; COLOR: #0000ff; FONT-SIZE: 11pt; TEXT-DECORATION: underline
}
SPAN.rvts20 {
FONT-FAMILY: 'calibri'; COLOR: #0000ff; FONT-SIZE: 11pt; TEXT-DECORATION: underline
}
SPAN.rvts21 {
FONT-FAMILY: 'arial'; FONT-SIZE: 12pt
}
SPAN.rvts22 {
FONT-FAMILY: 'arial'
}
SPAN.rvts23 {
FONT-FAMILY: 'segoe ui'
}
A.rvts24 {
FONT-FAMILY: 'segoe ui'; COLOR: #0000ff; TEXT-DECORATION: underline
}
SPAN.rvts24 {
FONT-FAMILY: 'segoe ui'; COLOR: #0000ff; TEXT-DECORATION: underline
}
SPAN.rvts25 {
FONT-FAMILY: 'times new roman'
}
UL {
TEXT-ALIGN: left; PADDING-BOTTOM: 0px; TEXT-INDENT: 0px; MARGIN: 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; PADDING-TOP: 0px
}
OL {
TEXT-ALIGN: left; PADDING-BOTTOM: 0px; TEXT-INDENT: 0px; MARGIN: 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; PADDING-TOP: 0px
}
.rvps1 {
TEXT-ALIGN: center
}
</style><style id="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle="1" ocsi="0">
<div style="FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZE: 13px">
<div>For clarification, the vast majority of domain investors do NOT see major new business opportunities in new gTLDs<a></a><a></a> (Michael Castello<a></a><a></a> and his brother<a></a> David are in the forefront on that view). To the extent that they have
a business model based on owning non-infringing generic<a></a> word domains and benefit from ad revenue driven<a></a> by type-in direct search<a></a> traffic there will be almost no such traffic at new gTLDs<a></a><a></a> and it is doubtful a domain could
generate sufficient PPC<a></a><a></a> revenue<a></a> to offset annual registration costs. Now there is a big movement<a></a> among domainers<a></a><a></a> to developing their best domains -- both because PPC<a></a><a></a> revenue is down as well as that this
is a more profitable use of a good domain -- but time will tell if developing a new gTLD<a></a><a></a> domain is a worthwhile enterprise. Domainers<a></a><a></a> feel very burned by past gTLD<a></a><a></a> rollouts in which investments were not at all rewarded
-- .travel is usually cited as a prime disappointment -- and are skeptical about the business opportunities in any new ones coming along.
</div>
<div> </div>
<div>So ICA's<a></a><a></a> attitude has been anything but "let her rip" in regard to new gTLDs<a></a><a></a> being rolled out. In fact, we are on the record in our prior comment letters as questioning the wisdom<a></a> of near-simultaneous rollout of 500+
new gTLDs<a></a><a></a> on a variety of grounds, and urged ICANN<a></a><a></a> to proceed cautiously and consider paced and prioritized<a></a> introduction.
</div>
<div> </div>
<div>We fully understand the concerns of trademark owners, although we do think they are somewhat exaggerated<a></a>. That is, just as brand owners don't register at every ccTLD<a></a><a></a> there will be lots of new gTLDs<a></a><a></a> where the opportunities
for profitable infringement will be low to nil (that is, a .phone could pose a threat to Verizon but a .cuisine much less so). We have consistently proposed a balanced UDRP<a></a><a></a> reform process that addressed the default case issue for rights holders while<a></a>
also considering<a></a> registrant concerns with the current UDRP<a></a><a></a> -- what<a></a> we have opposed is consideration<a></a> of major new changes in the new gTLD<a></a><a></a> context<a></a> that amounted to one-sided UDRP<a></a><a></a> reform (and
many rights holders and even ICANN<a></a><a></a> staff stated publicly that they hoped that any new rights protections adopted for new gTLDs<a></a><a></a> would rapidly be applied to incumbents<a></a>, so this was hardly an unwarranted concern).</div>
<div> </div>
<div>Finally, to the extent that any new gTLDs<a></a><a></a> achieve market success this is to be welcomed as it will provide new opportunities for domain investors and developers<a></a>, and businesses and individuals generally<a></a>, and hopefully will provide
some pricing constraints at .com and other incumbents<a></a>. My perception<a></a> is that even VeriSign would welcome that development, as being regarded in the DNS space as akin to Microsoft for PCs and Google for search imposes costs as well as benefits
for them. </div>
<div><br>
<div><font size="2" face="Tahoma">
<p style="MARGIN: 4.8pt 0in; FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt"><font color="navy" size="2" face="Arial Black"><span style="FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt"><font face="Arial Black">Philip S. Corwin<span class="Apple-converted-space"> </span><br>
Partner<span class="Apple-converted-space"> </span><br>
Butera<a></a><a></a> & Andrews<span class="Apple-converted-space"> </span><br>
1301 Pennsylvania Ave., NW<span class="Apple-converted-space"> </span><br>
Suite 500<span class="Apple-converted-space"> </span><br>
Washington, DC 20004</font></span></font></p>
<p style="MARGIN: 4.8pt 0in; FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt"><font color="navy" size="2" face="Arial Black"><span style="FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt"><font face="Arial Black"><font face="arial black">202-347-6875 (office)</font><span class="Apple-converted-space"> </span></font></span></font></p>
<p style="MARGIN: 4.8pt 0in; FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt"><font color="navy" size="2" face="Arial Black"><span style="FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt"><font face="Arial Black">202-347-6876 (fax</font>)</span></font></p>
<p style="MARGIN: 4.8pt 0in; FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt"><font color="navy" size="2" face="Arial Black"><span style="FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt"><font face="Arial Black">202-255-6172 (cell)</font></span></font></p>
<p style="MARGIN: 4.8pt 0in; FONT-FAMILY: 'Times New Roman'; FONT-SIZE: 12pt"><font face="Arial"><font face="Arial Black"><em><i><font color="navy" size="2"><span style="COLOR: navy; FONT-SIZE: 10pt">"Luck is the residue of design."</span></font></i></em><font color="navy" size="2"><span style="COLOR: navy; FONT-SIZE: 10pt"><span class="Apple-converted-space"> </span>--
Branch Rickey</span></font></font><font color="navy" size="2"><span style="FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt"></span></font></font></p>
</font></div>
</div>
<div style="FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px">
<hr tabindex="-1">
<div style="DIRECTION: ltr" id="divRpF204530"><font color="#000000" size="2" face="Tahoma"><b>From:</b> Rick Anderson [randerson@waltonglobal.com]<br>
<b>Sent:</b> Sunday, July 18, 2010 7:44 PM<br>
<b>To:</b> michaelc@traveler.com<br>
<b>Cc:</b> sarah.b.deutsch@verizon.com; Phil Corwin; mike@haven2.com; jb7454@att.com; randruff@rnapartners.com; ffelman@markmonitor.com; bc-gnso@icann.org<br>
<b>Subject:</b> DRAFT BC Public Comments on DAGv4<br>
</font><br>
</div>
<div></div>
<div>
<p><font color="navy" size="2" face="Arial">Hi Michael.<br>
<br>
I think it's important that ICANN and the Business Constituency thereof remain focussed upon our own role.<br>
<br>
It could well be that Google has too great a market dominance in search, and it could well be that pro-competition regulatory authorities in various jurisdictions will wish to address that. Perhaps, perhaps not.
<br>
<br>
But this is some distance from our role with regards to the policies we (the ICANN community) put in place around the domain name system.
<br>
<br>
It is NOT our (ICANN's) job to regulate Google, nor to regulate the search advertising market.
<br>
<br>
Our (ICANN's) job is to oversee "...IP address space allocation, protocol identifier assignment, generic and country code Top-Level Domain name system management, and root server system management functions....(through being) dedicated to preserving the operational
stability of the Internet; to promoting competition..."<br>
<br>
Try starting a new business or organization today, and see what .com domain choices are available to you. I know you know the answer - very limited, unless you go to the secondary market. Is this our intent - that future domain name registrants continue to
crowd into the saturated .com space and pay high rates to secondary providers for .com names?<br>
<br>
If it is, then I guess we should continue to drag our heels with respect to new gTLDs, and thereby protect the market for incumbent players.<br>
<br>
If it is not, we should take further steps to open the market.<br>
<br>
<br>
<br>
cheers/Rick <br>
<br>
Rick Anderson <br>
EVP, Walton Global Investments Ltd <br>
randerson@WaltonGlobal.com <br>
cell (403) 830-1798 <br>
<br>
PS: Please note our updated corporate name and email address <br>
</font></p>
<p></p>
<hr tabindex="-1" align="center" size="2" width="100%">
<font size="2" face="Tahoma"><b>From</b>: Michael Castello <br>
<b>To</b>: Rick Anderson <br>
<b>Cc</b>: sarah.b.deutsch@verizon.com ; pcorwin@butera-andrews.com ; mike@haven2.com ; jb7454@att.com ; randruff@rnapartners.com ; ffelman@markmonitor.com ; bc-gnso@icann.org
<br>
<b>Sent</b>: Sun Jul 18 17:03:56 2010<br>
<b>Subject</b>: Re: DRAFT BC Public Comments on DAGv4 <br>
</font>
<p></p>
<p>Rick,</p>
<p><br>
</p>
<p>Thanks for your comments. Ten years ago that might have been the case. Today the monopoly could be seen as Google. It is not Google's fault since many were using direct navigation in the early net but those that did not find tangible content searched for
it. In doing so, search has dominated the way people navigate today. Having hundreds more gTLDs will only enhance that monopoly. Today anyone can register ANY gTLD and get high search ranking and relevance with the right kind of content and input. There is
speculation in gold but in reality it is what people make gold out to be. Scarcity in itself creates worth ONLY to those that see the worth of its scarcity (;>. We have had many gTLDs since dot com but where did they go wrong? That is a matter of opinion since
I know many that made millions from them. The ONLY difference is the worth that the global community places in them over time. As I said earlier, there will be great wealth in the short term exposure to the new gTLDs in sales. You have to get the public perception
to buy into developing them in order for them to become a global brand. Those are two drastically differing returns. If you really want to make all navigation equal to everyone we could revert back to the IP system. </p>
<p><br>
</p>
<p>Michael Castello</p>
<p>CEO/President</p>
<p>Castello Cities Internet Network, Inc.</p>
<p><a class="rvts6" href="http://www.ccin.com" target="_blank">http://www.ccin.com</a></p>
<p><a class="rvts6" href="mailto:michael@ccin.com" target="_blank">michael@ccin.com</a></p>
<p><br>
</p>
<p>--</p>
<p>Sunday, July 18, 2010, 1:28:36 PM, you wrote:</p>
<p><br>
</p>
<div>
<table style="BACKGROUND-COLOR: #ffffff" border="0" cellspacing="2" cellpadding="1">
<tbody>
<tr valign="top">
<td style="BACKGROUND-COLOR: #0000ff" width="2"><br>
</td>
<td width="1683">
<p><span class="rvts7">Hi Michael.</span></p>
<p><br>
</p>
<p><span class="rvts7">Not sure where I said .com should be undone, I agree it has been a success. </span></p>
<p><br>
</p>
<p><span class="rvts7">What I say is that amidst the successful evolution of the domain name system we have also seen the (unintended) consequence of .com being so dominant as to be a near-monopoly. It will not always be this way, and it is in the community's
interest to move more quickly than we have done to diversify domain name demand away from an over-concentration on .com.</span></p>
<p><br>
</p>
<p><span class="rvts7">Because .com is still seen by so many as the only way to go, we have created the circumstances which have lead to speculation in .com names with most of the attractive names now registered, leading to an artificial scarcity of domain
name real estate. But this is really just a perceptual scarcity, and a policy-induced one, not a real scarcity. The best way to eliminate that artificial scarcity, in my view, is through the creation of more real estate, as has been done with some success
(but not yet enough) with ccTLDs . More gTLDs are part of the answer, this is a matter of basic market economics.</span></p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">cheers/Rick </span></p>
<p><br>
</p>
<p><span class="rvts7">Rick Anderson </span></p>
<p><span class="rvts7">EVP, Walton Global Investments Ltd </span></p>
<p><span class="rvts7">randerson@WaltonGlobal.com </span></p>
<p><span class="rvts7">cell (403) 830-1798 </span></p>
<p><br>
</p>
<p><span class="rvts7">PS: Please note our updated corporate name and email address </span></p>
<hr size="2" noshade="">
<p class="rvps1"><span class="rvts8">From</span><span class="rvts9">: Michael Castello </span></p>
<p><span class="rvts8">To</span><span class="rvts9">: Rick Anderson </span></p>
<p><span class="rvts8">Cc</span><span class="rvts9">: sarah.b.deutsch@verizon.com ; pcorwin@butera-andrews.com ; mike@haven2.com ; jb7454@att.com ; randruff@rnapartners.com ; ffelman@markmonitor.com ; bc-gnso@icann.org </span></p>
<p><span class="rvts8">Sent</span><span class="rvts9">: Sun Jul 18 13:52:57 2010</span></p>
<p><span class="rvts8">Subject</span><span class="rvts9">: Re: DRAFT BC Public Comments on DAGv4 </span></p>
<p><span class="rvts10">Hello Rick,</span></p>
<p><br>
</p>
<p><span class="rvts10">In all due respect your third reason absolutely floored me. The virtual world will be built by those that take the time, effort and sacrifice to do so. Dot com (commercial) was the only available gTLD to me and many others like me in
1994. It was what we had to build upon. ICANN does not determine what the public chooses or uses. The 1994 Internet, in my circles, was considered a fad. We could have simply used IPs to navigate and allowed search to do the workload. What had happened was
actually quite beautiful. Average citizens could find a global distributional channel for ideas and products that used words to navigate. There was clarity in that a "word" with a dot com. It was understood as "the Internet". Dot com in itself became a brand.
That was something the general public decided not the DNSO or ICANN. To purposely try to undo something that was natural will be futile in my opinion. There is a lot of growth in the name space for the global future. The new gTLDs will offer great wealth to
those that sell, purchase and resell but it remains unseen if the global community chooses to "build upon" it. I personally think your intentions would have better served you unsaid. </span></p>
<p><br>
</p>
<p><span class="rvts10">Michael Castello</span></p>
<p><span class="rvts10">CEO/President</span></p>
<p><span class="rvts10">Castello Cities Internet Network, Inc.</span></p>
<p><a class="rvts6" href="http://www.ccin.com" target="_blank">http://www.ccin.com</a></p>
<p><a class="rvts6" href="mailto:michael@ccin.com" target="_blank">michael@ccin.com</a></p>
<p><br>
</p>
<p><span class="rvts10">--</span></p>
<p><span class="rvts10">Sunday, July 18, 2010, 11:55:07 AM, you wrote:</span></p>
<p><br>
</p>
<div>
<table style="BACKGROUND-COLOR: #ffffff" border="0" cellspacing="2" cellpadding="1">
<tbody>
<tr valign="top">
<td style="BACKGROUND-COLOR: #0000ff" width="15"><br>
</td>
<td width="1662">
<p><span class="rvts7">Sarah does a good job of identifying two of the three key drivers in the gTLD discussion, namely </span></p>
<p><br>
</p>
<p><span class="rvts7">1. The commercial interest of service providers and domain name investors in having access to a new universe of products to provide and-or invest in</span></p>
<p><br>
</p>
<p><span class="rvts7">2. The interest of trademark owners in not being subject to fresh new rounds of defensive registrations and trademark protection</span></p>
<p><br>
</p>
<p><span class="rvts7">There is a third driver though, and it is the one which prompts BC members who are not in the domain business to support new gTLDs:</span></p>
<p><br>
</p>
<p><span class="rvts7">3. The need for the ICANN community to dissolve the perceptual and economic domination of .com in the domain space. </span></p>
<p><br>
</p>
<p><span class="rvts7">To some of us, eliminating the .com dominance/monopoly is the single most important policy challenge facing ICANN. ICANN's practices and polices have had the (unintended) consequence of creating a near-monopoly, and an artificial scarcity
of supply where none in fact exists, a near-monopoly and scarcity which distort prices and limit access. We need to fix that, and I at least have not yet heard a better way to do so than through multiplying TLDs.</span></p>
<p><br>
</p>
<p><span class="rvts7">This is more than a debate between those with a commercial interest in the domain business vs those with a defensive interest in trademark protectionism</span></p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">cheers/Rick</span></p>
<p><br>
</p>
<p><span class="rvts7">Rick Anderson</span></p>
<p><span class="rvts7">EVP, Walton Global Investments Ltd</span></p>
<p><span class="rvts7">randerson@WaltonGlobal.com</span></p>
<p><span class="rvts7">cell (403) 830-1798</span></p>
<p><br>
</p>
<p><span class="rvts7">PS: Please note our updated corporate name and email address</span></p>
<hr size="2" noshade="">
<p class="rvps1"><span class="rvts8">From</span><span class="rvts9">: owner-bc-gnso@icann.org </span></p>
<p><span class="rvts8">To</span><span class="rvts9">: Phil Corwin ; michaelc@traveler.com ; mike@haven2.com </span></p>
<p><span class="rvts8">Cc</span><span class="rvts9">: jb7454@att.com ; randruff@rnapartners.com ; ffelman@markmonitor.com ; bc-GNSO@icann.org </span></p>
<p><span class="rvts8">Sent</span><span class="rvts9">: Sun Jul 18 11:41:13 2010</span></p>
<p><span class="rvts8">Subject</span><span class="rvts9">: RE: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4</span></p>
<p><span class="rvts10">I'm not opposed to polling members on this issue. I can understand that many of Phil's members who are in the domain name business may see business opportunities from the introduction of new gTLDs. They and others who expressed concern
do not own a well known brand or have widespread trademark infringement problems. Those who object have different business interests and protecting corporate brands and consumers in the new gTLD spaces is not on their list of priorities. I respect that.</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts10">However, ICANN designated trademark protection as one of the overarching issues surrounding the rollout and pledged that these issues would be adequately addressed in the DAG. I'm not aware of any major brand owners, including the IPC
members participating on the IRT, who are happy with the diluted trademark protections currently contained in DAG 4. I would hope even members without trademark concerns, should respect the interests of BC members who have such concerns and allow them to
express those. Our BC GNSO councilors have consistently advocated for these protections on our behalf. The BC already submitted consistent comments in the past, including on DAG 3. Ron tried to keep much of the DAG 4 comments identical to the language to
the DAG 3 draft. I'm sure Ron is open to receiving additional constructive edits on tone and substance (e.g., Mike R's helpful suggestion to delete reference to the GPML since that appears to be dead in the water).</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts10">I'm hopeful that we can find a consructive way to move forward given the importance of this issue to so many BC members. We've heard from those raising concerns, but we've also heard from AT&T, News Corp, Mike Rodenbaugh, NetChoice,
Verizon and RNA Partners weighing in supporting the comments. I would urge others to weigh in on this as well.</span></p>
<p><span class="rvts10"></span> </p>
<p><br>
</p>
<p><span class="rvts10">Sarah</span></p>
<p><span class="rvts10"></span> </p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">Sarah B. Deutsch </span></p>
<p><span class="rvts7">Vice President & Associate General Counsel </span></p>
<p><span class="rvts7">Verizon Communications </span></p>
<p><span class="rvts7">Phone: 703-351-3044 </span></p>
<p><span class="rvts7">Fax: 703-351-3670 </span></p>
<p><span class="rvts10"></span> </p>
<p><br>
</p>
<p><br>
</p>
<hr size="2" noshade="">
<p><span class="rvts8">From:</span><span class="rvts9"> owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] </span><span class="rvts8">On Behalf Of </span><span class="rvts9">Phil Corwin</span></p>
<p><span class="rvts8">Sent:</span><span class="rvts9"> Saturday, July 17, 2010 9:48 PM</span></p>
<p><span class="rvts8">To:</span><span class="rvts9"> 'michaelc@traveler.com'; 'mike@haven2.com'</span></p>
<p><span class="rvts8">Cc:</span><span class="rvts9"> 'jb7454@att.com'; 'randruff@rnapartners.com'; 'ffelman@markmonitor.com'; 'bc-GNSO@icann.org'</span></p>
<p><span class="rvts8">Subject:</span><span class="rvts9"> Re: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4</span></p>
<p><br>
</p>
<p><span class="rvts11">Given the diversity of opinion within the BC, as well as the fact that other members appear to have broader concerns than those I raised, I would again suggest that a poll should be taken of BC members to take the Constituency's temperature
and determine if there is any consensus for the proposed position statement. </span></p>
<p><span class="rvts11">Philip S. Corwin </span></p>
<p><span class="rvts11">Partner, Butera & Andrews </span></p>
<p><span class="rvts11">1301 Pennsylvania Ave., NW </span></p>
<p><span class="rvts11">Suite 500 </span></p>
<p><span class="rvts11">Washington, DC 20004 </span></p>
<p><span class="rvts11">2026635347/Office </span></p>
<p><span class="rvts11">2022556172/Cell </span></p>
<p><br>
</p>
<p><span class="rvts11">"Luck is the residue of design." -- Branch Rickey </span></p>
<p><span class="rvts10"></span> </p>
<p><br>
</p>
<p><span class="rvts8">From</span><span class="rvts9">: Michael Castello [mailto:michaelc@traveler.com] </span></p>
<p><span class="rvts8">Sent</span><span class="rvts9">: Saturday, July 17, 2010 07:04 PM</span></p>
<p><span class="rvts8">To</span><span class="rvts9">: Mike O'Connor <mike@haven2.com> </span></p>
<p><span class="rvts8">Cc</span><span class="rvts9">: Phil Corwin; BRUEGGEMAN, JEFF (ATTSI) <jb7454@att.com>; Ron Andruff <randruff@rnapartners.com>; frederick felman <ffelman@markmonitor.com>; bc-GNSO@icann.org <bc-GNSO@icann.org> </span></p>
<p><span class="rvts8">Subject</span><span class="rvts9">: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4 </span></p>
<p><span class="rvts10"></span> </p>
<p><br>
</p>
<p><span class="rvts10">I agree with both Phil and Mikey. There was certainly a lot of freedom early on with the internet and closing ranks on the concerns of trademark holders and new entities were, over time, clearly needed. The name space was allowed to
flourish because it was so available to everyone. We need to make sure that these regulations, while needed, do not become too cumbersome to new participants. Everyone needs to be invited to the party. </span></p>
<p><br>
</p>
<p><span class="rvts10">Michael Castello</span></p>
<p><span class="rvts10">CEO/President</span></p>
<p><span class="rvts10">Castello Cities Internet Network, Inc.</span></p>
<p><a class="rvts6" href="http://www.ccin.com" target="_blank">http://www.ccin.com</a></p>
<p><a class="rvts6" href="mailto:michael@ccin.com" target="_blank">michael@ccin.com</a></p>
<p><br>
</p>
<p><span class="rvts10">--</span></p>
<p><span class="rvts10">Saturday, July 17, 2010, 5:39:34 AM, you wrote:</span></p>
<p><br>
</p>
<div>
<table style="BACKGROUND-COLOR: #ffffff" border="0" cellspacing="2" cellpadding="1">
<tbody>
<tr valign="top">
<td style="BACKGROUND-COLOR: #0000ff" width="20"><br>
</td>
<td width="1634">
<p><span class="rvts12">i am in Phil's camp on this. several years ago i started referring to myself as "a member of the business wing of the Business Constituency" just to make it clear that i'm not keen on our strident views with regard to rights protections
and cyber-security. </span></p>
<p><br>
</p>
<p><span class="rvts12">of course cyber-crime is important, but folks like Bruce Schneier make an extremely compelling case that there needs to be a culture of security in which all participants are active and aware rather than creating a culture of passive
consumers being "protected" by ever-increasingly intrusive "authorities" like governments and ICANN. </span></p>
<p><br>
</p>
<p><span class="rvts12">of course trademark violations are unacceptable -- but to make this our signature issue, to take our position beyond even those of the IPC, and leaving *small* business owners defenseless in the face of large corporate brand-owners,
leaves me continuing to feel disenfranchised (much the way i feel disenfranchised by the extreme politics in my country -- where the heck do moderates hang out??). </span></p>
<p><br>
</p>
<p><span class="rvts12">i would love to see the BC develop a positive message (based on positive positions) that truly reflect the needs of businesses large and small rather than recycling these views from our reactionary past. </span></p>
<p><br>
</p>
<p><span class="rvts12">i would also love to get out of the continuing role of being an apologist for our somewhat quirky positions. haarrrumph! :-)</span></p>
<p><br>
</p>
<p><span class="rvts12">so, just to be on record, i do not support these comments on DAGv4.</span></p>
<p><br>
</p>
<p><span class="rvts12">sorry about the rant. thanks for taking the time to craft these notes Phil,</span></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts12">mikey</span></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts12">On Jul 16, 2010, at 7:11 PM, Phil Corwin wrote:</span></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts9">Ron (and other BC members who contacted me to ask that I provide alternative URS language):</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts9">I appreciate the request, as I appreciate the hard work put in by Ron and Sarah on the draft.</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts9">That said, a few word changes will not suffice to alter ICA's dissent, as we have an entirely different perspective. We represent individuals and companies with substantial investments in domain portfolios. They view domains in the same
way that most of you (and we) view trademarks -- as an intangible asset with substantial value. When a trademark rights protection is proposed it might be useful to ask whether you would be willing to have one of your trademarks suspended, or forfeited, on
the basis of what is on the table. If not, then don't expect registrants to embrace it. In no way do we condone trademark infringement, but proposed responses to it need to assure basic due process.</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts9">If a majority wills it then the BC is within its rights to proffer a reworking of the same positions it has articulated on prior occasions, and it should expect essentially the same results -- especially after BC members participated
in an STI process that reworked the IRTrecommendations, and the STI's work was embraced by the GNSO and approved by the Board. If ICANN staff have significantly altered the STI's consensus recommendations then that certainly should be raised, but otherwise
the rights protections for new gTLDs have been pretty much baked into the DAG. Does anyone really think they will be reopened in any significant way?</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts9">As regards the specifics of the URS provision, we cannot agree that the URS should have the same substantive standard as the UDRP. The URS was proposed by the IRT as reserved for "obvious", "no brainer" rights disputes, and was originally
proposed with a higher evidentiary standard to distinguish URS cases from UDRPs. We don't think the BC's credibility on trademark matters is enhanced when it consistently articulates a harder line than that of the IPC, which conceived of and oversaw the IRT.
As for urging that the URS lead to a domain transfer and not just a suspension -- again, this goes beyond the IRT recommendation and would likewise blur the distinction between the URS and UDRP.</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts9">Finally, we find the discussion of the "impact" test for a finding of RDNH in the URS to be confusing -- but we do believe that if a complainant advances deliberate falsehoods with the intent of having a favorable impact on its complaint
then it is clearly guilty of attempting to abuse the available system.</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts9">Beyond the URS, our only other comment on the rights protection language is to note our strong questioning of a TM Clearinghouse regime in which an "identical match" is defined as "typographical variations". Identical means identical,
not variations. Variations to what degree? Having a trademark in one word doesn't provide a right to fire warning shots at tens of thousands of possible variants of that word, multiple degrees of separation away from it. If you're going to propose that variations
be encompassed then it really is incumbent to articulate some defining limits on that notion - "we know it when we see it" is really not adequate assurance for registrants. And, of course, these issues become even more problematic for dictionary words that
are trademarked for various purposes. Please let's remember that in most instances infringement can't just be determined by the name of a domain but requires a look at how it is being used.</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts9">Finally, to note an area of agreement -- we share the concern that ICANN devotes inadequate resources to compliance, and indeed in Brussels we suggested publicly that it earmark a meaningful portion of revenues from new gTLD applications
to that end.</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts9">Summing up, we would have to oppose the URS regime that the majority of the BC seems to favor as providing inadequate assurance of due process to registrants, and we think the overall position on rights protection is backwards looking
given that the STI train has left the station. Again, this does not mean we are unsympathetic to the concerns of rights holders. Throughout the past 18 months we have advocated comprehensive UDRP reform that would address the concerns of all parties across
the entire gTLD space, and we continue to believe that a good faith collaboration could produce positive changes that could be put in place in tandem with the opening of new gTLDs.</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts9">Regards to all,</span></p>
<p><span class="rvts9">Philip</span></p>
<p><span class="rvts9"> </span></p>
<p><span class="rvts13">Philip S. Corwin </span></p>
<p><span class="rvts13">Partner </span></p>
<p><span class="rvts13">Butera & Andrews </span></p>
<p><span class="rvts13">1301 Pennsylvania Ave., NW </span></p>
<p><span class="rvts13">Suite 500 </span></p>
<p><span class="rvts13">Washington, DC 20004</span></p>
<p><span class="rvts13">202-347-6875 (office) </span></p>
<p><span class="rvts13">202-347-6876 (fax</span><span class="rvts7">)</span></p>
<p><span class="rvts13">202-255-6172 (cell)</span></p>
<p><span class="rvts14">"Luck is the residue of design."</span><span class="rvts13"> -- Branch Rickey</span></p>
<hr size="2" noshade="">
<p><span class="rvts8">From:</span><span class="rvts9"> </span><a class="rvts15" href="mailto:owner-bc-gnso@icann.org" target="_blank">owner-bc-gnso@icann.org</a><span class="rvts9"> [owner-bc-gnso@icann.org] on behalf of BRUEGGEMAN, JEFF (ATTSI) [jb7454@att.com]</span></p>
<p><span class="rvts8">Sent:</span><span class="rvts9"> Friday, July 16, 2010 3:36 PM</span></p>
<p><span class="rvts8">To:</span><span class="rvts9"> Ron Andruff; frederick felman; </span><a class="rvts15" href="mailto:bc-GNSO@icann.org" target="_blank">bc-GNSO@icann.org</a></p>
<p><span class="rvts8">Subject:</span><span class="rvts9"> RE: [bc-gnso] DRAFT BC Public Comments on DAGv4</span></p>
<p><br>
</p>
<p><span class="rvts16">Thanks Ron and Sarah. AT&T supports filing comments and I like how you’ve updated them. While I was not involved in the original BC comments, I would note that you could add a reference to the recommendation in the Economic Study that
it may be wise for ICANC to continue its practice of introducing new gTLDs in discrete, limited rounds. </span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts16">Jeff Brueggeman</span></p>
<p><span class="rvts16">AT&T Public Policy</span></p>
<p><span class="rvts16">(202) 457-2064</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts8">From:</span><span class="rvts9"> </span><a class="rvts15" href="mailto:owner-bc-gnso@icann.org" target="_blank">owner-bc-gnso@icann.org</a><span class="rvts9"> [mailto:owner-bc-gnso@icann.org] </span><span class="rvts8">On Behalf Of </span><span class="rvts9">Ron
Andruff</span></p>
<p><span class="rvts8">Sent:</span><span class="rvts9"> Friday, July 16, 2010 12:34 PM</span></p>
<p><span class="rvts8">To:</span><span class="rvts9"> 'frederick felman'; </span><a class="rvts15" href="mailto:bc-GNSO@icann.org" target="_blank">bc-GNSO@icann.org</a></p>
<p><span class="rvts8">Subject:</span><span class="rvts9"> RE: [bc-gnso] DRAFT BC Public Comments on DAGv4</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts17">Thanks to Mark Monitor and AIM for your notes of support for the circulated draft.</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts17">I encourage other members to give the doc a quick read. While it is several pages long, please note that it is the same document we submitted for DAGv3 so what we are asking is for you to review the redlines and give your comments/amendments.
To that end, Phil Corwin, can you send your suggested URS text asap?</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts17">Thanks again everyone for taking a moment to review the DAGv4 draft comments.</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts17">RA</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts18">Ronald N. Andruff</span></p>
<p><span class="rvts18">President</span></p>
<p><span class="rvts18">RNA Partners, Inc.</span></p>
<p><span class="rvts18">220 Fifth Avenue</span></p>
<p><span class="rvts18">New York, New York 10001</span></p>
<p><span class="rvts18">+ 1 212 481 2820 ext. 11</span></p>
<p><span class="rvts10"></span> </p>
<hr size="2" noshade="">
<p><span class="rvts8">From:</span><span class="rvts9"> frederick felman [mailto:ffelman@markmonitor.com] </span></p>
<p><span class="rvts8">Sent:</span><span class="rvts9"> Friday, July 16, 2010 12:21 PM</span></p>
<p><span class="rvts8">To:</span><span class="rvts9"> Ron Andruff; </span><a class="rvts15" href="mailto:bc-GNSO@icann.org" target="_blank">bc-GNSO@icann.org</a></p>
<p><span class="rvts8">Subject:</span><span class="rvts9"> Re: [bc-gnso] DRAFT BC Public Comments on DAGv4</span></p>
<p><span class="rvts8">Importance:</span><span class="rvts9"> High</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts19">MarkMonitor support the BC comments to DAGv4.</span></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts19">On 7/15/10 7:20 AM, "Ron Andruff" <</span><a class="rvts20" href="https://exchange.sierracorporation.com/owa/UrlBlockedError.aspx" target="_blank">randruff@rnapartners.com</a><span class="rvts19">> wrote:</span></p>
<p><span class="rvts21">Dear Members,</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts21">Further to my reminder earlier this week regarding the need for a BC public comment on DAGv4, Sarah Deutsch and I have developed a draft for member review and comment. Effectively, we have taken the BC’s DAGv3 comments and added/amended
based on (1) staff having largely ignored our comments in DAGv2 and v3; and (2) utilized subsequent information that has come available in the interim (e.g., the latest economic study). FYI, Sarah drafted the RPM material and I took responsibility for the
other elements.</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts21">We ask that members review and comment on the document at your earliest convenience, so that we can meet the submission deadline of Wednesday, July 21st. Sorry for the late posting, but unfortunately with summer holidays and all, a
few things are slipping between the cracks...</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts21">Thanks in advance for your soonest input. </span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts21">Kind regards,</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts21">RA</span></p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts22">Ronald N. Andruff</span></p>
<p><span class="rvts22">President</span></p>
<p><br>
</p>
<p><span class="rvts22">RNA Partners, Inc.</span></p>
<p><span class="rvts22">220 Fifth Avenue</span></p>
<p><span class="rvts22">New York, New York 10001</span></p>
<p><span class="rvts22">+ 1 212 481 2820 ext. 11</span></p>
<p><br>
</p>
<p><span class="rvts10"></span> </p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts23">- - - - - - - - -</span></p>
<p><span class="rvts23">phone 651-647-6109 </span></p>
<p><span class="rvts23">fax 866-280-2356 </span></p>
<p><span class="rvts23">web </span><a class="rvts24" href="http://www.haven2.com" target="_blank">http://www.haven2.com</a></p>
<p><span class="rvts23">handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)</span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p><span class="rvts10"></span> </p>
<p><span class="rvts10"></span> </p>
<p><span class="rvts25">This e-mail message and any attachments may contain confidential and/or privileged information intended only for the addressee. In the event this e-mail is sent to you in error, sender and sender’s company do not waive confidentiality
or privilege, and waiver may not be assumed. Any dissemination, distribution or copying of, or action taken in reliance on, the contents of this e-mail by anyone other than the intended recipient is prohibited. If you have been sent this e-mail in error,
please destroy all copies and notify sender at the above e-mail address.</span></p>
<p><span class="rvts25"></span> </p>
<p><span class="rvts25">Computer viruses can be transmitted by e-mail. You should check this e-mail message and any attachments for viruses. Sender and sender’s company accept no liability for any damage caused by any virus transmitted by this e-mail. Like
other forms of communication, e-mail communications may be vulnerable to interception by unauthorized parties. If you do not wish to communicate by e-mail, please notify sender. In the absence of such notification, your consent is assumed. Sender will not
take any additional security measures (such as encryption) unless specifically requested.</span></p>
</td>
</tr>
</tbody>
</table>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</body>
</html>