On Wed, Jul 10, 2024 at 09:37:22PM -0400, Aliaksei Sheshka wrote:
On Wed, Jul 10, 2024 at 9:26 PM Job Snijders via NANOG <nanog@nanog.org> wrote:
Indeed, it appears both NTT’s and RADB’s mirror instances are desynchronized in relationship to ARIN’s IRR. Both NTT and RADB should do a database reload to rectify the issue.
Desynchronisation can happen at either server side or client side, so the root cause isn’t apparent to me.
Now I'm concerned about how frequent such silent corruptions are. Also, hard (impossible?) to tell when that happened.
Work is underway to at least get rid of NRTM v3 https://www.ietf.org/archive/id/draft-ietf-grow-nrtm-v4-04.html
IRR `route` and friend should be retired, the sooner the better.
I am with you on that one, eventually, because 'just turning it off' doesn't seem a great solution to me. Not everyone who has access to IRR services has access to RPKI services. Not everyone agrees with ARIN's Relying Party Agreement. RPKI doesn't do all the things that IRR does (but I am not in favor of blindly porting all features & misfeatures from IRR to RPKI!). There is a fair bit of study to be done in this space. Kind regards, Job