< draft-bernardos-manet-autoconf-survey-02.txt   draft-bernardos-manet-autoconf-survey-03.txt >
MANET Autoconfiguration (AUTOCONF) C. Bernardos MANET Autoconfiguration (AUTOCONF) C. Bernardos
Internet-Draft M. Calderon Internet-Draft M. Calderon
Intended status: Informational UC3M Intended status: Informational UC3M
Expires: April 12, 2008 H. Moustafa Expires: October 10, 2008 H. Moustafa
France Telecom France Telecom
October 10, 2007 April 8, 2008
Survey of IP address autoconfiguration mechanisms for MANETs Survey of IP address autoconfiguration mechanisms for MANETs
draft-bernardos-manet-autoconf-survey-02 draft-bernardos-manet-autoconf-survey-03
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 12, 2008. This Internet-Draft will expire on October 10, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract Abstract
This Internet Draft provides a detailed description of most of the This Internet Draft provides a detailed description of most of the
existing IP autoconfiguration solutions proposed so far. The main existing IP autoconfiguration solutions proposed so far. The main
aim of this document is to serve as a general reference for the aim of this document is to serve as a general reference for the
AUTOCONF solution space. We present most of the previously proposed AUTOCONF solution space. We present most of the previously proposed
IP AUTOCONF mechanisms in MANETs, showing their key characteristics, IP AUTOCONF mechanisms in MANETs, showing their key characteristics,
conforming to the AUTOCONF problem statement draft and the MANET conforming to the AUTOCONF problem statement draft and the MANET
architecture draft. Furthermore, each solution is analysed based on architecture draft. Furthermore, each solution is analysed based on
skipping to change at page 5, line 21 skipping to change at page 5, line 21
specifications have been developed by the IETF MANET WG. In order to specifications have been developed by the IETF MANET WG. In order to
allow wide deployment of ad hoc networks, in which IP routing is the allow wide deployment of ad hoc networks, in which IP routing is the
most candidate approach, IP configuration of nodes is a strong most candidate approach, IP configuration of nodes is a strong
requirement that need to be satisfied. In this context, the AUTOCONF requirement that need to be satisfied. In this context, the AUTOCONF
WG is working towards standard specifications and solutions for IP WG is working towards standard specifications and solutions for IP
address autoconfiguration within different MANET environments. address autoconfiguration within different MANET environments.
Ad hoc networks present particular characteristics that should be Ad hoc networks present particular characteristics that should be
taken into account when designing address auto-configuration taken into account when designing address auto-configuration
protocols. Since existing solutions for IP infrastructure-based protocols. Since existing solutions for IP infrastructure-based
networks (e.g., RFCs 2461, 2462, 3315 etc.) were designed for a networks (e.g., RFCs 4861, 4862, 3315 etc.) were designed for a
different scope that MANETs [1], there are several issues that need different scope that MANETs [1], there are several issues that need
to be tackled, mainly (but not only) the following: the lack of to be tackled, mainly (but not only) the following: the lack of
multi-hop support, the lack of dynamic topology support, the lack of multi-hop support, the lack of dynamic topology support, the lack of
network merging support and the lack of network partitioning support. network merging support and the lack of network partitioning support.
The main goal of the AUTOCONF WG is to develop solutions for IPv6 The main goal of the AUTOCONF WG is to develop solutions for IPv6
address auto-configuration (both MANET-local and global scoped). The address auto-configuration (both MANET-local and global scoped). The
group has identified two possible scenarios of MANET where IP address group has identified two possible scenarios of MANET where IP address
auto-configuration is required [1]: auto-configuration is required [1]:
skipping to change at page 46, line 9 skipping to change at page 46, line 9
another shape. another shape.
The work of Carlos J. Bernardos and Maria Calderon has been partly The work of Carlos J. Bernardos and Maria Calderon has been partly
supported by the Spanish Government under the POSEIDON (TSI2006- supported by the Spanish Government under the POSEIDON (TSI2006-
12507-C03-01) project. 12507-C03-01) project.
6. References 6. References
6.1. Normative References 6.1. Normative References
[1] Baccelli, E., "Address Autoconfiguration for MANET: Terminology [1] Baccelli, E., Mase, K., Ruffino, S., and S. Singh, "Address
and Problem Statement", draft-ietf-autoconf-statement-01 (work Autoconfiguration for MANET: Terminology and Problem
in progress), September 2007. Statement", draft-ietf-autoconf-statement-04 (work in
progress), February 2008.
[2] Moustafa, H., "Evaluation Considerations for IP [2] Moustafa, H., Bernardos, C., and M. Calderon, "Evaluation
Autoconfiguration Mechanisms in MANETs", Considerations for IP Autoconfiguration Mechanisms in MANETs",
draft-bernardos-autoconf-evaluation-considerations-00 (work in draft-bernardos-autoconf-evaluation-considerations-01 (work in
progress), August 2007. progress), October 2007.
[3] Chakeres, I., "Mobile Ad hoc Network Architecture", [3] Chakeres, I., Macker, J., and T. Clausen, "Mobile Ad hoc
draft-ietf-autoconf-manetarch-06 (work in progress), Network Architecture", draft-ietf-autoconf-manetarch-07 (work
October 2007. in progress), November 2007.
6.2. Informative References 6.2. Informative References
[4] Perkins, C., "IP Address Autoconfiguration for Ad Hoc [4] Perkins, C., "IP Address Autoconfiguration for Ad Hoc
Networks", draft-perkins-manet-autoconf-01 (work in progress), Networks", draft-perkins-manet-autoconf-01 (work in progress),
November 2001. November 2001.
[5] Weniger, K. and M. Zitterbart, "IPv6 Autoconfiguration in Large [5] Weniger, K. and M. Zitterbart, "IPv6 Autoconfiguration in Large
Scale Mobile Ad-Hoc Networks", European Wireless 2002 , 2002. Scale Mobile Ad-Hoc Networks", European Wireless 2002 , 2002.
skipping to change at page 48, line 23 skipping to change at page 48, line 23
[26] Laouiti, A., "Address autoconfiguration in Optimized Link State [26] Laouiti, A., "Address autoconfiguration in Optimized Link State
Routing Protocol", draft-laouiti-manet-olsr-address-autoconf-01 Routing Protocol", draft-laouiti-manet-olsr-address-autoconf-01
(work in progress), July 2005. (work in progress), July 2005.
[27] Cha, H., Park, J., and H. Kim, "Extended Support for Global [27] Cha, H., Park, J., and H. Kim, "Extended Support for Global
Connectivity for IPv6 Mobile Ad Hoc Networks", Connectivity for IPv6 Mobile Ad Hoc Networks",
draft-cha-manet-extended-support-globalv6-00 (work in draft-cha-manet-extended-support-globalv6-00 (work in
progress), October 2003. progress), October 2003.
[28] Templin, F., Russert, S., and S. Yi, "MANET Autoconfiguration", [28] Templin, F., Russert, S., and S. Yi, "The MANET Virtual
draft-templin-autoconf-dhcp-09 (work in progress), Ethernet (VET) Abstraction", draft-templin-autoconf-dhcp-14
September 2007. (work in progress), April 2008.
[29] Templin, F., "MANET Autoconfiguration over Virtual Ethernets", [29] Templin, F., "MANET Autoconfiguration over Virtual Ethernets",
draft-templin-autoconf-virtual-00 (work in progress), draft-templin-autoconf-virtual-00 (work in progress),
February 2007. February 2007.
[30] Templin, F., "MANET Autoconfiguration over Multilink Sites", [30] Templin, F., "MANET Autoconfiguration over Multilink Sites",
draft-templin-autoconf-multilink-00 (work in progress), draft-templin-autoconf-multilink-00 (work in progress),
February 2007. February 2007.
[31] Draves, R. and D. Thaler, "Default Router Preferences and More- [31] Draves, R. and D. Thaler, "Default Router Preferences and More-
Specific Routes", RFC 4191, November 2005. Specific Routes", RFC 4191, November 2005.
[32] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host [32] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host
Configuration Protocol (DHCP) version 6", RFC 3633, Configuration Protocol (DHCP) version 6", RFC 3633,
December 2003. December 2003.
Appendix A. Change Log Appendix A. Change Log
Changes from -02 to -03:
o New release to keep the document alive.
o Update of some references.
Changes from -01 to -02: Changes from -01 to -02:
o The classification criteria section has been removed, since it is o The classification criteria section has been removed, since it is
now part of the evaluation considerations in [2]. Solutions are now part of the evaluation considerations in [2]. Solutions are
now analysed conforming to some of these evaluation considerations now analysed conforming to some of these evaluation considerations
in [2]. in [2].
o The Conclusions section has been removed. o The Conclusions section has been removed.
o The Terminology section has been removed. o The Terminology section has been removed.
skipping to change at page 51, line 7 skipping to change at page 51, line 7
France Telecom France Telecom
38-40 rue du General Leclerc 38-40 rue du General Leclerc
Issy Les Moulineaux 92794 Cedex 9 Issy Les Moulineaux 92794 Cedex 9
France France
Phone: +33 145296389 Phone: +33 145296389
Email: hassnaa.moustafa@orange-ftgroup.com Email: hassnaa.moustafa@orange-ftgroup.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
skipping to change at page 51, line 44 skipping to change at line 2124
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 12 change blocks. 
23 lines changed or deleted 26 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/