Talk:Routing Information Protocol

message: 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)
thread_title: ARPANET

message: 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 220.227.114.98 (talk) 09:24, 11 December 2006 (UTC)
replies: text: 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)
thread_title:  convergence time 

message: 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)
thread_title: RIP-2B / RIP-2M

message: is it useful to deactivate RIP function in a single router network? Louis R14 18:18, 5 February 2007 (UTC)
replies: text: 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)
thread_title: question

message: 144.162.97.135 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)
thread_title:  Question from 144.162.97.135 

message: 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
--User talk:R.srinivaas  (talk) 06:09, 1 January 2009 (UTC)
thread_title:  Limitations of RIP 

message: 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 ...'?
78.108.141.145 (talk) 08:37, 4 May 2009 (UTC)
thread_title:  Technical details sentence issue 

message: 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
-- unsigned
http://uni-koblenz.de/~vnuml/docs/rip/Diplomarbeit_TKoch.pdf (german, 2005).
there should be another paper (more like a spec, the above concentrates a bit on performance research): "Andreas J. Schmid. RIP-MTI: Minimum-effort loop-free distance vector routing algorithm. Diplomarbeit, Universität Koblenz-Landau, 1999." but i wasn't able to find this online.
according to the 2005 paper, there should be a rip-mti implementation for quagga. but i wasn't able to find that either. iirc the paper should be sufficient to easily produce a patch, so there is a chance to easily build a working implementation.
i think the title should be "where is rip mti"? i didn't find it in the (english, i.e. this) article - and that's a shame if you ask me...
it should be noted that rip-mti isn't a different protocol. it is used with ripv2, and "just" changes how the routing daemon behaves.
--212.18.18.20 (talk) 12:23, 3 July 2014 (UTC)
thread_title:  What is RIP MTI 

message: 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 208.146.43.6 (talk) 07:05, 27 January 2011 (UTC)
thread_title:  Technical Details should be based on the latest protocol version.  

message: 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)
thread_title:  Discuss links here 

message: 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 165.138.41.45 (talk) 19:46, 20 January 2012 (UTC)
thread_title:  Sentence copied from Cisco? 

message: These "Hold Down" and "Flush Timer" etc, are from Cisco, which has been taken from a link  , and "in that link" that person has made notes to pass in CCNA,CCNP (cisco exams). There are different timers in Actual Standard. (Such as "timeout" and "garbage-collection time") I think those timeouts should be included. Should we include those timers ? Shrivastava Dinesh (talk) 12:59, 9 May 2017 (UTC)
replies: text: whereas Juniper implementation has different definitions  for hold-down ( However, the expired route is retained in the routing table for a specified period so that neighbors can be notified that the route has been dropped. This time period is set by configuring the hold-down timer. Upon expiration of the hold-down timer, the route is removed from the routing table.) Shrivastava Dinesh (talk) 12:59, 9 May 2017 (UTC)
thread_title:  Timers in RIP Standard 

message: RFC2453 states on page 13, that a network direct connected to a router has the metric 1 in that router's routing table:
  https://tools.ietf.org/html/rfc2453#page-13
In this article it says:
"The hop count 0 denotes a network that is directly connected to the router"
can anybody explain those differences?
Dannori (talk) 20:24, 21 October 2019 (UTC)
thread_title:  RIP Metric / Hop count