IP addresses configuration in spontaneous networks

To participate in IP networking, a host needs to be configured with IP addresses for its interfaces, either manually by the user or automatically from a source on the network such as a Dynamic Host Configuration Protocol (DHCP) server. Many common TCP/IP protocols [1] such as DHCP [2], DNS [3][4], MADCAP [5], and LDAP [6] must be configured and maintained by an administrative staff. Other times, administrative staff won't be necessary, however we'll need the help of central servers to configure the network. This is unacceptable for emerging networks such as home networks, automobile networks, airplane networks, or ad hoc networks at conferences, emergency relief stations, and many others. Such networks may be nothing more than two isolated laptop PCs connected via a wireless LAN. For all these networks, neither will exist an administrative staff nor possibly will exist central servers that help to configure this data, then the users of these networks neither have the time nor inclination to learn network administration skills. Instead, these networks need protocols that require zero user configuration and administration. Spontaneous networks are an example of these networks, in which central servers don't usually exist, for this reason, the nodes will be in charge of both forming the network and configuring their IP address. In this article we deal with the problematic of IP addresses configuration in a particular case: spontaneous networks, we'll have into account the identifier ownership problems.