The MPLS-OPS Archive

["Eric Osborne" <eosborne@cisco.com>]

 > >I think we have already come out with solutions which
 > >obviates the need for principals
 > >like count to infinity, etc. As a consequence we have
 > >now done away with a protocol like
 > >RIP.
 > 
 > Can you please tell me what are the best solutions to
 > such a class of problems? 
 >

There's that Dijkstra-based stuff that's all the rage nowadays....



eric
 
 > I believe here is one I have seen:
 > Are you saying we "tag the source of the information"
 > along with the information and ensure that if the
 > "loop" occurs we look at the source of the information
 > and drop the "feedback"?
 > In essence what you are saying is that topologically
 > from the routing viewpoint, we are making a "tree"
 > though we may have a wire connecting the point of
 > input and the point of feedback?
 > 
 > Would we not need to make these information source
 > identifiers to be unique "within a network"  in some
 > manner?
 > 
 > -Sylvia
 > 
 > 
 > 
 > 
 > 	
 > 	
 > 		
 > ___________________________________________________________
 > Yahoo! Messenger - Communicate instantly..."Ping" 
 > your friends today! Download Messenger Now 
 > http://uk.messenger.yahoo.com/download/index.html
 > 
 > -------
 > The MPLS-OPS Mailing List
 > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
 > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
 > 

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml