[anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

Hi,

On Fri, Nov 06, 2015 at 06:01:53AM +0530, Suresh Ramasubramanian wrote:
> +1 here - though for step 3 it might be an idea to check just how many such objects are there and with what frequency they pop up.
> 
> Some of these funny announcements can be short lived indeed - only lasting a few hours.

Step 3 will only be relevant if another RIR withdraws address space
(so a route: object that has been properly validated before now points
to no-longer-valid address space), which I see as a somewhat infrequent
event.

Of course there is the issue of cleanup of "dangling" objects when the
address space changes hands (properly documented, and all that) - but 
that's not much different from "people forget to remove stale route:
objects after a transfer" in just a single registry.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 811 bytes
Desc: not available
URL: </ripe/mail/archives/anti-abuse-wg/attachments/20151106/503a156a/attachment.sig>