-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Integrate roto-api in Krill replacing RISwhois #1233
Conversation
|
||
use crate::commons::api::TypedPrefix; | ||
use crate::commons::api::{Ipv4Prefix, Ipv6Prefix, TypedPrefix}; | ||
|
||
//------------ IpRange ----------------------------------------------------- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to clean up the range code in rpki-rs further and then use its types directly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For that there would first need to be a V4/V6 range in rpki-rs (which strikes me as a good idea). However, the Krill counterparts are used far and wide throughout the system and slightly differ implementation-wise, so I am not sure if we want to do that as part of this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I guess this goes onto the Big Cleanup pile.
This PR replaces the downloading and parsing of RISwhois files in Krill with the roto-api.
Requires NLnetLabs/rpki-rs#306 to work