Hi Robert,
Hmm, perhaps I still wasn't clear enough.
I want to know *who* is going to use a protocol between the server an an L3
d-lNVE? Who has got product/prototype that needs such a protocol, standardized
or not? You don't need to be explicit if you are concerned about revealing
future product plans, just a coy raising of a hand.
I don't see anyone in cloud space right now who has any such
product/prototype/concept for upcoming implementation with an L3 d-lNVE. Now,
that doesn't mean that there isn't someone, but there are multiple NVO3 drafts
out there based on this concept, and I assume that someone must have something
cooking to devote so much text writing and email time to discussing it.
If not, then I think the WG would be better to spend its time on discussing
protocols for architectures that are deployed or have some hope of deployment.
jak
> -----Original Message-----
> From: Robert Raszuk [mailto:[email protected]]
> Sent: Tuesday, July 24, 2012 3:06 PM
> To: James Kempf
> Cc: Kireeti Kompella; [email protected]
> Subject: Re: [nvo3] (no subject)
>
> Hi James,
>
> I think actually Kireeti has precisely answered your
> question. L3VPN model addresses very well the L3
> virtualization requirement IMHO.
>
> Of course I do agree with those who say that PE should reside
> on the hypervisor rather then TOR. So rather then asking for
> yet another proprietary virtualization protocol you could
> consider perhaps using a solution which is standards based
> yet allow flexible creation of virtual topologies for the
> tenant interconnects (both intra and inter data center).
>
> Best regards,
> R.
>
> > Hi Kireeti,
> > I don't think you've answered my question. My question was whether
> > there is any product or prototype currently that has a
> distributed lNVE.
> > If I ask the same question about a localized lNVE, I get
> the following:
> >
> > OVS/Nicira (um, I mean VMWare :-) NVP
> > Cisco Nexus 1000V and VMWare ESX
> > VMWare ESX Server Virtual Switch
> > VSphere Distributed Virtual Switch (the control plane is
> distributed,
> > not the NVE termination point).
> >
> > I'd like to see the same list of products or prototypes for a
> > distributed lNVE.
> > jak
> >
> >
> --------------------------------------------------------------
> ----------
> > *From:* Kireeti Kompella [mailto:[email protected]]
> > *Sent:* Tuesday, July 24, 2012 2:09 PM
> > *To:* James Kempf
> > *Cc:* [email protected]
> > *Subject:* Re: [nvo3] (no subject)
> >
> > Hi James,
> >
> > On Tue, Jul 24, 2012 at 1:43 PM, James Kempf
> > <[email protected]
> <mailto:[email protected]>> wrote:
> >
> > I had a question on something in draft-kompella:
> >
> > >In some cases, the lNVE is co-resident with the server
> > > hosting the VM; in other cases, the lNVE is separate
> > (distributed
> > > lNVE). The latter case is the one of interest in this
> > document.
> >
> > Is there any product/prototype currently under
> development which
> > anyone is aware of where there is an L3 (not L2)
> lNVE that falls
> > into the latter case?
> >
> >
> > Anyone's boxes that do IP VPNs (RFC 4364) could in
> principle be used
> > as an L3 lNVE. However, they vary in their ability to
> comply with
> > other requirements of the data center environment.
> >
> > If you view E-VPNs as L3-ish, that adds to the list.
> >
> > Kireeti.
> >
> > jak
> > _______________________________________________
> > nvo3 mailing list
> > [email protected] <mailto:[email protected]>
> > https://www.ietf.org/mailman/listinfo/nvo3
> >
> >
> >
> >
> > --
> > Kireeti
> >
> >
> >
> > _______________________________________________
> > nvo3 mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/nvo3
> >
>
>
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
