| draft-ietf-nvo3-vmm-02.txt | draft-ietf-nvo3-vmm-03.txt | |||
|---|---|---|---|---|
| Network Working Group B. Sarikaya | Network Working Group B. Sarikaya | |||
| Internet-Draft | Internet-Draft Independent | |||
| Intended status: Best Current Practice L. Dunbar | Intended status: Best Current Practice L. Dunbar | |||
| Expires: November 3, 2018 Huawei USA | Expires: November 3, 2018 Huawei USA | |||
| B. Khasnabish | B. Khasnabish | |||
| ZTE (TX) Inc. | ZTE (TX) Inc. | |||
| T. Herbert | T. Herbert | |||
| Quantonium | Quantonium | |||
| S. Dikshit | S. Dikshit | |||
| Cisco Systems | Cisco Systems | |||
| May 2, 2018 | May 25, 2018 | |||
| Virtual Machine Mobility Protocol for L2 and L3 Overlay Networks | Virtual Machine Mobility Protocol for L2 and L3 Overlay Networks | |||
| draft-ietf-nvo3-vmm-02.txt | draft-ietf-nvo3-vmm-03.txt | |||
| Abstract | Abstract | |||
| This document describes a virtual machine mobility protocol commonly | This document describes a virtual machine mobility protocol commonly | |||
| used in data centers built with overlay-based network virtualization | used in data centers built with overlay-based network virtualization | |||
| approach. For layer 2, it is based on using a Network Virtualization | approach. For layer 2, it is based on using a Network Virtualization | |||
| Authority (NVA)-Network Virtualization Edge (NVE) protocol to update | Authority (NVA)-Network Virtualization Edge (NVE) protocol to update | |||
| Address Resolution Protocol (ARP) table or neighbor cache entries at | Address Resolution Protocol (ARP) table or neighbor cache entries at | |||
| the NVA and the source NVEs tunneling in-flight packets to the | the NVA and the source NVEs tunneling in-flight packets to the | |||
| destination NVE after the virtual machine moves from source NVE to | destination NVE after the virtual machine moves from source NVE to | |||
| skipping to change at page 5, line 13 ¶ | skipping to change at page 5, line 13 ¶ | |||
| change its IP address. Because of this an IP based virtual machine | change its IP address. Because of this an IP based virtual machine | |||
| mobility protocol is not needed. However, when a virtual machine | mobility protocol is not needed. However, when a virtual machine | |||
| moves, NVEs need to change their caches associating VM Layer 2 or | moves, NVEs need to change their caches associating VM Layer 2 or | |||
| Medium Access Control (MAC) address with NVE's IP address. Such a | Medium Access Control (MAC) address with NVE's IP address. Such a | |||
| change enables NVE to send outgoing MAC frames addressed to the | change enables NVE to send outgoing MAC frames addressed to the | |||
| virtual machine. VM movement across Layer 3 boundaries is not | virtual machine. VM movement across Layer 3 boundaries is not | |||
| typical but the same solution applies if the VM moves in the same | typical but the same solution applies if the VM moves in the same | |||
| link such as in WSCs. | link such as in WSCs. | |||
| Virtual machine moves from its source NVE to a new, destination NVE. | Virtual machine moves from its source NVE to a new, destination NVE. | |||
| The move is initiated by the source NVE and is in the same L2 link, | After the move | |||
| the virtual machine IP address(es) do not change but this virtual | the virtual machine IP address(es) do not change but this virtual | |||
| machine is now under a new NVE, previously communicating NVEs will | machine is now under a new NVE, previously communicating NVEs will | |||
| continue to send their packets to the source NVE. Address Resolution | continue to send their packets to the source NVE. Address Resolution | |||
| Protocol (ARP) cache in IPv4 [RFC0826] or neighbor cache in IPv6 | Protocol (ARP) cache in IPv4 [RFC0826] or neighbor cache in IPv6 | |||
| [RFC4861] in the NVEs need to be updated. | [RFC4861] in the NVEs need to be updated. | |||
| It takes a few seconds for a VM to move from its source NVE to the | It may take some time to refresh ARP/ND cache when a VM is moved to a | |||
| new destination one. During this period, a tunnel is needed so that | new destination NVE. During this period, a tunnel is needed so that | |||
| source NVE forwards packets to the destination NVE. | source NVE forwards packets to the destination NVE. | |||
| In IPv4, the virtual machine immediately after the move sends a | In IPv4, the virtual machine immediately after the move should send a | |||
| gratuitous ARP request message containing its IPv4 and Layer 2 or MAC | gratuitous ARP request message containing its IPv4 and Layer 2 or MAC | |||
| address in its new NVE, destination NVE. This message's destination | address in its new NVE, destination NVE. This message's destination | |||
| address is the broadcast address. NVE receives this message. NVE | address is the broadcast address. NVE receives this message. NVE | |||
| should update VM's ARP entry in the central directory at the NVA. | should update VM's ARP entry in the central directory at the NVA. | |||
| NVE asks NVA to update its mappings to record IPv4 address of VM | NVE asks NVA to update its mappings to record IPv4 address of VM | |||
| along with MAC address of VM, and NVE IPv4 address. An NVE-to-NVA | along with MAC address of VM, and NVE IPv4 address. An NVE-to-NVA | |||
| protocol is used for this purpose [RFC8014]. | protocol is used for this purpose [RFC8014]. | |||
| Reverse ARP (RARP) which enables the host to discover its IPv4 | Reverse ARP (RARP) which enables the host to discover its IPv4 | |||
| address when it boots from a local server [RFC0903] is not used by | address when it boots from a local server [RFC0903] is not used by | |||
| End of changes. 6 change blocks. | ||||
| 7 lines changed or deleted | 7 lines changed or added | |||
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||