draft-ietf-nvo3-vmm-13.txt   draft-ietf-nvo3-vmm-14.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Expires: October 1, 2020 Denpel Informatique Expires: October 1, 2020 Denpel Informatique
B.Khasnabish B.Khasnabish
Independent Independent
T. Herbert T. Herbert
Intel Intel
S. Dikshit S. Dikshit
Aruba-HPE Aruba-HPE
April 1, 2020 April 1, 2020
Virtual Machine Mobility Solutions for L2 and L3 Overlay Networks Virtual Machine Mobility Solutions for L2 and L3 Overlay Networks
draft-ietf-nvo3-vmm-13 draft-ietf-nvo3-vmm-14
Abstract Abstract
This document describes virtual machine mobility solutions commonly This document describes virtual machine mobility solutions commonly
used in data centers built with overlay-based network. This document used in data centers built with overlay-based network. This document
is intended for describing the solutions and the impact of moving is intended for describing the solutions and the impact of moving
VMs (or applications) from one Rack to another connected by the VMs (or applications) from one Rack to another connected by the
Overlay networks. Overlay networks.
For layer 2, it is based on using an NVA (Network Virtualization For layer 2, it is based on using an NVA (Network Virtualization
skipping to change at page 2, line 21 skipping to change at page 2, line 21
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on September 30, 2020. This Internet-Draft will expire on October 1, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 6, line 36 skipping to change at page 6, line 36
the communication with external entities are via NVO3 Gateway the communication with external entities are via NVO3 Gateway
functionality as described in Section 5.3 of RFC 8014 functionality as described in Section 5.3 of RFC 8014
[RFC8014]. NVO3 Gateways relay traffic onto and off of a virtual [RFC8014]. NVO3 Gateways relay traffic onto and off of a virtual
network, enabling communication both across different VNs and with network, enabling communication both across different VNs and with
external entities. external entities.
NVO3 Gateway functionality enforces appropriate policies to NVO3 Gateway functionality enforces appropriate policies to
control communication among VNs and with external entities (e.g., control communication among VNs and with external entities (e.g.,
hosts). hosts).
After a VM is moved to a new NVE, the VM's corresponding Gateway Moving a VM a new NVE may move the VM away from the NVO3
may need to change as well. If there is no other entity (or node) Gateway(s) used by the VM's traffic, e.g., some traffic may be
to take over the corresponding NVO3 Gateway function for the VM better handled by an NVO3 Gateway that is closer to the new NVE
under the new NVE, the network path between the VM and the than the NVO3 Gateway that was used before the VM move. If NVO3
external entities needs to be hair-pinned to the NVO3 Gateway used Gateway changes are not possible for some reason, then the VM's
prior to the VM move. traffic can continue to use the prior NVO3 Gateway(s), which may
have some drawbacks, e.g., longer network paths.
4.2. VM Migration in Layer 2 Network 4.2. VM Migration in Layer 2 Network
In a Layer-2 based approach, VM moving to another NVE does not In a Layer-2 based approach, VM moving to another NVE does not
change its IP address. But this VM is now under a new NVE, change its IP address. But this VM is now under a new NVE,
previously communicating NVEs may continue sending their packets previously communicating NVEs may continue sending their packets
to the Old NVE. Therefore, Address Resolution Protocol (ARP) to the Old NVE. Therefore, Address Resolution Protocol (ARP)
cache in IPv4 [RFC0826] or neighbor cache in IPv6 [RFC4861] in the cache in IPv4 [RFC0826] or neighbor cache in IPv6 [RFC4861] in the
NVEs that have attached VMs communicating with the VM being moved NVEs that have attached VMs communicating with the VM being moved
need to be updated promptly. If the VM being moved has need to be updated promptly. If the VM being moved has
 End of changes. 3 change blocks. 
8 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/