Autoconfiguration in Wired Networks

In wired networks, the Dynamic Host Configuration Protocol (DHCP) or in case of dialup access the Point-to-Point Protocol (PPP) usually perform the autoconfiguration of network interfaces. Furthermore, they configure the name resolution via Domain Name System (DNS). However, these protocols require preconfigured and permantly available servers, that means an administrated infrastructure. This assumption makes them useless for the typical end-user application: spontaneous, local networks.

In the past, various proprietary protocols like AppleTalk, NETBIOS or IPX were used in such networks. Though being incompatible among each other, these protocols asked little to zero network configuration of the user. The enormous success of the Internet and with it the succes of IP-based networks superseded these network configuration protocols. The reason for this was the great effort needed to support different protocols for each platform. Even this did not solve the problem of incompatibility in local networks, where IP was the only cross-platform protocol.

The IETF Zeroconf Working Group tried to form a common approach for IP-based networks which comprises the ease-of-use of the former protocols, especially of AppleTalk. From their point of view a protocol for autoconfiguration of networks should be able to perform the following tasks: IP interface configuration, translation between host name and IP address, IP multicast address allocation, and service discovery. Their results are given in the RFC Dynamic Configuration of IPv4 Link-Local Addresses and the Internet-Drafts Multicast DNS and DNS-Based Service Discovery. A proposal for IP multicast address allocation has not yet been published by the IETF.