scispace - formally typeset
Search or ask a question

Ad hoc On-Demand Distance Vector (AODV) Routing

TL;DR: A logging instrument contains a pulsed neutron source and a pair of radiation detectors spaced along the length of the instrument to provide an indication of formation porosity which is substantially independent of the formation salinity.
Abstract: The Ad hoc On-Demand Distance Vector (AODV) routing protocol is intended for use by mobile nodes in an ad hoc network. It offers quick adaptation to dynamic link conditions, low processing and memory overhead, low network utilization, and determines unicast routes to destinations within the ad hoc network. It uses destination sequence numbers to ensure loop freedom at all times (even in the face of anomalous delivery of routing control messages), avoiding problems (such as "counting to infinity") associated with classical distance vector protocols.

Content maybe subject to copyright    Report

Citations
More filters
Patent
15 Apr 2004
TL;DR: A protocol for extending session endpoints in an ad-hoc network environment first performs device discovery to determine local devices within its coverage area and the capability of those devices, then exchange session descriptions with the endpoint device as mentioned in this paper.
Abstract: A protocol for extending session endpoints in an ad-hoc network environment first performs device discovery to determine local devices within its coverage area and the capability of those devices. These local devices then exchange session descriptions with the endpoint device. If the current session may be supported by one of the local devices, the endpoint device, responsive to a command from a user, transfers the session endpoint to the local device and the endpoint device acts as a proxy for the local device in the session. Optionally, if the local device has a path to the correspondent node that is independent of the path through the endpoint device, it establishes the session along this path and then signal the endpoint node to terminate its session.

54 citations

Proceedings ArticleDOI
24 Sep 2007
TL;DR: The results show that ICRP can effectively achieve the goals of energy efficiency and low data delivery delay and is suitable stationary, mobile and hybrid network.
Abstract: In this paper, we tackle one fundamental problem in underwater sensor networks (UASNs), routing. Aiming at many challenges to the routing protocol design of UASNs, which are bought by the features of UASNs, such as low bandwidth, high latency, dynamics topology resulted by node float mobility, high error probability and so on, a novel reactive routing protocol is proposed, called information-carrying based routing protocol (ICRP), to provide energy efficient, real-time and scalable routing. Because the control packet of establishing path is carried by the data packet, the information-carrying mechanism not only is energy efficient, but also results in low end-to-end delivery delay. It does not depend one the location information of nodes. No state information is required on the sensor nodes and only a small fraction of the nodes are involved in routing. Hence, the protocol is also scalable and is suitable stationary, mobile and hybrid network. We evaluate the performance of ICRP through extensive simulations and physical experiments. Our results show that ICRP can effectively achieve the goals of energy efficiency and low data delivery delay.

54 citations

Proceedings ArticleDOI
31 Jul 2006
TL;DR: This paper identifies a new routing attack, called node isolation attack, against optimized link state routing (OLSR) protocol, one of the four standard routing protocols for MANETs.
Abstract: Recent advances in wireless networking technologies have made it possible to construct a mobile ad hoc network (MANET) which can be applied in infrastructureless situations. However, due to their inherent characteristics, they are much more vulnerable to malicious attacks than a conventional wired network. In MANET, routing plays an important role in providing connectivity for mobile nodes who are not within the same radio range. Existing routing protocols in MANET assume a trusted and reliable environment. However, in hostile environment mobile nodes are susceptible to various types of routing attacks. This paper identifies a new routing attack, called node isolation attack, against optimized link state routing (OLSR) protocol, one of the four standard routing protocols for MANETs. We analyze in detail and demonstrate the impact of this attack in order to show the necessity for a countermeasure to guard against the attack. As a first step to defend against the attack, we present a simple technique to detect the attack and identify the source of the attack.

54 citations


Cites methods from "Ad hoc On-Demand Distance Vector (A..."

  • ...At present, the Internet Engineering Task Force (IETF) MANET Working Group has selected four standard routing protocols: Ad hoc On Demand Vector (AODV) protocol [2], Dynamic Source Routing (DSR) protocol [3], Optimized Link State Routing (OLSR) protocol [4], and Topology Broadcast based on…...

    [...]

Journal ArticleDOI
TL;DR: This paper study's how much the scalability is enhanced with the use of Fish eye techniques in addition to the link state routing framework, and shows that with this enhancement, the theoretical scalability bounds are reached.
Abstract: Scalability is one of the toughest challenges in ad hoc networking. Recent work outlines theoretical bounds on how well routing protocols could scale in this environment. However, none of the popular routing solutions really scales to large networks, by coming close enough to these bounds. In this paper, we study the case of link state routing and OLSR, one of the strongest candidates for standardization. We analyze how these bounds are not reached in this case, and we study how much the scalability is enhanced with the use of Fish eye techniques in addition to the link state routing framework. We show that with this enhancement, the theoretical scalability bounds are reached.

54 citations


Cites background from "Ad hoc On-Demand Distance Vector (A..."

  • ...In fact, none of the pop ular ad hoc routing solutions ([4][9][8] etc....

    [...]

01 Nov 2002
TL;DR: The initial design of Milan is described, which combines the separation of the policy for managing the network, defined by the application, from the mechanisms for implementing the policy, which are effected within Milan.
Abstract: Current trends in computing include increases in both distribution and wireless connectivity, leading to highly dynamic, complex environments on top of which applications must be built. The task of designing and ensuring the correctness of applications in these environments is similarly becoming more complex. The unified goal of much of the research in distributed wireless systems is to provide higher level abstractions of complex low-level concepts to application programmers, easing the design and implementation of applications. This is also the goal of the proposed Milan middleware platform, but Milan''s unique feature is its ability to continuously control the network functionality with respect to the application''s changing demands. .pp Applications targeted by Milan are characterized by their ability to adapt to changing sets of available components, and their need to further constrain the active components for application-performance reasons. Physical resources (e.g., transmission distance, bandwidth) and minimum application performance limit the input to certain subsets of available components. It is the job of Milan to identify these feasible sets and determine which set optimizes the tradeoff between application performance and network cost (e.g., energy dissipation). Milan must then configure the network so that components in the selected feasible set are linked to the application. A key feature of Milan is the separation of the policy for managing the network, which is defined by the application, from the mechanisms for implementing the policy, which is effected within Milan. This report describes the initial design of Milan as well as our plans for future research.

54 citations

References
More filters
01 Mar 1997
TL;DR: This document defines these words as they should be interpreted in IETF documents as well as providing guidelines for authors to incorporate this phrase near the beginning of their document.
Abstract: In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. Authors who follow these guidelines should incorporate this phrase near the beginning of their document:

3,501 citations

12 Nov 2001
TL;DR: In this article, a logging instrument contains a pulsed neutron source and a pair of radiation detectors spaced along the length of the instrument to provide an indication of formation porosity which is substantially independent of the formation salinity.
Abstract: A logging instrument contains a pulsed neutron source and a pair of radiation detectors spaced along the length of the instrument. The radiation detectors are gated differently from each other to provide an indication of formation porosity which is substantially independent of the formation salinity. In the preferred embodiment, the electrical signals indicative of radiation detected by the long-spaced detector are gated for almost the entire interval between neutron pulses and the short-spaced signals are gated for a significantly smaller time interval which commences soon after the termination of a given neutron burst. The signals from the two detectors are combined in a ratio circuit for determination of porosity.

574 citations

01 Jan 1998
TL;DR: In this article, the authors discuss issues that should be considered in formulating a policy for assigning values to a name space and provide guidelines to document authors on the specific text that must be included in documents that place demands on the IANA.
Abstract: Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication algorithm for IPSec). To insure that such quantities have consistent values and interpretations in different implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA). In order for the IANA to manage a given name space prudently, it needs guidelines describing the conditions under which new values can be assigned. If the IANA is expected to play a role in the management of a name space, the IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on the IANA.

536 citations

01 Oct 1998
TL;DR: Many protocols make use of identifiers consisting of constants and other well-known values that must be administered by a central authority to insure that such quantities have consistent values and interpretations in different implementations.
Abstract: Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication algorithm for IPSec). To insure that such quantities have consistent values and interpretations in different implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).

334 citations

01 Jun 2004
TL;DR: This document defines terms for mobility related terminology out of work done in the Seamoby Working Group but has broader applicability for terminology used in IETF-wide discourse on technology for mobility and IP networks.
Abstract: There is a need for common definitions of terminology in the work to be done around IP mobility. This document defines terms for mobility related terminology. The document originated out of work done in the Seamoby Working Group but has broader applicability for terminology used in IETF-wide discourse on technology for mobility and IP networks. Other working groups dealing with mobility may want to take advantage of this terminology. This memo provides information for the Internet community.

207 citations


"Ad hoc On-Demand Distance Vector (A..." refers methods in this paper

  • ...This section defines other terminology used with AODV that is not already defined in [3]....

    [...]