Implement RFC 4684 Route Target Constraint for optimizing VPN route distribution between BGP peers #302
Conversation
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
Contributor
Author
Implement RFC 4684 Route Target Constraint for optimizing VPN route distribution between BGP peers. Features: - Wildcard matching (0 bits) - Origin AS filtering (32 bits) - Full RT constraint (96 bits) with three Extended Community types - Support for 2-byte AS, IPv4, and 4-byte AS Route Targets - Comprehensive test coverage with performance benchmarks Implementation: - NLRI parser in pkg/rtc with RFC 4684 compliant wire format parsing - Message producer for BMP Route Monitoring messages - BGP integration for MP_REACH_NLRI and MP_UNREACH_NLRI - Kafka topics: RTCV4Msg (194), RTCV6Msg (196)
len() for nil slices is defined as zero, making the nil check unnecessary
fenilp1
force-pushed
the
rtc-support-CLEAN
branch
from
08e0816 to
a6986b5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Features
Implementation
Summary
RFC 4684 enables selective VPN route distribution using route target filters, reducing unnecessary BGP updates and improving scalability in large VPN deployments.