Hi Robert, great idea to spawn the new discussion thread, thank you! Please find my notes in-lined below under the GIM>> tag.
Regards, Greg On Mon, Nov 29, 2021 at 4:08 PM Robert Raszuk <[email protected]> wrote: > Hi Greg, > > /* Changing the subject as the other thread just tried to re-focus on IGP > */ > /* Keeping lsr WG cc-ed just as FYI */ > > From my OAM PoV, the most reliable option is, as you've pointed out, to >> run BFD over EVPN underlay between PEs. >> > > If BFD would have autodiscovery built in, that would indeed be the > ultimate solution. Of course folks will worry about scaling and number of > BFD sessions to be run PE-PE. > GIM>> I sense that it is not "BFD autodiscovery" but an advertisement of BFD multi-hop system readiness to the particular PE. That, as I think of it, can be done in a control or management plane. > > But if BFD between all PEs would be an option why RR to PE in the local > area would not be a viable solution ? > GIM>>Because, in the case of PE-PE, BFD control packets will be fate-sharing with data packets. But the path between RR and PE might not be used for carrying data packets at all. > > Both would be multihop, both would be subject to all transit failures etc > ... > GIM>> I think that there's a difference between the impact a path failure has on the data traffic. In the case of monitoring PE-PE path in the underlay and using the same encapsulation as data traffic is representative of the data experience. A failure of the PE-RR path, in my understanding, may be not representative at all. BFD session between RR and PE may fail while PE is absolutely functional from the service PoV. On the other hand, PE might be disconnected from the service while the BFD session to RR is in the Up state. > > Also just FYI this discussion is not about EVPN :) Some people claimed > that the solution should not even consider BGP presence for any service. > > Thx, > R. > >
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
