Ad-Hoc Network Autoconfiguration BOF (autoconf) xxxxxxxx, November x at xxxx-xxxx ================================= CHAIRS: Shubhranshu Singh Thomas Clausen DESCRIPTION: In order to communicate among themselves, ad hoc nodes (refer to RFC 2501) need to configure their network interface(s) with local addresses that are valid within an ad hoc network. Ad hoc nodes may also need to configure globally routable addresses, in order to communicate with devices on the Internet. From the IP layer perspective, ad hoc networks present several challenges. Unlike in the traditional IP networks, each ad hoc node, besides being a traffic end-point, should be capable of forwarding traffic destined for other hosts. Additionally, nodes constituting an ad hoc network do not share access to a single multicast-capable link for signaling. Many protocol specifications used in the traditional IP networks e.g. RFCs 2462, 2461 etc. do, however, assume that subnet-local signals (e.g. link-local multicast signal) are received by each of the hosts on the particular subnet without being forwarded by the routers defining the subnet boundary. Hence ad hoc networks (as defined and understood by the IETF MANET WG), supporting at least one routing protocol at the network layer in order to provide multi-hop communication, cannot use these protocol specifications as-is. The main purpose of the AUTOCONF WG is to standardize mechanisms to be used by ad hoc nodes for configuring unique local and/or globally routable IPv6 addresses. The ad hoc nodes under consideration are, once configured, expected to be able to support multi-hop communication by running the MANET routing protocol developed by the IETF MANET WG. An AUTOCONF mechanism should not be dependent on any specific MANET routing protocol, however the routing protocol may provide for optimizations. With this in mind, the goals of AUTOCONF WG are to: - Produce a "terminology and problem statement" document, defining the problem statement and goals for AUTOCONF. - Develop an IPv6 address autoconfiguration mechanism to be used by ad hoc nodes for configuring unique local addresses as well as, in cases where Internet connectivity exists, globally routable unique addresses. - Develop a DHCPv6 based address configuration mechanism to be used by ad hoc nodes for configuring globally routable unique addresses, if an address providing entity such as DHCPv6 server is available. - Develop a mechanism to promote configured address uniqueness in the situation where different ad hoc networks merge. Issues and requirements related to prefix and/or address providing entities, such as an Internet gateway, will be addressed within the group to the extent that they are directly related to the AUTOCONF mechanisms. Security concerns related to AUTOCONF mechanisms will also be discussed within the group. The working group will reuse existing specifications whenever reasonable and possible. Goals and Milestones: Oct 05 : Submit "terminology and problem statement" document for WG review Oct 05: Submit initial I-D(s) of candidate proposed AUTOCONF mechanisms and design frameworks Feb 06: Submit "terminology and problem statement" document to IESG for publication as an informational RFC Apr 06: Submit initial I-D of "IPv6 address autoconfiguration mechanism" for WG review Apr 06: Submit initial I-D of "DHCPv6 based address configuration mechanism" for WG review Apr 06: Submit initial -ID of "configured address uniqueness maintenance" for WG review Aug 06: Revise WG documents and review Dec 06 Revise documents based upon implementation experience Apr 07: Submit "IPv6 address autoconfiguration mechanism" specification and supporting documentation to IESG for publications as Proposed Standard Apr 07: Submit "DHCPv6 based address configuration mechanism" specification and supporting documentation to IESG for publications as Proposed Standard Apr 07: Submit "configured address uniqueness maintenance" specification and supporting documentation to IESG for publications as Proposed Standard Oct 07: Close or recharter the WG AGENDA: Agenda bashing :05 min Charter presentation: 10 min Terminology & Problem statement discussion : 25 min Solution/framework discussion: 20 min Mailing List: General Discussion: manetautoconf@ml.free.fr To Subscribe: manetautoconf-request@ml.free.fr