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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-06-28
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
dhc Working Group                                           S. Gandhewar
Internet-Draft                                    Juniper Networks, Inc.
Intended status: Standards Track                           June 28, 2015
Expires: December 30, 2015

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

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.  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 relinquish network resources sooner than the lease expiration
   time.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 30, 2015.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Gandhewar               Expires December 30, 2015               [Page 1]
Internet-Draft        DHCP Relay Initiated Release             June 2015

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  New Message and Option Value Definitions  . . . . . . . . . .   4
     3.1.  DHCPRELEASEBYRELAY  . . . . . . . . . . . . . . . . . . .   4
     3.2.  DHCPRELAYREPLY  . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  NoBinding . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.4.  NotConfigured . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Functionality . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  First DHCP Network Device Behavior  . . . . . . . . . . .   5
       4.1.1.  Generation and Transmission of DHCPRELEASEBYRELAY
               Message . . . . . . . . . . . . . . . . . . . . . . .   5
       4.1.2.  Receipt of DHCPRELAYREPLY Message . . . . . . . . . .   6
       4.1.3.  Receiving No Response . . . . . . . . . . . . . . . .   7
     4.2.  DHCP Server Behavior  . . . . . . . . . . . . . . . . . .   7
       4.2.1.  Receipt of DHCPRELEASEBYRELAY Message . . . . . . . .   7
       4.2.2.  Generation and Transmission of DHCPRELAYREPLY Message   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   DHCP [RFC2131] provides a framework for configuring clients with
   network addresses and other network parameters.  It includes a relay
   agent capability where DHCP server may not be directly connected to
   the DHCP client.  A relay agent is an intermediate node that passes
   DHCP messages between DHCP clients and DHCP servers.  As per
   [RFC2131], a relay agent cannot generate a message on its own which
   can control the client binding.  Figure 1 below shows a typical
   network with multiple DHCP devices.

Gandhewar               Expires December 30, 2015               [Page 2]
Show full document text