One thought when reading the SRv6 part: shouldn't the failure detection and restoration behaviour described in section 4.2 also be part of the End.DX2/End.DT2U.Reroute behaviors (something like, if down && erl present then reroute ..)?
cheers, Eduard On Wed, Sep 6, 2023 at 6:25 PM Luc André Burdet <laburdet.i...@gmail.com> wrote: > SPRING WG, > > > > My co-authors and myself have presented a document in BESS WG which > describes fast convergence in EVPN networks without relying on control > plane actions. In the latest version SRV6 support was introduced. > > > > https://datatracker.ietf.org/doc/draft-burdet-bess-evpn-fast-reroute/ > > > > The draft specifies two forwarding behaviours which must be implemented: > > - “Terminal disposition” to prevent loops, esp. in EVPN’s All-Active > (MLAG) case > - “DF-Bypass” to address the dropping of rerouted packets on blocked > ports until control-plane catches up (BGP route withdraw) > > > > For SRV6, these are mapped to 2 proposed new behaviours (variants of > existing behaviours) both taking optional Args > > - End.DT2U.Reroute : End.DT2U with Fast Reroute > > - End.DX2.Reroute : End.DX2 with Fast Reroute > > > > The authors would appreciate feedback and any comments on the SRV6 > proposal contained in the document > > > > Regards, > > Luc André > > > > Luc André Burdet | Cisco | laburdet.i...@gmail.com | Tel: +1 613 254 > 4814 > > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring >
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
