The Mini-DHCP Server
draft-aboba-dhc-mini-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Bernard D. Aboba | ||
| Last updated | 2001-10-01 | ||
| 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
Today, with the rapid rise of home networking, there is a need for simple mechanisms of IPv4 address allocation and name resolution. This document describes the behavior of the mini-DHCP server, a small scale DHCP server that is typically implemented as part of a home gateway. As described in this document, the mini-DHCP server is capable of allocating addresses either in single or multi-segment networks. It supports dynamic DNS, and is capable of automatically detecting the presence of a full-fledged DHCP server, or other mini-DHCP servers, and shutting down as required.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)