I agree with Tom & David that this draft only describes the solutions to address the issues associated with hosts' (VMs') addresses floating across multiple NVEs or PODs, but not cover the state aspects (on middleware boxes) of the VM mobility.
What do people think of "NVO3 Address Mobility Scheme"? Anyone has better suggestions? Thank, Linda -----Original Message----- From: nvo3 [mailto:[email protected]] On Behalf Of Black, David Sent: Friday, October 03, 2014 8:15 PM To: Tom Herbert Cc: [email protected] Subject: Re: [nvo3] FW: New Version Notification for draft-merged-nvo3-vm-mobility-scheme-00.txt > I would suggest that "Address mobility scheme" might be a better > title. VM migration is one instance of when we need address mobility, > but we'll need this in with container migration or when we just want > to move an virtual address between servers. I agree, and I think Larry pointed this out earlier. > Also, w.r.t. VM or > container migration, addresses are not the only networking state we > need to consider, we need consider how to move connection state (e.g. > open TCP connections bond to the address being moved)-- this seems to > be out of scope for this draft. OTOH, I would caution about getting too involved in this as both ends of the spectrum of connection state preservation are reasonable and used in practice: - VM live migration preserves TCP connections and the like. - IP address takeover on hardware failure doesn't preserve anything whose state was solely on the hardware that's now a smoking pile of parts. Thanks, --David > -----Original Message----- > From: Tom Herbert [mailto:[email protected]] > Sent: Friday, October 03, 2014 9:04 PM > To: Linda Dunbar > Cc: [email protected]; Larry Kreeger (kreeger); Black, David > Subject: Re: [nvo3] FW: New Version Notification for > draft-merged-nvo3-vm- mobility-scheme-00.txt > > On Fri, Oct 3, 2014 at 10:22 AM, Linda Dunbar <[email protected]> wrote: > > As NVO3 new charter encourage solutions proposals, we added more > comprehensive solutions for the issues described in the > draft-ietf-nvo3-vm- mobility-issues. We now call it > "draft-merged-nvo3-vm-mobility-scheme-00" > > > I would suggest that "Address mobility scheme" might be a better > title. VM migration is one instance of when we need address mobility, > but we'll need this in with container migration or when we just want > to move an virtual address between servers. Also, w.r.t. VM or > container migration, addresses are not the only networking state we > need to consider, we need consider how to move connection state (e.g. > open TCP connections bond to the address being moved)-- this seems to > be out of scope for this draft. > > Tom > > > Comments and suggestions are greatly appreciated. > > > > Linda > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > > Sent: Friday, October 03, 2014 12:18 PM > > To: Rahul Aggarwal; Wim Henderickx; Ravi Shekhar; Luyuan Fang; Linda > > Dunbar; > Rahul Aggarwal; Luyuan Fang; Wim Henderickx; Ravi Shekhar; Yakov > Rekhter; Yakov Rekhter; Linda Dunbar; Ali Sajassi; Ali Sajassi > > Subject: New Version Notification for > > draft-merged-nvo3-vm-mobility-scheme- > 00.txt > > > > > > A new version of I-D, draft-merged-nvo3-vm-mobility-scheme-00.txt > > has been successfully submitted by Linda Dunbar and posted to the > > IETF > repository. > > > > Name: draft-merged-nvo3-vm-mobility-scheme > > Revision: 00 > > Title: NVO3 VM Mobility Scheme > > Document date: 2014-10-03 > > Group: Individual Submission > > Pages: 24 > > URL: http://www.ietf.org/internet-drafts/draft-merged-nvo3-vm- > mobility-scheme-00.txt > > Status: https://datatracker.ietf.org/doc/draft-merged-nvo3-vm- > mobility-scheme/ > > Htmlized: http://tools.ietf.org/html/draft-merged-nvo3-vm-mobility- > scheme-00 > > > > > > Abstract: > > This document describes the schemes to overcome the network-related > > issues to achieve seamless Virtual Machine mobility in the data > > center and between data centers. > > > > > > > > > > Please note that it may take a couple of minutes from the time of > > submission > until the htmlized version and diff are available at tools.ietf.org. > > > > The IETF Secretariat > > > > _______________________________________________ > > nvo3 mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
