Restructure limiting of ASPA provider set sizes.#996
Merged
Merged
Conversation
Koenvh1
approved these changes
Jan 21, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR changes how the ASPA provider ASN set is limited. It drops the
aspa-provider-limitconfig option again and instead hard-codes the limit to 16380 as per the latest version of the RTR draft. Since this limit can be exceeded when merging multiple ASPAs, the check has been moved to the very end when the new snapshot is created which also avoid having to track customer ASNs. A new metric was added to count the ASPA customer ASNs ignored this way.