Luyuan, I saw that Thomas and Larry responded. Let me do it separately, so we don't get confused.
> 1) If NVE and TES are in the same physical device - there is no > external wire between them, then no VDP or VDP-like protocol is needed, > regardless L2 or L3 is used. Yes. > 2) If NVE and TES are not in the same physical device, but TES to NVE > using L3 protocols only, there is still no need for VDP or VDP-alike > protocol. We need a protocol here also since the VPN endpoint membership information must be communicated to NVE by the end-system (TES). The end-system L3VPN proposal uses XMPP for that purpose (as well as for communication with the VPN controller/signaling gateway). > 3) If NVE and TES are not in the same physical device, TES to NVE using > L2, then VDP or VDP-like protocol plays important role for discovery > and more. > > Thanks, > Luyuan > > > -----Original Message----- > > From: Paul Unbehagen [mailto:[email protected]] > > Sent: Wednesday, July 11, 2012 1:18 PM > > To: NAPIERALA, MARIA H > > Cc: Thomas Narten; Luyuan Fang (lufang); [email protected] > > Subject: Re: [nvo3] TES-NVE attach/detach protocol security > (mobility- > > issues draft) > > > > VDP isn't that complicated of a protocol. It was designed to > > autoconnect VMs to the proper VLAN and any tenant profile required by > > involving communication to a management system which then configures > > the proper tenant parameters in the ToR/EoR in a automated way. This > > is all transparent to the routing layer as the IP and default gateway > > and vlan assignment take care of all that automatically. > > > > I believe it's already in a few server vendors products already as I > > saw prototypes of it a couple years ago. > > > > -- > > Paul Unbehagen > > > > > > On Jul 11, 2012, at 10:20 AM, "NAPIERALA, MARIA H" <[email protected]> > > wrote: > > > > >> Also VDP is between the Hypervisor and NVE. Thus, it may still be > > >> needed, even if the service provided to the TES is L3 only. > > > > > > In a layer 3 solution (whether encapsulation starts at the > hypervisor > > or on a switch outside of the hypervisor) there is no need to run a > > complicated (IEEE) protocol such as VDP. VDP was invented to > > interoperate a virtual server with an external layer 2 switch/bridge. > > > A layer 3 solution can use much simpler IP-based protocol > (developed > > in IETF) such as Extensible Messaging and Presence Protocol (XMPP). > > > > > > Maria > > > _______________________________________________ > > > nvo3 mailing list > > > [email protected] > > > https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
