[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <55AFBA3E.80209@cumulusnetworks.com>
Date: Wed, 22 Jul 2015 08:43:58 -0700
From: roopa <roopa@...ulusnetworks.com>
To: thomas.morin@...nge.com
CC: Thomas Graf <tgraf@...g.ch>, rshearma@...cade.com,
ebiederm@...ssion.com, hannes@...essinduktion.org,
pshelar@...ira.com, jesse@...ira.com, davem@...emloft.net,
daniel@...earbox.net, tom@...bertland.com, edumazet@...gle.com,
jiri@...nulli.us, marcelo.leitner@...il.com,
stephen@...workplumber.org, jpettit@...ira.com, kaber@...sh.net,
simon.horman@...ronome.com, joestringer@...ira.com, ja@....bg,
ast@...mgrid.com, weichunc@...mgrid.com, dev@...nvswitch.org,
netdev@...r.kernel.org
Subject: Re: [ovs-dev] [PATCH net-next 00/22 v2] Lightweight & flow based
encapsulation
On 7/22/15, 1:58 AM, thomas.morin@...nge.com wrote:
> Hi Thomas,
>
> This looks promising.
>
> One question: will this approach allow MPLS-in-GRE and MPLS-in-UDP ?
>
The current series was focused on IP to MPLS tunnels. But, the
infrastructure allows associating encap state with routes and calling
the respective encapsulation output handlers.
For MPLS-in-GRE and MPLS-in-UDP, it appears that MPLS LSP routes
(af_mpls.c) could support associating GRE and UDP encap info (RTA_ENCAP
and RTA_ENCAP_TYPE) similar to IP routes and the re-direction from MPLS
to GRE or MPLS to UDP can be achieved in a similar way using the same
infrastructure.
Thanks,
Roopa
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists