Customizing DHCP Configuration on the Basis of Network Topology
draft-lemon-dhc-topo-conf-01
| Document | Type |
Replaced Internet-Draft
(dhc WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Ted Lemon | ||
| Last updated | 2013-10-15 (Latest revision 2013-04-13) | ||
| Replaced by | draft-ietf-dhc-topo-conf | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dhc-topo-conf | |
| Consensus boilerplate | Unknown | ||
| 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
DHCP servers have evolved over the years to provide significant functionality beyond that which is described in the DHCP base specifications. One aspect of this functionality is support for context-specific configuration information. This memo describes some such features and makes recommendations as to how they can be used.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)