.XXX TLD proposal does not have community/constituency support
Dear ICANN members, Much like with .travel TLD, there is a requirement under ICANN rules that the TLD service the needs of the community for which the TLD was created. .travel is a closed TLD, where only professionals within the travel organization are allowed to register. The controversy has been that private individuals wanted to have their own .travel domain, but they are not allowed. With .XXX, ICM has failed to demonstrate that the adult online internet community wants and supports this .TLD To the contrary, many more have spoken up against it. Please refer to http://www.FightTheDotXXX.com for the online public demonstration against .XXX There were some notable companies in the very beginning that had given support. Fast forward several years and looking at the political climate, almost all have retracted. Protecting children from the harms of the internet is in the interest of adult webmasters, hence the adult online industry funding of ASACP.org .XXX will not protect against child pornography as ICM/IFFOR says, that is what law enforcement can do, and the recent issues with registrars shutting down domains due to lack of 2257 documentation has demonstrated that registrars can have influence to the process. if there is Child Porn on a website, it would seem a report to the registar to have them look at the site and confirm such content, would make it easy for them to shut it down. While the pedofiles are sick, they are not stupid. They won't register a .XXX name, they will use .COM If you refer to Appendix S, part 8 of ICM's Revised Proposed Agreement, the first couple entries that pertain to protecting against child pornography are seriously flawed by the obvious observation above. If .XXX was such a desired TLD like .mobi and .travel, etc.. but the adult online industry has clearly demonstrated that it does not want to be taxed or ruled over by a .XXX TLD. -brandon "fight the patent" |