I'd like to do a submit (a few?) more contributions in the realm of BGP routing security of IX Route Servers, but I'm a bit blocked on the following.
Imagine opportunistic security feature X is available in Feathered Friend software starting at version 5; and perhaps broken in versions 5 and 6; but starting at version 7 feature X really is ready for use and a great improvement to everyone. If version 7 is in play, feature X should be enabled.
In this comment #908 (comment) the poster refers to $t->router->software_version - is that variable the recommended way to implement version-based feature gating?
Or - how should I implement gating certain routing policy depending on the version? Is there a way for IXP manager's software stack to know the version? Or can this be added if it does not exist yet?
I'd like to do a submit (a few?) more contributions in the realm of BGP routing security of IX Route Servers, but I'm a bit blocked on the following.
Imagine opportunistic security feature X is available in Feathered Friend software starting at version 5; and perhaps broken in versions 5 and 6; but starting at version 7 feature X really is ready for use and a great improvement to everyone. If version 7 is in play, feature X should be enabled.
In this comment #908 (comment) the poster refers to
$t->router->software_version- is that variable the recommended way to implement version-based feature gating?Or - how should I implement gating certain routing policy depending on the version? Is there a way for IXP manager's software stack to know the version? Or can this be added if it does not exist yet?