[Search] [pdf|bibtex] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 rfc3203                   Standards Track
A new Request for Comments is now available in online RFC libraries.


        RFC 3203

        Title:      DHCP reconfigure extension
        Author(s):  Y. T'Joens, C. Hublet, P. De Schrijver
        Status:     Standards Track
        Date:       December 2001
        Mailbox:    yves.tjoens@alcatel.be, p2@mind.be,
                    Christian.Hublet@alcatel.be
        Pages:      6
        Characters: 11857
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-dhc-pv4-reconfigure-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3203.txt


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.

This document is a product of the Dynamic Host Configuration Working
Group of the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.