<<<
Chronological Index
>>> <<<
Thread Index
>>>
Deny .XXX sTLD
- To: rssac-wg-report@xxxxxxxxx
- Subject: Deny .XXX sTLD
- From: Basil <basilstergiou@xxxxxxxxx>
- Date: Wed, 05 May 2010 15:35:46 +0200
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body style="font-size: small; font-family: Arial;" bgcolor="#ffffff"
text="#3333ff">
<font size="-1"><font face="Arial">Hello there,<br>
<br>
</font></font>As an affiliate program for the adult entertainment
industry, my
business' foundation is internet based. If ICM's application were
granted and a .XXX sTLD were to be created it would negatively impact
my business. Also it would put ICANN in the position of creating an
entity to impose regulations and policy for the adult entertainment
community-a situation that could easily stifle what is now a robust
adult entertainment internet presence. <br>
<br>
I do not support the creation of a .XXX sTLD and believe
that the ICANN Board was well within its rights to deny ICM's
application in the 2007 Board meeting in Lisbon. <br>
<br>
It is imperative that ICANN consider the widespread
opposition from the adult entertainment community to a .XXX sTLD as it
makes its decision. For that reason, I support Option # 3 of the March
26, 2010 process options submitted by ICANN for public comment.<br>
<br>
Believe me we do not want to see a .XXX sTLD, it would ruin many homes,
the world is in a big recession as it is, lets not make things worse!<br>
<br>
Yours Faithfully,<br>
<br>
Mike Stevens<br>
Sure Click Media<br>
<BR>
<BR>
__________ Information from ESET Smart Security, version of virus signature
database 5088 (20100505) __________<BR>
<BR>
The message was checked by ESET Smart Security.<BR>
<BR>
<A HREF="http://www.eset.com";>http://www.eset.com</A><BR>
</body>
</html>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|