[ovs-dev] [PATCH 0/2] Add support for LISP into Open vSwitch

Kyle Mestery (kmestery) kmestery at cisco.com
Thu Jan 24 15:44:29 UTC 2013


On Jan 23, 2013, at 12:02 PM, Jesse Gross <jesse at nicira.com> wrote:
> On Tue, Jan 22, 2013 at 10:36 AM, Kyle Mestery <kmestery at cisco.com> wrote:
>> The following two patches provide support for the LISP tunneling protocol into
>> Open vSwitch. See the latest IETF draft for LISP here:
>> 
>> http://tools.ietf.org/html/draft-ietf-lisp-24
>> 
>> Kyle Mestery (1):
>>  Add support to the tunneling code for a "pre_tunnel" function.
>>    This allows the tunneling code to perform operations on the
>>    packet before the outer IP header is added.
>> 
>> Lorand Jakab (1):
>>  Add support for LISP tunneling
> 
> Hi Kyle,
> 
> I'm curious if you can share your long term plan for LISP.  In
> particular there are three areas that I was wondering about:

We're working on the long-term plan now, I'll send out the plan
tomorrow.

> * L3 support.  Obviously OVS is very Ethernet centric at this point,
> resulting in the need to play games with MAC addresses.

For L3 support, we had discussed this previously on the mailer, but
never came to a conclusion. I think this is a big challenge to tackle,
but would provide benefits to OVS, and certainly would benefit
LISP. We'll work on this infrastructure and propose something around
this.

> * Additional LISP data plane support.  LISP encodes more control
> information in the protocol itself compared to the existing OVS tunnel
> implementations, which basically only have the tunnel ID.  It looks
> like this implementation generates nonces on transmit but otherwise
> doesn't try to handle the other pieces.

I think this can be addressed with future patches. For now, we've simply
enabled a very basic version of LISP.

> * LISP control plane components.
> 
This is the most interesting aspect, and is something we'll have more to
say about soon.

> What do you guys see as the ideal end result?


Well, ultimately having OVS be able to participate in a LISP network would
be the ideal end result. I think this is just a first step to getting us there.


More information about the dev mailing list