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 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  TCP/IP Routing Information Protocol (RIP, RIP-2 and RIPng)                           9  RIP Fundamentals and General Operation

RIP Fundamentals and General Operation 1 2 3 RIP Route Determination Algorithm and Metric

Development of RIP Version 2 (RIP-2) and RIPng for IPv6

Some other issues with RIP were a result of its having been developed in the early 1980s when TCP/IP was still in its infancy. Over time, as the use of TCP/IP protocols changed, RIP became outdated. In response, RIP Version 2, or RIP-2 was created in the early 1990s. RIP-2 defines a new message format for RIP and includes a number of new features, including support for classless addressing, authentication, and the use of multicasting instead of broadcasting to improve network performance. It was first defined in RFC 1388, RIP Version 2 Carrying Additional Information, published in January 1993. This RFC was revised in RFC 1723, and finalized in RFC 2453, RIP Version 2, November 1998.

Over two decades after it was first created, RIP continues to be a popular interior routing protocol. Its limitations have led to many internetworking experts hoping that the protocol would eventually “go away”, in favor of newer protocols like OSPF that are superior on a strictly technical basis. Some have gone so far as to sarcastically suggest that maybe it would be best if RIP would “R. I. P.” (“rest in peace”.) J Once a protocol becomes popular, however, it's hard to resist momentum, and RIP is likely to continue to be used for many years to come.

In order to ensure that RIP can work with TCP/IP in the future, it was necessary to define a version that would work with the new Internet Protocol version 6 (IPv6). In 1997, RFC 2080 was published, titled RIPng for IPv6. The ng stands for next generation—recall that IPv6 is also sometimes called IPng. RIPng is not just a new version of RIP, like RIP-2, but is defined as a new standalone protocol. It is, however, based closely on the original RIP and RIP-2 standards. A distinct protocol (as opposed to a revision of the original) was needed due to the changes made between IPv4 and IPv6, though RIP and RIPng work in the same basic way. RIPng is sometimes also called RIPv6.

RIP Fundamentals and General Operation 1 2 3 RIP Route Determination Algorithm and Metric