Zero configuration networking

From Wikipedia, the free encyclopedia

The five-layer TCP/IP model
5. Application layer

DHCP · DNS · FTP · Gopher · HTTP · IMAP4 · IRC · NNTP · XMPP · POP3 · RTP · SIP · SMTP · SNMP · SSH · TELNET · RPC · RTCP · RTSP · TLS (and SSL) · SDP · SOAP · GTP · STUN · NTP · (more)
4. Transport layer
TCP · UDP · DCCP · SCTP · RSVP · ECN · (more)
3. Network/internet layer
IP (IPv4 · IPv6) · OSPF · IS-IS · BGP · IPsec · ARP · RARP · RIP · ICMP · ICMPv6 · IGMP · (more)
2. Data link layer
802.11 (WLAN) · 802.16 · Wi-Fi · WiMAX · ATM · DTM · Token ring · Ethernet · FDDI · Frame Relay · GPRS · EVDO · HSPA · HDLC · PPP · PPTP · L2TP · ISDN · ARCnet · LLTD · (more)
1. Physical layer
Ethernet physical layer · RS-232 · SONET/SDH · G.709 · Optical fiber · Coaxial cable · Twisted pair · (more)
This box: view • talk • edit

Zeroconf or Zero Configuration Networking is a set of techniques that automatically create a usable IP network without configuration or special servers. This allows inexpert 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 services, 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 currently solves three problems :

  • Choose numeric network addresses for networked items
  • Figure out which computer has a certain name
  • Figure out where to get services, like printing (service discovery)

Contents

[edit] Choosing addresses

Both IPv4 and IPv6 have standard ways of choosing IP addresses without help. By RFC 3927, IPv4 uses the 169.254.* (link-local) set of addresses. For IPv6, see RFC 2462.

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).

[edit] Name resolution

The paper describing how name resolution might be accomplished was published by Bill Manning and Bill Woodcock in 2000 as "Multicast Domain Name Service"[1] which spawned the work done by Apple and Microsoft.

There are two very similar ways of figuring out which networked item has a certain name. Apple's Multicast DNS (mDNS) is in use, and is published freely. Microsoft's Link-local Multicast Name Resolution (LLMNR) is little used, and also not on the IETF standards track. It has been published as informational RFC 4795.

The two protocols have minor differences in their approach to name resolution. 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,[2] which is considered a problem by some members of the IETF.[3] 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.[4] mDNS is compatible with DNS-SD as described in the next section, while LLMNR is not.[5]

[edit] Service discovery

[edit] Apple's protocol: Multicast DNS/DNS-SD

Multicast DNS (mDNS) is a protocol that uses similar APIs to the unicast DNS system but implemented differently. Each computer on the LAN stores its own list of DNS records (e.g. A, MX, PTR, SRV, etc) and when an mDNS client wants to know the IP address of a PC given its name, the PC with the corresponding A record replies with its IP address. The mDNS multicast address is 224.0.0.251.

DNS based Service Discovery (DNS-SD) is the other half of Apple's solution, built on top of the Domain Name System. It is used in Apple products, many network printers and a number of third party products and applications on various operating systems. In contrast to Microsoft's competing technology, SSDP, 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.

Many Mac OS X networking clients, such as the Safari browser and the iChat instant messaging software, use DNS-SD to locate nearby servers. On Windows, instant messaging and VoIP clients such as Gizmo support DNS-SD. Some Linux distributions also include DNS-SD functionality.

mDNS/DNS-SD was developed by Apple Computer employee Stuart Cheshire in the company's move from AppleTalk to IP.

[edit] Microsoft's protocol: UPnP SSDP

Simple Service Discovery Protocol (SSDP) is a UPnP protocol, used in Windows XP and several brands of network equipment. 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 is facilitated using SSDP.

[edit] Efforts toward an IETF standard protocol

Service Location Protocol (SLP), the only protocol for service discovery to have reached the IETF Proposed Standard status, is supported by Hewlett-Packard's network printers, Novell, Sun Microsystems, and Apple Inc, but ignored by some other large vendors. SLP is described in RFC 2608 and RFC 3224 and implementations are available for both Solaris and Linux.

[edit] 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.[6]

LLMNR was submitted for official adoption in the DNSEXT IETF working group, however failed to gain consensus and thus has been published as informational RFC only: RFC 4795.[7] Following the failure of LLMNR to become an Internet standard Apple was asked by the IETF to submit the mDNS/DNS-SD specs for publishing as informational RFC as well, given that mDNS/DNS-SD is used much more widely than LLMNR.

RFC 2608, the SLP standard for figuring out where to get services, was published by the SVRLOC IETF working group.[8]

[edit] Major implementations

[edit] Apple Bonjour

The most widely adopted[citation needed] Zeroconf solution is Bonjour (formerly Rendezvous) from Apple Inc., 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[9] and is available on BSD, Mac OS X, Linux, other POSIX based operating systems and Windows. The Windows downloads are available from Apple's website.[10]

[edit] Avahi

Avahi is a Zeroconf implementation for Linux and BSDs. It implements IPv4LL, mDNS and DNS-SD. It is part of most Linux distributions, and is installed by default on some. If run in conjunction with nss-mdns it also offers host name resolution.[11]

Avahi also implements binary compatibility libraries that emulate Bonjour and the historic mDNS implementation Howl, so software made to use those implementations can also utilize Avahi through the emulation interfaces.

[edit] Windows CE 5.0

Windows CE 5.0 includes Microsoft's own implementation of LLMNR.

[edit] Link-local IPv4 addresses

There are some implementations available:

  • Windows and Mac OS have both supported link-local addresses since 1998. Apple released its open-source implementation in the Darwin bootp package.
  • Avahi contains a implementation of IPv4LL in the avahi-autoipd tool.
  • zcip (Zero-Conf IP)
  • BusyBox can embed a simple IPv4LL implementation
  • Stablebox, a fork from Busybox, offers a slightly modified IPv4LL implementation named llad.
  • zeroconf, a package based on Simple IPv4LL, a shorter implementation by Arthur van Hoff.[12]

The above implementations are all stand-alone daemons or plugins for DHCP clients that only deal with link-local IP addresses. Another approach is to modify existing DHCP clients:

  • Elvis Pfützenreuter has written a patch for the uDHCP client/server.[13]

Neither of these implementations addresses kernel issues like the broadcasting of ARP replies[14] or closing of existing network connections.

[edit] References

  • Erik Guttman (2001). "Autoconfiguration for IP Networking: Enabling Local Communication". IEEE Internet Computing 5 (3): 81-86. 
  1. ^ http://www.watersprings.org/pub/id/draft-manning-dnsext-mdns-00.txt
  2. ^ Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard
  3. ^ Re: Summary of the LLMNR Last Call
  4. ^ Summary of the LLMNR Last Call
  5. ^ More details on the differences
  6. ^ Zero Configuration Networking (zeroconf) Charter
  7. ^ DNS Extensions (dnsext) Charter
  8. ^ Service Location Protocol (svrloc) Charter
  9. ^ MacDevCenter.com - A Rendezvous with Java
  10. ^ Apple - Support - Downloads - Bonjour for Windows 1.0.4
  11. ^ nss-mdns 0.10
  12. ^ http://www.zeroconf.org/AVH-IPv4LL.c
  13. ^ [udhcp] Fwd: Zeroconf in udhcpc
  14. ^ AIR Wiki: Link-Local ARP Measurements

[edit] See also

[edit] External links