The Intrazone Routing Protocol (IARP) for Ad Hoc Networks
draft-ietf-manet-zone-iarp-02
| Document | Type |
Expired Internet-Draft
(manet WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zygmunt Haas , Marc R. Pearlman , Prince Samar | ||
| Last updated | 2023-06-09 (Latest revision 2002-07-05) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Dead WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes the Intrazone Routing Protocol (IARP), a limited scope proactive routing protocol used to improve the performance of existing globally reactive routing protocols. With each node monitoring changes in its surrounding R-hop neighborhood (routing zone), global route discoveries to local destinations can be avoided. When a global route search is needed, the IARP's routing zones can be used to efficiently guide route queries outwards (via bordercasting) rather than blindly relaying queries from neighbor to neighbor. The proactive maintenance of routing zones also helps improve the quality of discovered routes, by making them more robust to changes in network topology. Once routes have been discovered, IARP's routing zone offers enhanced, real-time, route maintenance. Link failures can be bypassed by multiple hop paths within the routing zone. Similarly, suboptimal route segments can be identified and traffic re-routed along shorter paths.
Authors
Zygmunt Haas
Marc R. Pearlman
Prince Samar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)