Just add one more comment to the Question 2) asked by Benson:
> -----Original Message----- > From: Luyuan Fang (lufang) [mailto:[email protected]] > Sent: Tuesday, October 16, 2012 3:00 PM > To: Henderickx, Wim (Wim); Benson Schliesser > Cc: Yakov Rekhter; Bocci, Matthew (Matthew); [email protected]; Linda > Dunbar; Ali Sajassi (sajassi) > Subject: Re: draft-rekhter-nvo3-vm-mobility-issues-03.txt as nvo3 WG > document > > Sounds good, Wim. > > On 10/16/12 3:56 PM, "Henderickx, Wim (Wim)" > <[email protected]> wrote: > > >Benson, inline > > > >> Date: Fri, 12 Oct 2012 10:28:41 -0500 > >> From: Benson Schliesser <[email protected]> > >> To: Yakov Rekhter <[email protected]> > >> cc: [email protected], [email protected], > >>[email protected], > >> [email protected], [email protected], > [email protected] > >> , > >> [email protected] > >> Subject: Re: draft-rekhter-nvo3-vm-mobility-issues-03.txt as nvo3 WG > >>document > >> > >> > >> On 10/12/12 8:23 AM, Yakov Rekhter wrote: > >> > The authors of draft-rekhter-nvo3-vm-mobility-issues-03.txt would > >> > like to ask nvo3 WG to accept > >>draft-rekhter-nvo3-vm-mobility-issues-03.txt > >> > as an nvo3 WG document. > >> Hi, Yakov. > >> > >> Can you and/or your co-authors please comment on the following two > >> questions: 1. How does the draft apply to our charter and milestones? > > > >WH> it 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. > >Regarding milestones this is part of the framework for mobility > >> 2. > >> How does the draft relate to existing WG drafts? > >> > >WH> it highlights the detailed framework on how we should support > >mobility in > >NVO3 architecture [Linda] this draft identifies issues associated with VM mobility, some of which are not so obvious but necessary to be addressed by future solutions. Those problems haven't been addressed by "draft-ietf-nvo3-overlay-problem-statement". Since "nvo3 problem statement" already has covered too many areas, merging this draft will make those "not so obvious issues" even less visible. > >> > >> Maybe the answers are obvious, but I'd like to see some mailing list > >> discussion. It will help Matthew and I determine how we should > proceed. > >> > >> Cheers, > >> - -Benson _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
