Thanks Sasha,
understood. There are two different types of served user instances (routing
logic versus fault/alarm management of operators).
Santosh,
>Just curious to know why do you have this use case? I mean why not use CFM
> itself?
we are considering a use case of
1. a private netwo
If you have an Ethernet that is not carrying IP, and want to use BFD you could
still wrap the BFD in IP, and pull those packets off by recognising the IP
Ethertype. No other protocol on the wire can be using that Ethertype, so there
is no ambiguity. You no need to send the payload to an IP handl
It seems there are “20% non-Ethernet at link layer” in the network in question.
Therefore I think that IP-based BFD is the only way to address end-to-end
connectivity.
As Stewart has said, you only need some lightweight IP in your devices to do
that.
Regards,
Sasha
Office: +972-39266302
Cell:
On Sat, Jun 08, 2019 at 12:45:50PM +, Alexander Vainshtein wrote:
> To the best of my recollection the BFD WG hss tried to cooperate with IEEE
> 802.1, but these attempts have failed.
I think that's a mis-characterization.
Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (L
