XPost: comp.dcom.lans.ethernet   
   From: mark_cruzNOTFORSPAM@hotmail.com   
      
   Hello Stephen,   
      
   thanks for your comments.   
      
   "Stephen"  wrote in message   
   news:n5ben7dtdqi1bjmomj6v1j3spkvjfts2o8@4ax.com...   
   > You need a way to get routes into the router (just like you would with   
   > IP) - the common way is to use routing protocols since MPLS networks   
   > normally are large scale.   
      
   [skip]   
      
   > The issue is whether the routing protocol and actual router   
   > implementation you are using knows what to do to load balance traffic   
   > across those paths.   
   > This at least involves recognising multiple equal paths, putting more   
   > than 1 into a forwarding table at the same time, and splitting the   
   > traffic load across the paths.   
      
   The one thing I'm trying to understand now is about relation between FTN,   
   ILM and NHLFE -- reading rfc3031 it appears that on LSR  ILM can map an   
   incoming label to a *set* of NHLFEs, that means we can have multiple   
   nexthops per label.   
      
   But can we have multiple labels per FTN entry?   
      
   So we have such relations:   
      
   FTN <-> NHLFE  for un-labeled packets   
   ILM <-> NHLFE  for labeled packets   
      
   Does it make sense?   
      
   Thanks.   
      
   Mark   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)