Intermediate RREP for dynamic MANET On-demand (AODVv2) Routing
draft-perkins-irrep-01
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Authors |
|
Charles Perkins
,
Ian Chakeres
|
|
Last updated |
|
2012-10-22
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Mobile Ad hoc Networks Working Group C. Perkins
Internet-Draft Futurewei
Intended status: Standards Track I. Chakeres
Expires: April 26, 2013 CenGen
October 23, 2012
Intermediate RREP for dynamic MANET On-demand (AODVv2) Routing
draft-perkins-irrep-01
Abstract
The Dynamic MANET On-demand (AODVv2) routing protocol is intended for
use by mobile routers in wireless, multihop networks. AODVv2
determines unicast routes among AODVv2 routers within the network in
an on-demand fashion, offering on-demand convergence in dynamic
topologies. This document specifies an extension to AODVv2 (and
possibly other reactive routing protocols) enabling intermediate
nodes to shorten route discovery times.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 26, 2013.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Perkins & Chakeres Expires April 26, 2013 [Page 1]
Internet-Draft Intermediate RREP October 2012
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Intermediate AODVv2 Router RREP Creation . . . . . . . . . . . 4
4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Perkins & Chakeres Expires April 26, 2013 [Page 2]
Internet-Draft Intermediate RREP October 2012
1. Overview
The Dynamic MANET On-demand (AODVv2) routing protocol enables on-
demand, multihop unicast routing among participating AODVv2 routers.
The basic operations of the AODVv2 protocol are route discovery and
route maintenance. Route discovery is performed by an AODVv2 router
when one of its clients transmits a packet towards a destination for
which the router does not have a route. Route maintenance is
performed to help ensure that the route being used to forward packets
from the source to the destination remains operational.
During route discovery, the originator's AODVv2 router initiates
flooding of a Route Request (RREQ) throughout the network to find a
route to a particular destination, via the AODVv2 router responsible
for this destination. During this hop-by-hop flooding process, each
intermediate AODVv2 router records a route to the originator. If the
intermediate router has a route to the destination requested in the
RREQ, it may by following the specification in this document supply
that routing information to the originator of the RREQ. Such an RREP
message is termed an "Intermediate RREP" (iRREP). The Intermediate
router also forwards another RREP message to the requested
destination, supplying the destination and other intermediate routers
with a route towards the originator of the RREQ. When the
originator's AODVv2 router receives the iRREP, and the destination
receives iRREP for the originator, routes have then been established
Show full document text