Implementation Issues with RFC 2131, "Dynamic Host Configuration Protocol (DHCPv4)"
draft-ietf-dhc-implementation-02
| Document | Type | Expired Internet-Draft (dhc WG) | |
|---|---|---|---|
| Last updated | 2006-06-16 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-dhc-implementation-02.txt
Abstract
This memo identifies implementation issues with RFC 2131, "Dynamic Host Configuration Protocol," reported by a number of implementers, assesses the severity of the problem, then proposes changes to RFC 2131 intended to overcome the issues. This is intended for use as the basis for discussion of RFC 2131 before it is proposed for Internet Standard status.
Authors
Robert Stevens
(robs@cruzio.com)
Richard Hibbs
(rbhibbs@pacbell.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)