Support for configuring IPv4 routes to be sent/withdrawn using Traditional REACH/UN_REACH NLRI. #439
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.
Current model does not provide the control to be able specify that BGP IPv4 routes sent by BGPv4 peer should be sent using Traditional NLRI so implementations are currently expected to normally always send IPv4 routes in MP_REACH and withdraw routes using MP_UNREACH.
This PR allows user to optionally allow IPv4 routes only for IPv4 BGP peers to be configured to be advertised or withdrawn using Traditional REACH/UN_REACH methods .
Redocli view of proposed model
devices[i].bgp.ipv4_interfaces[j].peers[k].traditional_nlri_for_ipv4_routes
Note: This is applicable only for BGPv4 peers and not for BGPv6 peers ( which can send IPv4 routes only using MP_REACH NLRI )
Design note:
Another way to do this could have been to expose this control per route per peer instead of per BGPv4 peer.
Did not choose to go down this path since
Example usage: