Sorry for cross posting. This should have go to the correct WG for the policy. Erik On 08/09/2017, 09:22, "Erik Bais" <ebais@a2b-internet.com> wrote: Hi, Having correct and up to date contact information is already a part of the ARC Process for the RIPE NCC. Each and every LIR will get a regular out-reach call / email from the RIPE NCC to go over their contact details, specific questions about their resources, usage and other stuff. Not having a valid or up to date or working abuse mailbox as an option to be able to de-register resources is something I would not recommend. Any kind of de-registration of resources should not be dictated by only a missing or invalid abuse-c … This means that if by some reason .. a LIR can’t be reached by mail, it might cause their resources to be removed … So I would strongly object to this policy or kind of thinking. You also need to keep in mind that there are a lot of resource holders that have no contract (Legacy holders) with the RIPE NCC.. so RIPE wouldn’t even be able to enforce this. Also, the Legacy space is not under policy .. so the biggest group of ‘problematic’ resources won’t be fixed by this .. Regards, Erik Bais On 07/09/2017, 14:05, "Marco Schmidt" <mschmidt@ripe.net> wrote: Dear colleagues, We just published RIPE Policy proposal, 2017-02, "Regular abuse-c Validation", to the Anti-Abuse Working Group mailing list. 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. As this proposal relates to contact information put into the RIPE Database, we would like to notify the Database Working Group specifically. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2017-02 We encourage you to review this proposal and send your comments to <anti-abuse-wg@ripe.net> before 6 October 2017. Regards, Marco Schmidt Policy Development Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum