MANET Autoconf WG Blog

This document specifies one method for autoconfiguration for the Optimized Link State Routing (OLSR) protocol for stand-alone ad hoc networks.  OLSR is a routing protocol for mobile ad hoc networks, designed for use in multi-hop wireless ad hoc networks ; and as such it specifies how individual nodes can construct routes to each other. To achieve this, it relies on preliminary assignment of unique IP addresses to OLSR interfaces ; hence the task of generating addresses, checking their uniqueness and assigning them to interfaces is defined externally.  This document proposes a complementary method, called “No Overhead Autoconfiguration for OLSR” (NOA-OLSR), to perform this task of ensuring uniqueness of addresses which have been generated.  It also performs to ensure uniqueness of addresses which have been assigned and used when network merger occurs.  This method consists of modifications in the OLSR specification.
A permalink to this I-D is here:  draft-mase-manet-autoconf-noaolsr-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title : A common framework for autoconfiguration of stand-alone ad hoc networks
Author(s) : K. Mase, et al.
Filename : draft-mase-autoconf-framework-01.txt
Pages : 21
Date : 2006-2-9

We consider the unique local address autoconfiguration problem for
stand-alone ad hoc networks (MANETs). Specifically, we consider two
cases. First, a node without a pre-assigned and valid local address
acquires a new local address and becomes a member of a new or
existing MANET. Second, two or more MANETs merge. In the first
case, a mechanism of IP address generation based on a stateful or
stateless method is needed. We also should have MANET-wide duplicate
address detection (MANET-DAD) on newly generated address (tentative
address) for suppressing occurrence of duplicate addresses regardless
of whether stateful or stateless method is employed for address
generation (pre-service MANET-DAD). In the second case, duplicate
address may occur as the result of a merger of two formerly
independent networks. We should have MANET-DAD on addresses in use
for resolving duplicate addresses and suppressing routing information
contamination due to existence of duplicate addresses (in-service
MANET-DAD). To realize pre-service MANET-DAD and in-service MANET-
DAD, we define autoconfiguration states that are common for both
proactive and reactive routing protocol. Each node exists in one of
the autoconfiguration states at any time. The specific MANET-DAD
algorithm is beyond the scope of this document.

A permanent link to this specification is available here: draft-mase-autoconf-framework-01.txt