<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bess-evpn-irb-extended-mobility" target="https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-irb-extended-mobility-00">
   <front>
      <title>Extended Mobility Procedures for EVPN-IRB</title>
      <author initials="N." surname="Malhotra" fullname="Neeraj Malhotra">
         <organization>Arrcus</organization>
      </author>
      <author initials="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco</organization>
      </author>
      <author initials="A." surname="Pattekar" fullname="Aparna Pattekar">
         <organization>Cisco</organization>
      </author>
      <author initials="A. R." surname="Lingala" fullname="Avinash Reddy Lingala">
         <organization>AT&amp;T</organization>
      </author>
      <author initials="J." surname="Rabadan" fullname="Jorge Rabadan">
         <organization>Nokia</organization>
      </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         <organization>Juniper Networks</organization>
      </author>
      <date month="March" day="27" year="2019" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bess-evpn-irb-extended-mobility-00" />
   
</reference>
