sage-
> > From: Ilya Maximets
> > Sent: Saturday, April 18, 2020 1:54 AM
> > To: Martin Varghese ; d...@openvswitch.org;
> > pshe...@ovn.org; Drennan, Scott (Nokia - US/Mountain View)
> >
> > Cc: Varghese, Martin (Nokia - IN/Bangalore) ;
> > i.maxim...@o
- IN/Bangalore) ;
> i.maxim...@ovn.org; Greg Rose
> Subject: Re: [ovs-dev] [PATCH v2] Encap & Decap actions for MPLS Packet Type
>
> On 12/10/19 9:17 AM, Martin Varghese wrote:
>> From: Martin Varghese
>>
>> The existing PUSH MPLS & POP MPLS ac
To: Martin Varghese ; d...@openvswitch.org;
pshe...@ovn.org; Drennan, Scott (Nokia - US/Mountain View)
Cc: Varghese, Martin (Nokia - IN/Bangalore) ;
i.maxim...@ovn.org; Greg Rose
Subject: Re: [ovs-dev] [PATCH v2] Encap & Decap actions for MPLS Packet Type
On 12/10/19 9:17 AM, Martin Varg
On 12/10/19 9:17 AM, Martin Varghese wrote:
> From: Martin Varghese
>
> The existing PUSH MPLS & POP MPLS actions inserts & removes 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
>
On 12/10/2019 12:17 AM, Martin Varghese wrote:
From: Martin Varghese
The existing PUSH MPLS & POP MPLS actions inserts & removes 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
From: Martin Varghese
The existing PUSH MPLS & POP MPLS actions inserts & removes 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 requirements. In L2 VPN the
