1 / 4

draft-rekhter-nvo3-vm-mobility-issues-03

draft-rekhter-nvo3-vm-mobility-issues-03. Yakov Rekhter Wim Henderickx Ravi Shekhar LuYuan Fang Linda Dunbar Ali Sajassi. Status Update. We presented the draft(s) in Vancouver IETF (84 th ) http://tools.ietf.org/pdf/draft-raggarwa-data-center-mobility-03.pdf

farren
Download Presentation

draft-rekhter-nvo3-vm-mobility-issues-03

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-rekhter-nvo3-vm-mobility-issues-03 YakovRekhter WimHenderickx Ravi Shekhar LuYuan Fang Linda Dunbar Ali Sajassi

  2. Status Update • We presented the draft(s) in Vancouver IETF (84th) • http://tools.ietf.org/pdf/draft-raggarwa-data-center-mobility-03.pdf • https://datatracker.ietf.org/doc/draft-dunbar-nvo3-overlay-mobility-issues/ • We have requested WG adoption (Oct 12, 2012) after revision based on the discussion from the mailing list • Responded the questions asked by the Chair (Oct 16, Oct 25) in response to our request for WG adoption

  3. Further answers to the Chair questions • The draft addresses the following part of the charter: • "Support the placement and migration of VMs anywhere within the data center, without being limited by DC network constraints such as the IP subnet boundaries of the underlying DC network.“ • It highlights how we should support VM mobility in NVO3 and the issues related to such support • Those issues haven't been covered in details by "draft-ietf-nvo3-overlay-problem-statement". • This draft shouldn't be merged with general NVo3 framework nor problem statement draft due to: • The draft emphasizes on detailed issues related to VM mobility beyond the general NVo3 problem statement draft • This topic is big enough to deserve its own place. • Merging those detailed issues make the general draft not readable.

  4. Next Step • This draft is ready for WG adoption • as the companion draft to general NVo3 problem statement and general framework with special focus on the network related issues associated with VM mobility.

More Related