<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Andrei,<br>
<br>
There is a simple para-dyne to answer many questions of why;
"Follow the money trail".<br>
<br>
Lou <br>
<br>
On 2/7/2013 2:51 AM, Andrei Barburas wrote:<br>
</div>
<blockquote
cite="mid:CALZ4X4P5jO0WmvHAL_LqMm557F+dvODQz+YNeCGMsjBD5CxmRA@mail.gmail.com"
type="cite">
<div dir="ltr"><font face="verdana,sans-serif">I am wondering why
didn't ICANN open up domain registrations for those generic
TLDs so anybody can register their .app/.music/.whatever
domain?</font>
<div><font face="verdana,sans-serif"><br>
</font></div>
<div><font face="verdana,sans-serif">I think a lot of issues
would have been avoided and from a revenue perspective it
would have been more profitable on the long term.</font></div>
<div><font face="verdana,sans-serif"><br>
</font></div>
<div><font face="verdana,sans-serif">Yet, this is only my
personal opinion about this matter...</font></div>
</div>
<div class="gmail_extra"><br clear="all">
<div><span style="background-color:rgb(255,255,255)"><font
face="trebuchet ms, sans-serif">
<p style="margin:0cm 0cm 0.0001pt;font-size:13px">
<font size="1" color="#6d90a6"><span
style="font-size:7.5pt;color:rgb(109,144,166)"><br>
</span></font></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:13px"><font
size="1" color="#6d90a6"><span
style="font-size:7.5pt;color:rgb(109,144,166)"><br>
</span></font></p>
<p style="margin:0cm 0cm 0.0001pt"><font color="#6d90a6"><span
style="color:rgb(109,144,166)"><b>Andrei Barburas</b></span></font></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:13px"><font
size="1" color="#6d90a6"><span
style="font-size:7.5pt;color:rgb(109,144,166)">Community
Relations Services Officer</span></font></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:13px"><font
size="3"><span style="font-size:12pt"> </span></font></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:13px"><font
size="1" color="#6d90a6"><span
style="font-size:7.5pt;color:rgb(109,144,166)">International
Institute for Communication and Development (IICD)</span></font></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:13px"><font
size="1"><span style="font-size:7.5pt"><font
color="#6d90a6"><span
style="color:rgb(109,144,166)">P.O. Box</span></font><font
color="#6d90a6"><span
style="color:rgb(109,144,166)"> 11586, </span></font></span></font><font
size="1" color="#6d90a6"><span style="font-size:7.5pt">2502
AN </span></font><font size="1"><span
style="font-size:7.5pt"><font color="#6d90a6">The
Hague, </font></span></font><font size="1"
color="#6d90a6"><span style="font-size:7.5pt">The </span></font><font
size="1"><span style="font-size:7.5pt"><font
color="#6d90a6">Netherlands</font></span></font></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:13px"><font
size="1"><span style="font-size:7.5pt"><font
color="#6d90a6">NPOC, ICANN member</font></span></font></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:13px"><font
size="1"><span style="font-size:7.5pt"><font
color="#6d90a6"><span
style="color:rgb(109,144,166)"><br>
</span></font></span></font></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:13px"><font
size="1"><span style="font-size:7.5pt"><font
color="#6d90a6"><span
style="color:rgb(109,144,166)">Mobile: +31 62
928 2879</span></font></span></font></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:13px"><font
size="3"><span style="font-size:12pt"></span></font><font
size="1" color="#6d90a6"><span
style="font-size:7.5pt;color:rgb(109,144,166)">Phone:
+31 70 311 7311<br>
Fax: +31 70 311 7322<br>
Website: </span></font><font color="blue"><span
style="font-size:10pt;color:blue"><a
moz-do-not-send="true" href="http://www.iicd.org/"
title="http://www.iicd.org/
blocked::http://www.iicd.org/
http://www.iicd.org/" style="color:rgb(42,93,176)"
target="_blank"><font title="http://www.iicd.org/
blocked::http://www.iicd.org/
http://www.iicd.org/" size="1" color="#6d90a6"><span
title="http://www.iicd.org/
blocked::http://www.iicd.org/
http://www.iicd.org/"><span
title="http://www.iicd.org/
blocked::http://www.iicd.org/
http://www.iicd.org/"><span
style="font-size:7.5pt;color:rgb(109,144,166)"><span
title="http://www.iicd.org/"><span
title="http://www.iicd.org/"><span
title="http://www.iicd.org/"><span
title="http://www.iicd.org/
blocked::http://www.iicd.org/">www.iicd.org</span></span></span></span></span></span></span></font></a></span></font><font
size="1" color="#6d90a6"><span
style="font-size:7.5pt;color:rgb(109,144,166)"></span></font></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:13px">
<font size="3"><span style="font-size:12pt"> </span></font></p>
<p style="margin:0cm 0cm 0.0001pt;font-size:13px"><strong><b><font
size="1" color="#ff5c00"><span
style="font-size:7.5pt;color:rgb(255,92,0)">People </span></font></b></strong><strong><b><font
size="1" color="#6d90a6"><span
style="font-size:7.5pt;color:rgb(109,144,166)"> </span></font></b></strong><strong><b><font
size="1" color="#ff5c00"><span
style="font-size:7.5pt;color:rgb(255,92,0)">ICT
Development</span></font></b></strong></p>
</font></span></div>
<br>
<br>
<div class="gmail_quote">On Thu, Feb 7, 2013 at 7:56 AM, Ron
Wickersham <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:rjw@itsmyinternet.org" target="_blank">rjw@itsmyinternet.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
A possible confusion exists for individual/consumer users of
the Internet<br>
with regard to second-level host names in closed new gtld's.
See below:
<div>
<div class="h5"><br>
<br>
On Wed, 6 Feb 2013, Milton L Mueller wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I stand ready to be educated by those with different
views.<br>
<br>
OK. Here is a different view.<br>
<br>
It is not a free speech issue at all. It is a vertical
integration or business model issue, exclusively.
Some registries want to create a specific image or
environment inside a particular TLD. Those registries
are not trying to sell domain name registrations per
se, they are selling or doing other things with the
domain, perhaps even giving domains away to promote a
service. They might also use their authority to
control registrations to prevent speculators from
grabbing all the "good" names, or to impose a taxonomy
on the second level, or to prevent undesirable types
from squatting or tarnishing the overall image of the
domain.<br>
<br>
Other registries want to maximize the number of
registrations under a TLD. In that case, it makes
sense to be "open". In other words, if you are a
registrar and want to sell hundreds of thousands or
millions of domains to whoever will buy them for
whatever reason, then you want "open" or FCFS TLDs.<br>
<br>
Not surprisingly, the real push for "open" and against
"closed" TLDs is coming from traditional registrars
who want all the potentially popular domains to be
available for them to exploit as registrars. The free
speech and competition policy claims are pure
diversions.<br>
<br>
Take .BOOK for example. If someone wants to open that
up for anyone on a first-come, first-served basis,
there are advantages and disadvantages. Sure, I could
register networksandstates.book in an open domain, if
I wanted to. But someone else might register it before
me, or someone might register nonfiction.books (so
there's that "terrible" appropriation of a generic
term again). Wrose, 600 different link farms might
appropriate other generic terms (sex.books,
good.books) and just pile pay per click ads onto them,
so that anyone using the domain would never know
whether a specific domain was useful or just a
commercial diversion.<br>
<br>
I don't think it's ICANN's job to say that either one
of these business models is the right one. I think
there is an important place for both models, and the
proper decision maker to decide which one to use is
the person who risked about $1 million to get the
domain and operate it.<br>
<br>
The competition policy claims are especially
laughable, because unless you confuse the market for
books with the market for names under .book, it is
obvious that possession of the latter does not do
anything to give you monopoly control of the former.<br>
<br>
Likewise, I don't see the freedom issue here. In fact,
freedom of expression and property rights are mutually
reinforcing in this case. If I register a domain like
.IGP and want to use it to push a particular topic or
point of view, it's my right NOT to allow, say,
advocates of Scientology to register domains under
IGP. If I have to lend my domain to promotion of
causes and ideas I don't support, my freedom of
association and expression rights are being
restricted.<br>
<br>
Edward, you have a domain under <a
moz-do-not-send="true" href="http://USC.EDU"
target="_blank">USC.EDU</a>. USC is not obliged, on
free speech grounds, to allow me to register a name
under their domain. This is not a restriction of my
right of free speech so much as it is an extension of
USC's right of free association and free speech. There
are plenty of domains to accommodate diverse views.<br>
<br>
Generic words in the SLD space have been registered -
and restricted to what their owners want them to do -
for more than a decade. I don't see how TLD vs SLD
changes the issue in any relevant way. Would you
contend that your right to freedom of expression is
restricted because you can't register <foo>.<a
moz-do-not-send="true" href="http://book.com"
target="_blank">book.com</a>? If not, why is it a
restriction to not be allowed to register
<foo>.book? I think we would both probably
agree that if someone else registers <a
moz-do-not-send="true" href="http://book.com"
target="_blank">book.com</a> before me, then I don't
have any right to use the domain <a
moz-do-not-send="true" href="http://book.com"
target="_blank">book.com</a>. Why is it any
different for .book?<br>
<br>
Remember, new domains are NOT .com; i.e., they have no
monopoly power or lock in power on existing
registrants. No one has to use them or register in
them.<br>
</blockquote>
<br>
</div>
</div>
But in .com, there is a protection for trademarks at the
second level,<br>
and a mechanism to contest the _use_ of names at the second
level based<br>
on confusing a consumer.<br>
<br>
For instance, if I see the name of a bank, followed by .com,
I don't<br>
expect that <a moz-do-not-send="true"
href="http://wellsfargo.com" target="_blank">wellsfargo.com</a>
will belong to a competitive bank. And if<br>
.bank were to be an open tld, then Wells Fargo Bank would be
able to<br>
register wellsfargo.bank, and if someone else registered
wellsfargo.bank<br>
the real wellsfargo.bank would be able to contest the
registration.<br>
<br>
Yet if, for instance, citi bank were to apply for and be
granted .bank, then a totally hands-off approach would
permit them to provide a web page<br>
at wellsfargo.bank. They are extremely unlikely to use
that page to<br>
ask for Wells Fargo Bank customers to log in with their
password, but<br>
they could create a page that offers Wells Fargo Bank
customers a special<br>
offer to switch banks, and Wells Fargo would not have any
mechanism to<br>
contest the 2nd level use of wellsfargo.bank in this manner
thru ICANN.<br>
<br>
Of course, web traffic is only a part of Internet
capability. And I grant<br>
that a solution to the above dilemma may not exist. I am
interested in<br>
hearing more discussion on second level in closed generic
tld's.<span class="HOEnZb"><font color="#888888"><br>
<br>
-ron wickersham<br>
</font></span></blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>