1 / 10

MANT Address Autoconfiguration Issues

MANT Address Autoconfiguration Issues. draft-jeong-manet-addr-autoconf-reqts-01.txt draft-jeong-adhoc-ip-addr-autoconf-02.txt draft-jeong-manet-aodv-addr-autoconf-00.txt. Jaehoon Paul Jeong ETRI paul@etri.re.kr http://www.adhoc.6ants.net/~paul/ 2 nd March 2004. Contents.

griffith-newton
Download Presentation

MANT Address Autoconfiguration Issues

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. MANT Address Autoconfiguration Issues draft-jeong-manet-addr-autoconf-reqts-01.txt draft-jeong-adhoc-ip-addr-autoconf-02.txt draft-jeong-manet-aodv-addr-autoconf-00.txt Jaehoon Paul Jeong ETRI paul@etri.re.kr http://www.adhoc.6ants.net/~paul/ 2nd March 2004 IETF-59 MANET WG

  2. Contents • Why is MANET Address Autoconf necessary? • Requirements for MANET Address Autoconf • Procedure of MANET Address Autoconf • MANET Address Autoconf for AODV • Further Work of Our Solution Mechanism • Discussion IETF-59 MANET WG

  3. Why is MANET Address Autoconf necessary? • Four basic MANET unicast routing protocols will be in the status of experimental RFC. • 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 • Active DAD vs. Passive DAD • Prophet Address Allocation • 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-59 MANET WG

  4. 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-59 MANET WG

  5. 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-59 MANET WG

  6. 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? • We need your feedback and suggestion. IETF-59 MANET WG

  7. Procedure of MANET Address Autoconf(draft-jeong-adhoc-ip-addr-autoconf-02.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-59 MANET WG

  8. MANET Address Autoconf for AODV(draft-jeong-manet-aodv-addr-autoconf-00.txt) • Step 1: Address selection • Random Address Selection • Step 2: Duplicate address detection • Hybrid DAD: Strong DAD + Weak DAD • Step 3: Address change negotiation • Address change indication similar to MIP binding update • Step 4: Maintenance of upper-layer sessions • Data delivery through IP tunneling • Address Mapping Cache management is necessary. IETF-59 MANET WG

  9. Further Work of Our Solution Mechanism • Victim Node Selection • Which node should give up its address ? • Consideration of the number of on-going sessions • Consideration of fairness • Maintenance of Upper-layer Sessions • How to avoid the connection breakage even after address change • Address Mapping Cache • Data structure of the cache and how to maintain it • Applicability into each MANET routing protocol • DSR, OLSR and TBRPF IETF-59 MANET WG

  10. Discussion • Will MANET WG accept MANET Address Autoconf as next item? • draft-jeong-manet-addr-autoconf-reqts-01.txt • Suggestion and Question? IETF-59 MANET WG

More Related