Dear Councillors, The following motions were adopted at the Council meeting on Thursday, 16 May 2013. Motion 1: Address the Final Issue Report on the Uniformity of Reporting ========================================================= Whereas, The Registration Abuse Policies Working Group (RAPWG) identified in its Final Report the 'need for more uniformity in the mechanisms to initiate, track, and analyze policy-violation reports'; The RAPWG as a result recommended in its Final Report that 'the GNSO and the larger ICANN community in general, create and support uniform reporting processes'. The GNSO Council at its meeting on 6 October 2011 requested ICANN Compliance Department to report on existing systems to report and track violations and/or complaints; improvements / changes made since the RAPWG Report or foreseen in the near future, and: identify gaps and any improvements that might be desirable but not foreseen at this stage; The ICANN Compliance Department provided a response to the GNSO Council on 18 March 2012 and presented it to the GNSO Council at its meeting on 12 April 2012 (see http://gnso.icann.org/issues/rap/contractual-compliance-report-reporting-uni...); The GNSO Council discussed the RAPWG recommendation in light of the feedback received from the ICANN Compliance Department and RAPWG Alumni volunteered to provide some further thoughts on how the RAPWG recommendation could be implemented; RAPWG Alumni submitted their proposed approach to the GNSO Council on 3 September 2012 (see http://gnso.icann.org/mailing-lists/archives/council/msg13484.html); The GNSO Council reviewed and discussed the proposed approach at its meeting on 13 September 2012; The GNSO Council requested an Issue Report on the current state of uniformity in the mechanisms to initiate, track, and analyze policy-violation reports. ICANN Staff completed and released the Preliminary Issue Report on Uniformity of Reporting on 22 March 2013 for public comment. No comments were received; ICANN Staff submitted the Final Issue Report to the GNSO Council on 2 April 2013 (see http://gnso.icann.org/en/issues/uofr-final-31mar13-en.pdf). The GNSO Council has reviewed the Final Issue Report and supports the staff recommendation to not initiate a Policy Development Process at this stage but to await the completion of the ICANN Contractual Compliance three-year plan. Resolved, The GNSO Council does not initiate a Policy Development Process at this stage but will review at the completion of the ICANN Contractual Compliance three-year plan expected for 31 December 2013 whether additional action is required; The GNSO Council further approves the creation of a drafting team to develop a charter for a non-PDP Working Group to consider additional methods for collecting necessary metrics and reporting from Contracted Parties and other external resources to aid the investigation. Motion 2: Adopt Revised PDP Manual Incorporating Modifications to Include the Suspension of a PDP =============================================================================== WHEREAS: Having encountered the need to suspend a Policy Development Process (PDP) for a limited amount of time, the GNSO Council realized that currently the PDP Manual does not contain a specific provision on how to deal with such a situation; The GNSO Council requested the Standing Committee on Improvements Implementation (SCI) in April 2012 to review whether there should be a modification to the GNSO PDP Manual to address the possible suspension of a PDP following its initiation; The SCI deliberated on provisions for suspension of a PDP and reached consensus on proposed modifications to be incorporated in Section 15 of the GNSO PDP Manual, which also is included as Annex 2 in the GNSO Council Operating Procedures; The revised PDP manual, including the proposed provisions for suspension of a PDP, was put out for a minimum 21-day public comment period on 06 March 2013 ending on 06 April 2013 (see http://www.icann.org/en/news/public-comment/pdp-suspension-07mar13-en.htm) as required by the ICANN Bylaws; As a result of the public comment period, no further changes were deemed necessary by the SCI; NOW THEREFORE, BE IT RESOLVED The GNSO Council adopts the revised PDP Manual including the providing for the suspension of a PDP (see http://gnso.icann.org/en/council/op-procedures-pdp-redline-03may13-en.pdf) The GNSO Council instructs ICANN staff to post the new version of the PDP Manual and to include it as a revised Annex 2 in the GNSO Operating Procedures, effective immediately upon adoption. Please let me know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat@gnso.icann.org http://gnso.icann.org