Transcript PPT Version
Requirements for Ad Hoc IP
Address Autoconfiguration
draft-jeong-manet-addr-autoconf-reqts-02.txt
Jungsoo Park & Jaehoon Paul Jeong
ETRI
{pjs, paul}@etri.re.kr
http://www.adhoc.6ants.net
2nd August 2004
IETF-60 MANET WG
1
Why is MANET Address Autoconf necessary?
• Four basic MANET unicast routing protocols have been experimental RFCs.
– AODV, DSR, OLSR and TBRPF
• Next Step of MANET WG?
– Addressing is one of the most essential requirements in IP networking.
• Automatic IP address configuration is necessary in MANET experiencing
dynamic topology changes.
– Various approaches have been suggested in the research domain
• Stateless vs. Stateful approaches
• Strong DAD vs. Weak DAD
– MANET WG has already included MANET Address Autoconf in its
Charter.
• Therefore, it is time to develop MANET IP Address Auto-configuration
from Engineering Philosophy.
– First of all, MANET WG should define the requirements for MANET
Address Autoconf.
IETF-60 MANET WG
2
Requirements for MANET Address Autoconf
(draft-jeong-manet-addr-autoconf-reqts-01.txt) - 1/3
• Join and Departure of Mobile Nodes
[R1] Address autoconf protocol MUST support timely
autoconfiguration of IP address for a mobile node.
[R2] Address autoconf protocol MAY support mechanisms to
probe whether a mobile node moves into another MANET.
[R3] Mobile nodes using address autoconf protocol MUST
validate allocated IP addresses when powering up or
rebooting.
[R4] Mobile nodes using address autoconf protocol MAY
validate allocated IP addresses when moving into a new
network.
IETF-60 MANET WG
3
Requirements for MANET Address Autoconf
(draft-jeong-manet-addr-autoconf-reqts-01.txt) - 2/3
• Network Partitioning and Merging
[R5] Ad hoc address autoconf protocol MUST detect and
resolve address conflicts in a timely manner and on an
ongoing basis.
[R6] Ad hoc address autoconf protocol MUST allow conflicted
address replaced with another.
[R7] Ad hoc address autoconf protocol SHOULD minimize the
damage, such as loss of delivered packets, due to address
replacement.
[R8] Addresses SHOULD be allocated or autoconfigured in a
way that minimizes the probability that two or more nodes
will have the same address.
[R9] In order to detect duplicate addresses, ad hoc address
autoconf protocol MAY get the aid of ad hoc routing protocol.
IETF-60 MANET WG
4
Requirements for MANET Address Autoconf
(draft-jeong-manet-addr-autoconf-reqts-01.txt) - 3/3
• Internet Connectivity
[R10] MANET SHOULD allow configuration of zero or more
gateways for the global connectivity to the Internet.
[R11] Mobile Node that desires Internet connectivity MAY have
a globally routable IP address.
• Other Scenarios?
– IPv6 Considerations
– We need your feedback and suggestion.
IETF-60 MANET WG
5
Procedure of MANET Address Autoconf
(draft-jeong-adhoc-ip-addr-autoconf-03.txt), discussed at IETF-57
• Step 1: Address Selection
– How to select one of IP addresses in the address space.
• Step 2: Duplicate Address Detection
– How to detect a duplicate address
• Step 3: Address Change Negotiation
– Which node should perform a reallocation procedure
• Step 4: Maintenance of Upper-layer Sessions
– How to let an upper-layer session avoid a connection breakage
IETF-60 MANET WG
6
Discussion
• Will MANET WG accept MANET Address
Autoconf Requirements as a new WG item?
– draft-jeong-manet-addr-autoconf-reqts-02.txt
– This work will make MANET WG’s new objective more
concrete.
• Suggestion and Question?
IETF-60 MANET WG
7