DHCP Option Processing, Explained
draft-dhankins-atomic-dhcp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | David Hankins | ||
| Last updated | 2006-10-05 | ||
| 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
Most protocol developers ask themselves if a protocol will work, or work efficiently. These are important questions, but another less frequently considered is wether the proposed protocol changes present themselves barriers to adoption by deployed software (more importantly, needlessly so). This document seeks to provide information on the challenges to DHCP Option software implementers, and in doing so to provide guidance to prospective DHCP Option authors to help them produce options that are easily adoptable.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)