EVPN multi-homing port-active load-balancing
draft-brissette-bess-evpn-mh-pa-02

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)
INTERNET-DRAFT                                         Patrice Brissette
Intended Status: Proposed Standard                          Samir Thoria
                                                             Ali Sajassi
                                                           Cisco Systems
                                                                        
Expires: April 25, 2019                                 October 22, 2018

              EVPN multi-homing port-active load-balancing
                  draft-brissette-bess-evpn-mh-pa-02 

Abstract

   The Multi-Chassis Link Aggregation Group (MC-LAG) technology enables
   the establishment of a logical port-channel connection with a
   redundant group of independent nodes. The purpose of multi-chassis
   LAG is to provide a solution to achieve higher network availability,
   while providing different modes of sharing/balancing of traffic. EVPN
   standard defines EVPN based MC-LAG with single-active and all-active
   multi-homing load-balancing mode. The current draft expands on
   existing redundancy mechanisms supported by EVPN and introduces
   support of port-active load-balancing mode. In the current draft,
   port-active load-balancing mode is also referred to as per interface
   active/standby.

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

 

Patrice Brissette        Expires April 25, 2019                 [Page 1]
INTERNET DRAFT      draft-brissette-bess-evpn-mh-pa     October 22, 2018

Copyright and License 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
   (http://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.

Table of Contents

   1  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  4
   2. Multi-Chassis Ethernet Bundles  . . . . . . . . . . . . . . . .  4
   3. Port-active load-balancing procedure  . . . . . . . . . . . . .  4
   4. Algorithm to elect per port-active PE . . . . . . . . . . . . .  5
   5. Port-active over Integrated Routing-Bridging Interface  . . . .  6
   6. Convergence considerations  . . . . . . . . . . . . . . . . . .  7
   6. Applicability . . . . . . . . . . . . . . . . . . . . . . . . .  7
   7. Overall Advantages  . . . . . . . . . . . . . . . . . . . . . .  8
   8  Security Considerations . . . . . . . . . . . . . . . . . . . .  9
   9  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  9
   10.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  9
   11  References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     11.1  Normative References . . . . . . . . . . . . . . . . . . .  9
     11.2  Informative References . . . . . . . . . . . . . . . . . .  9
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  9

 

Patrice Brissette        Expires April 25, 2019                 [Page 2]
INTERNET DRAFT      draft-brissette-bess-evpn-mh-pa     October 22, 2018

1  Introduction

   EVPN, as per [RFC7432], provides all-active per flow load balancing
   for multi-homing. It also defines single-active with service carving
   mode, where one of the PEs, in redundancy relationship, is active per
   service.  

   While these two multi-homing scenarios are most widely utilized in
   data center and service provider access networks, there are scenarios
   where active-standby per interface multi-homing redundancy is useful
   and required. Main consideration for this mode of redundancy is the
   determinism of traffic forwarding through specific interface rather
Show full document text