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

Ben Pfaff blp at nicira.com
Mon Jun 10 22:14:38 UTC 2013

On Mon, Jun 10, 2013 at 03:09:33PM -0700, Jesse Gross wrote:
> On Wed, Jun 5, 2013 at 2:56 PM, Lori Jakab <lojakab at cisco.com> wrote:
> > At a high level, we would introduce layer 3 (tunnel) vports, and LISP
> > would be such a vport.  Whenever a packet that ingressed on a L2 vport
> > needs to egress on a L3 vport, we apply the internal pop_eth action
> > automatically.  For packets going from L3 vports to L2 vports, a
> > push_eth action would add a MAC header, with addresses determined by ARP
> > resolution in user space.
> One other thing that you might want to keep in the back of your mind
> as you implement this is how it might interact with MAC-in-MAC
> encapsulation. OVS doesn't currently support this but if it did (and
> there have been requests), it would presumably want to use these
> actions as well.

In case some of you guys didn't know, recent versions of OpenFlow
include specifications for PBB encapsulation, which is one form of
MAC-in-MAC.  (I don't know anything more about it than that, so I'm
just pointing it out in case it's relevant.)

More information about the dev mailing list