The problem statement draft-baccelli-autoconf-problem-statement-00 has been submitted as shown here. Now is the time to read it and to provide your comments!

Regards,
Emmanuel

Trying to converge the great work of adp, scenario and framework drafts into one document, please find here an initial version of a proposed problem statement draft:

drat-baccelli-autoconf-statement-00.txt
Notice that this is an initial version, and that there is room for improvement - so comments are more than welcome.

Cheers,

EB.

A permalink to this I-D can be found here: draft-templin-autoconf-dhcp-01.txt

This document specifies a DHCP-based solution for the AUTOCONF
and NETLMM problem spaces. In this solution, a mobile node (MN)
autoconfigures addresses by selecting access routers (ARs) and
informing a mobility anchor point (MAP) of its current AR
location using DHCP. Mobility management is negotiated and
confirmed by the communication between the MN and MAP.
Solutions for both IPv4 and IPv6 are given, and IP version
differences are discussed.

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

Title : Autoconfiguration and Network Localized
Mobility Management using DHCP
Author(s) : F. Templin
Filename : draft-templin-autoconf-netlmm-dhcp-02.txt
Date : 2006-6-21

Mobile nodes that require global Internet access must have a way to
automatically configure globally routable and unique IP addresses
that remain stable across localized mobility events. This document
specifies mechanisms for address autoconfiguration (AUTOCONF) and
network localized mobility management (NETLMM) based on the Dynamic
Host Configuration Protocol (DHCP). Solutions for both IPv4 and IPv6
are given.

A permalink to this I-D is here: draft-templin-autoconf-netlmm-dhcp-02.txt

Title        : Automatic configuration of IPv6 addresses for MANET with multiple gateways (AMG)
Author(s)    : S. Ruffino, P. Stupar
Filename    : draft-ruffino-manet-autoconf-multigw-03.txt
Pages        : 35
Date        : 2006-6-29

This document describes AMG, a mechanism for stateless
autoconfiguration of IPv6 addresses for Mobile Ad-hoc Networks
(MANETs), connected to the Internet by means of one or more gateways.
Network prefixes are disseminated by Internet gateways and are used
by nodes to configure a set of global IPv6 addresses.  An algorithm
is specified, by which nodes can choose the optimal address for data
traffic.  Configured global addresses are also advertised to other

MANET nodes, to minimize latencies in case of gateway failures, MANET
partitions and mergers.  The specified mechanism aims to be
independent from any particular MANET routing protocol and to
effectively exploit multiple gateways.
A permanlink to this I-D is here: draft-ruffino-manet-autoconf-multigw-03.txt

Title        : Address Autoconfiguration for Hybrid Mobile Ad Hoc Networks
Author(s)    : I. Park, et al.
Filename    : draft-ikpark-autoconf-haa-01.txt
Pages        : 18
Date        : 2006-6-27

Most of current address autoconfiguration mechanisms for MANET
introduce significant load like message flooding, or are dependent on
the underlying routing protocols. This document proposes a new
mechanism that is intended to minimize these drawbacks.  It is also
designed to be applicable for hybrid MANET, where a MANET is
connected to Internet through one or more Interet gateways.
A permanent link to this I-D is here: draft-ikpark-autoconf-haa-01.txt

A permalink to this I-D is included here:  draft-weniger-autoconf-pdad-olsr-01.txt

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 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 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. A node, that detects duplicate address between other nodes, should advertise the detected duplicate address to all other nodes In the MANET. This is termed “MANET duplicate address advertisement” (MANET-DAA). The specific MANET-DAD and MANET-DAA algorithm is beyond the scope of this document.

The abstract is below:

Mobile Ad-hoc Networks (MANETs) comprise MANET routers and their attached devices, and connect to the global Internet via one or more MANET gateways. MANET routers that require global Internet access must have a way to automatically configure globally routable and unique IP addresses/prefixes. This document specifies mechanisms for MANET address autoconfiguration (AUTOCONF) based on the Dynamic Host Configuration Protocol (DHCP). Solutions for both IPv4 and IPv6 are given.