On 7/22/16 9:47 AM, Tom Herbert wrote:

On Jul 22, 2016 11:44 AM, "Tom Herbert" <[email protected] <mailto:[email protected]>> wrote:
>
> On Jul 22, 2016 3:38 AM, "Dino Farinacci" <[email protected] <mailto:[email protected]>> wrote:
> >
> > > - VXLAN-GPE does not appear compatible with VXLAN-GPE. If a VXLAN host receives a VXLAN packet for some protocol other than Ethern the payload will be misinterpreted. A separate port number was required. I assume that a user using VXLAN in HW must upgrade HW to use VXLAN-GPE
> >
> > Tom, one clarification. Did you really mean VXLAN-GPE is not compatible with VXLAN-GPE or did you mean VXLAN?
> >
> Yes
>MB
That is to day VXLAN-GPE is not compatible with VXLAN.


We have had in the past the discussion about forward/backward compatibility, and IMO it wasn't very productive.

I observe that a VXLAN-GPE packet that carries an ethernet frame can be parsed by a VXLAN receiver (provided UDP port is properly configured). I think some implementors/deployers may take advantage of this property, but this is a minor point.

What I think is important, and it was one of the design goals of VXLAN-GPE, is that an implementation of VXLAN-GPE includes an implementation of VXLAN at no additional cost. This is one of the reasons that makes VXLAN-GPE attractive for HW implementations.


Fabio

> > This is how a VXLAN-GPE encapsulator (an upgraded system) can talk to a VXLAN decapsulator (an existing system) with the LISP control-plane:
> >
> > (1) The encapsulator does a lookup on a MAC address to the mapping system. > > (2) What gets retunred is the decapsultor’s IP address and an encapsulation format. In this case the encapsulation format is VXLAN. > > (3) The VXLAN-GPE supuported encapsulator then encapsulates packets with UDP port 4789.
> >
> > I am told you can do this with BGP as well by negotiating what encapsulations are supported.
> >
> > Dino
> >



_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3


_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3

Reply via email to