ICANN/GNSO GNSO Email List Archives

[council]

<<< Chronological Index >>>    <<< Thread Index >>>

[council] Response from ICANN Compliance re. RAP recommendations

  • To: "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
  • Subject: [council] Response from ICANN Compliance re. RAP recommendations
  • From: Marika Konings <marika.konings@xxxxxxxxx>
  • Date: Wed, 23 Feb 2011 00:47:54 -0800
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • List-id: council@xxxxxxxxxxxxxx
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: AcvTNl49uD/xx2U0Tvyk4FWyH2a23w==
  • Thread-topic: Response from ICANN Compliance re. RAP recommendations
  • User-agent: Microsoft-MacOutlook/14.2.0.101115
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

Attachment: Response to GNSO Council re RAP WG Recommendations (23Feb2011).doc
Description: Response to GNSO Council re RAP WG Recommendations (23Feb2011).doc

<<< Chronological Index >>>    <<< Thread Index >>>