bgp: ADD-PATH support for IPv4/IPv6 unicast (RFC 7911) - #146
Open
gusbourg wants to merge 4 commits into
Open
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
BGP Additional Paths / ADD-PATH (RFC 7911) for IPv4 and IPv6 unicast.
receive/sendmodes, negotiated per (AFI, SAFI). The NLRI path-id codec is driven by the per-direction negotiated capability (via encode/decode contexts): decode reads a path-id only when receive is negotiated, encode writes one only when send is negotiated.(neighbour, path-id), so multiple paths per prefix from one peer coexist; update/withdraw match a specific path-id.send-all) with stable path-ids.Tests: packet round-trip with path-ids, and path-ids-omitted-without-negotiation (the wire-format guard).
Scope: IPv4/IPv6 unicast. Deferred: VPN/EVPN/labeled AFs;
best-per-ASTX mode; paths-limit (RFC 9184). Behavioral conformance tests for RX multi-path storage and TX all-paths advertisement are a recommended follow-up.🤖 Generated with Claude Code