Implementation Issues with RFC 2131, "Dynamic Host Configuration Protocol (DHCPv4)"
draft-ietf-dhc-implementation-02
| Document | Type |
Expired Internet-Draft
(dhc WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Robert Stevens , Richard Barr Hibbs | ||
| Last updated | 2006-06-16 | ||
| 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 | Expired | |
| 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
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
Dr. Robert Stevens
Richard Barr Hibbs
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)