[j-nsp] BFD/IS-IS wait to re-establish adjacency after failure tweak knob?

Mark Tinka mark.tinka at seacom.mu
Thu May 19 06:30:35 EDT 2016



On 19/May/16 12:13, Saku Ytti wrote:

> +1 why create higher abstraction layers and complicated notifications
> per protocols, when usually if we need single-hop BFD, we need it
> because we broke physical liveliness detection

+1.

It has always been assumed that routing or signaling protocols are the
clients of BFD. If BFD can be protocol-independent, that would be great.

Mark.


More information about the juniper-nsp mailing list