1 / 10

MANET Autoconf Problem Statement July 12 th 2006

MANET Autoconf Problem Statement July 12 th 2006. Status. Problem Statement : converging the ADP, Framework and Scenario drafts into one single doc. Initial document ready . http://manetautoconf.online.fr/Blog/ towards a 00 draft 17 or 18 July. Comments are thus very welcomed .

kisha
Télécharger la présentation

MANET Autoconf Problem Statement July 12 th 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MANET Autoconf Problem Statement July 12th 2006

  2. Status • Problem Statement: converging the ADP, Framework and Scenario drafts into one single doc. • Initial document ready. • http://manetautoconf.online.fr/Blog/ • towards a 00 draft 17 or 18 July. • Comments are thus very welcomed 

  3. Contents

  4. Constraints • Wireless interfaces : different characteristics • Pseudo-broadcast: prefix-per-link to re-evaluate • Dynamic topology: MANET partitionning, merging • Relying on peers for autoconf: new security concerns • (ref. Architecture doc.)

  5. Considered Scenarios • Mobile ad hoc network w.r.t. the IP infrastructure: • Disconnected (i.e. Standalone MANET) • Connected with one gateway (i.e. Stub MANET) • Connected with multiple gateways (i.e. Multi-homed MANET) (Gateways may be themselves mobile)

  6. Framework

  7. Framework • Mechanisms needed for transitions between states: • To generate tentative addresses • To ensure “reasonable belief” in their uniqueness • To detect incorrect or conflicting addresses • To resolve address conflicts

  8. Goals and Requirements • Goals: provide solutions for the needed mechanisms • Requirements: convergence time, overhead w.r.t. network size • Security considerations: need a threat model

  9. Where are we at ? Initial version done Being developped in parallel with the architecture draft ? To de done

  10. Links to check out • http://manetautoconf.online.fr/Blog/ • http://www.lix.polytechnique.fr/hipercom/Hipertracker

More Related