Hi Andrew, VM speaking up using RARP, is discounted as one of the potential cases ?
Thanks Saumya. From: "Andrew G. Malis" <[email protected]<mailto:[email protected]>> Date: Monday, March 7, 2016 at 4:02 PM To: sadikshi <[email protected]<mailto:[email protected]>> Cc: "B. Khasnabish" <[email protected]<mailto:[email protected]>>, Matthew Bocci <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Benson Schliesser <[email protected]<mailto:[email protected]>>, sarikaya <[email protected]<mailto:[email protected]>>, Alia Atlas <[email protected]<mailto:[email protected]>> Subject: Re: [nvo3] Fwd: New Version Notification for draft-sarikaya-nvo3-vmm-dmm-pmip-08.txt Saumya, Either you’re using static IP addresses, in which case this is a configuration error and needs to be manually corrected, or you’re using dynamic IP addresses, in which case if the VM receives a GARP reply because of a duplicated IP address, it then uses DHCP to get a new one. Cheers, Andy On Mon, Mar 7, 2016 at 1:45 AM, Saumya Dikshit (sadikshi) <[email protected]<mailto:[email protected]>> wrote: Hi Andrew, Is it assumed that IP address will be known and not dynamically re-assigned and all VM’s are capable of sending out GARP at boot-up. I agree RARP may not be new, but I think still used. Whats happens in a case where VM is migrated to DC-network (may be across geographies and NVO domains) where the IP is already assigned to another VM/entity Thanks Saumya. From: "Andrew G. Malis" <[email protected]<mailto:[email protected]>> Date: Monday, March 7, 2016 at 2:12 PM To: sadikshi <[email protected]<mailto:[email protected]>> Cc: "B. Khasnabish" <[email protected]<mailto:[email protected]>>, Matthew Bocci <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Benson Schliesser <[email protected]<mailto:[email protected]>>, sarikaya <[email protected]<mailto:[email protected]>>, Alia Atlas <[email protected]<mailto:[email protected]>> Subject: Re: [nvo3] Fwd: New Version Notification for draft-sarikaya-nvo3-vmm-dmm-pmip-08.txt Saumya, No, Gratuitous ARP is used to update the other ARP tables when a VM moves. RARP was used to request your own IP address when you don’t know it, but is obsolete, and anyway, the VM already knows its IP address (see section 8 in the draft). Cheers, Andy On Sun, Mar 6, 2016 at 9:31 PM, Saumya Dikshit (sadikshi) <[email protected]<mailto:[email protected]>> wrote: Hello Authors of draft-sarikaya-nvo3-vmm-dmm-pmip, Do we need to take care of cases in which VM speaks with Reverse-ARP and not Gratuitous-ARP ? Thanks Saumya. From: "B. Khasnabish" <[email protected]<mailto:[email protected]>> Date: Monday, March 7, 2016 at 7:13 AM To: Matthew Bocci <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Benson Schliesser <[email protected]<mailto:[email protected]>> Cc: sarikaya <[email protected]<mailto:[email protected]>>, Andrew Malis <[email protected]<mailto:[email protected]>>, Alia Atlas <[email protected]<mailto:[email protected]>> Subject: [nvo3] Fwd: New Version Notification for draft-sarikaya-nvo3-vmm-dmm-pmip-08.txt Dear All, We have addressed all of the outstanding issues, comments, and suggestions in the latest version (ver-08) of this draft on Virtual Machine Mobility (VMM, https://datatracker.ietf.org/doc/draft-sarikaya-nvo3-vmm-dmm-pmip/) and look forward to your support for WG adoption and subsequent publication. Many thanks in advance. Best. Bhumip ---------- Forwarded message ---------- From: <[email protected]<mailto:[email protected]>> Date: Thu, Mar 3, 2016 at 7:28 PM Subject: New Version Notification for draft-sarikaya-nvo3-vmm-dmm-pmip-08.txt To: Bhumip Khasnabish <[email protected]<mailto:[email protected]>>, Linda Dunbar <[email protected]<mailto:[email protected]>>, Behcet Sarikaya <[email protected]<mailto:[email protected]>>, Frank Xia <[email protected]<mailto:[email protected]>>, Linda Dunbar <[email protected]<mailto:[email protected]>> A new version of I-D, draft-sarikaya-nvo3-vmm-dmm-pmip-08.txt has been successfully submitted by Behcet Sarikaya and posted to the IETF repository. Name: draft-sarikaya-nvo3-vmm-dmm-pmip Revision: 08 Title: Virtual Machine Mobility Protocol for Overlay Networks Document date: 2016-03-03 Group: Individual Submission Pages: 11 URL: https://www.ietf.org/internet-drafts/draft-sarikaya-nvo3-vmm-dmm-pmip-08.txt Status: https://datatracker.ietf.org/doc/draft-sarikaya-nvo3-vmm-dmm-pmip/ Htmlized: https://tools.ietf.org/html/draft-sarikaya-nvo3-vmm-dmm-pmip-08 Diff: https://www.ietf.org/rfcdiff?url2=draft-sarikaya-nvo3-vmm-dmm-pmip-08 Abstract: This document describes a virtual machine mobility protocol commonly used in data centers built with overlay-based network virtualization approach. It is based on using a NVA-NVE protocol to update ARP table or neighbor cache entries at the NVA and the source NVEs tunneling in-flight packets to the destination NVE after the virtual machine moves from source NVE to the destination NVE. 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<http://tools.ietf.org>. The IETF Secretariat
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
