Perhaps we should think about some of the features usually associated with Link State protocols:
- develop a map of the area so that all participating routers in the area have the same understanding of the topology.
- after an initial synchronization of the routing information with a neighbor there is no periodic advertisement of the routing information.
- does not need to use split horizon because developing the map of links in the area takes care of that need.
And think of some of the features usually associated with Distance Vector protocols:
- learns prefixes from a neighbor and advertises those prefixes plus its own local prefixes to other neighbors.
- periodically advertises all of its prefixes to neighbors as a way to synchronize the routing information.
- uses split horizon to prevent advertising back to a neighbor routes that it learned from that neighbor.
Then think about EIGRP
- it does not develop a map of the links in the area. So not so much like Link State.
- it does advertise prefixes learned from a neighbor plus its own local prefixes to other neighbors. So more like Distance Vector.
- it does use Split Horizon. So more like Distance Vector.
- it does not do periodic advertisements of all of its prefixes. So is more like Link State.
HTH
Rick
