EVPN Egress Fast ReRoute
draft-jiang-bess-evpn-egress-frr-00

Document Type Active Internet-Draft (individual)
Authors He Jiang  , Xianmin Li  , Zhe Zhou  , Haifeng Qu 
Last updated 2020-06-29
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
BESS Working Group                                            J. He, Ed.
Internet-Draft                                                     X. Li
Intended status: Standards Track                                 Z. Zhou
Expires: December 31, 2020                                         H. Qu
                                                                Ericsson
                                                           June 29, 2020

                        EVPN Egress Fast ReRoute
                  draft-jiang-bess-evpn-egress-frr-00

Abstract

   Ethernet Virtual Private Network (EVPN) multi-homing accommodates
   load balance, link/node redundancy and fast convergence.  Once link
   failure happens, egress traffic can be fast rerouted to multi-homed
   peer(s) to reach CE.  However, this fast reroute brings transient
   loops among multi-homed peers.  This document specifies a fast
   reroute approach with loop prevention.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 31, 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

He, et al.              Expires December 31, 2020               [Page 1]
Internet-Draft               EVPN Egress FRR                   June 2020

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Approach  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Loop Prevention . . . . . . . . . . . . . . . . . . . . .   4
   4.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Constructing EVPN Routes  . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Ethernet Virtual Private Network (EVPN) multi-homing accommodates
   load balance, link/node redundancy and fast convergence.  Upon link
   failure, the PE withdraws the corresponding set of Ethernet A-D per
   ES routes, which triggers all PEs to switchover traffic towards other
   multi-homed peers for the PE.  However, failure propagation still
   consumes much time.  The switchover performance can be improved by
   using local protection at the same time, called egress Fast ReRoute
   (eFRR).

   For example in figure 1, CE1 is multi-homed to PE1 and PE2 with All-
   Active mode, CE2 and CE3 are single-homed to PE2 and PE3 separately.
   EVPN VPLS is provided for CE1, CE2,and CE3.

   In case link failure happens between CE1 and PE2, PE2 withdraws EAD/
   ES route for this link which triggers PE3 to switchover traffic
   towards CE1 from PE2 to PE1.  At the same time, traffic towards CE1
   via PE2 (CE2->CE1 or CE3->CE1) is rerouted to PE1 to reach CE1.  The
   local protection improves the traffic switchover performance.

                               +-----------+
               /-------- PE1   |           |
           CE1(AA mode)        |   EVPN    |   PE3 --- CE3
               \-------- PE2   |           |
                          |    +-----------+
                         CE2

              Figure 1 EVPN All-Active multi-homing scenario

He, et al.              Expires December 31, 2020               [Page 2]
Internet-Draft               EVPN Egress FRR                   June 2020

   [RFC8679] specifies a fast reroute approach for egress traffic
Show full document text