Closed agbcix closed 5 months ago
Hello @agbcix, thanks a lot for this PR, very helpful. I've started a similar branch on the repo, at https://github.com/pierky/arouteserver/tree/rfc8950, where I merged your commits and added some others to start adding some tests in order to move this forward. Please check out my commits from that branch if you plan to add more to your branch. I'll keep you posted on the updates using this PR. Stay tuned ;-)
Making some slow progress on my branch... I'm working on a scenario to test RFC8950... nothing yet to push besides the initial tests that I've already pushed.
@agbcix I've just merged my branch (that includes your commits) into master and triggered the CI/CD pipeline to release v1.22.0. The new version will be out in about 1 hours, if everything goes well with the pipeline. It will include the support of IPv4 routes with an IPv6 NEXT_HOP RFC8950. Thanks for your contribution, much appreciated!
RFC8950 (Advertising IPv4 NLRI with an IPv6 Next Hop) will eventually allow IXP peering LANs to be IPv6 only.
IXP route servers will need to accept and forward IPv4 NLRI in IPv6 peering sessions with an IPv6 next hop.
RFC8950 support may be enabled globally or per client. Default: disabled
OpenBGPD support for RFC8950 is still on the RSSF roadmap. BIRD support introduced in 2.0.0.