Page History

Brief

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

Please see the response from the ICANN Compliance Department.

"Quis custodiet ipsos custodes?" -Juvenal

I. NARALO Q&A - This is an opportunity for At-Large and members of the community to pose questions directly to ICANN Staff concerning Compliance issues.

...

II. Review of Compliance Newsletter

Comments or questions here refer to the last (October 2012) Compliance Newsletter

...

III. Review of Compliance Meeting in Toronto

...

IV. Review of Compliance Recent Activities

...

• In general breaches marked as "cured" do not have any dates or specifics provided. Therefore the community has no transparent information as to the timelessness or conditions of the cure. Our specific question is: Can Compliance at a minimum post the date which the Registrar responded and a brief of the actions taken?

V. Previous Questions

There are a number of outstanding unanswered compliance questions which can be found here

VI. Miscellaneous

The above questions are asked in the context of the ICANN Compliance stated goals to:

• Demonstrate the openness and transparency of ICANN's operations
• Provide fair and equitable treatment to all business partners
• Establish clear and easy-to-use channels for communication on compliance matters
• Supplement staff knowledge and enable greater responsiveness to changes in the environment
• Provide clear and regular communications to the community regarding contractual compliance activities, accomplishments and ongoing work
• Identify areas for reform to be considered by the ICANN community

This recent Article in SecurityWeek notes a number of concerns without any response or quotes from ICANN staff