Extended Mobility Procedures for EVPN-IRB
draft-malhotra-bess-evpn-irb-extended-mobility-01

Document Type Active Internet-Draft (individual)
Last updated 2017-10-26
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                                          N. Malhotra, Ed.
                                                              A. Sajassi
                                                             A. Pattekar
Intended Status: Proposed Standard                               (Cisco)
                                                              A. Lingala
                                                                  (AT&T)
                                                              J. Rabadan
                                                                 (Nokia)
                                                                J. Drake
                                                      (Juniper Networks)

Expires: April 29, 2018                                 October 26, 2017

               Extended Mobility Procedures for EVPN-IRB 
           draft-malhotra-bess-evpn-irb-extended-mobility-01

Abstract

   The procedure to handle host mobility in a layer 2 Network with EVPN
   control plane is defined as part of RFC 7432. EVPN has since evolved
   to find wider applicability across various IRB use cases that include
   distributing both MAC and IP reachability via a common EVPN control
   plane. MAC Mobility procedures defined in RFC 7432 are extensible to
   IRB use cases if a fixed 1:1 mapping between VM IP and MAC is assumed
   across VM moves. Generic mobility support for IP and MAC that allows
   these bindings to change across moves is required to support a
   broader set of EVPN IRB use cases, and requires further
   consideration. EVPN all-active multi-homing further introduces
   scenarios that require additional consideration from mobility
   perspective. Intent of this draft is to enumerate a set of design
   considerations applicable to mobility across EVPN IRB use cases and
   define generic sequence number assignment procedures to address these
   IRB use cases.

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
 

Malhotra et al.          Expires April 29, 2018                 [Page 1]
INTERNET DRAFT         EVPN-IRB Extended Mobility       October 26, 2017

   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

Copyright and License Notice

   Copyright (c) 2017 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  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Optional MAC only RT-2 . . . . . . . . . . . . . . . . . . . .  5
   3.  Mobility Use Cases . . . . . . . . . . . . . . . . . . . . . .  6
     3.1  VM MAC+IP Move  . . . . . . . . . . . . . . . . . . . . . .  6
     3.2  VM IP Move to new MAC . . . . . . . . . . . . . . . . . . .  6
       3.2.1  VM Reload . . . . . . . . . . . . . . . . . . . . . . .  6
       3.2.2  MAC Sharing . . . . . . . . . . . . . . . . . . . . . .  6
       3.2.3  Problem . . . . . . . . . . . . . . . . . . . . . . . .  7
     3.3  VM MAC move to new IP . . . . . . . . . . . . . . . . . . .  8
       3.3.1  Problem . . . . . . . . . . . . . . . . . . . . . . . .  8
   4.  EVPN All Active multi-homed ES . . . . . . . . . . . . . . . . 10
   5.  Design Considerations  . . . . . . . . . . . . . . . . . . . . 11
   6.  Solution Components  . . . . . . . . . . . . . . . . . . . . . 12
     6.1  Sequence Number Inheritance . . . . . . . . . . . . . . . . 12
     6.2  MAC Sharing . . . . . . . . . . . . . . . . . . . . . . . . 13
     6.3  Multi-homing Mobility Synchronization . . . . . . . . . . . 14
Show full document text