[ovs-dev] [RFC] Making OVS less Ethernet specific

Lori Jakab lojakab at cisco.com
Fri Jun 7 11:47:49 UTC 2013

On 6/7/13 3:18 AM, Ben Pfaff wrote:
> On Thu, Jun 06, 2013 at 12:56:35AM +0300, Lori Jakab wrote:
>> The LISP tunneling support as of now is not yet ready for upstreaming,
>> for reasons outlined in this message:
>> http://openvswitch.org/pipermail/dev/2013-February/025459.html
>> One solution to the above issues is to make OVS less Ethernet specific,
>> meaning that it should accept and work with packets/flows without an
>> Ethernet header.
> Most of this email was about the datapath implications.  I'll leave
> those for Jesse.
> Have you considered the OpenFlow implications?  OpenFlow itself is
> somewhat Ethernet centric.  Improving this has been in discussion, in
> various ways, in the "extensibility" working group at ONF for a couple
> of years now, e.g. in these tickets:
>      https://rs.opennetworking.org/bugs/browse/EXT-56
>      https://rs.opennetworking.org/bugs/browse/EXT-111
>      https://rs.opennetworking.org/bugs/browse/EXT-112
> (If you don't have an account, you'll need to get one to view those
> tickets.  That should be easy for anyone at an ONF member company,
> including Cisco.)
> EXT-56 was resolved with OpenFlow 1.2.  EXT-111 and EXT-112 are still
> unresolved, but they are also quite vague.

Thanks for pointing this out Ben, we will join the discussion.


More information about the dev mailing list