Routing Information Protocol
|Internet protocol suite|
The Routing Information Protocol (RIP) is one of the oldest distance-vector routing protocols which employ the hop count as a routing metric. RIP prevents routing loops by implementing a limit on the number of hops allowed in a path from source to destination. The maximum number of hops allowed for RIP is 15, which limits the size of networks that RIP can support. A hop count of 16 is considered an infinite distance and the route is considered unreachable. RIP implements the split horizon, route poisoning and holddown mechanisms to prevent incorrect routing information from being propagated.
Originally, each RIP router transmitted full updates every 30 seconds. In the early deployments, routing tables were small enough that the traffic was not significant. As networks grew in size, however, it became evident there could be a massive traffic burst every 30 seconds, even if the routers had been initialized at random times. It was thought, as a result of random initialization, the routing updates would spread out in time, but this was not true in practice. Sally Floyd and Van Jacobson showed in 1994 that, without slight randomization of the update timer, the timers synchronized over time.
In most networking environments, RIP is not the preferred choice for routing as its time to converge and scalability are poor compared to EIGRP, OSPF, or IS-IS.. However, it is easy to configure, because RIP does not require any parameters unlike other protocols.
There are three versions of the Routing Information Protocol: RIPv1, RIPv2, and RIPng.
RIP version 1
The original specification of RIP, defined in RFC 1058, was published in 1988 and uses classful routing. The periodic routing updates do not carry subnet information, lacking support for variable length subnet masks (VLSM). This limitation makes it impossible to have different-sized subnets inside of the same network class. In other words, all subnets in a network class must have the same size. There is also no support for router authentication, making RIP vulnerable to various attacks.
RIP version 2
Due to the deficiencies of the original RIP specification, RIP version 2 (RIPv2) was developed in 1993 and last standardized in 1998. It included the ability to carry subnet information, thus supporting Classless Inter-Domain Routing (CIDR). To maintain backward compatibility, the hop count limit of 15 remained. RIPv2 has facilities to fully interoperate with the earlier specification if all Must Be Zero protocol fields in the RIPv1 messages are properly specified. In addition, a compatibility switch feature allows fine-grained interoperability adjustments.
In an effort to avoid unnecessary load on hosts that do not participate in routing, RIPv2 multicasts the entire routing table to all adjacent routers at the address 220.127.116.11, as opposed to RIPv1 which uses broadcast. Unicast addressing is still allowed for special applications.
Route tags were also added in RIP version 2. This functionality allows a distinction between routes learned from the RIP protocol and routes learned from other protocols.
- Support of IPv6 networking.
- While RIPv2 supports RIPv1 updates authentication, RIPng does not. IPv6 routers were, at the time, supposed to use IPsec for authentication.
- RIPv2 encodes the next-hop into each route entry, RIPng requires specific encoding of the next hop for a set of route entries.
RIPng sends updates on UDP port 521 using the multicast group FF02::9.
RIP defines two types of messages.
- Request Message
- Response Message
When a RIP router comes online, it sends a broadcast Request Message on all of its RIP enabled interfaces. All the neighbouring routers which receive the Request message respond back with the Response Message containing their Routing table. The Response Message is also gratuitously sent when the Update timer expires. On receiving the Routing table, the router processes each entry of the routing table as per the following rules
- If there are no route entry matching the one received then the route entry is added to the routing table automatically, along with the information about the router from which it received the routing table
- If there are matching entry but the hop count metric is lower than the one already in its routing table, then the routing table is updated with the new route.
- If there are matching entry but the hop count metric is higher than the one already in its routing table, then the routing entry is updated with hop count of 16 (infinite hop). The packets are still forwarded to the old route. A Holddown timer is started and all the updates for that from other routers are ignored. If after the Holddown timer expires and still the router is advertising with the same higher hop count then the value is updated into its routing table. Only after the timer expires, the updates from other routers are accepted for that route.
The routing information protocol uses the following timers as part of its operation:-
- Update Timer
- Invalid Timer
- Flush Timer
- Holddown Timer
The update timer controls the interval between two gratuitous Response Message. By default the value is 30 seconds. The response message is broadcast to all its RIP enabled interface.
The invalid timer specifies how long a routing entry can be in the routing table without being updated. This is also called as expiration Timer. By default, the value is 180 seconds. After the timer expires the hop count of the routing entry will be set to 16, marking the destination as unreachable.
The flush timer controls the time between the route is invalidated or marked as unreachable and removal of entry from the routing table. By default the value is 240 seconds. This is 60 seconds longer than Invalid timer. So for 60 seconds the router will be advertising about this unreachable route to all its neighbours. This timer must be set to a higher value than the invalid timer. 
The hold-down timer is started per route entry, when the hop count is changing from lower value to higher value. This allows the route to get stabilized. During this time no update can be done to that routing entry. This is not part of the RFC 1058. This is Cisco's implementation. The default value of this timer is 180 seconds.
- The hop count cannot exceed 15, or routes will be dropped.
- Most RIP networks are flat. There is no concept of areas or boundaries in RIP networks (but aggregation is possible).
- Variable Length Subnet Masks are not supported by RIP version 1 (which is obsolete).
- RIP has slow convergence and count to infinity problems.
- Cisco IOS, software used in Cisco routers (supports version 1, version 2 and RIPng)
- Cisco NX-OS software used in Cisco Nexus data center switches (supports RIPv1 and RIPv2)
- Junos software used in Juniper routers, switches, and firewalls (supports RIPv1 and RIPv2)
- Routing and Remote Access, a Windows Server feature, contains RIP support
- Quagga, a free open source routing software suite based on GNU Zebra
- BIRD, a free open source routing software suite
- Zeroshell, a free open source routing software suite
- A RIP implementation first introduced in 4.2BSD, routed, survives in several of its descendants, including FreeBSD and NetBSD.
- OpenBSD introduced a new implementation, ripd, in version 4.1 and retired routed in version 4.4.
- Netgear routers commonly offer a choice of two implementations of RIPv2; these are labelled RIP_2M and RIP_2B. RIP_2M is the standard RIPv2 implementation using multicasting - which requires all routers on the network to support RIPv2 and multicasting, whereas RIP_2B sends RIPv2 packets using subnet broadcasting - making it more compatible with routers that do not support multicasting, including RIPv1 routers.
Cisco's proprietary Interior Gateway Routing Protocol (IGRP) was a somewhat more capable protocol than RIP. It belongs to the same basic family of distance-vector routing protocols. Cisco has ceased support and distribution of IGRP in their router software. It was replaced by the Enhanced Interior Gateway Routing Protocol (EIGRP) which is a completely new design. While EIGRP still uses a distance-vector model, it relates to IGRP only in using the same routing metrics. IGRP supports multiple metrics for each route, including bandwidth, delay, load, MTU, and reliability.
- The Synchronization of Periodic Routing Messages, S. Floyd & V. Jacobson,April 1994
- "Port Numbers" (plain text). The Internet Assigned Numbers Authority (IANA). 22 May 2008. Retrieved 25 May 2008.
- RFC 1058, Routing Information Protocol, C. Hendrik, The Internet Society (June 1988)
- RFC 2453, RIP Version 2, G. Malkin, The Internet Society (November 1998)
- RFC 2082, RIP-2 MD5 Authentication, F. Baker, R. Atkinson, The Internet Society (January 1997)
- RFC 4822, RIPv2 Cryptographic Authentication, R. Atkinson, M. Fanto, The Internet Society (January 2007)
- RFC 2080, RIPng for IPv6, G. Malkin, R. Minnear, The Internet Society (January 1997)
- Balchunas, Aaron. "Routing Information Protocol (RIP v1.03)" (PDF). http://www.routeralley.com. Retrieved 25 April 2014.
- "routed, rdisc — network RIP and router discovery routing daemon". FreeBSD manual pages.
- "routed, rdisc — network RIP and router discovery routing daemon". NetBSD manual pages.
- "ripd — Routing Information Protocol daemon". OpenBSD manual pages.
- "How do I change the LAN TCP/IP settings on my Nighthawk router?". Netgear Support pages.
- Malkin, Gary Scott (2000). RIP: An Intra-Domain Routing Protocol. Addison-Wesley Longman. ISBN 0-201-43320-6.
- Edward A. Taft, Gateway Information Protocol (revised) (Xerox Parc, Palo Alto, May, 1979)
- Xerox System Integration Standard - Internet Transport Protocols (Xerox, Stamford, 1981)