2004
DOI: 10.17487/rfc3684
|View full text |Cite
|
Sign up to set email alerts
|

Topology Dissemination Based on Reverse-Path Forwarding (TBRPF)

Abstract: Status of this Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
230
0
5

Year Published

2005
2005
2010
2010

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 426 publications
(235 citation statements)
references
References 16 publications
0
230
0
5
Order By: Relevance
“…However, due to the random and continuous mobility of the network's nodes, such a protocol must periodically perform inspection process using control packets, which presses a continuous overhead on the network bandwidth [7][8][9]. We can easily notice that any sudden increase in the nodes-mobility can cause more frequent need of network topology inspection and thus an extensive amount of overhead [10][11][12]. This problem becomes even worse with the increase of the network size (i.e., nodes-density and network coverage area size), since a huge amount of information will need to be constantly and frequently inspected.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…However, due to the random and continuous mobility of the network's nodes, such a protocol must periodically perform inspection process using control packets, which presses a continuous overhead on the network bandwidth [7][8][9]. We can easily notice that any sudden increase in the nodes-mobility can cause more frequent need of network topology inspection and thus an extensive amount of overhead [10][11][12]. This problem becomes even worse with the increase of the network size (i.e., nodes-density and network coverage area size), since a huge amount of information will need to be constantly and frequently inspected.…”
Section: Related Workmentioning
confidence: 99%
“…Deterministic protocols require instant network topology information to construct and maintain the routes [4][5][6]. Due to the dynamic changes of network topology in MANETs, however, such a protocol must constantly acquire new information to exactly reflect the network topology up to date, which will trigger a high overhead (especially in presence of high mobility and large number of nodes) and significantly limit its practicability [7][8][9][10][11][12]. Therefore, the available deterministic protocols can carry out the routing process only under a group of restricted constraints on the network coverage area size, nodes-density or mobility.…”
Section: Introductionmentioning
confidence: 99%
“…Several major features of OLIVE address many important shortcomings of the on-demand routing protocols (DSR [1], AODV [2]) and proactive routing protocols (TBRPF [7], OLSR [8]) that have been proposed for standardization in the IETF working group on mobile ad hoc networks (MANET). Here, we describe some of those features and try to explain whether we can achieve those with the existing routing protocols.…”
Section: G Critique Of Olive With Respect To Other Routing Protocolsmentioning
confidence: 99%
“…We have compared the performance of OLIVE with the on-demand routing protocols (DSR [1], AODV [2]) and proactive routing protocols (TBRPF [7], OLSR [8]) that have been proposed for standardization in the IETF working group on mobile ad hoc networks (MANET). The performance evaluation has been done in the ns2 simulation platform [9], using the code of DSR, AODV, and TBRPF provided with the simulator.…”
Section: Performance Comparisonmentioning
confidence: 99%
See 1 more Smart Citation