tree 26201a85773baac274b0c05ffa20ded79429ab15
parent a2519929aba78e8cec7955d2c2a0c1e230d1f6e6
author Eric W. Biederman <ebiederm@xmission.com> 1425431599 -0600
committer David S. Miller <davem@davemloft.net> 1425446766 -0500

mpls: Functions for reading and wrinting mpls labels over netlink

Reading and writing addresses in network byte order in netlink is
traditional and I see no reason to change that.  MPLS is interesting
as effectively it has variabely length addresses (the MPLS label
stack).  To represent these variable length addresses in netlink
I use a valid MPLS label stack (complete with stop bit).

This achieves two things: a well defined existing format is used,
and the data can be interpreted without looking at it's length.

Not needed to look at the length to decode the variable length
network representation allows existing userspace functions
such as inet_ntop to be used without needed to change their
prototype.

Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Signed-off-by: David S. Miller <davem@davemloft.net>