Misplaced Pages

Routing Information Protocol: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 15:44, 28 September 2005 edit141.202.248.11 (talk) Versions← Previous edit Revision as of 11:17, 29 September 2005 edit undoBarberio (talk | contribs)Extended confirmed users4,269 edits RIP *not* developed for ARPANET. Pre-dates the first RFC on the standard.Next edit →
Line 3: Line 3:
The '''Routing Information Protocol''' (RIP) is one of the most commonly used ] (IGP) ] protocols on internal networks (and to a lesser extent, networks connected to the ]), which helps ]s dynamically adapt to changes of network connections by communicating information about which networks each router can reach and how far away those networks are. Although RIP is still actively used, it is generally considered to have been obsoleted by routing protocols such as ] and ]. The '''Routing Information Protocol''' (RIP) is one of the most commonly used ] (IGP) ] protocols on internal networks (and to a lesser extent, networks connected to the ]), which helps ]s dynamically adapt to changes of network connections by communicating information about which networks each router can reach and how far away those networks are. Although RIP is still actively used, it is generally considered to have been obsoleted by routing protocols such as ] and ].


The algorithm used in RIP, the ] ], was first deployed in ]'s ] ] protocol suite. Initialy named the Gateway Information Protocol (GWINFO), it was later renamed as the Routing Information Protocol. RIP was later included into the ] (BSD) of the ] operating system as the ] server, and various other vendors would impliment their own versions of the routing server. Eventualy RFC 1058 was issued to unify the various implimentations under a single standard.
The algorithm used in RIP, the ] ], was first deployed in 1969 as part of the ].


RIP is a ], which employs the ''hop count'' as a routing metric. The maximum number of hops allowed with RIP is 15. Each RIP router transmits full updates every 30 seconds by default, generating large amounts of network traffic in lower bandwidth networks. It runs ''above'' the ] of the ], using ] port 520 to carry its data. A mechanism called ] with limited ] is used to avoid routing loops. Routers of some brands also use a ] mechanism known as heuristics, whose usefulness is arguable and is not a part of the standard protocol. RIP is a ], which employs the ''hop count'' as a routing metric. The maximum number of hops allowed with RIP is 15. Each RIP router transmits full updates every 30 seconds by default, generating large amounts of network traffic in lower bandwidth networks. It runs ''above'' the ] of the ], using ] port 520 to carry its data. A mechanism called ] with limited ] is used to avoid routing loops. Routers of some brands also use a ] mechanism known as heuristics, whose usefulness is arguable and is not a part of the standard protocol.

Revision as of 11:17, 29 September 2005

This article is chiefly about the Routing Information Protocol for IPv4 and IPv6.

The Routing Information Protocol (RIP) is one of the most commonly used Interior Gateway Protocol (IGP) routing protocols on internal networks (and to a lesser extent, networks connected to the Internet), which helps routers dynamically adapt to changes of network connections by communicating information about which networks each router can reach and how far away those networks are. Although RIP is still actively used, it is generally considered to have been obsoleted by routing protocols such as OSPF and EIGRP.

The algorithm used in RIP, the Bellman-Ford algorithm, was first deployed in Xerox Parc's PARC Universal Packet intertnetworking protocol suite. Initialy named the Gateway Information Protocol (GWINFO), it was later renamed as the Routing Information Protocol. RIP was later included into the Berkeley Standard Distribution (BSD) of the UNIX operating system as the routed server, and various other vendors would impliment their own versions of the routing server. Eventualy RFC 1058 was issued to unify the various implimentations under a single standard.

RIP is a distance-vector routing protocol, which employs the hop count as a routing metric. The maximum number of hops allowed with RIP is 15. Each RIP router transmits full updates every 30 seconds by default, generating large amounts of network traffic in lower bandwidth networks. It runs above the network layer of the Internet protocol suite, using UDP port 520 to carry its data. A mechanism called split horizon with limited poison reverse is used to avoid routing loops. Routers of some brands also use a holddown mechanism known as heuristics, whose usefulness is arguable and is not a part of the standard protocol.

In many current networking environments RIP would not be the first choice for routing as its convergence times and scalability are poor compared to OSPF or IS-IS, and the hop limit severely limits the size of network it can be used in. On the other hand, it is easier to configure.

Versions

There are three versions of RIP, RIPv1, RIPv2, and RIPng.

RIPv1, defined in RFC 1058, uses classful routing. The routing updates do not carry subnet information, lacking support for variable length subnet masks. 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 be the same size. There is also no support for router authentication, making RIPv1 slightly vulnerable to various attacks.

Due to the above deficiencies of RIPv1, RIPv2 was developed in 1994 and included the ability to carry subnet information, thus supporting Classless Inter-Domain Routing. However to maintain backwards compatibility the 15 hop count limit remained. Rudimentary plain text authentication was added to secure routing updates; later, MD5 authentication was defined in RFC 2082.

RIPv2 is specified in RFC 2453 or STD 56.

RIPng, defined in RFC 2080, is an extension of the original protocol to support IPv6.

See also

Categories: