Virtual Machine Mobility Solutions for L2 and L3 Overlay Networks
draft-ietf-nvo3-vmm-16
Document | Type |
Expired Internet-Draft
(nvo3 WG)
Expired & archived
|
|
---|---|---|---|
Authors | Linda Dunbar , Behcet Sarikaya , Bhumip Khasnabish , Tom Herbert , Saumya Dikshit | ||
Last updated | 2020-12-19 (Latest revision 2020-06-17) | ||
Replaces | draft-sarikaya-nvo3-vmm-dmm-pmip | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats | |||
Reviews | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Matthew Bocci | ||
Shepherd write-up | Show Last changed 2020-06-18 | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Yes | ||
Telechat date | (None) | ||
Responsible AD | Martin Vigoureux | ||
Send notices to | Matthew Bocci <matthew.bocci@nokia.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Linda Dunbar
Behcet Sarikaya
Bhumip Khasnabish
Tom Herbert
Saumya Dikshit
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)