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 Hello, MANET members! Welcome to Korea. My name is Jungsoo Park. I will talk about MANET Address Autoconfiguration Issues. IETF-60 MANET WG

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. Four basic MANET unicast routing protocols have been in the status of experimental RFC. AODV, DSR, OLSR and TBRPF What is the 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. 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

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. The first scenario is about Join and Departure of Mobile Nodes IETF-60 MANET WG

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. The second scenario is about Network Partitioning and Merging IETF-60 MANET WG

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. The last scenario is about Internet Connectivity. There may be other scenarios including IPv6 considerations. We need your feedback and suggestion. IETF-60 MANET WG

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 From now, I will suggest a framework for MANET Address Autoconf. This draft was presented at IETF fifty seventh meeting. The mechanism consists of four steps: Step 1 is Address Selection. Step 2 is Duplicate Address Detection. Step 3 is Address Change Negotiation. Step 4 is Maintenance of Upper-layer Sessions. This draft suggests an example of MANET Address Autoconf and can be used to develop our MANET Address Autoconf Requirements draft. IETF-60 MANET WG

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? Will MANET WG accept MANET address autoconf requirements as a new WG item? If so, I would like to ask MANET WG to adopt our requirements draft as a working group document. This work will make MANET WG’s new objective more concrete. Is there any suggestion and question? IETF-60 MANET WG