Dear Working Group, The Non-authoritative Route Object cleanup job ran for the first time last night. We identified 978 route(6) objects with conflicting ROA(s) which are now marked for cleanup, and emailed 269 addresses.
Regards Ed Shryane RIPE NCC > On 6 Jan 2020, at 15:26, Edward Shryane via db-wg <[email protected]> wrote: > > Dear Working Group, > > The RIPE NCC Database team have now implemented the 2018-06 proposal (now > ripe-731), "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up". > > We plan to deploy this to production on Wednesday 15th January. > > A nightly job will run from that evening onwards. We expect approximately 965 > route objects will be initially marked for cleanup (which will happen 2 weeks > after that). > > Regards > Ed Shryane > RIPE NCC > > > >> >> From: Petrit Hasani <[email protected] <mailto:[email protected]>> >> Subject: [policy-announce] 2018-06 Proposal Accepted (RIPE NCC IRR Database >> Non-Authoritative Route Object Clean-up) >> Date: 6 November 2019 at 16:03:18 GMT+1 >> To: [email protected] <mailto:[email protected]> >> >> Dear colleagues, >> >> Consensus has been reached on 2018-06, "RIPE NCC IRR Database >> Non-Authoritative Route Object Clean-up". >> >> This proposal aimed at creating a process to delete a non-authoritative >> object stored in the RIPE IRR, if it conflicts with an RPKI ROA. >> >> You can find the full proposal at: >> https://www.ripe.net/participate/policies/proposals/2018-06 >> <https://www.ripe.net/participate/policies/proposals/2018-06> >> >> The new RIPE Document is called ripe-731 and is available at: >> https://www.ripe.net/publications/docs/ripe-731 >> >> We estimate that this proposal will take around two to three months to fully >> implement. >> >> We will send another announcement once the implementation is complete and >> the new procedures are in place. >> >> Thank you to everyone who provided us with your input. >> >> Kind regards, >> >> -- >> Petrit Hasani >> Policy Officer >> RIPE NCC >> >> >> >> >> >
