Re: [mpls-linux-devel] Re: 2.6 Spec: Random comments.

[James R. L. <jl...@mi...>]

The MPLS tunnel interface fits well into the 'cisco' model of TE LSPS, which
represents them as a ptp Tunnel interface with a peer address of the
end-point of the LSP.  The 'juniper' model represents TE LSPs and just
another route in the MPLS 'routing' table (/32 route for the end-point of
the TE LSP).  I personally perfer the 'cisco' model, it provides more
flexibility (anything that can work with a netdevice can use it).

On Fri, Feb 13, 2004 at 06:10:13PM +0100, Ramon Casellas wrote:
> On 13 Feb 2004, Jamal Hadi Salim wrote:
> 
> > you are sure you dont want nh somewhere in there?
> > since this is a reference to the NHlfe;
> > heck why dont we just call it nhlfe_id ? ;->
> 
> 
> nhlfe_id is fine for me.
> 
> 
> > Refer to my earlier email for the suggestions i made.
> 
> Agreed.
> 
> 
> >
> > > comment: I *do* think that mpls_tunnel.c from James impl can directly be
> > > used and it's very convenient. Just %s/moi/fwd_id/g
> >
> > What is the mpls_tunnel.c for? Is it a netdevice? What is it used for?
> 
> 
> Yes. It is a virtual netdevice that is allocated upon request and
> basically holds a MOI (the equivalent of a nhlfe_id). User sees it as a
> unidirectional netdevice (ifconfig, etc),
> 
> Take a look at the file if you happen to find some spare time (Indeed, it
> can be improved and the sysfs integration was a little hairy) but I think
> it is very convenient and extensively used when RSVP-TE sets up LSPs.
> 
> regards,
> Ramon
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

-- 
James R. Leu
jl...@mi...