<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-nvo3-vmm" target="https://datatracker.ietf.org/doc/html/draft-ietf-nvo3-vmm-16">
   <front>
      <title>Virtual Machine Mobility Solutions for L2 and L3 Overlay Networks</title>
      <author initials="L." surname="Dunbar" fullname="Linda Dunbar">
         <organization>Futurewei</organization>
      </author>
      <author initials="B." surname="Sarikaya" fullname="Behcet Sarikaya">
         <organization>Denpel Informatique</organization>
      </author>
      <author initials="B." surname="Khasnabish" fullname="Bhumip Khasnabish">
         <organization>Independent</organization>
      </author>
      <author initials="T." surname="Herbert" fullname="Tom Herbert">
         <organization>Intel</organization>
      </author>
      <author initials="D." surname="Dikshit" fullname="Saumya Dikshit">
         <organization>Aruba-HPE</organization>
      </author>
      <date month="June" day="17" year="2020" />
      <abstract>
	 <t>   This document describes virtual machine (VM) mobility
   solutions commonly used in data centers built with an overlay
   network. This document is intended for describing the
   solutions and the impact of moving VMs, or applications, from
   one rack to another connected by the overlay network.

   For layer 2, it is based on using an NVA (Network
   Virtualization Authority) to NVE (Network Virtualization
   Edge) protocol to update ARP (Address Resolution Protocol)
   tables or neighbor cache entries after a VM moves from an old
   NVE to a new NVE.  For Layer 3, it is based on address and
   connection migration after the move.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-nvo3-vmm-16" />
   
</reference>
