Rebind Capability in DHCPv6 Reconfigure Messages
RFC 6644

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 09
• 10

Internet Engineering Task Force (IETF)                          D. Evans
Request for Comments: 6644                                 IPfonix, Inc.
Updates: 3315                                                   R. Droms
Category: Standards Track                            Cisco Systems, Inc.
ISSN: 2070-1721                                                 S. Jiang
                                            Huawei Technologies Co., Ltd
                                                               July 2012

            Rebind Capability in DHCPv6 Reconfigure Messages

Abstract

   This document updates RFC 3315 (DHCPv6) to allow the Rebind message
   type to appear in the Reconfigure Message option of a Reconfigure
   message.  It extends the Reconfigure message to allow a DHCPv6 server
   to cause a DHCPv6 client to send a Rebind message.  The document also
   clarifies how a DHCPv6 client responds to a received Reconfigure
   message.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by
   the Internet Engineering Steering Group (IESG).  Further
   information on Internet Standards is available in Section 2 of
   RFC 5741.

   Information about the current status of this document, any
   errata, and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6644.

Evans, et al.                Standards Track                    [Page 1]
RFC 6644             DHCPv6 Reconfigure with Rebind            July 2012

Copyright Notice

   Copyright (c) 2012 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
   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1. Introduction ....................................................3
   2. Terminology .....................................................3
   3. The Reconfigure Message Option of the DHCPv6 Reconfigure
      Message .........................................................3
   4. Server Behavior .................................................4
   5. Client Behavior .................................................7
   6. Clarification of Section 19.4.2, RFC 3315 .......................8
   7. Security Considerations .........................................8
   8. Acknowledgements ................................................9
   9. References ......................................................9
      9.1. Normative References .......................................9
      9.2.  Informative References.....................................9

Evans, et al.                Standards Track                    [Page 2]
RFC 6644             DHCPv6 Reconfigure with Rebind            July 2012

1.  Introduction

   DHCPv6 [RFC3315] allows a server to send an unsolicited Reconfigure
   message to a client.  The client's response to a Reconfigure message,
   according to Section 19 of RFC 3315, is either a Renew or an
   Information-request message, depending on the contents of the
   msg-type field in the Reconfigure Message option of the Reconfigure
   message.  If the client sends a Renew message, it includes a Server
   Identifier option in the Renew message to specify the server that
   should respond to the Renew message.  The specification defined in
   RFC 3315 is suitable only for scenarios in which the client would
   communicate with the same DHCPv6 servers.

   There are also scenarios where the client must communicate with a
   different server; for example, a network administrator may choose to
   shut down a DHCPv6 server and move the clients who most recently