[rfc-dist] RFC 4728 on The Dynamic Source Routing Protocol (DSR) for Mobile Ad Hoc Networks for IPv4
rfc-editor at rfc-editor.org
Thu Feb 8 17:47:43 PST 2007
A new Request for Comments is now available in online RFC libraries.
Title: The Dynamic Source Routing Protocol
(DSR) for Mobile Ad Hoc Networks
Author: D. Johnson, Y. Hu,
Date: February 2007
Mailbox: dbj at cs.rice.edu,
yihchun at uiuc.edu,
dmaltz at cs.cmu.edu
I-D Tag: draft-ietf-manet-dsr-10.txt
The Dynamic Source Routing protocol (DSR) is a simple and efficient
routing protocol designed specifically for use in multi-hop wireless
ad hoc networks of mobile nodes. DSR allows the network to be
completely self-organizing and self-configuring, without the need for
any existing network infrastructure or administration. The protocol
is composed of the two main mechanisms of "Route Discovery" and
"Route Maintenance", which work together to allow nodes to discover
and maintain routes to arbitrary destinations in the ad hoc network.
All aspects of the protocol operate entirely on demand, allowing
the routing packet overhead of DSR to scale automatically to only
what is needed to react to changes in the routes currently in use. The
protocol allows multiple routes to any destination and allows each
sender to select and control the routes used in routing its packets,
for example, for use in load balancing or for increased robustness.
Other advantages of the DSR protocol include easily guaranteed
loop-free routing, operation in networks containing unidirectional
links, use of only "soft state" in routing, and very rapid recovery
when routes in the network change. The DSR protocol is designed
mainly for mobile ad hoc networks of up to about two hundred nodes
and is designed to work well even with very high rates of mobility.
This document specifies the operation of the DSR protocol for routing
unicast IPv4 packets. This memo defines an Experimental Protocol for the
This document is a product of the Mobile Ad-hoc Networks
Working Group of the IETF.
EXPERIMENTAL: 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
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist