DHCP Relay Initiated Release
draft-gandhewar-dhc-relay-initiated-release-01

Document Type Expired Internet-Draft (dhc WG)
Last updated 2016-04-04 (latest revision 2015-10-01)
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
Polled for WG adoption but not adopted, Revised I-D Needed - Issue raised by WG
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-gandhewar-dhc-relay-initiated-release-01.txt

Abstract

The Dynamic Host Configuration Protocol (DHCP) is initiated by a DHCP client. A DHCP server can force DHCP client to send DHCPRENEW by sending a DHCPFORCERENEW message. There may be multiple DHCP network devices connected in between a DHCP client and a server, each one reserving resources for the DHCP client. There are no DHCP messages that a relay can initiate in order to control the client binding. A DHCP client may not always send a DHCPRELEASE message when it no longer needs the IP address and network resources for the associated services it is using. This document specifies a way to request release message to be initiated by an intermediate DHCP network device, e.g. DHCP relay, on behalf of DHCP client. This helps to relinquish network resources sooner than the lease expiration time.

Authors

Sunil Gandhewar (sgandhewar@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)