<br><br><div class="gmail_quote">On Mon, Feb 25, 2013 at 3:24 PM, Kathy Kleiman <span dir="ltr"><<a href="mailto:kathy@kathykleiman.com" target="_blank">kathy@kathykleiman.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Milton, <br>
Because a domain name is not a Top Level Domain. </div></div></blockquote><div><br></div><div><br></div><div>a TLD IS a domain name.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div> If we follow
your reasoning, there's no reason to perform extensive Technical,
Operational and Financial Showings/Review of New Registries. We
don't examine registrants, so why should we examine New gTLD
Registries?<br>
<br></div></div></blockquote><div><br></div><div>high barrier of entry methinks.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
<div>
Clearly, it's because they are fundamentally different. Here's
something I wrote awhile ago -- my thoughts based on my background
as both a Registrant and a Registry:<font size="+1"><br>
--------------------<br>
</font>
<p><font size="+1"><b>Why
is <a href="http://COMPUTER.COM" target="_blank">COMPUTER.COM</a> different from .COMPUTER?<u></u><u></u></b></font></p>
<font size="+1">
</font>
<p class="MsoNormal" style="text-indent:.25in"><font size="+1">Given
the history of ICANN and our
Applicant Guidebook, the answer to this question follows from
the existing gTLD
program as we have extended it into the New gTLD Program. It
is the expectation
set by our Community, by the Board and by our New gTLD rules
that Registries
register domain names on a non-discriminatory basis to
Registrants and
Registrars. </font></p>
<font size="+1">
</font>
<p class="MsoNormal" style="text-indent:.25in"><font size="+1"><br></font></p></div></div></blockquote><div><br></div><div><br></div><div>except if they apply for and get an "exception" as you pointed out earlier.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><div><p class="MsoNormal" style="text-indent:.25in"><font size="+1">
Dot-COM, .ORG and .NET are the
public’s models for .BOOK, .APP and .CLOUD.</font></p></div></div></blockquote><div><br></div><div><br></div><div>.org <a href="http://and.net">and.net</a> were originally limited to non-profits and network infrastructure bodies respectively.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><div><p class="MsoNormal" style="text-indent:.25in"><font size="+1"> <span> </span>People know that Verisign
registers .COM to a
wide variety of companies and businesses. While <a href="http://computer.com" target="_blank">computer.com</a>
is registered to a
single entity, monopolizing its use, the same is not true of
the TLD itself. <b><i>Verisign
must operate .COM in a non-discriminatory way – to
registrants and registrars.
That’s the essence of being a gTLD Registry. <u></u><u></u></i></b></font></p>
<font size="+1">
</font>
<p class="MsoNormal" style="text-indent:.25in"><font size="+1"><br>
Thus, for the top level and based
on our rules, the public expects generic words such as “com,”
“biz,” “book,”
“app” <span> </span>and “cloud” to
be run as
Registries in the truest sense of the world – as entities
engaged in the
management, operation and security of the TLD -- committed to
registering domain
names on a non-discriminatory basis to registrants and
registrars
globally.<span> </span>That’s a
promise set out in
the rules. The public will expect to find the normal array of
competitors and
innovators in New gTLDs, just as within existing TLDs.<br></font></p></div></div></blockquote><div><br></div><div><br></div><div><br></div><div>except for .cat, .museum and several others.</div><div><br></div><div>
My point is that there is a precedent, there are rules as you have pointed out, and the application of those rules will be where decisions are made.</div></div><div><br></div>-- <br>Cheers,<br><br>McTim<br>"A name indicates what we seek. An address indicates where it is. A route indicates how we get there." Jon Postel