EVPN Enhanced Mass Withdraw
draft-yu-bess-evpn-mass-withdraw-02

Document Type Active Internet-Draft (individual)
Last updated 2019-06-19
Stream (None)
Intended RFC status (None)
Formats plain text xml 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 Workgroup                                                     T. Yu
Internet-Draft                                             June 20, 2019
Intended status: Standards Track
Expires: December 22, 2019

                      EVPN Enhanced Mass Withdraw
                  draft-yu-bess-evpn-mass-withdraw-02

Abstract

   This document aims to define an enhanced mass withdraw process in
   case of failure of multiple ESs or vESs.  This document also improves
   the withdraw efficiency of failure of single-homed ES or vES.

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 22, 2019.

Copyright Notice

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

Yu                      Expires December 22, 2019               [Page 1]
Internet-Draft             EVPN Mass Withdraw                  June 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Specification of Requirements . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Solution Description  . . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   EVPN [RFC7432] defines a mass withdraw mechanism to efficiently and
   quickly signal to remote PE nodes in case of a connection to ES
   fails.  But there are particular scenarios that cannot be covered by
   [RFC7432]:

   Multi-homed scenario:

   o  EVC scenario (described in section 1.1 of
      [I-D.ietf-bess-evpn-virtual-eth-segment]):

      *  Failure of physical port leads to failure of multiple multi-
         homed vESs aggregating EVC.

      *  Failure of LAG leads to failure of multiple multi-homed vESs
         aggregating EVC.

   o  PW scenario (described in section 1.2 of
      [I-D.ietf-bess-evpn-virtual-eth-segment]):

      *  Failure of PW leads to failure of multiple multi-homed vESs in
         EVPN.  One of the example is: PW is using RAW mode (section
         4.4.1 of [RFC4448]), with multiple VLAN services inside, and
         EVPN is using vlan-based interface and the services.  This
         scenario is called "PW 1:N" in the following context of this
         document.

      *  Failure of PW leads to failure of particular VLAN(s) in EVPN.
         One of the example is: a couple of PWs terminated by a EVPN
         using vlan-aware-bundle interface.  This scenario is called "PW
         N:1" in the following context of this document.

Yu                      Expires December 22, 2019               [Page 2]
Internet-Draft             EVPN Mass Withdraw                  June 2019

   o  A single point of failure leads to failure of multiple ESs/vESs
      (e.g. failure of a line-card).

   The mass withdraw mechanism MUST handle both single-active and
   active-active multi-homed vES in scenarios described above.

   Single-homed scenario:

   o  A failure of single-homed ES or vES interface requires a per-MAC
      based flush, which brings burden to the control plane.

   o  EVC scenario:

      *  Failure of physical port leads to failure of multiple single-
         homed vESs aggregating EVC.

      *  Failure of LAG leads to failure of multiple single-homed vESs
         aggregating EVC.
Show full document text