DHCP Reconfigure Extension Option
draft-vinokour-dhcp-reconfigure-option-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Vitali Vinokour , Wojciech Dec , James Bristow , David Miles | ||
| Last updated | 2008-06-06 | ||
| 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
The current use of DHCP (Dynamic Host Configuration Protocol) Reconfigure extension is limited by a requirement that FORCERENEW message is authenticated. This document defines a mechanism allowing the use of FORCERENEW without DHCP authentication.Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
Authors
Vitali Vinokour
Wojciech Dec
James Bristow
David Miles
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)