Thanks, Marika. I suspect I'll have questions about this. In the meantime, reading this response made me realize that ICANN is about to hit the 8-month mark for not having a Compliance Director. Would the appropriate staff person please provide a short email update as to the current status of the efforts to hire one? (I'd prefer an email update to this list so it can be shared and accessed by others in the community.) Many thanks! Kristina ________________________________ From: owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Marika Konings Sent: Wednesday, February 23, 2011 3:48 AM To: council@gnso.icann.org Subject: [council] Response from ICANN Compliance re. RAP recommendations Dear All, Please find attached the response from ICANN's Compliance Department in relation to resolved #1 of the recently adopted motion on the Registration Abuse Policies Working Group Final Report (RESOLVED #1, the GNSO Council instructs ICANN Policy Staff to forward the two issues identified by the RAP IDT as having low resource requirements, WHOIS Access recommendation #2 and Fake Renewal Notices recommendation #1, to ICANN Compliance Staff for resolution. ICANN Compliance Staff is requested to provide the GNSO Council with its feedback on the two recommendations and proposed implementation in a timely manner). Pam Little, Interim Head of Contractual Compliance, is not available to participate in the Council meeting coming Thursday, but she is happy to take further comments / questions by email. In addition, she has indicated that she is available to discuss the response and any further questions in person with the Council during the weekend session at the ICANN meeting in San Francisco, if required. With best regards, Marika