-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
bgpd: Some BGP-LS adjustments #14536
bgpd: Some BGP-LS adjustments #14536
Conversation
According to https://datatracker.ietf.org/doc/html/rfc7606 BGP-LS Attribute does have error handling consistent with Section 8 and thus are not further discussed herein. Section 8: The "treat-as-withdraw" approach is generally preferred and the "session reset" approach is discouraged. Signed-off-by: Donatas Abraitis <[email protected]>
Signed-off-by: Donatas Abraitis <[email protected]>
Increase to 2 bytes and also check if we don't go beyond the maximum packet size. When a BGP-LS Propagator finds that it is exceeding the maximum BGP message size due to the addition or update of some other BGP Attribute , it MUST consider the BGP-LS Attribute to be malformed, apply the "Attribute Discard" error-handling approach. Signed-off-by: Donatas Abraitis <[email protected]>
I'm going to say we should put a hold on this as that I plan to introduce a PR tomorrow morning that will back out the LS code until such time it is fixed in a different manner |
I am going to publish a patch on this today. Kindly let us some times for its review. There is no urgency to revert BGP Link-State at the moment. |
Here is the fix: #14539 |
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.
Thank you for the patches Donatas
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Closing due to #14560. |
No description provided.