-
-
Notifications
You must be signed in to change notification settings - Fork 23
Initial attempt to add ASPA SLURM support #325
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
Conversation
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.
The version only being checked in the FromStr
impl is a bit problematic: When you are reading Slurm from a file, you are likely to use serde_json::from_reader
which would bypass this check.
I think there is no way other than doing your own Serialize
and Deserialize
impls for SlurmFile
.
Actually, it occurs to me now that for parsing, we can also not care. As long as it has the bits we expect, we might as well ignore the version number. |
This PR makes the changes to SLURM in #325 non-breaking by removing the aspa argument from ValidationOutputFilters::new and LocallyAddedAssertions::new and setting the aspa fields of these structs initially to None. The braces constructor can be used to create fully populated values.
New * Added support for ASPA to SLURM. ([#325], [#329]) Bug fixes * Fix access to flags in the ASPA and router key RTR PDUs. ([#327]) * Fix reported version in EndOfData RTR PDUs. ([#328]) * Fix an overflow in `AddressRange::to_vX_prefixes` for prefix length 0. ([#323]) Other changes * The minimum supported Rust version is now 1.81. ([#326])
Attempt to add support for ASPA SLURM as defined in https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-aspa-slurm-02
Main open issue is how to handle version 1 vs version 2.