Brief
Several years of research by the community into ICANN Compliance handling of various complaints has created considerable concern. The main outcome is that the Compliance department does not appear to be independent and does not operate in the interest of the Internet user or consumer. The problems were most recently highlighted in a Wall Street Journal article which focused on a case brought to ICANN's attention by At-Large in 2011. In brief, ICANN Compliance seemed to be unable to recognize the simple fact that the cited domain was in violation for over three years. It was only after persistent work by At-Large that the registrar, BizCn, was issued a 2014 breach notice for just the violations cited by At-Large in 2011. A memo has been drafted, listing the issues, but more importantly recommending fundamental changes to ICANNs structure. The main recommendation is that the Compliance function be made independent of ICANN. A timeline of the difficulties is also provided for reference.
I. APPROVEDONLINEPHARMACY, RAPETUBE, BIZCN and ICANN COMPLIANCE
II. ICANN's Internal Structure Questioned
III. Prior Relationships Between Officers
IV. Rejection of Complaints following Transcribed Request
V. Ombudsman Problems
VI. Recommendations
"Quis custodiet ipsos custodes?" -Juvenal
