A zeroconf network is one that can exist without a central control element, and works without any kind of user configuration.
A zeroconf protocol is able to operate correctly in the absence of configured information from either a user or infrastructure services such as conventional DHCP or DNS servers. Zeroconf protocols may use configured information, when it is available, but do not rely on it being present. For example, the use of MAC addresses (i.e. layer two addresses) as parameters in zeroconf protocols is generally acceptable because they are globally unique and readily available on most devices of interest. | ||
| --draft-ietf-zeroconf-reqts-12.txt: | ||
A zeroconf network may require four functional elements:
Network layer address assignment
Translation between network names, and network addresses
Location or discovery of services by name and protocol
Multicast address assignment
The IETF has existing or developmental work in the first three element areas. There is a general acceptance that the need for multicast address assignment is very low, and while there is an equivalent to DHCP for multicast (known as MADCAP, for Multicast Address Dynamic Client Allocation Protocol[1]), its usage is very low. Work on multicast address assignment in a zeroconf environment has effectivelybeen abandoned.
| [1] | MADCAP is specified in RFC2730, with additional information in RFC2907. |
| <<< Previous | Home | Next >>> |
| Technology - Part 1 - Address Assignment |