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

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

On Thu, Feb 19, 2004 at 09:26:01AM -0500, Jamal Hadi Salim wrote:
> On Wed, 2004-02-18 at 23:28, James R. Leu wrote:
> [..]
> > > Note, as i described earlier, we should be able to just look at
> > > anything on the packet with the u32 classifier which can be activated
> > > before MPLS ILM is consulted. Also based on the top label we can
> > > do a classification again to peek into further packet data before making 
> > > a decision the next hop.
> > 
> > What do that work for ILM which are just a swap?  It should only be done
> > when needed, otherwise what's the point of the LS in MPLS?
> > 
> 
> I was thinking more of you would use the u32 to detect which flows and
> use flowid to help in in the m-hop.
> We could always do this later in addition to what you are proposing.
> Your proposal is the quickest way to get us there.
> BTW, look at my earlier email (Ramon reached a similar conclusion)
> on the algorithm plugins for selecting the Nhops. If we agree on that
> algorithm plugin, lets have someone raise their hand to implememt.
> If neitehr of you guys raise your hands i can take it.

Since it is a nice modular piece.  Maybe Ramon or you can work on it.
I'll focus on the dst stacking stuff.

> > I'll make the change.  I'll send it to the list for review. I'd just
> > like to note that by ignoring hierachy, we're designing/developing by only
> > looking at about 25% of the requirements.  As I'm sure your familiar with,
> > it usually requires a re-spin to support the other 75% :-)
> 
> Sorry, didnt mean ignore it in the design - unless it overcomplicates
> things immensely. What i meant is when we sell it to Davem (which i dont
> see as a complication given the dst stacking is useful) is not to sell
> the LSP hierachies to start with. But lets see the code then we can make
> the call. Please do factor in the hierachies.

The key for implementing hierachy is indirection and the realization that
not all traffic that arrives on a particular in-segment gets the same actions
applied (this goes back to the idea that the meaning of 'pop' is determined
by which position in the stack it is being applied to).

> 
> cheers,
> jamal
> 
> 
> 
> 
> -------------------------------------------------------
> 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...