Open
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
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.
Proposes RFC-21 covering multicast FPGA filtering — extends the FPGA routing
architecture from @ben-malbeclabs's unicast EF RFC to multicast.
Introduces a new
multicast-EFuser mode whose GRE tunnel lands in a newvrf-mcast-filtrationso received multicast transits the DZD's FPGA beforedelivery. Regular multicast users are unchanged and interoperate cleanly.
Control plane borrows the inter-VRF eBGP pattern from the unicast EF RFC
(asdot sub-ASN per DZD, FPGA-loopback route-maps). A publisher's outbound
multicast is double-GRE'd client-side so it's unicast-routable in the
filtration VRF and sidesteps PIM short-circuiting to local subscribers.
Cross-DZD propagation rides the existing ipv4 iBGP mesh; no new MSDP.
Architecture validated end-to-end on
chi-dn-dzd7/dzd8including cross-DZD, same-DZD hairpin, and mixed-mode(regular publisher + multicast-EF subscriber) cases.
Intentionally leaves client-side doublezerod out for now, but will be amended with that when work commences. The client behaviors were simulated in python.