MANET Autoconf WG Blog

Hi all,

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

Folks,

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.

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 autoconfiguration (AUTOCONF) based on the Dynamic Host

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

Fred Templin adds to the “official” announcement:

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

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

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

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

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

This draft proposes PDAD-OLSR, a solution for configured address uniqueness maintenance in MANETs running the OLSR protocol.  It utilizes the Passive Duplicate Address Detection (PDAD) concept, which enables nodes to passively detect duplicate addresses in the network (e.g., occurring after network merging) by analyzing received routing protocol messages.  Due to its passive nature, PDAD-OLSR is very efficient in terms of bandwidth consumption.  Moreover, it can prevent the contamination of routing tables with wrong routing information resulting from address conflicts.

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

Kenichi Mase has published a new version of the framework document: draft-mase-autoconf-framework-02.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.

Fred Templin has submitted this draft: draft-templin-autoconf-dhcp-00.txt

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.

Kenichi Mase has submitted the following document, with this message:

An Internet draft entitled “Gateway Aggregation Protocol (GAP) for Mobile Ad Hoc Networks” has been submitted. Comments are welcome.

A permalink to this I-D is here: draft-mase-autoconf-gap-00.txt

This document defines how Unique Local IPv6 Unicast Addresses (RFC-4193) can be used in wireless mobile ad hoc networks (MANETs) as MANET Local IPv6 Addresses (MLAs).  MLAs are intended to be used inside a MANET and are not expected to be routable on the global Internet.  Each MANET node is expected to generate its MLA locally without any coordination with other MANET nodes.

Here’s a permalink to this I-D: draft-jelger-autoconf-mla-00.txt

Just a quick note from the AUTOCONF meeting. Dave gave a presentation of this draft: draft-thaler-intarea-multilink-subnet-issues-00.txt at the INTAREA meeting. This draft may be highly relevant to the AUTOCONF work, so I thought I’d include it here.

Also, check the presentation slides for his presentation at the INTAREA meeting in Dallas — I think they should come on-line?

Title : IPv6 Support on Mobile Ad-hoc Network
Author(s) : R. Wakikawa, et al.
Filename : draft-wakikawa-manet-ipv6-support-02.txt
Pages : 13
Date : 2006-3-13

This draft defines the IPv6 addressing architecture for Mobile Ad-hoc
Network. This document includes problem statements when manet using
IPv6, IPv6 addressing model, IPv6 manet node’s required addresses.
Note that this document does not discuss how an IPv6 address is
allocated to each manet node.
A non-expireing URL for this Internet-Draft is: draft-wakikawa-manet-ipv6-support-02.txt

New version of global6. Unfortunately I cannot attend the AUTOCONF WG meeting @ Dallas

draft-wakikawa-manet-globalv6-05.txt

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

Title : Extensible MANET Auto-configuration Protocol (EMAP)
Author(s) : P. Ruiz, F. Ros
Filename : draft-ros-autoconf-emap-02.txt
Pages : 27
Date : 2006-3-7

Mobile Ad Hoc Networks need an auto-configuration protocol being able
to satisfy their self-deployment requirements while remaining
flexible enough to accommodate special features for different
devices.

The Extensible Manet Auto-configuration Protocol (EMAP) tries to
fullfil these requirements both for IPv4 and IPv6 mobile ad hoc
networks. It provides auto-configuration mechanisms for isolated as
well as hybrid MANETs, and is envisioned to be integrated within
unicast routing protocols (like DYMO [1] or OLSRv2 [2]).

EMAP allows nodes to create a (highly likely) unique IP address which
can be used locally inside the MANET. In a similar way, nodes can
auto-configure globally routable IP addresses when one (or more)
gateways to the Internet are present in the network. The general
framework provided by the protocol may be used as a service discovery
protocol for MANETs. As an example, this document also specifies an
optional feature which consists on the discovery of DNS servers
reachable from the MANET. However, the approach is extensible to
other services like SIP proxies, authentication entities, etc.
Therefore, EMAP has been designed taking into consideration the
possibility of extending it later on with new features, uses, and
optimizations.

A permanent link to the draft can be found here: draft-ros-autoconf-emap-02.txt

A new Internet-Draft has been submitted for publication.

Title : Address autoconfiguration for MANETs: definition and problem statement
Filename : draft-singh-autoconf-adp-03
A Mobile Ad Hoc NETwork (MANET) is formed by the association of mobile devices, usually wireless and capable of multi-hop communication among themselves even if there is no networking infrastructure available.  MANET properties such as multi-hop, autonomous, etc requires separate address autoconfiguration mechanism.  This document provides definition, problem statement and goals for ad hoc networks address autoconfiguration.

A non-expiring link to the draft can be found here: draft-singh-autoconf-adp-03

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

Title : Multihop Radio Access Network (MRAN) Protocol Specification
Author(s) : P. Hofmann
Filename : draft-hofmann-autoconf-mran-00.txt
Pages : 22
Date : 2006-3-2

This document presents an IPv6-based protocol for the interconnection
of ad hoc networks and the Internet. The protocol enables mobile
nodes in ad hoc networks to communicate with correspondent nodes in
the Internet.

A non-expiring link to the draft can be found here: draft-hofmann-autoconf-mran-00.txt

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

Title : Connectivity Scenarios for MANET

Author(s) : S. Ruffino, et al.
Filename : draft-ruffino-autoconf-conn-scenarios-00.txt
Pages : 18
Date : 2006-2-24

This Internet Draft aims at describing a wide spread set of possible
connectivity scenarios involving mobile ad-hoc networks, in order to
provide a reference for the AUTOCONF Working Group. The aspects
considered for definition and classification of the scenarios are
number and characteristics of the gateways that connect MANET nodes
to external networks. Analysis will range from a scenario where no
connectivity is provided, i.e. an isolated MANET, to more complex
scenario where a MANET has multiple mobile gateways.

A non-expiring link to the draft can be found here: draft-ruffino-autoconf-conn-scenarios-00.txt

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

Title : Multi-Subnet MANETs
Author(s) : D. Thaler
Filename : draft-thaler-autoconf-multisubnet-manets-00.txt
Pages :
Date : 2006-2-28

This document describes an approach to addressing nodes in Mobile
Ad-hoc Networks (MANETs) which involves assigning a separate subnet
to each MANET router. This approach avoids many of the problems
that arise in other approaches, and is intended to allow existing
protocols and applications to work unmodified.

A non-expiring link to the draft can be found here: draft-thaler-autoconf-multisubnet-manets-00.txt

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

Title : Address Autoconfiguration for Hybrid Mobile Ad Hoc Networks
Author(s) : I. Park, et al.
Filename : draft-ikpark-autoconf-haa-00.txt
Pages : 17
Date : 2006-3-1

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 non-expiring link to the draft can be found here: draft-ikpark-autoconf-haa-00.txt

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

This document specifies the steps which a mobile node in the ad hoc network takes in deciding how to autoconfigure its IPv4 or IPv6 address in its network interface.  Because the ad hoc IP address autoconfiguration in this document considers the ad hoc network’s partition and mergence, the address duplication caused by the ad hoc network’s mergence can be resolved through an address resolution protocol.  Also, this document specifies how to resolve the address duplication in order to guarantee the maintenance of upper-layer sessions, such as TCP session.
A permalink to this I-D is here:  draft-jeong-adhoc-ip-addr-autoconf-06.txt

Title : Survey of IP address autoconfiguration mechanisms for MANETs
Author(s) : C. Bernardos, M. Calderon
Filename : draft-bernardos-manet-autoconf-survey-00.txt
Pages : 25
Date : 2005-07-13

This Internet Draft aims at describing some of the already proposed
mechanisms for the autoconfiguration of IP addresses in MANET
networks, trying to provide a useful reference in the standardisation
process. Solutions proposed in research papers and submitted as I-Ds
are presented and classified by a simple criteria. The analysis of
the solutions includes a brief description of the mechanism and also
a summary of the key characteristics.

A non-expiring link to the draft can be found here: draft-bernardos-manet-autoconf-survey-00.txt