The existing Junos routing policy framework uses a BGP community to indicate a route is accepted. With the changes in #3283 that might no longer be needed:
- Default route is advertised with a route policy that accepts the default route
- Advertised and redistributed prefixes are accepted in a single route policy which rejects all other prefixes
- The outbound route map could just accept or reject prefixes.
The only thing we'd still need is an 'accept all' policy that would be used in place of per-neighbor route map because the "advertise/propagate/redistribute" policy kicks the can down the road to the next policy which has to accept the prefixes.
The chain of export policies would thus be:
- next-hop-self (based on neighbor flags), using next-policy for further processing
- default route policy (optional), accepting defaults, and skipping everything else (which would be equivalent to next-policy)
- advertise/redistribute/propagate policy (always present), resulting in either a hard reject or next-policy
- accept-all policy (to terminate the next-policy chain) or per-neighbor output policy resulting in accept or (default) reject.
Any thoughts @ssasso @nmodena? Am I missing something?
The existing Junos routing policy framework uses a BGP community to indicate a route is accepted. With the changes in #3283 that might no longer be needed:
The only thing we'd still need is an 'accept all' policy that would be used in place of per-neighbor route map because the "advertise/propagate/redistribute" policy kicks the can down the road to the next policy which has to accept the prefixes.
The chain of export policies would thus be:
Any thoughts @ssasso @nmodena? Am I missing something?