Talk:Routing Information Protocol
- 1 ARPANET
- 2 "above the network layer" ???
- 3 convergence time
- 4 RIP-2B / RIP-2M
- 5 question
- 6 Question from 184.108.40.206
- 7 Limitations of RIP
- 8 Technical details sentence issue
- 9 What is RIP MTI
- 10 Technical Details should be based on the latest protocol version.
- 11 Discuss links here
- 12 Sentence copied from Cisco?
I didn't add the mention of the ARPANET, merely corrected] the erroneous reference that was already there, from "RIP was first developed in 1969 as part of ARPANET" to "The algorithm used in RIP, the Bellman-Ford algorithm, was first deployed in 1969 as part of the ARPANET." Noel (talk) 01:06, 1 October 2005 (UTC)
Could a list of entry level Products which support RIP be added, so others can learn by 'doing'?
"above the network layer" ???
<SSPecteR> I really didn't liked this phrase: "It runs above the network layer of the Internet protocol suite, using UDP port 520 to carry its data." Isn't it from the network layer? What does it mean as "above"? application layer? Heaven? Please, someone specify it. ♠ Saturday, 2006-06-10, 06:23 (UTC)
- It is a layer management protocol for the network layer, and thus a network layer protocol even though it runs over UDP (Port 520).Hcberkowitz 20:01, 23 June 2007 (UTC)
- I have to disagree here, it's not implimented in the base stack, can be interchanged with any number of other protocols, and is dependant directly on the transport control layer, thus it's an application layer protocol. (In that it is implimented at that layer.)
- Sorry, but this is not true architecturally either from the full OSI (i.e., beyond seven simple layers) or the IETF perspectives. If you are going to cite OSI layering, then please consider the Management Annex (ISO 7498/4) to the basic OSI Reference Model, and the OSI Routeing Framework. Additional ISO work on the user, control, and management planes, under the ATM architectural work, made very clear that there are parallel stacks, not a "base stack". Routing protocols are in a parallel management stack. OSI routing and management documents are quite explicit that it is the nature of the payload, not the means of encapsulation, that determines what protocol is being managed. As you point out, basic ISIS does not run over a network layer protocol, but its total purpose is a set of functions invisible to the end user, or what I assume you mean by "base stack."
- Since RIP, in any event, is not used in any OSI stack, how it is characterized by a simplified version of OSI architecture is irrelevant. The authoritative reference is IETF, and the Routing Area of the IETF, with responsibility for all IP-related routing protocols, simply does not use the OSI terminology. I challenge you to find one standards-track RFC that puts a routing protocol into the application layer. SNMP is an application-layer management protocol that does affect routing, but it does not exchange information about routes (e.g., network layer reachability information).Howard C. Berkowitz 14:11, 8 August 2007 (UTC)
It manages a lower layer, so it does have to reach back down, but all routing protocols have to do this and many are not listed as network layer ptotocols. (At least one, IS-IS, doesn't use IP for their own communications at all.)
- 220.127.116.11 13:29, 8 August 2007 (UTC)
I dont see why one says that convergence time is bad in RIP As long as prefixes are not "withdrawn", RIP works just as well as say BGP. The metric /hops is a good discriminator to choose the correct path. the older versions of RIP had something similar to Origin identifier at a time, which was used to cut out loops —The preceding unsigned comment was added by 18.104.22.168 (talk) 09:24, 11 December 2006 (UTC).
- In real networks, prefixes are frequently withdrawn, as routers or links go down. One of the main reasons to have a routing protocol is to facilitate failover, and RIP, depending on timer settings, can take 90-180 seconds to declare a route down and reconverge. With timer tuning, modern OSPF implementations can reconverge sometimes in less than a second, and often in low seconds. Hcberkowitz 20:00, 23 June 2007 (UTC)
RIP-2B / RIP-2M
my router has these two options but the instruction manual is not that detailed. does anyone know what are the differences? it should be mentionned in the article too. Louis R14 18:16, 5 February 2007 (UTC)
They're probably RIPv2 over broadcast and RIPv2 over multicast. Use multicast if your network is fully RIPv2, broadcast if you still have RIPv1 routers. Jec 00:47, 6 July 2007 (UTC)
is it useful to deactivate RIP function in a single router network? Louis R14 18:18, 5 February 2007 (UTC)
- Not always, if the hosts passively listen for RIP updates to learn the address of the default router. This is common with UNIX hosts, especially which run the routeD package in passive mode.Hcberkowitz 20:01, 23 June 2007 (UTC)
Question from 22.214.171.124
126.96.36.199 asks (via a question inserted into the article that I've just removed) whether RIP is dynamic or static. --Northernhenge (talk) 16:28, 8 November 2008 (UTC) RIP is dynamic--[[User talk:R.srinivaas ]] (talk) 06:08, 1 January 2009 (UTC)
Limitations of RIP
can i introduce a new section in this article ?
There are several disadvantages of using RIP,
1) Hop count can not exceed 15, in case if it exceeds it will be considered invalid 2) Mostly RIP networks are flat , there are no concepts of areas or boundaries in networks 3) Variable Length Subnet Masks is not supported by RIP 1, which is considered as a flaw 4) RIP has slow convergence or count to infinity problem 5) RIP does not have mechanism to detect Routing Loops
Technical details sentence issue
Near the end of the 'technical details' there is a sentence which doesn't sound right, but I'm not sure how to fix it: 'RIP is a UDP-base breaks the often defended encapsulation hierarchy of OSI.' Maybe it should be 'RIP is a UDP-based protocol and breaks ...'?
What is RIP MTI
Can somebody clarify which RFC specifies RIP MTI
This is nothing the one type of feature which is used to prevent loop back or propogate to wested network. and to speedup the convergence
Technical Details should be based on the latest protocol version.
Is it within the realm of this discussion to modify the RIP Techical details to use the latest up to date information for RIPv2 as the basis for information, and not the original protocol values?
Stating that RIP uses a hop count of 15 in the summary, while correct for RIPv1, it is not correct for today's use. The majority of RIP users will be using the latest version in the devices they purchase. (ripv2) —Preceding unsigned comment added by 188.8.131.52 (talk) 07:05, 27 January 2011 (UTC)
Editors regularly clean out undiscussed links from this article. Please discuss here if you want a link not to be cleaned out regularly. (You can help!) — UncleBubba ( T @ C ) 03:49, 9 December 2011 (UTC)
Sentence copied from Cisco?
Now, I know there are only so many ways to word it, but the first sentence
The Routing Information Protocol (RIP) is a distance-vector routing protocol, which employs the hop count as a routing metric.
I suspiciously similar to the first sentence on Cisco's page
The Routing Information Protocol (RIP) is a distance-vector protocol that uses hop count as its metric. — Preceding unsigned comment added by 184.108.40.206 (talk) 19:46, 20 January 2012 (UTC)