EVPN ELAN FRR Loop Prevent label
draft-wang-bess-evpn-frr-label-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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                                               H. Wang
Internet-Draft                                               D. Eastlake
Intended status: Experimental                        Huawei Technologies
Expires: April 25, 2019                                 October 22, 2018

                    EVPN ELAN FRR Loop Prevent label
                   draft-wang-bess-evpn-frr-label-00

Abstract

   This document describes how to use Fast Re-Route (FRR) labels avoid
   loop problems in CE failures when deploying FRR protection in EVPN
   scenarios.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 April 25, 2019.

Copyright Notice

   Copyright (c) 2018 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

Wang & Eastlake          Expires April 25, 2019                 [Page 1]
Internet-Draft            EVPN FRR Loop Prevent             October 2018

   to this document.  Code Components extracted from this document must
   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.  FRR Label Extended Community  . . . . . . . . . . . . . . . .   3
   3.  The Control Plane Process . . . . . . . . . . . . . . . . . .   4
   4.  The Data Plane Process  . . . . . . . . . . . . . . . . . . .   4
   5.  Other considerations  . . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   In the EVPN active-active scenario, to solve the failure of a CE
   access channel to one PE, we can deploy Fast Re-Route (FRR)
   protection mode to achieve fast convergence.  All active PEs can be
   deployed with FRR.  When a link failure occurs on the CE connection
   to the PE, traffic can be rapidly FRRed to another PE to improve the
   switching performance.  However, if the CE device fails, both the two
   PEs sense that their CE link is faulty at the same time.  They will
   each perform fast switching according to the FRR.  Then the traffic
   will loop between the dual PEs.  If one PE detects a failure and
   cancels the ES-AD route, the other PE, after receiving the withdrawal
   of the ES-AD route, deletes the FRR path to the PE, and the loop is
   eliminated.  The time until the loop is eliminated may be short, but
   during this time, the loop will cause traffic congestion between the
   dual-homing PEs.

Wang & Eastlake          Expires April 25, 2019                 [Page 2]
Internet-Draft            EVPN FRR Loop Prevent             October 2018

                                         +-----+
                                         | CE2 |
                                         +-----+
                                            |
                                         +-----+
                                         | EVI1|
                                         | PE3 |
                                         +-----+
                                         /      \
                                        /        \
                                       /          \
                                      /            \
                                     /              \
                                +-----+             +-----+
                                | PE1 |             | PE2 |
Show full document text