Repository navigation
Babel - RFC 9079 source-specific routing #20145
Replies: 4 comments
|
I am not aware of anyone currently working on this. The FRR community would not be opposed to this work at all. |
|
Should we potentially try and get this assigned to the folks working on SRv6 given the slight overlap and margin for optimizing route cost? |
|
What do you mean by assigned? People who work on FRR, do so at their companies behest. In other words pretty much all features someone has an actual use case that is directly funding the work being done. This would be fine work to do, but someone needs to convince a company that this feature is worth the time implementing. If you are using FRR via some companies product then I would suggest you lobby that company for the work to be done. |
|
I didn't say it but you are also welcome to do the work as well. Anyone is free to contribute to FRR. |
Uh oh!
There was an error while loading. Please reload this page.
Hello Team,
Afaik, current FRR 10.5 does expose destination-only options for Babel with no knobs available yet to configure RFC 9079 source-specific routing, doesn't it?
If that's the case, if I may ask, any future plans of supporting Babel's source-specific routing natively with FRR?
Thanks,
All reactions