[db-wg] RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*

Dear colleagues,

It has now been one week since the cleanup job was enabled. Last night we emailed the maintainers of 890 route(6) objects, which will be eligible for deletion in two weeks time.

Regards
Ed Shryane
RIPE NCC


> On 29 Jun 2021, at 11:27, Edward Shryane via db-wg <db-wg at ripe.net> wrote:
> 
> Dear colleagues,
> 
> The implementation of the cleanup of RIPE NONAUTH route(6) objects using unregistered space is now complete, we plan to deploy to production *today*.
> 
> This means that the cleanup job will run for the first time tonight.
> 
> * Each night, all RIPE NONAUTH route(6) objects with an unregistered prefix ("available" or "reserved" in delegated stats) are selected.
> * If a prefix remains unregistered for 1 week, notify the maintainers of any related route(6) objects.
> * The maintainer can ask to make an exception, not to delete a route(6) object.
> * Otherwise, after a further 2 weeks, delete the route(6) objects.
> 
> See the solution definition for more details:
> https://www.ripe.net/ripe/mail/archives/db-wg/2021-March/006876.html
> 
> Note for now, the AS origin status is *not* considered. Please discuss further whether this should be included.
> 
> If you have any feedback, please let us know.
> 
> Regards
> Ed Shryane
> RIPE NCC
> 
> 
> 
>