EVPN Suppport in L2NM: IP FRR

billwuqin commented 3 years ago

FRR can be supported without MPLS-TE, see two relevant work: https://www.apricot.net/apricot2006/slides/conf/thursday/Stefano_Previdi_IPFRR-Apricot.pdf https://tools.ietf.org/html/rfc5714 If IP FRR needs to be supported, we can add the following two parameter under vpn-node list " list vpn-node { ….

    leaf remote-frr {
        type boolean;
        default "false";
        description
            "Remote FRR is enabled or disabled on the remote PE.";
    }
    leaf local-remote-frr {
        type boolean;
        default "false";
        description
            "fast reroute (FRR) for MAC routes between the local and 
             remote ends in an EVPN instance is disabled or enabled.";
    }

"

boucadair commented 3 years ago

The only mention of FRR in https://tools.ietf.org/html/rfc7432 is:


   The PEs may be connected by an MPLS Label Switched Path (LSP)
   infrastructure, which provides the benefits of MPLS technology, such
   as fast reroute, resiliency, etc.

sbarguil commented 3 years ago

Present the scenario for the FRR implementation at the EVPN. @billwuqin

boucadair commented 3 years ago

This is more related to the underlay transport. We don't expose such policies at in the model. I suggest to close this issue without any change.

@billwuqin: any objection?

billwuqin commented 3 years ago

Agree to close this issue.

IETF-OPSAWG-WG / lxnm

EVPN Suppport in L2NM: IP FRR #201