[anti-abuse-wg] working in new version of 2019-04 (Validation of "abuse-mailbox")

> The policy proposal here is: if the registry doesn't comply, then it
> is in explicit violation of RIPE policies.
> 
> According to the "Closure of Members, Deregistration of Internet
> Resources and Legacy Internet Resources" document (currently RIPE
> 716), if you don't comply with RIPE policies or RIPE NCC procedures,
> then the RIPE NCC is obliged to follow up with the resource holder and
> if they continue not to comply, then the number resources will be
> withdrawn.
> 
> The purpose behind RIPE-716 is to ensure accurate registration of
> number resources, which the core function of the RIPE registry.
> 
> Jordi has confirmed that the intention behind 2019-04 is to force
> resource holders to comply with the abuse handling procedures defined
> in his policy, and that if they don't comply for whatever reason, that
> their number resources are withdrawn under the terms of RIPE-716.
> 
> To be clear, deregistration of resources would make it difficult or
> impossible for almost any holder of addresses to continue their
> business.
> 
> So what's being proposed here is that RIPE-716 - whose purpose was to
> ensure integrity and accuracy of the the RIPE registry - should now be
> repurposed as a mechanism to enforce social behaviour practices on the
> Internet.
> 
> There are some pretty serious and fundamental problems with this.
> 
> Many of these problems were discussed in the context of RIPE policy
> 2019-03 ("Resource Hijacking is a RIPE Policy Violation"), and some of
> them were formally addressed in the RIPE NCC review of that policy.

exactly

the ncc is supposed to be a registry, not a police force.  enforcing
proper quality registration is turning out to be hard and contentious
enough in these days of ipv4 resource struggles.

randy