RFC 3203: DHCP reconfigure extension
In plain English — editorial summary, not part of the RFC
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). [STANDARDS-TRACK]
Document record
- Document ID
- RFC3203
- Published
- December 2001
- Authors
- Y. T'Joens; C. Hublet; P. De Schrijver
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 6
- Also known as
- —
- Updated by:
- RFC 6704
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2939Procedures and IANA Guidelines for Definition of New DHCP Options and Message TypesCurrent
September 2000
- RFC 3679Unused Dynamic Host Configuration Protocol (DHCP) Option CodesUpdated
January 2004
- RFC 2132DHCP Options and BOOTP Vendor ExtensionsUpdated
March 1997
- RFC 1534Interoperation Between DHCP and BOOTPCurrent
October 1993
- RFC 1533DHCP Options and BOOTP Vendor ExtensionsObsoleted
October 1993
- RFC 2462IPv6 Stateless Address AutoconfigurationObsoleted
December 1998
- RFC 2729Taxonomy of Communication Requirements for Large-scale Multicast ApplicationsCurrent
December 1999
- RFC 3220IP Mobility Support for IPv4Obsoleted
January 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?