Requirements for IP Autoconfiguration Mechanisms in Backbone Wireless Mesh Network scenarios
draft-bernardos-autoconf-backbone-mesh-reqs-01

Document Type Expired Internet-Draft (individual)
Last updated 2008-11-02
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-bernardos-autoconf-backbone-mesh-reqs-01.txt

Abstract

This Internet Draft presents the multi-hop Backbone Wireless Mesh Network scenario, summarising its basic characteristics and describing the requirements and desired properties of an IP Autoconfiguration mechanism aimed at being used in this kind of networks. Once that the AUTOCONF WG has almost finalised the documents that describe the general architecture of MANETs and the IP autoconfiguration problem statement in MANETs, the WG is expected to start working on solutions. This document describes an ad-hoc scenario that is getting a lot of attention from both telecommunication operators and end-users: Backbone/infrastructure Wireless Mesh Networking. This document identifies and explains the requirements posed by this particular scenario to an IP autoconfiguration mechanism. The goal is to help the AUTOCONF WG identify the requirements that need to be taken into account when designing IP autoconfiguration solution(s) suitable for this Wireless Mesh environment.

Authors

Carlos Bernardos (cjbc@it.uc3m.es)
Maria Calderon (maria@it.uc3m.es)
Ignacio Soto (isoto@it.uc3m.es)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)