draft-ietf-nvo3-vmm-01.txt   draft-ietf-nvo3-vmm-02.txt 
Network Working Group B. Sarikaya Network Working Group B. Sarikaya
Internet-Draft Internet-Draft
Intended status: Best Current Practice L. Dunbar Intended status: Best Current Practice L. Dunbar
Expires: May 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
October 30, 2017 May 2, 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-01.txt draft-ietf-nvo3-vmm-02.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 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 3, 2018. This Internet-Draft will expire on November 3, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 6, line 46 skipping to change at page 6, line 46
accomplished seamlessly in L3 data center networks by just giving accomplished seamlessly in L3 data center networks by just giving
each virtual network an IP subnet and a default route that points to each virtual network an IP subnet and a default route that points to
NVE. This means no explosion of ARP/ neighbor cache in guests (just NVE. This means no explosion of ARP/ neighbor cache in guests (just
one ARP/ neighbor cache entry for default route) and we do not need one ARP/ neighbor cache entry for default route) and we do not need
to have Ethernet header in encapsulation [RFC7348] which saves at to have Ethernet header in encapsulation [RFC7348] which saves at
least 16 bytes. least 16 bytes.
In L3 based data center networks, since IP address of the task has to In L3 based data center networks, since IP address of the task has to
change after move, an IP based task migration protocol is needed. change after move, an IP based task migration protocol is needed.
The protocol mostly used is the identifier locator addressing or ILA The protocol mostly used is the identifier locator addressing or ILA
[I-D.herbert-intarea-ila]. Address and connection migration [I-D.herbert-nvo3-ila]. Address and connection migration introduce
introduce complications in task migration protocol as we discuss complications in task migration protocol as we discuss below.
below. Especially informing the communicating hosts of the migration Especially informing the communicating hosts of the migration becomes
becomes a major issue. Also, in L3 based networks, because a major issue. Also, in L3 based networks, because broadcasting is
broadcasting is not available, multicast of neighbor solicitations in not available, multicast of neighbor solicitations in IPv6 would need
IPv6 would need to be emulated. to be emulated.
Task migration involves the following steps: Task migration involves the following steps:
Stop running the task. Stop running the task.
Package the runtime state of the job. Package the runtime state of the job.
Send the runtime state of the task to the destination NVE where the Send the runtime state of the task to the destination NVE where the
task is to run. task is to run.
skipping to change at page 10, line 50 skipping to change at page 10, line 50
This usually happens in cases like the virtual machines running third This usually happens in cases like the virtual machines running third
part applications. This requires the usage of stronger security part applications. This requires the usage of stronger security
mechanisms. mechanisms.
10. IANA Considerations 10. IANA Considerations
This document makes no request to IANA. This document makes no request to IANA.
11. Acknowledgements 11. Acknowledgements
The authors are grateful to Dave R. Worley, Qiang Zu, Andrew Malis The authors are grateful to Qiang Zu, Andrew Malis for helpful
for helpful comments. comments.
12. Change Log 12. Change Log
o submitted version -00 as a working group draft after adoption o submitted version -00 as a working group draft after adoption.
o submitted version -01 with these changes: references are updated, o submitted version -01 with these changes: references are updated,
added packets in flight definition to Section 2 added packets in flight definition to Section 2
o submitted version -02 with updated address.
13. References 13. References
13.1. Normative References 13.1. Normative References
[RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or [RFC0826] Plummer, D., "An Ethernet Address Resolution Protocol: Or
Converting Network Protocol Addresses to 48.bit Ethernet Converting Network Protocol Addresses to 48.bit Ethernet
Address for Transmission on Ethernet Hardware", STD 37, Address for Transmission on Ethernet Hardware", STD 37,
RFC 826, DOI 10.17487/RFC0826, November 1982, RFC 826, DOI 10.17487/RFC0826, November 1982,
<https://www.rfc-editor.org/info/rfc826>. <https://www.rfc-editor.org/info/rfc826>.
[RFC0903] Finlayson, R., Mann, T., Mogul, J., and M. Theimer, "A [RFC0903] Finlayson, R., Mann, T., Mogul, J., and M. Theimer, "A
Reverse Address Resolution Protocol", STD 38, RFC 903, Reverse Address Resolution Protocol", STD 38, RFC 903,
DOI 10.17487/RFC0903, June 1984, DOI 10.17487/RFC0903, June 1984,
<https://www.rfc-editor.org/info/rfc903>. <https://www.rfc-editor.org/info/rfc903>.
skipping to change at page 12, line 13 skipping to change at page 12, line 19
<https://www.rfc-editor.org/info/rfc7364>. <https://www.rfc-editor.org/info/rfc7364>.
[RFC8014] Black, D., Hudson, J., Kreeger, L., Lasserre, M., and T. [RFC8014] Black, D., Hudson, J., Kreeger, L., Lasserre, M., and T.
Narten, "An Architecture for Data-Center Network Narten, "An Architecture for Data-Center Network
Virtualization over Layer 3 (NVO3)", RFC 8014, Virtualization over Layer 3 (NVO3)", RFC 8014,
DOI 10.17487/RFC8014, December 2016, DOI 10.17487/RFC8014, December 2016,
<https://www.rfc-editor.org/info/rfc8014>. <https://www.rfc-editor.org/info/rfc8014>.
13.2. Informative references 13.2. Informative references
[I-D.herbert-intarea-ila] [I-D.herbert-nvo3-ila]
Herbert, T. and P. Lapukhov, "Identifier-locator Herbert, T. and P. Lapukhov, "Identifier-locator
addressing for IPv6", draft-herbert-intarea-ila-00 (work addressing for IPv6", draft-herbert-nvo3-ila-04 (work in
in progress), October 2017. progress), March 2017.
Authors' Addresses Authors' Addresses
Behcet Sarikaya Behcet Sarikaya
Plano, TX, USA
Email: sarikaya@ieee.org Email: sarikaya@ieee.org
Linda Dunbar Linda Dunbar
Huawei USA Huawei USA
5340 Legacy Dr. Building 3 5340 Legacy Dr. Building 3
Plano, TX 75024 Plano, TX 75024
Email: linda.dunbar@huawei.com Email: linda.dunbar@huawei.com
Bhumip Khasnabish Bhumip Khasnabish
ZTE (TX) Inc. ZTE (TX) Inc.
55 Madison Avenue, Suite 160 1900 McCarthy Blvd., Suite 205
Morristown, NJ 07960 Milpitas, CA 95035
Email: vumip1@gmail.com, bhumip.khasnabish@ztetx.com Email: vumip1@gmail.com, bhumip.khasnabish@ztetx.com
Tom Herbert Tom Herbert
Quantonium Quantonium
Email: tom@herbertland.com Email: tom@herbertland.com
Saumya Dikshit Saumya Dikshit
Cisco Systems Cisco Systems
Cessna Business Park Cessna Business Park
Bangalore, Karnataka, India 560 087 Bangalore, Karnataka, India 560 087
Email: sadikshi@cisco.com Email: sadikshi@cisco.com
 End of changes. 15 change blocks. 
21 lines changed or deleted 23 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/