Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

describe propagation speed of RPKI/ROV as an advantages over RIR/filter generation #63

Open
maertsen opened this issue Jun 16, 2022 · 2 comments

Comments

@maertsen
Copy link
Member

maertsen commented Jun 16, 2022

Some points that came up when discussing this:

  • operators have decreased validation frequency of RP sofware over time (Routinator's currently at 10min), in contrast to filter generation where updates are created daily(?)
  • this speed advantage is a result of participation of all major stakeholders during standardization, from RIRs to operators and from router platform vendors to developers of RPs, publication points etc.
@lukastribus
Copy link

  • operators have decreased validation frequency of RP sofware over time (currently at 10min)

Could you elaborate? Are you saying most operates are validating at 10 minute intervals? I find that very hard to believe.

Considering the amount of operators still running the RIPE RPKI validator, I'd say that you'd have to account for at least 2 hours, considering only non-hanging RP instances. Of course those instances that are hanging won't produce any updates at all, pushing obsolete VRPs to routers.

@maertsen
Copy link
Member Author

hi @lukastribus, my 10 mins referred to the Routinator default, I've just clarified that. It seems there are/were even RP's with a interval of 2 mins: https://labs.apnic.net/?p=1338. And yes, there's also RP's with longer intervals.
Anyway, the point is not about the specifics, the point is about the relative difference vs. IRR/filter generation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants