Skip to main content

IP Addressing Model in Ad Hoc Networks

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: Internet Architecture Board <>,
    RFC Editor <>, 
    autoconf mailing list <>, 
    autoconf chair <>
Subject: Document Action: 'IP Addressing Model in Ad Hoc Networks' to Informational RFC

The IESG has approved the following document:

- 'IP Addressing Model in Ad Hoc Networks '
   <draft-ietf-autoconf-adhoc-addr-model-03.txt> as an Informational RFC

This document is the product of the Ad-Hoc Network Autoconfiguration Working Group. 

The IESG contact persons are Jari Arkko and Ralph Droms.

A URL of this Internet-Draft is:

Ballot Text

Technical Summary

   This document describes a model for configuring IP addresses and
   subnet prefixes on the interfaces of routers which connect to links
   with undetermined connectivity properties. While the considerations
   in this document are general, they are specifically written with the
   most stringent requirements of MANETs in mind; essentially, a router
   configured according to the principles set forth in this document
   will be able to support operation of a MANET routing protocol.

Working Group Summary

   Variations of this document have been in the working group process
   for four years. Earlier incarnations attempted to specify much more
   than this document does. In 2009, the working group was rechartered
   to focus on documenting *a* workable address configuration model,
   as opposed to attempting to describe all possible theoretical models.
   The model described in this document is the one most widely used
   by networks that employ ad hoc routing techniques.

   The recommendation in the document to not use
   Link Local addresses for operation over interfaces towards links with
   undetermined connectivity properties was not unanimous, and on this
   point, consensus was rough.

Document Quality

   While the document does not specify a protocol, there are about a
   decade of experience with running MANETs in which routers have
   their interfaces configured according to the recommendations in this


   Ryuji Wakikawa is the Document Shepherd, and Jari Arkko is
   the responsible Area Director.

RFC Editor Note