Network Working Group D. Evans Internet-Draft ARRIS International, Inc. Intended status: Informational R. Droms Expires:
February 15,May 20, 2007 Cisco Systems, Inc. August 14,November 16, 2006 Rebind Capability in DHCPv6 Reconfigure Messages draft-ietf-dhc-dhcpv6-reconfigure-rebind-00.txtdraft-ietf-dhc-dhcpv6-reconfigure-rebind-01.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of 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/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on February 15,May 20, 2007. Copyright Notice Copyright (C) The Internet Society (2006). Abstract TheThis document updtaes RFC 3315 to allow the Rebind message type to appear in the Reconfigure Message option of a Reconfigure messagemessage, which allows DHCPv6 servers to instruct clients to perform a Rebind operation as well as a Renew operation. 1. Introduction DHCPv6  allows a server to send an unsolicited Reconfigure message to a client. The client's response to a Reconfigure message, according to  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. In a network with multiple DHCPv6 servers, the Reconfigure message may not be sent by the same server as the one from which the client last obtained configuration and/or addressing information. If the Reconfigure message commands the client to perform a Renew,  does not specify to which server the client should send the Renew. This difficulty is avoided if the server commands the client to perform an Information-Request, since such messages are multicast. However, Information-Request messages do not cause addressing configuration to be returned. This document expands the allowed values of the msg-type field to allow the server to indicate that the client is to attempt to perform a Rebind; since Rebind messages are multicast, this avoids the necessity of the client contacting a particular server. Rebind messaegs also cause all configuration information, including addresses, to be returned from a server. This document updates section 19 of RFC 3315. 2. Terminology 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 . 3. The Reconfigure Message option of the DHCPv6 Reconfigure Message A server includes a Reconfigure Message option in a Reconfigure message to indicate to the client whether the client responds with a Renew, an Information-request, or a Rebind message. The format of this option is: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | OPTION_RECONF_MSG | option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | msg-type | +-+-+-+-+-+-+-+-+ option-code OPTION_RECONF_MSG (19). option-len 1. msg-type 5 for Renew message, 6 for Rebind, 11 for Information-request message. 4. Security Considerations This document adds no new security considerations beyond those present in . 5. IANA Considerations There are no actions for IANA associated with this document. 6. Normative References  Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.  Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003. Authors' Addresses D. R. Evans ARRIS International, Inc. 7912 Fairview Road Boulder, CO 80303 USA Phone: +1 303.494.0394 Email: N7DR@arrisi.com Ralph Droms Cisco Systems, Inc. 1414 Massachusetts Avenue Boxborough, MA 01719 USA Phone: +1 978.936.1674 Email: email@example.com Full Copyright Statement Copyright (C) The Internet Society (2006). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at firstname.lastname@example.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).