EVPN Multi-Homing Mechanism for Layer-2 Gateway Protocols
draft-brissette-bess-evpn-l2gw-proto-05

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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                                     P. Brissette, Ed.
Internet-Draft                                                A. Sajassi
Intended status: Standards Track                               L. Burdet
Expires: May 7, 2020                                       Cisco Systems
                                                                D. Voyer
                                                             Bell Canada
                                                        November 4, 2019

       EVPN Multi-Homing Mechanism for Layer-2 Gateway Protocols
                draft-brissette-bess-evpn-l2gw-proto-05

Abstract

   The existing EVPN multi-homing load-balancing modes defined are
   Single-Active and All-Active.  Neither of these multi-homing
   mechanisms are appropriate to support access networks with Layer-2
   Gateway protocols such as G.8032, MPLS-TP, STP, etc.  These Layer-2
   Gateway protocols require a new multi-homing mechanism defined in
   this draft.

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 May 7, 2020.

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

Brissette, et al.          Expires May 7, 2020                  [Page 1]
Internet-Draft         EVPN MH for L2-GW Protocols         November 2019

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terms and Abbreviations . . . . . . . . . . . . . . . . .   3
   2.  Solution  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Single-Flow-Active redundancy mode  . . . . . . . . . . .   4
     2.2.  Backwards compatibility . . . . . . . . . . . . . . . . .   5
       2.2.1.  The two-ESI solution  . . . . . . . . . . . . . . . .   5
       2.2.2.  RFC7432 Remote PE . . . . . . . . . . . . . . . . . .   6
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Handling of Topology Change Notification (TCN)  . . . . . . .   7
   5.  ESI-label Extended Community Extension  . . . . . . . . . . .   9
   6.  EVPN MAC-Flush Extended Community . . . . . . . . . . . . . .   9
   7.  EVPN Inter-subnet Forwarding  . . . . . . . . . . . . . . . .  10
   8.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .  10
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     12.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Existing EVPN multi-homing mechanisms of Single-Active and All-Active
   are not sufficient to support access Layer-2 Gateway protocols such
   as G.8032, MPLS-TP, STP, etc.

   These Layer-2 Gateway protocols require that a given flow of a VLAN
   (represented by {MAC-SA, MAC-DA}) to be only active on one of the PEs
   in the multi-homing group.  This is in contrast with Single-Active
   redundancy mode where all flows of a VLAN are active on one of the
   multi-homing PEs and it is also in contrast with All-Active
   redundancy mode where all L2 flows of a VLAN are active on all PEs in
   the redundancy group.

   This draft defines a new multi-homing mechanism "Single-Flow-Active"
   which defines that a VLAN can be active on all PEs in the redundancy
   group but a single given flow of that VLAN can be active on only one
   of the PEs in the redundancy group.  In fact, the carving scheme,
Show full document text