The Association of Sites Advocating Child Protection (ASACP) neither approves nor disapproves of .xxx.
In 2003, ASACP was approached by ICM Registry to support .xxx. The ASACP Advisory Council decided that such support was not within the ASACP mission; therefore, ASACP does not take a position on the concept of .xxx.
ASACP works with other associations such as Distributed Computing Industry Association (DCIA) to help them be more effective in their efforts in the battle against child pornography. In fact, last month, ASACP launched cpHotline.org with DCIA’s P2P Patrol.
If the Internet Corporation for Assigned Names and Numbers (ICANN) approves .xxx, ASACP would finalize a service agreement with ICM Registry/ International Foundation for Online Responsibility (IFFOR) for the use of cphotline.org. In addition, since IFFOR plans to contribute to various child protection associations, ASACP would accept such a contribution.
Therefore, on May 17, 2004, ASACP posted a letter, “applauding IFFOR and ICM Registry's initiative to integrate tools and technology for finding and reporting child pornography websites into their proposed registry application.”
“I am surprised that people are attacking ASACP for potentially providing the use of cpHotline.org to IFFOR. Plus, this has been public information for over a year” says Joan Irvine, executive director of ASACP. “When people asked, I told them ASACP’s position and the potential for the service agreement. I will be attending Cybernet Expo in San Diego next week and will be on the Hot Issues and Problems in the Adult Internet seminar on Tuesday, June 14th at 1:45 p.m. If anyone has additional questions, please feel free to contact me.”
For further information contact Joan Irvine at [email protected].
