From: David Miller <davem@davemloft.net>
To: martinvarghesenokia@gmail.com
Cc: netdev@vger.kernel.org, pshelar@ovn.org, scott.drennan@nokia.com,
jbenc@redhat.com, martin.varghese@nokia.com
Subject: Re: [PATCH net-next v5 0/3] New openvswitch MPLS actions for layer 2 tunnelling
Date: Tue, 24 Dec 2019 22:25:04 -0800 (PST) [thread overview]
Message-ID: <20191224.222504.1002685539423182176.davem@davemloft.net> (raw)
In-Reply-To: <cover.1576896417.git.martin.varghese@nokia.com>
From: Martin Varghese <martinvarghesenokia@gmail.com>
Date: Sat, 21 Dec 2019 08:49:36 +0530
> The existing PUSH MPLS action inserts MPLS header between ethernet header
> and the IP header. Though this behaviour is fine for L3 VPN where an IP
> packet is encapsulated inside a MPLS tunnel, it does not suffice the L2
> VPN (l2 tunnelling) requirements. In L2 VPN the MPLS header should
> encapsulate the ethernet packet.
>
> The new mpls action ADD_MPLS inserts MPLS header at the start of the
> packet or at the start of the l3 header depending on the value of l3 tunnel
> flag in the ADD_MPLS arguments.
>
> POP_MPLS action is extended to support ethertype 0x6558
...
Series applied, thanks.
prev parent reply other threads:[~2019-12-25 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 3:19 [PATCH net-next v5 0/3] New openvswitch MPLS actions for layer 2 tunnelling Martin Varghese
2019-12-21 3:20 ` [PATCH net-next v5 1/3] net: skb_mpls_push() modified to allow MPLS header push at start of packet Martin Varghese
2019-12-21 17:25 ` Pravin Shelar
2019-12-21 3:20 ` [PATCH net-next v5 2/3] net: Rephrased comments section of skb_mpls_pop() Martin Varghese
2019-12-21 17:25 ` Pravin Shelar
2019-12-21 3:20 ` [PATCH net-next v5 3/3] openvswitch: New MPLS actions for layer 2 tunnelling Martin Varghese
2019-12-21 17:26 ` Pravin Shelar
2019-12-25 6:25 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191224.222504.1002685539423182176.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jbenc@redhat.com \
--cc=martin.varghese@nokia.com \
--cc=martinvarghesenokia@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
--cc=scott.drennan@nokia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).