draft-ietf-dhc-pv4-reconfigure-05.txt   draft-ietf-dhc-pv4-reconfigure-06.txt 
Submitted to DHC Working Group Yves T'Joens A new Request for Comments is now available in online RFC libraries.
INTERNET DRAFT Christian Hublet
<draft-ietf-dhc-pv4-reconfigure-05.txt> Alcatel
Peter De Schrijver
Mind
June 2001
Expires November, 2001
DHCP reconfigure extension
Status of this memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months. Internet-Drafts may be updated, replaced, or obsoleted by
other documents at any time. It is not appropriate to use Internet-
Drafts as reference material or to cite them other than as a
``working draft'' or ``work in progress.''
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
To view the entire list of current Internet-Drafts, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directorieson ftp.is.co.za (Africa), ftp.nordu.net (Northern Europe),
ftp.nis.garr.it (Southern Europe), munnari.oz.au(Pacific Rim),
ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
Distribution of this memo is unlimited.
Abstract
This draft defines extensions to DHCP [DHCP] to allow dynamic
reconfiguration of a single host triggered by the DHCP server (eg. 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 draft 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 [RFC2119].
2. DHCP force renew
This section describes the FORCERENEW message extension.
2.1 Terminology
DHCP client : host to be reconfigured using DHCP.
DHCP server : server which configured the DHCP client.
2.2 Force renew procedures
The DHCP server sends a unicast FORCERENEW message to the client.
Upon receipt of the unicast FORCERENEW message, the client will
change its state to the RENEW state, and will then try to renew its
lease according to normal DHCP procedures. If the server wants to
assign a new IP address to the client, it will reply to the DHCP
REQUEST with a DHCP NAK. The client will then go back to the init
state and broadcast a DHCP DISCOVER message. The server can now
assign a new IP address to the client by replying with a DHCP OFFER.
If the FORCERENEW message is lost, the DHCP server will not receive a
DHCP REQUEST from the client and it should retransmit the FORCERENEW
message using an exponential backoff algorithm. Depending on the
bandwidth of the network between server and client, the server should
choose a delay. This delay grows exponentially as retransmissions
fail. The amount of retransmissions should be limited.
The procedures described above assume the server to send a unicast
FORCERENEW message to the client. Receipt of a multicast FORCERENEW
message by the client should be silently discarded.
It can be that a client has obtained a network address through some
other means (e.g., manual configuration) and has used a DHCP INFORM
request to obtain other local configuration parameters. Such clients
should respond to the receipt of a unicast FORCERENEW message with a
new DHCP INFORM request so as to obtain a potential new set of local
configuration parameters. Note that the usage of these procedures are
limited to the set of options that are eligible for configuration by
DHCP and should not override manually configured parameters.
Note further that usage of the FORCERENEW message to reconfigure a
client address or local configuration parameters can lead to the
interruption of active sessions, and that as such these procedures
should be used in controlled circumstances.
2.3 Example usage
2.3.1 Embedded DHCP clients
The autoconfiguration of home gateways (more generically Network
Termination equipment) for public networking purposes can be achieved
through means of DHCP, as described in [DSL_autoconf]. In order to
allow service changes or service interruption, the FORCERENEW message
can trigger the home gateway to contact the DHCP server, prior to the
expiry of the lease.
2.3.2 Hospitality service scenario
In self provisioned networks, e.g., hotel rooms, the hotel owned DHCP
server can hand out limited use IP addresses, that allows the
customer to consume local services or select external services from a
web browser interface. In order to allow external services through
other service providers, e.g., global internet services or enterprise
VPN services, the DHCP server can trigger the client to ask for a new
DHCP initialization session so as to obtain e.g., a globally routed
IP address.
2.3.3 Network renumbering
Under tightly controlled conditions, the FORCERENEW procedures can be
used to brute force the renumbering of entire subnets, client per
client, under control of a DHCP server.
2.4 Rationale
The approach as described in this document has a number of
advantages. It does not require new states to be added to the DHCP
client implementation. This minimizes the amount of code to be
changed. It also allows lease RENEWAL to be driven by the server,
which can be used to optimize network usage or DHCP server load.
3. Extended DHCP state diagram
+--------+ +------+
| Init / | +-->+ Init +<---------------+-------------------+
| Reboot | | +--+---+ | |
+---+----+ DHCPNAK/ -/Send DHCPDISCOVER | |
| Restart | (broadcast) | |
| | v v-------------+ | |
-/Send DHCPREQUEST| +----+------+ DHCPOFFER/DHCPDECLINE |
| (broadcast)| | Selecting |----------+ | |
v | +----+------+ | |
+---+----+ | DHCPOFFER/DHCPREQUEST | |
| Reboot +---------+ (broadcast) | |
+---+----+ v | |
| +----+-------+ DHCPNAK /halt network
| + Requesting | | lease expired
DHCPACK/ +----+-------+ | |
Record lease | | |
set timers DHCPACK/Record lease | |
| v Set T1 & T2 | |
| +--+----+DHCPFORCE +---+---+ +----+---+
+----------------->+ Bound +---------->+ Renew +--------->+ Rebind |
+--+-+--+T1 expires +-+-+---+T2 expires+----+---+
^ /DHCPREQUEST | | /broadcast |
DHCPACK to leasing | | DHCPREQUEST |
| server | | |
+----------------------------------------+
4. Message layout
The FORCERENEW message makes use of the normal DHCP message layout
with the introduction of a new DHCP message type. DHCP option 53
(DHCP message type) is extended with a new value : DHCPFORCERENEW
(TBD)
5. IANA Considerations
The new value for DHCP option 53 (DHCP message type) to indicate a
DHCPFORCERENEW message is TBD.
6. Security Considerations
As in some network environments FORCERENEW can be used to snoop and
spoof traffic, the FORCERENEW message MUST be authenticated using the
procedures as described in [DHCP-AUTH]. FORCERENEW messages failing
the authentication should be silently discarded by the client.
7. References
[DHCP] R.Droms, "Dynamic Host Configuration Protocol", RFC 2131,
March 1997.
[DHCP-AUTH] R. Droms et al., "Authentication for DHCP Messages", RFC 3203
RFCxxxx, yyyy 2001.
[DSL_autoconf] Working Text WT-059, "Auto-configuration for Basic Title: DHCP reconfigure extension
Internet (IP-Based) Services", DSL Forum, May 2001 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
[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate I-D Tag: draft-ietf-dhc-pv4-reconfigure-06.txt
Requirement Levels", BCP 14, RFC 2119, March 1997.
8. Acknowledgements URL: ftp://ftp.rfc-editor.org/in-notes/rfc3203.txt
The authors would like to thank David Allan, Nortel, for the This document defines extensions to DHCP (Dynamic Host Configuration
constructive comments to these procedures. 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.
9. Contacts This document is a product of the Dynamic Host Configuration Working
Group of the IETF.
Yves T'joens This is now a Proposed Standard Protocol.
Alcatel Network Strategy Group
Francis Wellesplein 1, 2018 Antwerp, Belgium
Phone : +32 3 240 7890
E-mail : yves.tjoens@alcatel.be
Peter De Schrijver This document specifies an Internet standards track protocol for
Mind NV the Internet community, and requests discussion and suggestions
Vaartkom 11 for improvements. Please refer to the current edition of the
3000 Leuven "Internet Official Protocol Standards" (STD 1) for the
E-mail : p2@mind.be standardization state and status of this protocol. Distribution
of this memo is unlimited.
Christian Hublet This announcement is sent to the IETF list and the RFC-DIST list.
Alcatel Carrier Internetworking Division Requests to be added to or deleted from the IETF distribution list
De Villermontstraat 28, 2550 Kontich, Belgium should be sent to IETF-REQUEST@IETF.ORG. Requests to be
Phone : +32 3 450 3322 added to or deleted from the RFC-DIST distribution list should
E-mail : Christian.Hublet@alcatel.be be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
8. Full Copyright Statement 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:
This document and translations of it may be copied and furnished to To: rfc-info@RFC-EDITOR.ORG
others, and derivative works that comment on or otherwise explain it Subject: getting rfcs
or assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be help: ways_to_get_rfcs
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an Requests for special distribution should be addressed to either the
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION specifically noted otherwise on the RFC itself, all RFCs are for
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF unlimited distribution.echo
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.'' 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.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/