<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Cynthia,<div class=""><br class=""></div><div class="">Thanks for your support, my proposal is to automatically delete route(6) objects using de-registered prefixes from the NONAUTH database.</div><div class=""><br class=""></div><div class="">For example, this would apply to the routes using the revoked 196.52.0.0/14 prefix which was discussed in January.</div><div class=""><br class=""></div><div class="">If there is no objection from the DB-WG, I'd like to turn this proposal into a Numbered Work Item.</div><div class=""><br class=""></div><div class="">Regards</div><div class="">Ed Shryane</div><div class="">RIPE NCC </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 31 Mar 2021, at 07:36, Cynthia Revström <<a href="mailto:me@cynthia.re" class="">me@cynthia.re</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" class="">Hi Ed,<div dir="auto" class=""><br class=""></div><div dir="auto" class="">I am not sure if this was something to discuss or just something you wanted to mention.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Anyways as I saw this while looking through older emails, this sounds like a good idea to me.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">-Cynthia</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 11, 2021, 15:07 Edward Shryane via db-wg <<a href="mailto:db-wg@ripe.net" class="">db-wg@ripe.net</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear colleagues,<br class=""> <br class=""> In response to the recent discussion on "<a href="http://196.52.0.0/14" rel="noreferrer noreferrer" target="_blank" class="">196.52.0.0/14</a> revoked, cleanup efforts needed", I'd like to propose a regular automated cleanup of route(6) objects in the RIPE-NONAUTH database using unregistered space.<br class=""> <br class=""> Regards<br class=""> Ed Shryane<br class=""> RIPE NCC<br class=""> <br class=""> <br class=""> <br class=""> Problem Definition<br class=""> ------------------<br class=""> When an RIR deregisters IPv4/IPv6 address space, any route(6) objects in the RIPE-NONAUTH database using that address space are not cleaned up (deleted).<br class=""> <br class=""> <br class=""> Solution Definition<br class=""> -------------------<br class=""> Once a day, compare route(6) IPv4/IPv6 prefixes in the RIPE-NONAUTH database against the combined delegated stats from all RIRs.<br class=""> <br class=""> Only route(6) prefixes that are "allocated" or "assigned" in any RIRs delegated stats should remain in the RIPE NONAUTH database. If a prefix is "available" or "reserved" then it is considered to be unregistered, and any associated route(6) objects will be eligible for deletion.<br class=""> <br class=""> If a prefix is partially "available" or "reserved" then it is also considered to be unregistered.<br class=""> <br class=""> If a prefix is not listed in any RIRs delegated stats, that prefix is skipped.<br class=""> <br class=""> The origin AS status is not considered, only the IPv4/IPv6 prefix.<br class=""> <br class=""> If a newly unregistered prefix is discovered, first allow a grace period of 1 week. This allows time for mistakes in the delegated stats to be corrected.<br class=""> <br class=""> After 1 week, contact the route(6) maintainer(s) to notify them that the route(6) object will be deleted.<br class=""> <br class=""> After a further 2 weeks, delete the route(6) object.<br class=""> <br class=""> A maintainer can request the RIPE NCC to exclude a route(6) prefix from deletion (for example, the deregistration of the prefix is being disputed). For any excluded prefixes, any associated route(6) objects will not be deleted.<br class=""> <br class=""> <br class=""> Impact Analysis<br class=""> ------------------<br class=""> There are approximately 738 routes (out of 56,230) in the RIPE-NONAUTH database using a prefix with status "available" or "reserved" in an RIRs delegated stats, which will be eligible for deletion.<br class=""> <br class=""> There are approximately 94 route6's (out of 1,564) in the RIPE-NONAUTH database using a prefix with status "available" or "reserved", so also eligible for deletion.<br class=""> <br class=""> There are approximately 64 routes and 37 route6's with a prefix not listed in any RIR's delegated stats. These will not be affected.<br class=""> <br class=""> When this cleanup is implemented, the backlog of route(6) objects eligible for deletion will be processed at the same time, leading to a large amount of emails to affected maintainers. Once this backlog is processed, the number of route(6) objects affected is expected to be low.<br class=""> <br class=""> <br class=""> <br class=""> </blockquote></div> </div></blockquote></div><br class=""></div></body></html>