<html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Dear colleagues, Policy proposal 2017-02, "Regular abuse-c Validation" is now in the Review Phase. The goal of this proposal is to give the RIPE NCC a mandate to regularly validate "abuse-c:" information and to follow up in cases where the attribute is deemed to be incorrect. This proposal has been updated following the last round of discussion and is now at version v2.0. Some of the differences from version v1.0 include: - A focus on validating the "abuse-mailbox:" attribute and fixing incorrect contact information - Added references to RIPE Policies and RIPE NCC procedures The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: <a class="moz-txt-link-freetext" href="https://www.ripe.net/participate/policies/proposals/2017-02">https://www.ripe.net/participate/policies/proposals/2017-02</a> And the draft documents at: <a class="moz-txt-link-freetext" href="https://www.ripe.net/participate/policies/proposals/2017-02/draft">https://www.ripe.net/participate/policies/proposals/2017-02/draft</a> As per the RIPE Policy Development Process (PDP), the purpose of this four-week Review Phase is to continue discussing the proposal, taking the impact analysis into consideration, and to review the full draft policy document. At the end of the Review Phase, the WG Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document, and share your comments on <a class="moz-txt-link-rfc2396E" href="mailto:anti-abuse-wg@ripe.net"><anti-abuse-wg@ripe.net></a> before 16 February 2018. Kind regards, Marco Schmidt Policy Development Officer RIPE NCC </body> </html>