From: "James R. Leu" <jleu@mindspring.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Ramon Casellas <casellas@infres.enst.fr>, netdev@oss.sgi.com
Subject: Re: Request: Allocate a Netlink Family Number for MPLS
Date: Fri, 5 Dec 2003 11:35:32 -0600 [thread overview]
Message-ID: <20031205173507.GB2241@mindspring.com> (raw)
In-Reply-To: <20031201124532.3f6b6a65.davem@redhat.com>
On Mon, Dec 01, 2003 at 12:45:32PM -0800, David S. Miller wrote:
> On Mon, 1 Dec 2003 15:36:26 +0100 (MET)
> Ramon Casellas <casellas@infres.enst.fr> wrote:
>
> > We're working in porting mpls for linux to 2.6 and one of the planned
> > features is to move from an IOCTL based approach to a Netlink based one
> > for updating/querying the MPLS FTN/ILM/Label Mapping/... tables from
> > userspace. Since netlink families are public, I would
> > like to know if it is possible to reserve a family for MPLS, even though
> > the MPLS patch is not part of the official kernel.
>
> You don't need a whole new netlink family. Just create a dummy
> address family for MPLS (ie. AF_MPLS) and then just use
> NETLINK_ROUTE.
Agreed. One could also use AF_MPLS for applications to register for
data associated with the router alert label. I suppose one
could also go completly nuts and allow an application to open stream
connection that talks and listens on a specific label, but I think
that is a bit overboard.
--
James R. Leu
jleu@mindspring.com
prev parent reply other threads:[~2003-12-05 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 14:36 Request: Allocate a Netlink Family Number for MPLS Ramon Casellas
2003-12-01 15:30 ` Christoph Hellwig
2003-12-01 19:26 ` Ramon Casellas
2003-12-01 21:10 ` jamal
2003-12-01 20:45 ` David S. Miller
2003-12-05 17:35 ` James R. Leu [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=20031205173507.GB2241@mindspring.com \
--to=jleu@mindspring.com \
--cc=casellas@infres.enst.fr \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.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).