Requirements for Automatic Configuration of IP Hosts
draft-ietf-zeroconf-reqts-12

Document Type Expired Internet-Draft (zeroconf WG)
Author Aidan Williams 
Last updated 2015-10-14 (latest revision 2002-09-25)
Stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired (IESG: Dead)
Action Holders
(None)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Thomas Narten
IESG note This document has problems, and it is unclear that is worth the effort to try and fix them. This document is unlikely to be used as the basis for any followon work. Thus, the consensus of the authors, WG chair and ADs is to drop the item.
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-zeroconf-reqts-12.txt

Abstract

Many common TCP/IP protocols such as DHCP [RFC2131], DNS [RFC1034][RFC1035], MADCAP [RFC2730], and LDAP [RFC2251] must be configured and maintained by an administrative staff. 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, an administrative staff will not exist and 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. This document is part of an effort to define such zero configuration (zeroconf) protocols. Before embarking on defining zeroconf protocols, protocol requirements are needed. This document states the zeroconf protocol requirements for four protocol areas; they are: IP interface configuration, translation between host name and IP address, IP multicast address allocation, and service discovery. This document does not define specific protocols, just requirements. The requirements for these four areas result from examining everyday use or scenarios of these protocols.

Authors

Aidan Williams (aidan.williams@motorola.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)