Forcerenew Reconfiguration Extensions for DHCPv4
draft-ietf-dhc-dhcpv4-forcerenew-extensions-02

Document Type Active Internet-Draft (dhc WG)
Last updated 2017-02-22 (latest revision 2017-02-09)
Replaces draft-fang-dhc-dhcpv4-forcerenew-extensions
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document
Other - see Comment Log
Document shepherd Bernie Volz
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to "Bernie Volz" <volz@cisco.com>
INTERNET-DRAFT                                               Luyuan Fang
Intended Status: Standards Track                                    eBay
Expires: August 12, 2017                                   Deepak Bansal
                                                               Microsoft
                                                           Fabio Chiussi
                                                               Luiginius

                                                        February 9, 2017

            Forcerenew Reconfiguration Extensions for DHCPv4
             draft-ietf-dhc-dhcpv4-forcerenew-extensions-02

Abstract

   This document extends the definition of the DHCPFORCERENEW message
   for parameter reconfiguration in DHCPv4. This extension makes the
   DHCPFORCERENEW message more suitable to reconfigure configuration
   parameters other than IP addresses, and aligns the behavior of the
   reconfiguration procedure in DHCPv4 to the corresponding behavior in
   DHCPv6.

Status of this Memo

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

   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
   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."

   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

Copyright Notice

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

   This document is subject to BCP 78 and the IETF Trust's Legal
 

Fang et al.            Expires <August 12, 2017>                [Page 1]
INTERNET DRAFT   Forcerenew Reconfiguration Extensions  February 9, 2017

   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
     1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . .  4
   2. Extended DHCPFORCERENEW Message for DHCPv4  . . . . . . . . . .  4
     2.1 DHCPFORCERENEW Procedure . . . . . . . . . . . . . . . . . .  4
     2.2 DHCPFORCEINFORENEW: Extended DHCPFORCERENEW Message  . . . .  4
     2.3 DHCPFORCEINFORENEW Client Decline  . . . . . . . . . . . . .  5
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . .  5
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  6
   5.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .  6
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     6.1  Normative References  . . . . . . . . . . . . . . . . . . .  6
     6.2  Informative References  . . . . . . . . . . . . . . . . . .  7
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  7

1. Introduction

   Network and cloud operators increasingly use DHCP to distribute not
   just IP addresses, but also a variety of other configuration
   parameters to the clients. The DHCP servers may need to reconfigure
   such other configuration parameters in the clients in isolation,
   i.e., without reconfiguring IP addresses. In the case of
   reconfiguration of only configuration parameters other than IP
   addresses, it is especially important that service interruptions be
   avoided. Towards this goal, it is desirable for a DHCP client, when
   receiving a reconfiguration request from the DHCP server, to be made
   aware of whether such a request includes reconfiguration of IP
   addresses or only pertains to other configuration parameters, and
   have the client adapt its behavior to each situation. Currently, this
   is achieved in DHCPv6, but not in DHCPv4. This draft proposes an
   extension of the FORCERENEW message in DHCPv4 to provide this
   additional desired client behavior.

   For historical reasons, the procedure for server-initiated
   reconfiguration of configuration parameters uses a different
   mechanism and produces a different behavior in DHCPv4 and in DHCPv6.
Show full document text