|
Zeroconf or Zero Configuration Networking is a set of techniques that automatically create a usable IP network without configuration or special servers. This allows unknowledgeable users to connect computers, networked printers, and other items together and expect them to work automatically. Without Zeroconf or something similar, a knowledgeable user must either set up special servers, like DHCP and DNS, or set up each computer's network settings by hand, which is a tedious task, and is challenging for non-technical people. Zeroconf was pioneered by Apple Computer employee Stuart Cheshire in the company's move from AppleTalk to IP. Problems solved Zeroconf currently solves three problems Choosing addresses Both IPv4 and IPv6 have standard ways of choosing IP addresses without help. By RFC 3927, IPv4 uses the 169.254. The technique for IPv4 is called IPv4 Link-Local (IPV4LL) in the RFC, however Microsoft refers to this as Automatic Private IP Addressing (APIPA) or Internet Protocol Automatic Configuration (IPAC). Name resolution There are two very similar ways of figuring out which networked item has a certain name. Apple Computer's Multicast DNS (mDNS) is in use, and is published freely, though not by a standardization body. Microsoft's Link-local Multicast Name Resolution (LLMNR) is little used, but is in the process of standardization by the IETF.* The two protocols have minor differences. mDNS allows a network device to choose a domain name in the ".local" namespace and announce it using a special multicast IP address. This introduces special semantics for the .local namespace, which is considered a problem by some members of the IETF.** The current LLMNR draft allows a network device to choose any domain name, which is considered a security risk by some members of the IETF.* mDNS is compatible with DNS-SD as described in the next section, while LLMNR is not. More details on the differences are at * Apples protocol: mDNS/DNS-SD DNS Service Discovery (DNS-SD) is Apple's lightweight solution, built on top of the tested and robust Domain Name System. It is used in Apple products, many network printers and a considerable number of third party products and applications on various operating systems. It is considered simpler and easier to implement than Microsoft's competing technology, SSDP, because it uses DNS rather than HTTP. It uses DNS SRV (RFC 2782), TXT, and PTR records to advertise Service Instance Names. The hosts offering the different services publish details of available services like instance, service type, domain name and optional configuration parameters. Service types are given informally on a first-come basis. A service type registry is maintained and published by DNS-SD.org. Almost all Mac OS software such as the Safari browser and the iChat instant messaging software use DNS-SD. On Windows, many instant messaging and VoIP clients such as Gizmo support DNS-SD. On Linux, many Linux distributions already include DNS-SD functionality. Microsofts protocol: uPNP SSDP Simple Service Discovery Protocol (SSDP) is a UPnP protocol, used in Windows XP and several brands of network equipment. Despite its name, it is considered complex and requires more effort to implement than DNS-SD. SSDP uses HTTP notification announcements that give a service-type URI and a Unique Service Name (USN). Service types are regulated by the Universal Plug and Play Steering Committee. SSDP is supported in many SOHO firewall appliances, where host computers behind it may pierce holes for applications. It is also used in media center systems, where media exchange between host computers and the media center are facilitated using SSDP. Efforts toward an IETF standard protocol Service Location Protocol (SLP), the only protocol for service discovery to have reached the IETF RFC status, is usually ignored by large vendors, except Hewlett-Packard's network printers, Novell, Sun, and Apple Computer. SLP is described in RFC 2608; it is not yet an IETF Standard or Draft Standard, although implementations are available for both Solaris and Linux. Standardization RFC 3927, a standard for choosing addresses for networked items, was published in March 2005 by the Zeroconf IETF working group, which included individuals from Apple, Sun, and Microsoft. The DNSEXT IETF working group is working on standardizing LLMNR for figuring out which networked item has which name. Apple's mDNS won't probably be standardized, because it has largely been developed outside of the DNS extension working group. RFC 2608, the SLP standard for figuring out where to get services, was published by the SVRLOC IETF working group. Apple Bonjour The most widely adopted Zeroconf solution is Bonjour (formerly Rendezvous) from Apple Computer, which uses multicast DNS and DNS Service Discovery. Apple changed its preferred Zeroconf technology from SLP to mDNS and DNS-SD between Mac OS 10.1 and 10.2, though SLP continues to be supported by Mac OS. Apple's mDNSResponder has interfaces for C and Java and is available on BSD, Mac OS X, Linux, other POSIX based operating systems and Windows.** Howl Howl was a comparatively popular zeroconf implementation from Porchdog software. Many programs implemented support for it. For instance, a Howl-based zeroconf plugin is available for Internet Explorer. Avahi Avahi is a Zeroconf implementation for Linux and BSDs. It implements IPv4LL, mDNS and DNS-SD. It is part of every major and many minor Linux distributions, and is installed by default on e.g. Ubuntu version 6.10. If run in conjunction with nss-mdns it also offers host name resolution. Avahi also implements binary compatibility libraries that emulate Bonjour and Howl, so software made to use those implementations can also utilize Avahi through the emulation interfaces. Windows CE 5.0 Windows CE 5.0 includes Microsoft's own implementation of LLMNR. Link-Local IPv4 Addresses There are some implementations available: The above implementations are all stand-alone daemons that only deal with link-local IP addresses. Another approach is to modify existing DHCP clients. Neither of these implementations addresses kernel issues like the broadcasting of ARP replies or closing of existing network connections. See also Implementation links Books Videos | |||||||
|
| ||||||||
 |
|
| |