Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Searchable, convenient, complete TCP/IP information.
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Lower-Layer (Interface, Internet and Transport) Protocols (OSI Layers 2, 3 and 4)
      9  TCP/IP Internet Layer (OSI Network Layer) Protocols
           9  TCP/IP Routing Protocols (Gateway Protocols)
                9  TCP/IP Interior Routing Protocols (RIP, OSPF, GGP, HELLO, IGRP, EIGRP)
                     9  Other Interior Routing Protocols

Previous Topic/Section
The HELLO Protocol (HELLO)
Previous Page
Pages in Current Topic/Section
1
2
Next Page
Enhanced Interior Gateway Routing Protocol (EIGRP)
Next Topic/Section

Interior Gateway Routing Protocol (IGRP)
(Page 1 of 2)

If you have read a substantial portion of this Guide already, you have probably noticed that I greatly prefer universal, open standards to proprietary standards. (I explain the reasons why in the Networking Fundamentals section on standards.) I am far from alone in this view, and in fact, it's no exaggeration to say that much of the success of TCP/IP and the Internet is tied to the fact that they were both developed using the open RFC process, and still are to this day.

That said, there are certain situations where a proprietary protocol can be of benefit, and can even achieve considerable success, if a minimum of two factors are true. First, there must be either a lack of a suitable open protocol, or a gap in the feature coverage of existing open protocols that creates an “opportunity” for a proprietary protocol to succeed. Second, the proprietary protocol must be either initiated or strongly supported by a “big player” in the industry, to help ensure that other companies will take notice and give the protocol a chance to become a standard.

This situation arose in the 1980s in the world of routing protocols. At that time, the most popular interior routing protocol was the Routing Information Protocol (RIP). As described in the RIP section of this Guide, RIP does a basically good job, but has a number of limitations and problems that are inherent to the protocol and not easily resolved. In the mid-1980s, open alternatives like OSPF did not yet exist; even if it had, OSPF is much more complex than RIP and therefore sometimes not a good alternative.

Cisco Systems, definitely one of the “big names” in networking and especially internetworking and routing, decided to develop a new routing protocol that would be similar to RIP but would provide greater functionality and solve some of RIP's inherent problems: the Interior Gateway Routing Protocol (IGRP). IGRP—which conveniently uses both the words “gateway” and “routing” in its name to convey the equivalence of the two words in internetworking standards—was designed specifically to be a replacement for RIP. It is similar in many ways, and keeps RIP's simplicity, one of its key strengths. At the same time, IGRP overcomes two key limitations of RIP: the use of only hop count as a routing metric, and the hop count limit of 15.

Overview of Operation

Like RIP, IGRP is a distance-vector routing protocol designed for use with an autonomous system, and thus uses the same basic mechanism for route determination. Each router routinely sends out on each local network to which it is attached a message containing a copy of its routing table. This message contains pairs of reachable networks and costs (metrics) to reach each network. A router receiving this message knows it can reach all the networks in the message as long as it can reach the router that sent the message. It computes the cost to reach those networks by adding to their costs, the cost to reach the router that sent the message. The routers update their tables accordingly, and send this information out in their next routine update. Eventually, each router in the autonomous system has information about the cost to reach each network in it.


Previous Topic/Section
The HELLO Protocol (HELLO)
Previous Page
Pages in Current Topic/Section
1
2
Next Page
Enhanced Interior Gateway Routing Protocol (EIGRP)
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.