netdev - Re: [net-next RFC 05/14] route: Per route tunnel metadata with RTA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 2 Jun 2015 01:26:08 +0200
From:	Thomas Graf <tgraf@...g.ch>
To:	Robert Shearman <rshearma@...cade.com>
Cc:	netdev@...r.kernel.org, pshelar@...ira.com, jesse@...ira.com,
	davem@...emloft.net, daniel@...earbox.net, dev@...nvswitch.org,
	tom@...bertland.com, edumazet@...gle.com, jiri@...nulli.us,
	hannes@...essinduktion.org, marcelo.leitner@...il.com,
	stephen@...workplumber.org, jpettit@...ira.com, kaber@...sh.net
Subject: Re: [net-next RFC 05/14] route: Per route tunnel metadata with
 RTA_TUNNEL

On 06/01/15 at 05:51pm, Robert Shearman wrote:
> On 01/06/15 15:27, Thomas Graf wrote:
> >Introduces a new Netlink attribute RTA_TUNNEL which allows routes
> >to set tunnel transmit metadata and specify the tunnel endpoint or
> >tunnel id on a per route basis. The route must point to a tunnel
> >device which understands per skb tunnel metadata and has been put
> >into the respective mode.
> 
> We've been discussing something similar for the purposes of IP over MPLS,
> but most of the attributes for IP tunnels aren't relevant for MPLS. It be
> great if we can come up with something general enough that can serve both
> purposes. I've just sent a patch series ("[RFC net-next 0/3] IP imposition
> of per-nh MPLS encap") which I believe would allow this.

Nice! On a first glance, your series looks like an excellent complement
to this series. I'll comment directly in your series.
--
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