RFC 3203 (rfc3203) - Page 1 of 6
DHCP reconfigure extension
Alternative Format: Original Text Document
Network Working Group Y. T'Joens
Request for Comments: 3203 C. Hublet
Category: Standards Track Alcatel
P. De Schrijver
Mind
December 2001
DHCP reconfigure extension
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract
This document defines extensions to DHCP (Dynamic Host Configuration
Protocol) to allow dynamic reconfiguration of a single host triggered
by the DHCP server (e.g., a new IP address and/or local configuration
parameters). This is achieved by introducing a unicast FORCERENEW
message which forces the client to the RENEW state. The behaviour
for hosts using the DHCP INFORM message to obtain configuration
information is also described.
1. Introduction
The procedures as described within this document allow the dynamic
reconfiguration of individual hosts.
1.1 Conventions
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 [RFC 2119].
2. DHCP force renew
This section describes the FORCERENEW message extension.
T'Joens, et al. Standards Track