I agree with Kent..... Although the link you (Rick) provided uses the word "link-state", it uses it once in the opening and once in the summary... That's it! The fact is that one needs to analyze the protocol to see it's behavior... it may well have traits of this or that type of protocol but not be either one..... I mean, really the categories of Distance-Vector and Link-State are just descriptions, not hard boundaries.....
Priscilla has made a convincing argument that EIGRP acts mostly as a Distance-Vector protocol..... Although it has advanced features that may resemble those of a link-state protocol, that doesn't make it link-state. As she mentioned, Link-State means something very specific to mathematicians (where all of these magic algorithms come from... *not* network people)... Link-state machinesBut, again, as Kent says, if you disagree then lay out your arguments for people to read and decide... It's interesting to note that Distance-Vector protocols, because of their operation, require various things to help them prevent routing loops, like poison reverse and split-horizon. EIGRP uses split-horizon, but not poison reverse. Does that make it distance-vector? Not necessarily..... But it doesn't mean it's not either =) (I love riding the fence.. hehe) Check out the following link, and compare what it says to EIGRP and see what you think..... http://www.cs.bris.ac.uk/Teaching/Resources/COMS22100/AC/slides/lec8P.pdf Mike W. "Kent Yu" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Rick, > > I think the bottom line is no matter who says what, we want to take a look > where he/she is coming from. If after reading Priscilla's post closely and > comparing OSPF/IS-IS to RIP/EIGRP/IGRP, you still disagree with Priscilla on > this, > please let us your arguments. > > Thanks > Kent Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=44134&t=43994 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]