Source: ASACP (the Association of Sites Advocating Child Protection)
By: Company Press Release
Dear ASACP Sponsors & Members,
This is an official statement by ASACP (the Association of Sites Advocating Child Protection). I am making this statement in my capacity as Executive Director of ASACP, and it reflects current ASACP policy. Questions have been raised about ASACP and .XXX during the last couple of weeks. Therefore, I want to address these points:
1) ASACP’s past involvement with the .XXX issue, ICM Registry and IFFOR
2) ASACP’s (presumed) financial stake in an .XXX TLD under ICM/IFFOR
3) ASACP’s current, public position on the .XXX TLD issue
1) ASACP’s past involvement with the .XXX issue, ICM Registry and IFFOR
ASACP sent a letter to ICANN in 2004 in which we applauded ICM’s intent to include child protection provisions in their registry application. This letter was intended only as a comment upon those specific elements of the application, and definitely not intended as an endorsement of the .XXX TLD plan as a whole.
However, some in the industry felt that even those narrow, specific comments constituted an endorsement of the .XXX TLD and ICM’s registry application. Since we respect the opinions of our sponsors and members, ASACP sent a second letter to ICANN on 8/14/05 to clarify our position. That letter specified unequivocally that the original posted letter “Was not intended to be construed as support for .XXX. ASACP needs to reiterate – it neither approves nor disapproves of .XXX.” We continue to stand by this neutral position.
2) ASACP’s (presumed) financial stake in an .XXX TLD under ICM/IFFOR
While ASACP did not come out in support of an .XXX TLD, we did recognize that the TLD might be approved. Therefore, since ICM and IFFOR intended to incorporate child pornography reporting and other child protection provisions into their planned operation of the proposed TLD, we informally discussed with them how ASACP’s existing CP reporting hotline and member site review procedures might also be provided to .XXX registered sites.
ICM did propose at one point that ASACP receive a percentage of each registration fee, but ASACP rejected that proposal as inappropriate.
If ICM reps commented publicly about their plans to donate to ASACP or about how much such a donation might be, then those comments were their own and did not reflect any agreement or contract.
3) ASACP’s current, public position on the .XXX TLD issue
ASACP stands by the position mentioned above: we are neutral on the .XXX TLD question.
ASACP’s ability to educate the government, the media and the public effectively about the industry’s child protection efforts depends heavily upon establishing ASACP as the adult industry’s child protection association. ASACP is not the adult industry trade association. FSC capably fills that role, and we support their ongoing efforts. Much of the progress ASACP has made in gaining a voice in policy circles (and there has been progress in this regard, as I can attest from my recent trip to DC) also depends upon this.
For this reason, ASACP focuses on issues and legislation that relate to child protection, but is unlikely to take a position on some topics that – though they may be of great import to the industry – fall outside of ASACP’s mandate. Therefore, we cannot oppose an .XXX TLD on those grounds.
We also cannot actively support an .XXX TLD based on its child protection provisions because, as mentioned, such an endorsement would also exceed our mandate.
ASACP remains grateful for the support we receive from you – our sponsors and members.
Regards,
Joan
Joan Irvine
Executive Director ASACP
