Skip to main content

Multi-Router Zeroconf Network Requirements
draft-akinlar-zeroconf-multirouter-01

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Cuneyt Akinlar , David Braun , Sangeeta Mukherjee
Last updated 2000-08-16
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

Zero Configuration (Zeroconf) Networks are a particular class of TCP/IP networks that may be established in the home, in small offices or even for a variety of adhoc purposes. Zeroconf networks do not have and should not be expected to have user configurable network infrastructure such as DHCP, DNS and other administered network services. This is because typical zeroconf network users neither have the skill nor the desire to configure, administer or manage a network [1]. The IETF Zeroconf Requirements draft [1] presents the zeroconf protocol requirements for 4 areas: IP host configuration, domain name to IP address resolution, IP multicast address allocation, and service discovery. This draft builds on [1] and lists the zeroconf protocol requirements for IP router configuration and dynamic routing protocol in multi-router zeroconf networks. The IETF Zeroconf Requirements draft [1] presents the zeroconf protocol requirements for 4 areas: IP host configuration, domain name to IP address resolution, IP multicast address allocation, and service discovery. The most complex network topology addressed by the Zeroconf Requirements document [1] is a multi-segment zeroconf network connected by a single router. This drafts builds on that draft and lists the zeroconf protocol requirements for IP router configuration and dynamic routing protocols in multi-router zeroconf networks.

Authors

Cuneyt Akinlar
David Braun
Sangeeta Mukherjee

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