-
Notifications
You must be signed in to change notification settings - Fork 42
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
Live RPKI Origin Validation #19
Comments
Ping @alistairking @chiaraorsini? |
@waehlisch thanks for the reminder about this, and sorry for the delay in getting back to you. We've had a chat about how best to integrate this into BGPStream and I have a few comments. Background
In this model, annotation providers would be optional both at compile time (and disabled by default if they depend on external libraries), and at run time (disabled unless explicitly enabled before the stream starts). If anyone has any comments/suggestions about this model, we'd love to hear them. Reality
As another comment, please carefully consider the names of your data structures. Currently you have Lastly, you asked about the elem output format. I think for now your proposed format is fine. We may consider revising it depending on the exact details of how the annotation framework is implemented. |
Actually, the annotation concept sounds good to me! |
@alistairking thank you very much for your review and the effort. The annotation approach sounds pretty good. I'm working on your suggestions and will push it as soon as possible. |
- The BGPStream will be extended by Live PRKI Origin Validation Annotation - All details concerning the provided functions, annotation elements and output format are described in issue CAIDA#19
- The BGPStream will be extended by Live PRKI Origin Validation Annotation - All details concerning the provided functions, annotation elements and output format are described in issue CAIDA#19 and CAIDA/pull/26 (update)
- The BGPStream will be extended by Live PRKI Origin Validation Annotation - All details concerning the provided functions, annotation elements and output format are described in issue CAIDA#19 and CAIDA/pull/26 (update)
This issue was resolved in PR CAIDA/libbgpstream#33. |
As @reuteran discussed with you during the Hackathon, we want to extend BGPstream to support RPKI Prefix Origin Validation. The first step is validation of live data. Before we submit a PR, we want to clarify two questions.
Data structure
To store the ROA payload for validated prefixes, we need a data structure that contains all origin ASNs and prefixes of the covering ROAs.
My current solution consists of two
structs
implementing two nested dynamic arrays that contain origin ASNs and the corresponding prefixes (https://github.com/swp16/bgpstream/blob/master/lib/bgpstream_elem.h#L115).Since it does not use existing data structures there are some functions necessary (https://github.com/swp16/bgpstream/blob/master/lib/bgpstream_elem.c#L426).
My question is if you prefer this solution or if I should extend an existing data structure (which?)?
Output format
The current output of BGP Elem Format should be extended to show ROA data. My proposal
where
ROA-payload
separates multiple ROAs by;
and splits origin ASN and prefix(es) by ",", e.g.,What do you think?
The text was updated successfully, but these errors were encountered: