I support this proposal, it's a good step in the right direction. Valid contact (incl abuse-c) information is necessary for such a database.

Also a validation of the abuse-c should be made with the resource registration for new resources.

Furthermore i don't know why some guys think a resource will be deregistered right after the resource is tagged as invalid. The proposal is obviuos

In cases where the “abuse-mailbox:” contact attribute is invalid, the RIPE NCC will follow up with the resource holder and attempt to correct the issue.

So there are some more steps before it will be deregistered, so cool down.

Dear colleagues,

A new RIPE Policy proposal, 2017-02, "Regular abuse-c Validation", is now available for discussion.

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 contact information is found to be invalid.

You can find the full proposal at:
https://www.ripe.net/participate/policies/proposals/2017-02

As per the RIPE Policy Development Process (PDP), the purpose of this four-week Discussion Phase
is to discuss the proposal and provide feedback to the proposer.

At the end of the Discussion Phase, the proposer, with the agreement of the RIPE Working Group Chairs,
decides how to proceed with the proposal.

We encourage you to review this proposal and send your comments to
<anti-abuse-wg@ripe.net> before 6 October 2017.

Kind regards,

Marco Schmidt
Policy Development Officer
RIPE NCC

Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

-- 
Kind regards

Artfiles New Media GmbH

Andreas Worbs


Artfiles New Media GmbH | Zirkusweg 1 | 20359 Hamburg
Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95
E-Mail: support@artfiles.de | Web: http://www.artfiles.de
Geschäftsführer: Harald Oltmanns | Tim Evers
Eingetragen im Handelsregister Hamburg - HRB 81478