Hmm ... I suspect that people who are interested in use of routing protocols to distribute the mapping information might object to that term.
Thanks, --David > -----Original Message----- > From: Stiliadis, Dimitrios (Dimitri) [mailto:dimitri.stiliadis@alcatel- > lucent.com] > Sent: Tuesday, June 19, 2012 10:35 AM > To: Black, David; [email protected]; [email protected]; [email protected] > Cc: Bocci, Matthew (Matthew); draft-narten-nvo3-overlay-problem- > [email protected] > Subject: RE: [nvo3] call for adoption: draft-narten-nvo3-overlay-problem- > statement-02 > > >> Should we use the word "oracle" in the ID? IMHO using a more generic term > >> would be much better. > > >Please suggest an alternative word. > > I believe the original proposals of this concept used the term > "directory service" (see VL2 paper etc). > > Dimitri > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On Behalf Of > Dhruv > > Dhody > > Sent: Tuesday, June 19, 2012 12:17 AM > > To: 'Benson Schliesser'; [email protected] > > Cc: 'Matthew (Matthew) Bocci'; draft-narten-nvo3-overlay-problem- > > [email protected] > > Subject: Re: [nvo3] call for adoption: draft-narten-nvo3-overlay-problem- > > statement-02 > > > > Hi, > > > > Support! > > > > Here are a few comments/queries ... > > > > (1) Sec 2.2 > > "A key requirement for live migration is that a VM retain > > its IP address(es) and MAC address(es) in its new location > > (to avoid tearing down existing communication)." > > > > IP address must be retained but couldn't live migration be still supported > > if the MAC address of the VM changes in the routed semantics? > > > > > > (2) Sec 3.3 > > "The first component consists of a back-end "oracle" that > > is responsible for distributing and maintaining the mapping > > information for the entire overlay system." > > > > Should we use the word "oracle" in the ID? IMHO using a more generic term > > would be much better. > > > > Regards, > > Dhruv > > > > **************************************************************************** > > *** > > Dhruv Dhody, System Architect, Huawei Technologies, Bangalore, India, Ph. > > +91-9845062422 > > > > This e-mail and attachments contain confidential information from HUAWEI, > > which is intended only for the person or entity whose address is listed > > above. Any use of the information contained herein in any way (including, > > but not limited to, total or partial disclosure, reproduction, or > > dissemination) by persons other than the intended recipient's) is > > prohibited. If you receive this e-mail in error, please notify the sender by > > phone or email immediately and delete it! > > > > From: [email protected] [mailto:[email protected]] On Behalf Of > > Benson Schliesser > > Sent: Sunday, June 17, 2012 6:31 AM > > To: [email protected] > > Cc: Matthew (Matthew) Bocci; > > [email protected] > > Subject: [nvo3] call for adoption: > > draft-narten-nvo3-overlay-problem-statement-02 > > > > Dear NVO3 Participants - > > > > This message begins a two week Call for Adoption > > of http://tools.ietf.org/html/draft-narten-nvo3-overlay-problem-statement-02 > > by the NVO3 working group, ending on 30-June-2012. > > > > Please respond to the NVO3 mailing list with any statements of approval or > > disapproval, along with any additional comments that might explain your > > position. Also, if any NVO3 participant is aware of IPR associated with this > > draft, please inform the mailing list and/or the NVO3 chairs. > > > > Thanks, > > -Benson & Matthew > > > > > > _______________________________________________ > > 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
