idnits 2.17.1 draft-ietf-dhc-pv4-reconfigure-06.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3203 5 Title: DHCP reconfigure extension 6 Author(s): Y. T'Joens, C. Hublet, P. De Schrijver 7 Status: Standards Track 8 Date: December 2001 9 Mailbox: yves.tjoens@alcatel.be, p2@mind.be, 10 Christian.Hublet@alcatel.be 11 Pages: 6 12 Characters: 11857 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-dhc-pv4-reconfigure-06.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3203.txt 19 This document defines extensions to DHCP (Dynamic Host Configuration 20 Protocol) to allow dynamic reconfiguration of a single host triggered 21 by the DHCP server (e.g., a new IP address and/or local configuration 22 parameters). This is achieved by introducing a unicast FORCERENEW 23 message which forces the client to the RENEW state. The behaviour for 24 hosts using the DHCP INFORM message to obtain configuration 25 information is also described. 27 This document is a product of the Dynamic Host Configuration Working 28 Group of the IETF. 30 This is now a Proposed Standard Protocol. 32 This document specifies an Internet standards track protocol for 33 the Internet community, and requests discussion and suggestions 34 for improvements. Please refer to the current edition of the 35 "Internet Official Protocol Standards" (STD 1) for the 36 standardization state and status of this protocol. Distribution 37 of this memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.