Transcript PPT Version

MANET Autoconf
Problem Statement
July 12th 2006
Autoconf Problem
Statement
1
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 
Autoconf Problem
Statement
2
Contents
Autoconf Problem
Statement
3
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.)
Autoconf Problem
Statement
4
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)
Autoconf Problem
Statement
5
Framework
Autoconf Problem
Statement
6
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
Autoconf Problem
Statement
7
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
Autoconf Problem
Statement
8
Where are we at
?
?
Initial version done
Being developped in parallel with the architecture draft
To de done
Autoconf Problem
Statement
9
Links to check out
●
●
http://manetautoconf.online.fr/Blog/
http://www.lix.polytechnique.fr/hipercom/Hipertrack
er
Autoconf Problem
Statement
10