I didn't see anyone answer (sorry if I missed it and this is redundant) ...
In the path selection algorithm, local preference is processed before
AS-PATH.
Within your provider's AS, your prefixes could be a default localpref of
100, and learned prefixes from their peers 85, for example. In this
Hugo, I think those are all valid potential reasons to use BFD. I use it
for some of the same reasons even on direct connect peers.
Only time I ever recall actively avoiding it if I had the capability was if
I had NSF/SSO, since they didn't used to (still don't?) play very well
together.
On Tue,
Hopefully they would be flexible with this sort of policy under certain
circumstances.
I could see this as being somewhat problematic for mitigation providers,
since longer mask preemption is a commonly used method to take on traffic
for scrubbing, as well as customers potentially using a more
3 matches
Mail list logo
