You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Motion to Request an Issue Report on the Uniformity of Reporting

Made by: John Berard

Seconded by:

 

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’;

 

Whereas 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’;

 

Whereas 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;

 

Whereas 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-uniformity-16mar12-en.pdf);

 

Whereas the GNSO Council discussed the RAPWG recommendation in light of the feedback received from the ICANN Compliance Department and Mikey O’Connor volunteered to provide some further thoughts on how the RAPWG recommendation could be implemented;

 

Whereas Mikey O’Connor submitted his proposed approach to the GNSO Council on 3 September 2012 (see http://gnso.icann.org/mailing-lists/archives/council/msg13484.html);

 

Whereas the GNSO Council reviewed and discussed the proposed approach at its meeting on 13 September 2012.

 

RESOLVED,

 

The GNSO Council requests an Issue Report on the current state of uniformity in the mechanisms to initiate, track, and analyze policy-violation reports. This issue report should consider the issues highlighted in:

 

In addition to covering the required elements of an Issue Report, ICANN Staff is also explicitly requested to provide its recommendation(s) on how this issue can be further addressed outside of a PDP if recommendations in relation to this issue do not require consensus policies to implement.

  • No labels
For comments, suggestions, or technical support concerning this space, please email: ICANN Policy Department
© 2015 Internet Corporation For Assigned Names and Numbers